For good, functionality-related reasons at the time[0], and everyone in the Wayland space had been using the mesa library except nvidia with their own proprietary libgl.
I think Discord servers for a software project tend to attract a younger audience and are more noisy/active and have offtopic discussion, compared to something like a user/-dev channel on IRC.
I don't disagree with you, except browsing creepjs from Tor Browser it says there have been hundreds of visits with my fingerprint since June (when the 12.5 series was released).
If you want to be able to run most command-line programs (and probably GUI apps through VNC) in an isolated environment (similar to WSL or Chrome OS), then it will suffice, but there are some that appreciate having the desktop Linux environment and functionality across the whole of the device (like what sxmo is doing). Definitely a niche within a niche (desktop Linux users), I currently just avoid using a phone aside from the most basic tasks like using it as a phone to call/text or where it's required like banking.
I agree there is less bloat like iMessage and less installing random crap apps. The biggest holes if an attacker is determined are probably the browser and images/video, and maybe common networking libraries or networked games which often have poor security. Once the image/video decoder is exploited and you get RCE (if in the browser you'd have to escape the browser sandbox too), there are less exploit mitigations on desktop Linux and maybe less chaining you'd need to do. And the lack of/worse verified boot than Android/iOS if that's something you need to worry about.
That's definitely the appeal for many of its users, being able to escape the locked down and restrictive environment of Android/iOS and having the functionality of a general purpose desktop Linux device in your pocket.
I agree. I would use protonmail or something else for signing up for websites, as a domain would be linked to me (unless I buy dozens of domain names anonymously).
For Git commits or communication tied to my real identity, then yeah I'd use my own domain name. But for anonymity, nope.
You can hide it from other users by using a cloak (which some servers enforce on all connections), if that's a concern (but I don't think it's much of a concern). If you want some anonymity from both the server and users you're probably already connecting to the server from Tor (or maybe a VPN if it's blocked). OTOH discord is difficult/impossible to use from Tor Browser due to phone number requirements on suspicious connections and email verification when changing countries, which sucks.
Is this a supported feature by Google, or does it require client modifications/forks? If the latter, with Web Environment Integrity it's conceivable that this may not be possible with many sites in the future.
>Also out of curiosity, how adequate is Tor for bittorrenting? I would guess it constrains bandwidth pretty severely?
I've never done it, but it will have some problems: no UDP support (cannot connect to UDP trackers or use uTP with peers), no port forwarding (cannot connect to peers with closed ports), and some exit nodes might block outgoing activity towards the well-known ports (6881) though most peers don't use this port and instead use random ports.
Sensitive features like screenshots, input methods, screen locking and whatnot are behind extensions (or portals). I'm not familiar with the state of GNOME/KDE/Flatpak, but at least on the wlroots side of things it is true that currently these extensions are enabled and accessible by any process that can talk to the Wayland socket (breaking those security benefits, as you say). This is changing with protocols such as security-context that allow a sandbox engine like Flatpak (or your custom scripts) to restrict what features apps can use. (so your browser can't register an input method, or some random app can't lock the screen)
You could do some of this with an input method editor (IME). It's pretty much an authorized keylogger that can edit your inputs, and is mainly needed for Chinese/Japanese typing. An IME that provides English autocomplete on the desktop (like phones) or shortcuts using an IME framework (like fcitx5) would be an interesting concept.
This reminds me of a torrent on Nyaa that implemented Bad Apple!! in ASS subtitles by retracing the frames into SVG (seems to be better quality than simply using potrace by itself), converting the SVGs into ASS Dialogue events, and muxing it into a Matroska container with a placeholder video. Therefore the "video" window can be resized without rescaling raster images (and it actually runs well on most hardware and players, unlike his other torrents putting whole anime episodes in subtitles). The subtitle attachment could also be extracted from the container and executed as a valid shell script which would run mpv or ffplay, use the respective options to create a libavfilter filter to create a blank video (to overlay the subtitles on), use its own filename for subtitles, and play the song by decoding and piping a base64 string at the bottom of the script to mpv/ffmpeg's stdin.
Even ignoring the installed interpreter, libraries on Linux distributions are usually installed system-wide as their own packages which other packages depend on (neovim, mpv, cgit, etc.)
Fair enough, it may be more reliable against general/naive approaches like commercial uses though a sufficiently skilled adversary may only consider the fingerprinting techniques they have missed (one specifically targeting TB users).
The alternative (faking Chrome or something) is extremely difficult, especially with a different codebase. There's going to be differences. You can tell if someone is using this browser if they're using Tor/Mullvad too. It's just a better option to create a new identity (TB/Mullvad) and put everyone behind that.
As a side note, Tor Browser/Mullvad Browser does randomize canvas (and this changes every time you restart the browser or press New Identity). I don't remember what the reason for randomizing this specific feature is for, maybe it had better compatibility.
It's going to be extremely difficult to imitate another browser like that, especially one of a different codebase. Chrome is extremely fingerprintable too.