@ryo In theory it's possible, but a lot of work is needed (TBB exists but it forces everyone to use the same conf and their FF is not telemetry-free). There is what parameters you can change and what you shouldn't change.
@kino@ryo Blame the education system - a slave factory, and the ignorance of their parents (that just let or even welcome the system and others like Google to shit on their kids' brain).
The Eww has coersed Shitter owner Elon Musk saying the platform will be banned unless it gets subverted to its moderation policies and eliminates its rightful approach to reinstating banned users, according to the Financial Lies, after Musk significantly loosened rules prohibiting free speech and truth.
Meanwhile, it's Asia and Africa who are the "iron fist DICKtators" while Europe and Americuck are the "free DEMONcracies". All while the latter are the ones sticking their noses into everything and everyone even if they're off the lands they claim to rule over.
I should note, I know full well this is just theater for the masses, and it's exactly their goal to destroy Shitter to make room for their new, way worse replacement, so don't fall for the propaganda, Musk is controlled opposition.
@TerminalAutism@ryo Yeah Wine lacks (readable) documentation on what to do when things aren't working well. I think the existence of Steam Deck could imply Wine could be made to work, it's just we don't know how to configure them. Indeed I ended up having a separate hard drive for gaming, one on normie Linux and one on Windows AME (with internet disabled and installed simplewall just in case).
@ryo@Paultron@charliebrownau@kleeneks Yes we really need that. Ideally a browser that fully support XHTML1.1 and CSS2.1, plus some goodies from (((modern))) HTML5 and CSS3, and some measures against fingerprinting by randomizing the headers like Accept-Language.
@ryo@Paultron@charliebrownau@kleeneks Netsurf... I want them to finish their CSS 2.1 support first. And all these browsers don't have content control (like blocking 3rd party contents).
@ryo No, I don't think they are purposefully changed for fingerprinting. Fingerprinting is just collecting and comparing what features you have (or not), so there's no such "new ways" or not - everything you send (or not) can be profiled. If you are interested you can read my site. Although it's a bit incomplete but you can get the idea. I will probably add more details 2 weeks later (written in my "future plans" page).
@ryo@kleeneks@Paultron@charliebrownau There's actually more about the metatdata thing, about what useragent you choose. For example, after Firefox 92 it seems to be using HTTP2 by default and accept headers are also different. There's also TLS fingerprinting, etc.
@ryo@kleeneks@Paultron@charliebrownau Where did you get the i2pd from? I had that problem too until I recompile them, but new binaries seem to be more stable.