Hacker News Reader

Comment by gorhill | Hacker News Reader

Yes, it still is in the store as of now.

However the email I received is titled "Chrome Web Store: Removal notification for uBlock Origin".

In any case, it's just impossible for me to figure what is the issue. I could spend a inordinate amount of time guess-shuffling code around for no result.

Assuming the email title is misleading -- let's say uBlock Origin won't be removed from the Chrome store, there is nothing special in 1.3.2 compared to any other releases, and from the look of it I won't ever be able to fix whatever is deemed wrong without specifics, and as a consequence, no updates lead to abandonware.

Edit: I will add that with Firefox and Opera, there has always been communication with specifics when I was asked to fix something, and I always did fix as demanded (or suggested).

View on HN

> Please reply to this email for issues regarding this item removal.

Have you tried telling them that?

Failing that -- if it were me -- I'd resubmit perhaps with the only addition of a README that briefly explains the file layout.

It looks like 1.3.2 was released a day ago. Have you tried reaching out to get clarification? I'd give it a week or two before buying pitchforks and torches. The app reviewers are fallible just like anyone els. It seems that you never have had this issue before.

https://en.wikipedia.org/wiki/Hanlon%27s_razor

> In any case, it's just impossible for me to figure what is the issue. I could spend a inordinate amount of time guess-shuffling code around for no result.

I’d caution against the shuffling code around to try to reverse engineer the approval rules. I tried the same with a similar extension (Adblock Fast) that got rejected for similar reasons (no reasons as far as I could tell). Result: my dev account got automatically suspended. I had to get a Google friend to get me unsuspended. Google seems to have added very aggressive automated approval and suspension rules. I’d reply to their email and see if they reply back first.

Are the block lists maybe considered code?

Updating them at first start would fit the description of not having them visible in the package.

The filter lists which are selected by default are part of the package. An updated versions of these lists is progressively downloaded a few minutes after first install. But this has been like this since forever now, this is not new.

This demonstrates the problem here, we are left to speculate endlessly about what the is the issue(s) according to the Chrome store.

Or you could, you know, email them like the email says to do.

Looks like there's nothing wrong with 1.2, so we (the users) can just sit this one out, right?

Reply on news.ycombinator.com