Earlier quoted context omitted.
Why wait? Move to Firefox now.
Feels slow in old computers with 4GB and Chrome has a better built-in for freeing up memory from inactive tabs.
But will likely be plagued with performance degrading ads.
Pausing Manifest V2 phase-out changes
31–40 of 170 posts
Re: Pausing Manifest V2 phase-out changes
#32Manifest V3 is a perfect example of "great idea but terrible execution". The ability to have extension pages be suspended when not in use is great. Improving (and having finer grained) permissions is great. It should have stopped there: introduce a new "persistent" permission that extensions can request to stay around permanently, and when not requested, introduce lifecycle events so extensions can properly handle su…
MV2 background pages were already by default in a mode where they are suspended when not in use. MV3 doesn't improve on that except to make it impossible to have persistent background pages.
Re: Pausing Manifest V2 phase-out changes
#33Earlier quoted context omitted.
Why wait? Move to Firefox now.
Feels slow in old computers with 4GB and Chrome has a better built-in for freeing up memory from inactive tabs.
Not sure about that, works for me just fine on many (even old) computers. But even if it was true, I prefer keeping the number of open tabs below 100 if that means not running browser made by an advertising agency. Talk about conflict of interests...
Re: Pausing Manifest V2 phase-out changes
#34Great 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.
I remember getting into it with a Google person in a forum once. They kept insisting they couldn't do real, portable files in Google Drive for Docs because that would break collaboration. They didn't seem able to understand I didn't want collaboration. I wanted to be able to open my word processor/spreadsheet/etc files in other tools without needing to connect to the internet (predates offline mode). I wanted to be able to back them up somewhere (3-2-1 strategy). I wanted to be able to do automated analysis across all my writing. In short, I wanted to own my files.
They simply could not conceive of a use case that was offline or didn't trust Google to be reliable. I honestly don't think they ever used a real desktop office suite. They had no model in their head to understand it.
Re: Pausing Manifest V2 phase-out changes
#35Just 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 ren…
Or working on pressuring Firefox to implement MV3.
Re: Pausing Manifest V2 phase-out changes
#36Great 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…
> One thing that I'm sure about V3 is that it isn't well thought-out at all.
that's because it's been invented for the sole purpose of making "breaking effective ad-blocking" look legitimate
Re: Pausing Manifest V2 phase-out changes
#37Google is not even close to finishing MV3: "On the userScripts API, the proposal has been merged into the WECG but the engineering work has not started yet." https://github.com/w3c/webextensions/blob/f8f430f1904c2a6fa8...
MV2 is sticking around until at least 2024.
Re: Pausing Manifest V2 phase-out changes
#38Great 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…
Are you talking about local storage? If so the limit is 5 MB: https://developer.chrome.com/docs/extensions/reference/stora...
Re: Pausing Manifest V2 phase-out changes
#39Great 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…
> One thing that I'm sure about V3 is that it isn't well thought-out at all. that's because it's been invented for the sole purpose of making "breaking effective ad-blocking" look legitimate
And similarly, FLoC was invented for the sole purpose of making targeted advertising look legitimate.
Re: Pausing Manifest V2 phase-out changes
#40As someone who has made an extension for an actual product, this whole rollout/situation has been an absolute shitshow.
This is, what, the third pause of the rollout?
Google stopped accepting V2 extensions sometime last year, pushing V3 but totally ignoring MANY of the current use cases of extensions that V3 just doesn't work for. Firebase auth, a Google freaking product, doesn't work in V3 (you can make it work with a bunch of "I read it on a forum somewhere" work arounds).
The ONLY reason they're pushing this is to shore up their ads business by breaking add blockers.