Welcome to Walled Gardens... we should all read 'Carry On by Bruce Scheiner'
Google Killing Chrome Extensions with 1 Week Publishing Delays
31–40 of 46 posts
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#32Earlier quoted context omitted.
For a typo? Did you read the post? If I update the text or change a typo they take a week to release the update. During this time I can't release another version of my app.
Improve your QA process and you will not be waylaid by something as simple as a typo.
Hopefully there'd be an option to roll back to some previously approved/released version. So your users may have to wait longer for the exciting new functionality, but at least they won't be screwed.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#33Given how much malware the Chrome Web Store pushes, and how sensitive of data extensions have access to, actually taking the time to properly review updates is absolutely warranted.
The week long delay could also be a reflection of how understaffed that team is. Or they haven't yet automated what can be done automatically. It doesn't necessarily mean that the code review is thorough.
The week long delay may well be a mechanism to discourage developers from sending lots of small changes like OP, to lighten the workload.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#34Since when are apps allowed hn accounts?
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#35Clickbait title, no extensions are "killed".
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#36There are a lot pronouns used in this article referring to a "permission". What permission are they referring to? I pushed out an update to a Chrome extension a few days ago and it was live in a matter of hours. Is there some specific permission that triggers this review?
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#37We also noticed that publishing on the GSuite Marketplace (G Docs addon) is taking a while.
We started an OAuth verification process a little over two months ago for a new addon and we’re still not validated.
Looks like Google has strictly reviewed how third parties process their user data and is making important changes on that. It has started last year [1], I presume following Facebook scandals.
And indeed, the team is probably not staffed enough yet.
[1] https://developers.googleblog.com/2018/10/elevating-user-tru...
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#38Earlier quoted context omitted.
> First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. Are you a developer? This is literally the definition of continuous delivery.
I already don't like how you constantly push your product on HN, but now you're acting like an entitled asshole to boot. Maybe chill out and don't attack possible users?
Previously-possible users, maybe. After this, I'm guessing uptake from here is lower.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#39Between the attitude of the poster and the green-labeled accounts taking their side or talking up the product in question (!), any sympathy I might have had has evaporated.
Perhaps someone else could make this point in a way that would be better-received.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#40I think there's a miscommunication here.
When I say typo or image I'm talking about the appstore assets... not the binary.
There's the actual binary you push out to you chrome uses.
Then there is the text and images in the app store. This is NOT part of the app.
IF you fix a typo in the app store description, it causes a one week review.
Even when you didn't actually update the app AT ALL.
The exact same binary - bit for bit.
That's part of the the issue.
The other is that changing a small amount of code shouldn't require a full week to re-audit.