Before this becomes another metoo thread: I think Google is pushing the boundaries testing how far they can go. For many of us this was the thin red line, but probably the society at large hasn't noticed - or maybe they don't care. My predictions is that Google continues to make small steps in the same direction, with these small steps totaling to something that would cause a public outcry if implemented all at once.
This is why I ignore people who say about $TOPIC, "that's just a slippery slope argument." The fact is, people/companies/governments engage in slippery slope tactics every day, on purpose, because they know those tactics work.
Google did the same sang with G plus a couple years ago attempting to require people use their full names when signing up for accounts. There was an outcry and they backtracked on that but look where we're at now. In my view they're definitely moving the surveillance state forward in small increments. There was an article awhile back [linking Google to the CIA](https://qz.com/1145669/googles-true-origin-partly-lies-in-ci...), not sure how true it is.
I think that "boiling the frog" is a valid way to describe this strategy, and it's one that a lot of other companies (Microsoft with their resurgence of anticompetitive tactics) and governments implement today, because it's effective. Look around and you'll find it everywhere.
if you quickly swat at a fly on a window, the fly jumps and flies away. if you slowly lower the swatter and then jump the last inch, the fly will never see it coming and gets squished on the window
Firefox will be adopting the V3 API but it will not be dropping anything from V2. Their goal is to support all use-cases from V2 without requiring everyone to do major re-writes [1].
We've heard that song and dance before. Firefox features always take the same path: start as regular part of the browser, then accessible through an extension, then you have to set an about:config flag for the extension to work, then you have to set a flag and modify some configuration files, and then you can go fuck yourself if you needed that.
Brave is awesome and runs circles around the others. Librewolf is technically more private but breaks too much of the internet. Firefox has jumped the shark as of late.
I’m surprised why Opera doesn’t come up more often in HN discussions. Sure it is not open source like Firefox but it is pretty performant and a competitor to Chrome which we all agree is a good thing.
Reddit is also (partially) owned by a chinese company - people complain but ultimately not going to stop people from using. That's just global capital at work. Opera's team is still in Norway.
Even today uBlock Origin is not able to run as intended by the author in Chrome (and maybe all other Chromium-based browsers). According to gorhill, the only browser that is able to unleash uBlock Origin's full potential is Firefox.
Ad domains being cloaked through CNAME records is really common nowadays (actively used by Adobe, Criteo and Eulerian, etc), and most analytics and ad software providers employ these tactics.
They are more common when using trackers and analytics (in the title of both the articles I linked), which you don't "see", unlike ads. It happens in the background
This is from 2019. Has Manifest V3 already been implemented? I did notice my adblocker plus extension no longer has element blocking capabilities recently.
Manifest v3 is implemented however developers can no longer submit new MV2 extensions to the chrome web store. In January 2023, developers will no longer be able to update existing MV2 extensions and finally support for MV2 extensions will be removed in June 2023.
First, Google lied (or, at the very least, strongly bent the truth) about the performance impact of content blockers in order to push the Manifest V3 API[1].
Second, in February 2019, Google promised that the WebRequest API was not going to be "fully" removed, yet went ahead and did it anyway - another lie/strong bending of the truth.
Vivaldi will try to keep V2 functionality as long as its in codebase, meanwhile implementing own (lame static, pretty much 100% same thing V3 offers) adblocker.
Brave's adblocker is not an extension so it doesn't care. It also doesn't care about the Chromium API limitations snd does CNAME uncloaking like uBO on Firefox.
49 comments
[ 1.8 ms ] story [ 114 ms ] threadhumans are exactly the same
"Firefox - we still have adblock"
Part of why Chrome gained users was it's adblocking in the first place.
1: https://news.ycombinator.com/item?id=28954390
1. https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-fi...
According to this, Google wants to drop Manifest v2 support in Jan 2023.
Too bad. I used it occasionally and was happy to still have uBlock Origin.
I don’t use Chrome. Use mainly Firefox. But I might not even bother having chrome installed anymore.
https://brave.com/learn/best-private-browser/
https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
https://portswigger.net/daily-swig/web-trackers-using-cname-...
https://medium.com/nextdns/cname-cloaking-the-dangerous-disg...
https://brave.com/privacy-updates/6-cname-trickery/
https://news.ycombinator.com/item?id=20137669
https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/
First, Google lied (or, at the very least, strongly bent the truth) about the performance impact of content blockers in order to push the Manifest V3 API[1].
Second, in February 2019, Google promised that the WebRequest API was not going to be "fully" removed, yet went ahead and did it anyway - another lie/strong bending of the truth.
[1] https://www.zdnet.com/article/google-backtracks-on-chrome-mo...