Notably absent: X11 developer saying Wayland is bad, not X11.

I think it’s just because some things have country-specific formats. For example, if you want to prefill credit card details, you have to figure out how the credit card fields are labelled.

Hehe, I can be more explicit: why would Chromium “resist” MV3 when the Chromium developers are the ones pushing it?

That’s like asking if I can resist reading a book. Sure I could, but I want to read a book - why would I resist?

They actually did:

The Voyager team sent commands over the weekend for the spacecraft to restart the flight data system, but no usable data has come back yet, according to NASA.

Unfortunately, that didn’t help. So now they’ll have to find out what’s causing this, and then see if they can fix it.

So you’re saying: don’t release the GTK 3 port until colour spaces are also complete? Why not give people what’s ready, and then when colour spaces are ready, cut another release? No need to make people wait who don’t need colour spaces.

(Additionally, it’s easier to verify that bugs reported before the release of colour spaces are more likely to be related to the GTK3 port.)

It doesn’t matter if they do, as long as voters believe they do.

Almost nobody thinks this win is the result of fringe extreme elements within Islam. It has more to do with lack of housing, inflation, etc.

We can do that when it’s actually released; blogspam tries to publish on the expected release date before the actual release so it can scoop up the clicks. Release notes should be posted here later: https://www.mozilla.org/firefox/120.0/releasenotes/

As I understand it, the blocker has website-specific rules to automatically click the right buttons. For the first release, they’ve probably primarily tested those with German websites. I assume that if it works well there and they’ve ironed out most bugs, we can see it roll out more widely.

I stuck with Toolbox for a long time because it was default, but then I wanted to be able to easily recreate my *boxes with the same set of packages when e.g. they broke for some reason, or because the distro they were built on released a new major version. Distrobox supports that with its assemble command, so I switched. Otherwise it’s not too different really, for a casual user like me, and if I hadn’t needed assemble, Toolbox would’ve been just fine.

(Except that I keep forgetting whether Toolbox or Toolbx is the correct spelling now.)

Not OP, but for me, the main benefit is how uneventful major distro upgrades are. Yesterday I updated to Fedora 39, and it was so anticlimactic to reboot and then be like: is it over? But that was really all there was to it.

I’m very excited about how the Linux community generally seems to be moving towards various approaches to immutable systems - all of them having in common that system updates are going to be a lot less likely to break. The future is looking good!

Ah yes, people are indeed known for always reading long readmes and fully grasping the consequences of their actions, especially if those occur long after said actions :P

Great work by Sonny and Tobias. Really happy to hear that more effort will be invested into accessibility, as I feel it’s really been lagging over the past couple of years.

Yes, but as soon as it is accessible via the GUI, more and more people will start getting blurred Google Docs (and similar weird issues) without knowing how that happened - because that’s already happening even with people who know enough to make changes in about:config.

I mean, you’re just saying that if you don’t dial it up to eleven, but just to nine, then you’ll hit less breakage. Which, sure, but that’s kinda my point: a usable browser needs to strike a balance, and that’s exactly what Firefox is trying to do - which is really something different from “needing a 180-degree turn”. Firefox by default is stopping way more tracking than e.g. Chrome, and guides users to installing e.g. uBO.

Also note that most breakage isn’t immediately obvious. For example, if you turn on privacy.resistFingerprinting, then Google Docs will become blurred. However, by the time you see that, you won’t be able to link that to the flipped config. This is the kind of breakage that many “hardening guides” cause, and by that, they eventually lead people to switch to Chrome, which is the opposite of what they’re supposed to achieve.

And sure, Librewolf draws the line at a slightly different place than Firefox does. But the main difference is not sending data like hardware capabilities, crash stats, etc. to Mozilla - which don’t threaten democracy or result in hyper-targeted ads, but do enable Mozilla to optimise the code for real-world use.

A Mozilla dependent on Google seeing value in Firefox sending searches their way is at minimum as good as one in which Mozilla doesn’t exist and everybody uses Chromium-based browsers, by definition - and in practice, way better.

But yes, more non-Blink engines in use in general would also be a better world. Alas, that, too, isn’t the world we live in.

But also keep in mind that it couldn’t exist without Firefox/Mozilla existing. A world in which more people use Firefox over Chromium-based browsers is a better world.

Use Tor Browser if you want it dialed up to eleven. You’ll quickly find that it’s way more of a hassle to use, and also still pretty easy to accidentally compromise the security measures.

Of course Firefox isn’t perfect; nothing is. But a 180 turn implies it’s the opposite of perfect now, and it really isn’t - especially in a world where basically every other browser is waaaay closer to that.