I don’t know, but FF, although having nice options for privacy, don’t set them by default, leaving the user to go investigate what to set and whatnot… And adds is a sensitive topic, though it’s understandable they want to make money…
That’s why I use instead Librewolf, which is pretty much FF with sane settings by default (actually I have to modify some not allowing me to use the browser under some scenarios), and removing binary blobs (FF still includes binary blobs). For Librewolf, the other nice thing is that it comes with uBlock-Origin by default, however it might be it’ll be harder for uBlock to actually block new ways of adds…
If LXQt (what I use) and KDE ever opt into this, it’ll be the time for me to prefer GTK. I do like Qt better, but I guess such is life. I do not think that’ll happen any time soon though.
Not sure about the mobile KDE and apps, being mobile KDE the selected default environment for pine64, but I hope phones using KDE and non KDE Qt apps keep away from adds as well…
And not sure about independent Qt apps, like smplayer, cantata, and others. I really doubt this will come to GNU+Linux, but if so, then I guess there are choices, such as GTK apps, DE and toolkit…
Although the reddit comment indicates it’s misleading, because of being the commercial version of Qt, and KDE being free SW, that’s a blur area, I don’t know if being FOSS prevents being able to show adds. Perhaps the license might force to give an opt out option to the users, but again, I can’t tell that’s enforced by the freedoms enforced when using GPL. Also, other free SW apps, as the ones mentioned before, might not be KDE projects, and even if KDE chooses not to take advantage of adds, it might be non KDE developers do. Although not likely, this deserves paying attention on how this moves…
Not quite sure they are really that useful for torrents. There have been several announcements of VPN providers asked to block torrent searchers and trackers. So I think now a days, VPN doesn’t even live up to the torrenting functionality.
The best that can be done, I’d guess, for torrenting, is to use pseudo encryption, to prevent non sophisticated ISP snoopers detecting torrents, like for rtorrent:
protocol.encryption.set = allow_incoming,try_outgoing,enable_retry
Though I’d prefer:
protocol.encryption.set = require,require_RC4,allow_incoming,try_outgoing
But it doesn’t work, :(. I’m wondering if some more effective encryption would ever be achieved on torrents, without preventing finding seeders/leechers…