LLMs work by always predicting the next most likely token and LLM detection works by checking how often the next most likely token was chosen. You can tell the LLM to choose less likely tokens more often (turn up the heat parameter) but you will only get gibberish out if you do. So no, there is not.
Yes, because infrastructure, subsidies, education and social spending still need to happen and not paying your taxes will erode those things long before they stop a genocide. If you don’t care about getting in trouble with your government, there are more effective things that can be done.
player_hand and dealer_hand are only [DECK_SIZE/2] in length, but in initialize_decks you write zeros into them unti [DECK_SIZE -1]. Since the arrays are located next to each other in memory you end up overwriting the deck array.
Yes they are.
Here’s a TED talk on YouTube from “Hide the pain Herold” a guy who was in a stock photo that became a meme: https://youtu.be/FScfGU7rQaM?si=MFVrgwlJQ8DSOfVB
Considering MRTs use 1.5-7 Tesla, I can’t imagine microtesla will be doing anything, unless you have a piece of metal in your head. Maybe it’s an ear infection or a migraine or something like that gets worse from the cup pressure. If it’s a problem, ask a doctor.
Can someone give some context why this is so heavily downvoted? Is the content misleading, or is it just that people misread the title as anti-vegan?
The probability of getting a finite number is pretty much zero.
For any range [0; n], where n is finite, there are always infinitely many numbers larger than n, so the probability of getting a number in said range is n/(n+infinity). I feel very confident in saying that something with that probability will never happen.
Looks to me like they’re trying to build something like office 365, but open source. Mostly by wiring other open-source components together I think?
This is probably a better starting point, unfortunately the text is in German: https://gitlab.opencode.de/bmi/souveraener_arbeitsplatz/info
If your local branch and the branch on GitHub diverge, they need to be merged. If you pull using the console it will tell you that, apparently VScode does this automatically?
Anyways, nothing to be concerned about. If you’re annoyed by the merge commits, you can configure git to “rebase on pull”, google it, you’ll find instructions pretty quickly.
Here are some corrections:
Blockchain has nothing to do with P2P. Blockchains are federated ledgers that can’t be changed later, unless the majority of federated servers decides to. P2P means that two devices communicate without a server in the middle. Maybe you meant federated?
Blockchains can absolutely be hacked. You can gain majority control over the servers, in which case you can rewrite the blockchain as you want. Alternatively you can gain access to accounts/wallets by hacking the software that users store them in or by social-engineering people to give you their keys.
If proper end-to-end encryption is used, there is little security difference between server-based and P2P communication, but it’s much more inconvenient: You cannot save sent messages on the server for later retrieval, so if you’re trying to reach someone who’s currently offline, your device has to wait until they’re back before sending the message. Also if you use multiple devices, keeping them in sync is very complicated, because they have to be online at the same time.
Edit: formatting
Skill issue