Well they keep making them, so they probably have some buyers.
Honestly, its probably not a bad deal considering its a nice display + camera + speakers + microphone + laptop charger. Saves on a ton of desk real estate.
Believe it or not, its opt in when you click "I Agree", though it should be MUCH easier to opt out than it currently is.
States like California are helping to combat this, forcing companies to tell the state that they are collecting this data, and California providing an option for their citizens to do a one time massive opt out to all services. There are also services out there that you can pay and they will go out and continually try to keep your data from these data brokers.
Be warned though that some installers will yell at you for not having a "compatible version of Windows". Its rare, but some apps don't like the enterprise editions.
SQRL is not useful for encrypting data. What its useful for is management.
When you want to encrypt data, you use a solid symmetrical encryption algorithm with a strong key. How do you store that key? You want it to be something long and you can't memorize, and you want it to be unique per account/set of data.
The key management is where SQRL comes in. Think of it as a password manager, but you don't need to store it or sync it anywhere necessarily.
Hypothetically, if iMessage had SQRL functionality built in, you would login to your SQRL identity (using a master password and a public/private key pair). Then iMessage would provide a SQRL login, which you simply click an icon or scan a QR code with your phone. From there, iMessage and SQRL would create a public/private key between themselves that is deterministic. Any device that you are able to login to SQRL from would be able to generate that exact same public/private key pair.
Steve Gibson did a demonstration on how it functions:
This wouldn't be an issue if the world went with SQRL instead of passkeys. All SQRL credentials are deterministic based on your public/private key and the site/app you use. There are no passkeys to store, so you wouldn't be able to delete them. You generate them on the fly.
But i guess we'll have to deal with passkeys since that is the standard that won this time.
Solar flares and even the occasional random neutron particle hitting your equipment can cause some weird issues. If its just a one time occurrence and it doesn't happen again, I wouldn't worry too much about it.
This change is about preventing AI from trying to own the change. A human must own the change.
AI cannot own a Firefox contribution. AI cannot commit code to Firefox. Only a human may do that.
If a human uses AI (or autocomplete / a formatter / a transpiler / whatever else) to help them author code, that doesn't devolve them of responsibility. The human must take ownership and responsibility for the output.
For example, if we later run git-blame on a section of the code, we want to see the human that took responsibility for the code, not some AI.
Ive chosen the route of using Tor Browser or Mullvad Browser instead. They are fantastic browsers that probably have the best web browser fingerprint protection available, next to Vanadium Browser.
How much does each USB port cost per device?