That's only assuming the sub was running windows, where Xbox controllers work out of the box. On Linux there are no first party drivers, and Bluetooth support on the 1/S controllers simply didn't exist at the time this happened. If it was an embedded system there would be no support whatsoever.
You will probably have waaaay more issues trying to get the windows client working through wine than dealing with any hiccups on the Linux client. It was buggy but passable like 5-6 years ago so I'm sure it's much better now
You can try running it through a VM first before making the switch - 3d performance will be horrendously bad, but at least it will give you some piece of mind.
If unity gives a different download for each, you would have the best luck with whatever version matches closest (so the 22.04 download on current pop_os). Basically the more system dependencies the program has the more likely you will run into conflicts installing on a mismatched OS, but it isn't guaranteed to cause problems (e.g. program requires openSSL version 1.2, but my OS ships with 1.1). I think unity just bundles everything with the binary, so it should be fine.
For what it's worth, i used it on Ubuntu back when it was still in beta and it was super buggy (the installer and account stuff mostly, the engine itself seemed ok), so hopefully their Linux offering has since improved.
lol. Did this in my old building - the dryer was on an improperly rated circuit and the breaker would trip half the time, eating my money and leaving wet clothes.
It was one of the old, "insert coin, push metal chute in" types. Turns out you could bend a coat hanger and fish it through a hole in the back to engage the lever that the push-mechanism was supposed to engage. Showed everyone in the building.
The landlord came by the building a month later and asked why there was no money in the machines, I told him "we all started going to the laundromat down the street because it was cheaper"
These people aren't placing bets on who they want to win, they are placing bets where the house odds differ from the actual expected outcome. The people throwing big money on this are doing it based on actual data (amalgamating polls, etc), not just gut feelings.
If I think Kamala has a 45% chance of winning the election and the bookie is giving her implied odds of 40%, I should take that bet, because even though I think she will lose, I stand to make a 12.5% ROI on my bet. I can then hedge that bet on another bookmaker giving a 48% implied odds, and if enough people do this the bookmakers odds will converge on 44%
but either way I don't think this "market" knew more than the mainstream media was telling us.
No, but it is a culmination of all the available public information (and some private information you won't find elsewhere) in a single metric. If you read a single article you would assume there is either a 100% Biden drops out or a 0% chance - if you read every single news article in existence, aggregated all social media buzz, polls, etc, into a statistical likelihood, you would likely come out with a number that closely matches the odds.
Biden was only going to drop out once, so you can't say how closely these odds matched the actual likelihood on this specific measure, but if you analyze hundreds of predictive markets like this, the implied odds pretty strongly correlate with the actual binomial outcomes
If you know the key is composed of English language words you can skip strings of letters like "ZRZP" and "TQK" and focus on sequences that actually occur in a dictionary
we are talking about RSA keys - you don't memorize your RSA keys
if you rely on memorizing all your passwords, I assume that means you have ample password reuse, which is a million times worse than using a different less-secure password on every site
We are talking about RSA though, so there is a fixed character length and it isn't meant to be remembered because your private key is stored on disk.
Yes the word method is better than a random character password when length is unbounded, but creating secure and memorable passwords is a bit of an oxymoron in today's date and age - if you are relying on remembering your passwords that likely means you are reusing at least some of them, which is arguably one of the worst things you can do.
Words are the least secure way to generate a password of a given length because you are limiting your character set to 26, and character N gives you information about the character at position N+1
The most secure way to generate a password is to uniformly pick bytes from the entire character set using a suitable form of entropy
Edit: for the dozens of people still feeling the need to reply to me: RSA keys are fixed length, and you don't need to memorize them. Using a dictionary of words to create your own RSA key is intentionally kneecapping the security of the key.
That's only assuming the sub was running windows, where Xbox controllers work out of the box. On Linux there are no first party drivers, and Bluetooth support on the 1/S controllers simply didn't exist at the time this happened. If it was an embedded system there would be no support whatsoever.