I think there can be a difference. github encourages this behavior, even provides the tools for it. but if the forgejo community stands strongly against it from the beginning (users reporting true slop, moderators deleting and banning them, admins defederating from intentional slop sources), then maybe that kind will stay away from the platform

that probably depends on the blocklists used, like with ublock

fingerprinting can be based on detecting what resources are blocked, and sometimes also how are they blocked. but blocking will become the baseline, so nefarious companies will have less of chance to tell the difference

still it wasn’t blocking ads, and even I as a poweruser was not aware that I could add externally maintained ad blocklists

Waterfox has a much smaller market share and much smaller budget, and was able to clear this with search partners just by promising not to block ads on them by default.

my point is not actually about search providers, but more generally websites intentionally breaking support for gecko based browsers. waterfox itself is too little, most developers don’t even know about it I think. but firefox is the flagship/reference gecko browser, with more of a measurable number of users. if they implement a good ad blocker in the base browser, that could discourage advertising related sites from serving/supporting this browser.

brave is different in that it uses chromium, which the sites just happen to support already because of chrome. but firefox support is often not a priority even today

Rust is faster than JavaScript

isn’t ublock’s filtering compiled to webassembly?

Actual ad blocking is something Firefox users have been begging Mozilla to do

seems a bit dangerous though to risk for a browser with so small market share

how do you do that on samsungs?