From experience with Windows "freeware" some of us have seen what happens when such pop-up notices become commonplace. It is not pretty.
kbal
joined 1 year ago
3min 30s, sample for context
If you keep watching for 10 minutes, it's an interesting discussion. Too bad they had to cut it short due to time.
I wish Signal was developed more openly, more like the linux kernel for a "critical infrastructure" example. I wish it had more features, so it could take the place of something like Slack. I wish it supported interoperability like fedi.
But it's good for what it is and I sure am glad it's around. People who disrespect it don't know what they're talking about.
It's perfectly normal I guess but I'm still not quite used to seeing so many people who don't know much about linux talking about how they use linux.
Z-Library. Despite reports of its demise I've seen no interruption of service. And of course if there's one I want to pay for I'll buy a printed copy.
Disappointing, Germany. How can we trust you to find the best pirate sites when not even thepiratebay.org is on the list?
Update: According to various indications around the net it turns out that the problem (for Debian users at least) is not grub at all, it's shim itself. They did update the grub SBAT level in a way that should satisfy Microsoft's demands when they patched the CVE that everyone seems to be pointing to as the one Microsoft was aiming for.
What they didn't do in time is update shim (possibly related to CVE-2022-28737, I'm not sure.) There is a new version which has the required change but it has not yet made it to Debian stable. Microsoft added an SBAT for shim as well (which gets checked by shim, so if it's broken... uh... anyway, it's probably fine) and it's the one causing the problems.
(Edited to reflect that I don't really know if it was the fix for CVE-2022-28737 that was needed, the SBAT variable update related to that, or something else. Whichever it is, the shim update currently in the bookworm proposed updates queue should have it.)
that's kind of a violation of the social contract around all of this.
What an interesting journey to the conclusion that it's not the fucking around with non-Microsoft bootloaders that's wrong, it's the installing of bootloaders that aren't approved by Microsoft. That must be somewhere in the Microsoft social EULA you automatically agreed to when you chose to live in a society.
Somebody please tell me which specific CVEs Debian failed to account for in their many grub security updates.
Debian stable? It's probably about as safe as you can get for that. Problems are rare. Bookworm is supposed to get security updates until 2028. If they keep on being as stable as they have been in my experience the only one he's likely to notice is Firefox updating to a new major version once a year.
The claim that more users increases costs for the KDE project in any meaningful way is another thing that might be disputed. The examples given do not seem convincing.