I'm not sure if it's related, but I've been getting popups that prevent navigation away from pages on the Google Android browsers
Privacy
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
I’ve heard reasonably good reports about ublock origin lite (uBOL), the manifest V3 implementation. I haven’t made the jump yet, though.
It is never going to work the same. They are talking about dropping it entirely.
Why does it need to run remotely hosted code though?
Because the ads constantly change across the websites. Adblocking is naturally a cat-and-mouse dynamic. However, the "remotely hosted code" Adblockers use is not exactly "code" (as in a JavaScript code, for example), it's more a Regex code containing patterns for the different websites and different behaviors (for example, the pattern for the pesky HTML element containing the ad, or the pattern for some ad-serving domain). Google is extrapolating their meaning of "remotely hosted code" purposely, so they can "justify" their measures.
Fair. Pulling rules makes sense. Code wouldn’t. (I wouldn’t consider regex as code.)
Thanks for the details.
Honestly, I blame developers who, some years ago, decided it was a good idea to centralize the browsers into the same engine. Yeah, it was hellish to maintain code for all browsers at the time (IE5, IE6, Firefox, Safari, etc), but it was paradise compared to our current scenario: at least we really had options: WebKit, Trident, Gecko, as well as lots of smaller, almost unknown engines. Now, all modern browsers are different wrappings of Chromium or Firefox, while most modern sites are developed without the active worry to keep Firefox compatible (one can notice how modern HTML5 features varies across both of them). It has no easy solution. Don't update, maybe? (Until sites start to complain about the outdated version)