Google Killing Chrome Extensions with 1 Week Publishing Delays

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.

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

While this might be highly burdensome for developers, I much prefer the world where Google reviews even single-line changes to extensions.

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

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.<p>First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days.<p>In the meantime, you can offer your users to switch to &quot;developer mode&quot; and install the extension manually.<p>I personally would be against the centralized nature of Chrome extensions world anyway (which, by definition, leads to bottlenecks, for dubious benefits), but at one point Google claimed there were 180,000+ extensions in the web store, and if only 0,1% of those get updated every week, that&#x27;s 180 extensions to be reviewed every week.

Clickbait title, no extensions are &quot;killed&quot;.

Between 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.<p>Perhaps someone else could make this point in a way that would be better-received.

Does anyone else feel that the Chrome Webstore is completely neglected? <a href="https:&#x2F;&#x2F;presentio.us&#x2F;view&#x2F;c3c537" rel="nofollow">https:&#x2F;&#x2F;presentio.us&#x2F;view&#x2F;c3c537</a>

I think there&#x27;s a miscommunication here.<p>When I say typo or image I&#x27;m talking about the <i>appstore</i> assets... not the binary.<p>There&#x27;s the actual binary you push out to you chrome uses.<p>Then there is the text and images in the app store. This is NOT part of the app.<p>IF you fix a typo in the app store description, it causes a one week review.<p>Even when you didn&#x27;t actually update the app AT ALL.<p>The exact same binary - bit for bit.<p>That&#x27;s part of the the issue.<p>The other is that changing a small amount of code shouldn&#x27;t require a full week to re-audit.

This also appears to be selectively enforced. We have two different extensions with global permissions, but only one requires a 1-week review. For the other we can still push out updates in &lt; 30 minutes.

Welcome to Walled Gardens... we should all read &#x27;Carry On by Bruce Scheiner&#x27;

Slightly off-topic, but does anyone use this app as an ebook manager?<p>I&#x27;m looking to switch away from Calibre (which has a cluttered user interface) and if Polar supports common ebook formats it might be worth trying.

Since when are apps allowed hn accounts?

I really hope this gets changed as this currently makes fixing small changes a massive, and wanting to release a feature at the same time on a website and extension means the chrome version must be done a week in advance. This is really killing productivity