Pausing Manifest V2 phase-out changes
groups.google.com
Pausing Manifest V2 phase-out changes
1–10 of 170 posts
Re: Pausing Manifest V2 phase-out changes
#2Is Google sure of what they're doing at all anymore?
Re: Pausing Manifest V2 phase-out changes
#3Ultimately the biggest risk here I think is adblockers. It’s the universal extension
Re: Pausing Manifest V2 phase-out changes
#4Great 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 developers essentially refuse to understand the problem - https://bugs.chromium.org/p/chromium/issues/detail?id=118522...
Re: Pausing Manifest V2 phase-out changes
#5Anything 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.
Re: Pausing Manifest V2 phase-out changes
#6Great 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.
Re: Pausing Manifest V2 phase-out changes
#7Anything 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.
Re: Pausing Manifest V2 phase-out changes
#8[deleted]
Re: Pausing Manifest V2 phase-out changes
#9Great 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.
The customer is always right - except when I think I'm smarter than their stated needs.
Re: Pausing Manifest V2 phase-out changes
#10I 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!!!