And everyone that wants unbiased context should read the wikipedia page:

https://en.wikipedia.org/wiki/Hachette_v._Internet_Archive

The judgment basically completely ignored IA's arguments towards fair use. EFF filed an amicus brief that explains how baseless the judgment was. Assuming the entire US court system isn't in the corporate pocket yet they will win this on appeal.

It's ridiculous to assume that an organization whose main purpose is data archival would knowingly and blatantly ignore copyright law. IA didn't ignore it, they did they homework and saw that their use qualified as fair use. Then they met a judge who doesn't give a shit about that. Nobody can prepare for that in advance.

Also Gabe hates Microsoft, and Valve is a private company so he doesn't have to sell.

I expect the KeepassXC people are mostly bothered by the naming of the package because the version called "keepassxc" is now the basic one. Anyway, the maintainer has offered to call them -minimal and -full and to make "keepassxc" a metapackage that pops up a debconf dialog telling users that install it to choose one. There is precedent with other complex packages that are split into basic and full. This should solve things nicely for everyone.

Lol, from an Ars comment:

Discord finally has working search

I thought Arch was the only rolling distro that doesn't have the backdoor. Its sshd is not linked with liblzma, and even if it were, they compile xz directly from git so they wouldn't have gotten the backdoor anyway.

doing exactly what the caller intended.

No, no. Exactly what the user told it to do. Not what they intended. There's a difference.

Title is a bit misleading. Starting with 2024 the site will be moving to a new API. The payment is too be able to continue to use the old API a while longer (for software that can't be changed yet).

Only affects RSA keys, and then only 1 in a million keys are vulnerable. So this is mostly of academic (rather than practical) interest, but nevertheless it will lead to further hardening of the SSH protocol which is nice.

I've had Google temporarily lock my account even though:

• I knew my username and password.
• I knew the answer to my secret questions.
• I had the 2FA code from the authenticator app.
• I had access to my email and could confirm it's me using links they sent in mails.
• They had my phone number and could send a text with a confirmation code.
• They could pop up a confirmation notification right on the phone.
• They could probably have asked me to fart in B flat and they'd detect it, they're so far up my ass.

None of that matters. Their stupid system will automatically decide to lock you out for whatever reason and that's it.

I'm glad I reduced the use of that email address down to nothing and that I moved out my calendar and events and I'm no longer using Google Pay.

I thought this was about Slackware ditching X11 for a moment... which, arguably, would have been a more interesting piece of tech news.

It's basically all the bad things that tech writers have already warned about, except shit just got real. Google is actually shipping WEI in Chrome and large important sites and services are no longer working except in Chrome and with Goggle's blessing.

The author makes a very good comparison with Android, where you need a locked-down device and Google Services installed to be able to use Netflix, or your bank's services.

The rest of the article dives into what WEI claims to achieve vs what it's actually doing, and who it really benefits. Good read if you're still unclear about that.

If you try to access an old Linux install you could run into the exact same problem. Both Linux and Windows nowadays use filesystems with permissions embedded into them, so if the user on the new install doesn't match the old one you'll have a problem.