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

Google Killing Chrome Extensions with 1 Week Publishing Delays

getpolarized.io

Post reply on HN
Print view View original

21–30 of 46 posts

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#21

Post by chris_mc »

burtonator wrote: post #14
necovek wrote: post #10

While you are, of course, welcome to call upon Google to improve the review speed, there are obvious things you can do on your side as well. First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. In the meantime, you can offer your users to switch to "developer mode" and install the extension manually. I personally would be against the centralized nature of Chrome extens…

> 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?

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#22

Post by ldiracdelta »

burtonator wrote: post #8
MattSteelblade wrote: post #6

A "5 line diff" is absolutely enough code to add something malicious.

Why does it take a week to accept/deny that...? Note that they aren't actually DOING anything in this week. The Polar extension is literally just sitting waiting for someone to approve it because I updated the images.

They could be applying back pressure on the review queue. I'm going to guess that you'll be doing a lot fewer releases now.

Anyways, I get that the turnaround time stinks.

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#23

Post by derekp7 »

burtonator wrote: post #14
necovek wrote: post #10

While you are, of course, welcome to call upon Google to improve the review speed, there are obvious things you can do on your side as well. First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. In the meantime, you can offer your users to switch to "developer mode" and install the extension manually. I personally would be against the centralized nature of Chrome extens…

> 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.

Would it be appropriate to re-architecture your extension, so that only the minimal code necessary is in the actual extension? And put the rest into a progressive web app? The way I think of extensions is similar to a device driver for an OS, a way to add functionality that an app needs that isn't already provided by the base platform.

This way, you only need to push a new extension update whenever you need new api-level functionality, and you have total control over the rest of the user experience (regular HTML/CSS/javascript).

Or would this cause the extension to be rejected by Google, on the grounds that the "api" that it adds would be too open to abuse?

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#24

Post by monkin »

burtonator wrote: post #8
MattSteelblade wrote: post #6

A "5 line diff" is absolutely enough code to add something malicious.

Why does it take a week to accept/deny that...? Note that they aren't actually DOING anything in this week. The Polar extension is literally just sitting waiting for someone to approve it because I updated the images.

> Why does it take a week to accept/deny that...?

Because they have to check hundreds of thousands of applications a day, most of which improve stupid things like typos. Having the biggest part of the cake doesn't help either.

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#25

Post by vec »

burtonator wrote: post #14
necovek wrote: post #10

While you are, of course, welcome to call upon Google to improve the review speed, there are obvious things you can do on your side as well. First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. In the meantime, you can offer your users to switch to "developer mode" and install the extension manually. I personally would be against the centralized nature of Chrome extens…

> 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.

"continuous delivery" != "test in production"

But even if it were, why do you think continuous delivery is the appropriate choice of workflow when you don't actually control the "delivery" part?

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#27

Post by protomyth »

maccio92 wrote: post #9
burtonator wrote: post #7

Earlier 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.

They don't know you only fixed a typo until they've had time to review it

They don't do a check of the changes in some automated manner? Is that tooling not available for extensions?

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#28

Post by Scoundreller »

ocdtrekkie wrote: post #3

Given 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.

Limiting rollouts/updates velocity would probably be a good idea too.

We don’t let drug companies sell their products to everyone the second it’s produced. First you test in mice, then 10 people, then 100, then 1000, then, and only then, can you release it to an entire population (roughly speaking).

Re: Google Killing Chrome Extensions with 1 Week Publishing Delays

#30

Post by burtonator »

maccio92 wrote: post #9
burtonator wrote: post #7

Earlier 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.

They don't know you only fixed a typo until they've had time to review it

Yes they do. I'm not actually releasing code. This is just the images and text associated with the store. Not the actual app
Post reply on HN