Seems like a solid bunch of iterative improvements!

Luckily this will change next year with the new EU rules, as they explicitly call out allowing alternative browser engines.

I did, yes. TBH it is very anti-Matrix right out of the gate, makes a mountain out of a molehill and it even admits that it contains FUD.

There's a couple of things that are misleading in it (for example the section on bridges) and the critique basically boils down to "if you use the identity servers that are run by Matrix.org with your self-hosted homeserver they can see the info you send to them" and "Google Analytics in Element is bad".

All in all I didn't find it very convincing, and very lacking in nuance.

Proton uses XWayland, this is for proper, native Wayland support. It will make its way to Proton eventually.

It is supported by systemd to use FIDO2 + pin to decrypt luks partitions with many security keys, including Yubikeys. I use it every day on my laptop.

Can't Waypipe do this?

Not anymore, since as of October Gitea requires a copyright assignment for contributions. More info here.

True. Luckily it seems Mozilla has been preparing for this in advance: https://www.macrumors.com/2023/02/07/mozilla-developing-non-webkit-version-of-firefox/

Depends on which DE in which version it is using, but anything with recent Gnome (Fedora, Ubuntu) will. Not sure if KDE distros generally default to it, and for more niche DEs the answer is probably "no", unless it was explicitly made for Wayland.

Ordinary DNS requests are always plaintext and readable to anyone between you and the DNS server. So regardless of which DNS server you use, your ISP can see all your DNS lookups. For any amount of privacy for DNS, the minimum is something like DNS-over-TLS or DNS-over-HTTPS, the latter of which Firefox uses by default in some countries and supports everywhere.

I doubt it's ever going to be a part of the core protocols, but it doesn't have to be, you can just use Waypipe.

Because Pipewire only handles and understands media streams, so it can stream the output of a window or the whole desktop, but only because the Wayland compositor has already composed the windows and other data it gets from the application to a visual and hands the final result to Pipewire.

I mean most things are implemented as plugins, so you can just disable the ones with features you consider bloat.

I guess that depends on which power your agenda aligns with. That power is generally a safe choice, compared to services from a power where your agenda is orthogonal.

What do you do on your machine that requires you to completely disable a fundamental security feature of your distro? I haven't had SELinux cause any issues for years.

That seems like a shortcoming in those tools, that I'd expect them to fix as Flatpaks are pretty commonplace.

Won't most of those pieces of software work on xwayland?

Do you have a source for the claim that collecting userdata is ultimately what funds Matrix?

For the multiplexing, as I mentioned.

A V4L2 camera can only be opened by a single application at a time, but if that application is Pipewire, then Pipewire can allow multiple applications to make use of it simultaneously. Same thing with ALSA, it's the reason sound servers exist at all, though I suspect you're already familiar with that.

I also hear that ALSA has some support for multiple applications per device nowadays, though I understand it is much less pleasant to use than a fully featured sound server.

Does this support DRM protected streams, for example with Widevine? Whether one likes DRM or not, it is clear that support for it is a hard requirement for any streaming apps to support this.