they try to reinvent the desktop experience every 2 or 3 years

GNOME 3 was released 12 years ago, and hasn't changed that much (unless you consider horizontal virtual workspaces are a major paradigm shift somehow).

Just use something else if you don't like it; no one's "pushing" anything on to you. Clearly, other people do like it.

You mean the ones for a closed and unhealthy web? :P

Maybe they could recommend Windows as well, while they're at it, haha.

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.

They were kinda forced to, having to choose between two evils: https://community.signalusers.org/t/signal-blog-removing-sms-support-from-signal-android-very-soon/47954/57

You could make it a BMBH (Bring My Beer Home).

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.

They haven't messed with it yet. The EU's a democracy and we can still influence its course.

Well, there's a way to frame this as malicious. I'm not a fan of Brave, but it also installs, say, a spell checker without consent, or a Tor client. Sure, the code is there even if you don't use it, but... What's the actual harm?

I wouldn't call it a mistake, more like being caught between a rock and a hard place, where Android basically forced them to give up on SMS support even though they'd have liked to keep it: https://community.signalusers.org/t/signal-blog-removing-sms-support-from-signal-android-very-soon/47954/57

But yes, it was really nice when I could use it as my SMS app. Then again, very few people in my country use SMS in the first place - it's all WhatsApp, and it was never able to have support for that. Luckily, most of my friends have adopted Signal by now.

Ah, so blog authors will still need to enable it manually. That's a shame.

I think they mean Nvida cards don't work with Wayland - i.e. it's Nvidia's fault.

From the full report:

For the experiment, two panel providers helped us recruit 12,000 survey participants across Spain, Germany, and Poland.

So given that they used third-party providers, I don't think they would have been biased to Firefox users specifically. (And in fact, given the current state of the market, the majority probably wasn't a Firefox user.)