Live data from Hacker News

Google Begins Testing Extension Manifest V3 in Chrome Canary

bleepingcomputer.com

71–80 of 448 posts

Re: Google Begins Testing Extension Manifest V3 in Chrome Canary

#71

Meanwhile me laughing in Firefox. I hope no one here is surprised by this G was more and more anti ad-blocking for years now. This is only natural conclusion after u are a de-facto browser monopoly.

Google captcha makes some sites almost unusable on firefox if you dare to resist fingerprinting for full traceability.

https://news.ycombinator.com/item?id=20147015

Re: Google Begins Testing Extension Manifest V3 in Chrome Canary

#73
post #22
post #15

This is the point in the dominance cycle where the dominant player decides they no longer need to be the fastest or the most secure and that their dominance will allow them to coast along doing their thing. There’s nothing particularly inevitable about what happens next, but let’s hope they get an IE6-sized kick in the teeth.

> they get an IE6-sized kick in the teeth. as in: people will continue to suffer for about a decade while good alternatives readily spring up but suffer slow adoption?

Firefox is already here.

Re: Google Begins Testing Extension Manifest V3 in Chrome Canary

#75
post #60
post #32

Earlier quoted context omitted.

Pi-hole can't filter out ads that are embedded into the page though. I think adblockers have to be a browser extension to work conprehensively.

Pi-hole can switch from magicking the DNS to being a proxy that rewrites HTML.

Really? I thought recent dns improvements would prevent this sort of thing.

Re: Google Begins Testing Extension Manifest V3 in Chrome Canary

#76
post #62
post #50

> Simeon Vincent, a Google Developer Advocate for Chrome Extensions One has to love and admire the use of Newspeak by big companies... How is this Mr Vincent an "advocate"? He's in charge of destroying extensions! On his Twitter bio [1] he also says he likes "helping people" and "the open web". The cognitive dissonance must be hard to bear. [1] https://twitter.com/dotproto

And once asked a clear question, the developer advocate deflects and stops answering: https://github.com/uBlockOrigin/uBlock-issues/issues/745#iss...

Did you link to the right thing? That isn't a deflection, they're asking permission to sideline the issue on uBlock's issue tracker into a discussion about Chrome/Chromium's extension policies, which incidentally they didn't get a clear answer to.

> I also don't want to hijack this without the project's permission. @gorhill & contributors, do you mind having this discussion here or would you prefer if we moved it elsewhere?

I haven't really been following this issue, but I did read the linked reply, so I may be missing some bigger context.

Re: Google Begins Testing Extension Manifest V3 in Chrome Canary

#77
post #50

> Simeon Vincent, a Google Developer Advocate for Chrome Extensions One has to love and admire the use of Newspeak by big companies... How is this Mr Vincent an "advocate"? He's in charge of destroying extensions! On his Twitter bio [1] he also says he likes "helping people" and "the open web". The cognitive dissonance must be hard to bear. [1] https://twitter.com/dotproto

“Hello, fellow developers! I myself am a developer, just like you! How’s everyone developing today? By the way ” It’s so transparent, I boggle at how anyone falls for it, or that companies still think it is a viable strategy.

[deleted]

Re: Google Begins Testing Extension Manifest V3 in Chrome Canary

#79
post #71

Meanwhile me laughing in Firefox. I hope no one here is surprised by this G was more and more anti ad-blocking for years now. This is only natural conclusion after u are a de-facto browser monopoly.

Google captcha makes some sites almost unusable on firefox if you dare to resist fingerprinting for full traceability. https://news.ycombinator.com/item?id=20147015

Can you surpass it by faking user-agent and pretend to be Chrome?

Re: Google Begins Testing Extension Manifest V3 in Chrome Canary

#80
post #17

Earlier quoted context omitted.

Apple/Safari adopted pretty much the same architecture on Ad Blockers. Maybe just maybe the conspiracy theories are all wrong, and there was actually a legitimate, technical reason for choosing a restricted API.

Safari has a much larger limit for blocking list entries though.

+ the limit there is per-extension, not global
Post reply on HN