Earlier quoted context omitted.
The EFF doesn't need to give "the other side" because the other side is mostly obvious to the target audience (which isn't random people, Google itself is a huge part of the target audience). Note that Google doesn't give the other side either. Also, nothing in politics works like that, if you want to get people to join your cause you don't end everything you say with "But keep in mind that $foo".
So long as they're only interested in preaching to the choir, that's true. If they want to reach other people who are as zealous, they could stand to give a better full of the landscape.
Chrome users beware: Manifest v3 is deceitful and threatening
361–370 of 396 posts
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#362Earlier quoted context omitted.
Do you want to call out any particularly malicious ad blockers here? Just in case I happen to have installed one of them.
Since parent tested all of them and they’re not kidding, it follows that yours must be a scam. Unless they didn’t test everything or were exaggerating that is.
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#363Previously extensions could be background pages, with access to DOM & Web Platform apis. MV3 currently reduces them to Service Workers, able to use far far far less capabilities. This is a massive massive downgrade for Extensions, unfathomable really. A Mozillaian proposed a less limited Limited Events Page but Google has snubbed it & not discussed. https://github.com/w3c/webextensions/issues/134 Extensions are force…
> I generally find Google to be quite a good steward for the web & am so happy they advance so many different initiatives & capabilities. I don't. Especially not with FloC[0][1]. [0]: https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-... [1]: https://developer.chrome.com/docs/privacy-sandbox/floc/
As for FloC, still trying to understand FloC's implications & make a position on it. Hearing it proposed, it sounds enormously stupid, but I'm not convinced it's in fact bad. Part of me even thinks it indeed sounds like a significant privacy win over where we are.
Rather than discuss FloC though I'm wondering what other efforts you would malign.
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#364The day Chrome (and it’s derivatives) kill my extensions, is the day I switch to Firefox. I cannot live without my adblocking.
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#365Earlier quoted context omitted.
I’m sure you are an honest person working in good faith. But we saw very similar behavior from Google around AMP. They had a very narrow reasonable sounding explanation, and just ignored all criticism and requests from both users and publishers that didn’t fit their narrative. This went on for years. Today we know AMP was also a anticompetitive plot to kill off header bidding. Why should we to believe a word of what…
> Today we know AMP was also a anticompetitive plot to kill off header bidding. I completely disagree, and I think this will become clear as information continues to come out.
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#366Earlier quoted context omitted.
> Today we know AMP was also a anticompetitive plot to kill off header bidding. I completely disagree, and I think this will become clear as information continues to come out.
Stop astroturfing.. Your company is a scummy monster!!
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#367Earlier quoted context omitted.
This is just an attempt to rehash the same old arguments provided by Google that have been repeatedly debunked by developers and security researchers. > I work on ads at Google, speaking only for myself I'm doubtful about a person's ability to speak for themselves, when they have been consistently defending their employer on HN for years, at every occasion they got.
"It Is Difficult to Get a Man to Understand Something When His Salary Depends Upon His Not Understanding It"
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#368While a good message that does have actual merit if you know what's happening already, I don't see how this is a legitimate consideration of MV3. The entire argument regarding security doesn't mention any of the reasons Chrome developers cite its security improvement, instead it brings up that Firefox "does good enough already" and that malicious extensions can still get past the review process. the review process is…
To say browser extensions pose a risk is true, but it hardly makes it in the top list of threats anymore. Malicious sites however still do and Google just restricted our ability to let third party tools provide essential services. Sure, these could be malicious, but that is generally not a wide spread IT problem of today. That should be also obvious to Chrome developers.
Accidentally they also restrict ad blockers? Come on, you are getting played.
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#369It's hard to take EFF seriously when they write so hyperbolically. What's clearly also the case is that Chrome extensions are one of the great modern security and privacy challenges --- to the point where multiple tech company security teams have people whose job it is just to screen them. Another detail that EFF doesn't want to share is that ad blockers are some of the worst offenders --- they demand maximal access…
Every time someone mentions this I have to think about the messed up ecosystem of Safari Webextensions. Safari only allows extensions installed via the apple store, but every single adblocker there is a scam. I'm not kidding you, I audited most of them. Chances are it's either a three years outdated list of adblock plus that doesn't catch anything or it's an extension that replaces all google analytics identifiers wi…
Re: Chrome users beware: Manifest v3 is deceitful and threatening
#370Earlier quoted context omitted.
It does not allow request blocking as that has been understood in the context of extensions until now It is not a question that V3 breaks the gold standard privacy protecting extension.
I quibble with this. Request blocking "as that has been understood", is preventing the request from leaving the browser. That's still demonstrably doable with mv3. What's changed is the mechanism. You can argue about the value of changing the mechanism, about the burden placed on plugin developers, or the efficacy of various APIs, but the functionality is inarguably still there.
Therefore, it's not just about changing the mechanism, the end result is clearly a lot worse. One can say, they crippled ad-blocking which this change. Hopefully, once the millions of people using ublock origin start noticing what's happening, they will move away from Chrome. I already did, ublock origin is worth more to me than any feature Google puts in Chrome.