I might be missing something, but I’d trust WhatsApp to leak much less data about me than Telegram or Discord. Those don’t have any form of E2EE.

Also, what about using Signal?

The .mobi was a previous post where they bought the expired domain which was previously used by the .mobi WHOIS server.
A bunch of systems apparently didn’t update their WHOIS database and still tried to get WHOIS information from the old domain.
This could lead to RCE in some implementations if they provided a malicious response.
A bunch of CAs also accessed the old domain and use WHOIS to verify domain ownership. By setting their own email address for verification, they could have issued themselves a certificate for any .mobi domain (microsoft.mobi, google.mobi for examle).

Now to this article, here they looked at a bunch of webshells with backdoors added by the developers. Some of the domains had expired, so by getting those domains and setting up a webserver they got connections from different systems infected by the malware. They could have used the same backdoor previously used by the devs to access those same systems remotely and do whatever.

Your first amendment protects you from the government. It does not protect you from actions taken by companies or other people based on your speech.

Sadly we lost that fight to the other centralised platform in Bluesky

Not really. The reason is that Steam (and an unfortunate number of other programs) run through Xwayland when your compositor is using Wayland. If you then use fractional scaling, Xwayland will render at the fractional of your resolution and will be scaled linearly to your display. This results in general bluriness for X11 applications.

Kwin, to my knowledge, is the only Wayland compositor that allows decoupling Wayland scaling from Xorg (and does so by default). While this results in different scaling behaviour for X11 apps, it does mean they are never blurry.