Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pausing Manifest V2 phase-out changes

groups.google.com

Post reply on HN
Print view View original

11–20 of 170 posts

Re: Pausing Manifest V2 phase-out changes

#11

Post by whstl »

lewisjoe wrote: post #4

Great news. One thing that I'm sure about V3 is that it isn't well thought-out at all. For example, imagine your extension has to cache data for a browser session (across tabs but with a single cache), it's impossible as of now. The only workaround to do that has a 1MB storage limit, essentially forcing you to have a server-side cache mechanism (redis or whatever) for this trivial use-case. And worse, Google develope…

It is hubris. Google thinks it can get away with anything, since they're the market leader. The reality is that a certain number of people will migrate to Firefox over AdBlockers not working well anymore, and will give FF a second life. And those are the people who helped get Chrome off the ground by installing on the computers of relatives and recommending to friends.

Re: Pausing Manifest V2 phase-out changes

#12

Post by freedomben »

brucethemoose2 wrote: post #6
lewisjoe wrote: post #4

Great news. One thing that I'm sure about V3 is that it isn't well thought-out at all. For example, imagine your extension has to cache data for a browser session (across tabs but with a single cache), it's impossible as of now. The only workaround to do that has a 1MB storage limit, essentially forcing you to have a server-side cache mechanism (redis or whatever) for this trivial use-case. And worse, Google develope…

This seems to be a pattern among Google employees, as least as I'm seeing from the outside. They have their own company reality bubble, and clashes or inconsistencies with the outside world are met with disbelief.

Indeed, but it's a problem in engineering society-wide, not just Google. The more I think of it actually, it's just a human problem. Even kids default to this. I wish Socratic Ignorance were taught widely and often in school.

Re: Pausing Manifest V2 phase-out changes

#13

Post by freedomben »

shmde wrote: post #10

I love it when advertisment companies who make money handcrafting the perfect ad for you, analysing your search history, talk about Privacy. Yes, this V3 manifest will break adblockers but think about your pRiVaCy gUys!!!

I don't disagree with you (always follow the money), but on the other hand, who better to understand the privacy concerns than the people who work around them for a living? I would definitely want to listen to them. That doesn't mean we just take what they say uncritically, but their perspective is very important.

Re: Pausing Manifest V2 phase-out changes

#15

Post by poolopolopolo »

m_a_g wrote: post #5

Anything that breaks uBlock Origin is a deal breaker. With the chrome team making so many alterations to their plans, I guess we'll have to wait and see.

Pretty much, there will never be a "smooth" transition from V2 to V3 when you are purposely trying to kill the most used plugins.

Re: Pausing Manifest V2 phase-out changes

#16

Post by tyingq »

Just fine tuning how slowly to boil the frogs. At some point, they will pull the trigger. My hypothesis is that the various entities that want to work around ad-blockers hold back for now, because they don't want to push people from the more basic blockers to the more advanced ones. Once this is in place, pretty much all adblockers of note are dns based, or semi-static list based...."basic". I wonder if there's a renewed push fighting ad blockers then.

Re: Pausing Manifest V2 phase-out changes

#17

Post by lozenge »

lewisjoe wrote: post #4

Great news. One thing that I'm sure about V3 is that it isn't well thought-out at all. For example, imagine your extension has to cache data for a browser session (across tabs but with a single cache), it's impossible as of now. The only workaround to do that has a 1MB storage limit, essentially forcing you to have a server-side cache mechanism (redis or whatever) for this trivial use-case. And worse, Google develope…

Just raised to 10 MB?

Re: Pausing Manifest V2 phase-out changes

#18

Post by [deleted] »

Operative0198 wrote: post #7
m_a_g wrote: post #5

Anything that breaks uBlock Origin is a deal breaker. With the chrome team making so many alterations to their plans, I guess we'll have to wait and see.

Mv3 broke uBlock Lite for me (used uBlock to control js mostly). But that wasn't a deal breaker because I got to discover NoScript (still stuck on mv2 but I like the approach vastly better than original uBlock's implementation). Just waiting to see how this functionality will be handled in mv2 sunset since Noscript has no plans to migrate atm and uBlock lite should be "guttered" for the foreseeable future.

[deleted]

Re: Pausing Manifest V2 phase-out changes

#19

Post by Tempest1981 »

So the phase-out won't begin until 2024 at the earliest? Did I read that right? What was it previously, June 2023?

> We will provide sufficient migration time for developers - at least 6 months of heads-up - before beginning any experiments to turn off MV2 in the browser next year

So "next year" is 2023 or 2024?

Re: Pausing Manifest V2 phase-out changes

#20

Post by ollien »

Tempest1981 wrote: post #19

So the phase-out won't begin until 2024 at the earliest? Did I read that right? What was it previously, June 2023? > We will provide sufficient migration time for developers - at least 6 months of heads-up - before beginning any experiments to turn off MV2 in the browser next year So "next year" is 2023 or 2024?

Given this was posted 3 days ago, I'd say 2024 :)
Post reply on HN