3 ms·
As 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 r
by John23832 4y ago
As 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.
- tssva 4y agoThis isn't a new pause of the rollout. It is a message giving a general update on changes made to the APIs since the pause announced months ago began.
- gnicholas 4y agoMy reading is that this announcement indicates a new quasi-indefinite pause, beyond what was previously announced. They will probably still phase out v2, but every additional message about this pushes the timeline back further (even if it’s not explicitly mentioned). BTW, does anyone know how to subscribe to these Chrome updates? I’m kinda surprised not to get them via email, considering I manage multiple Chrome extensions.
- tssva 4y agoThe December pause announcement stated it was until at least January 2024. This update still mentions a timeline of next year for v3. I find it hard to read as anything beyond the update of progress which was promised for March when the pause was announced in December.
- hsbauauvhabzb 4y agoA few months back a HN user suggested it may be wise to continually delay an unpopular change, im no PR expert but I thought that was an interesting perspective.