Loading…
Chrome Web Store: "Removal notification for uBlock Origin" #880
14 participants
Mainly this amounts to: "There is somewhere one or more pieces of code I don't understand, but I won't tell you what it is. Your challenge is to find what I am talking about and modify it so that in my next review I will maybe understand it."
but does this mean the old version is still okay to be on the store?
but does this mean the old version is still okay to be on the store?
I don't think so, the email is titled "Removal notification". 1.3.2 was not in the Chrome store, it was merely submitted for publication, so it did not need to be removed -- just rejected.
Even assuming it would still be ok, that pretty much mean it is dead, since from now on I can't update it anymore (there were good bug fixes in 1.3.2). There is no way I will ever figure what is the specific issue given how large uBO's code base is.
haven't they heard of github?
maybe they can only understand it if it is on google code...
Seriously though, this reminds me of streamus and google (youtube)'s battle a few months back. The streamus developer struggled to bring his extensions upto google's standards and they just kept making absurd reasons for denial until he finally gave in. They made up a lot of "technical" reasons in his case too. you can go through the subreddit for more details. And of course, the bottom line is that he was cutting into their ad revenue by not being able to play youtube ads in his extensions..
I would advise you to look into an alternative delivery mechanism for the extension. Google just can't be trusted anymore..
@gorhill Did you reply yet?
My previous experience with the people behind "Chrome store" emails is that they never provide specifics.
2,160,627 users
They're not very smart are they? "I don't understand code, so lets take down a wildly popular extension for no reason whatsoever."
Hi everyone, I've forwarded this issue to Chrome Web Store's abuse team. Sorry for the hassle; we'll get it resolved as soon as we can.
"Chrome Web Store is Google's online store"
Hold on there!!! Wasn't Google also the owner of some Advertisement network???
"Google AdWords is an online advertising service"
The reason is at least still a lot more specific that what you'd get from the Play Store... Google needs to get their act together. My guess is that the removal was automated and as such they don't have much information to give. Otherwise, it's just an unwillingness to give more information on their part.
I'd send them an e-mail about it. There's probably an appeal procedure.
Solution: Firefox
Solution: Ignore the problem
Maybe I'm missing something, but uBlock Origin is still in the CWS and I was just able to install it?
@adamkdean maybe you should read the full thread before commenting?
@sowbug awesome. Hopefully they are able to do something before it gets pulled and 1.3.2 is able to go through unhindered. uBO is an essential extension for web performance for many users.
@adamkdean if you read #880 (comment), you'll see that the new(est) version wasn't accepted to be published in the store.
The existing version is still online, but it might be pending to be removed as well.
Received a response from the Chrome store:
Dear Developer,
We apologize that the update was rejected due to an snag in the review system. The updated item will be available in the Chrome Web Store within 30 minutes.
Thank you for your cooperation,
Google Chrome Web Store team
Developer Terms of Service:
https://developers.google.com/chrome/web-store/termsProgram Policies:
https://developers.google.com/chrome/web-store/program_policiesBranding Guidelines:
https://developers.google.com/chrome/web-store/branding
So this makes the issue resolved -- maybe @sowbug email helped? Thanks for your assistance.
Sorry for this, that really got me worried. If this happens again I will at wait a bit more for feedback from the Chrome store before reporting here. Unclear though whether making such issue widely known sooner than later helps with its resolution, or at least a faster one.
The fact that there are no specifics with such warning is still a Chrome store issue though. If this is caused by some kind of automated review, it would be nice to have at least the files + line numbers which triggered the issue, so that devs are not left completely in the dark as to what need to be worked on, or at least what need clarification, detailed explanation.
Note: as of writing the extension is still in the store -- despite the title of the email I received.
Sigh.
I received the following email regarding my submission of 1.3.2 to the Chrome store:
This is the diff between uBO 1.2.0 and 1.3.2. Many of the commits affect FF branch only.
Nothing out of the ordinary with 1.3.2: bug fixes and the only "new" feature (FF already had this implemented) is to read an entry from managed storage so that admins can enforce their own uBO settings (commit).
So essentially, the policy which is pointed out...
... doesn't tell me anything specific regarding the issue. uBO's code base is rather large, so I don't see how I can ever resolve this issue without specifics. There is no obfuscated code in uBO, it's rather well commented throughout, and I have no problem describing whatever piece of code does what. But having to guess what is the issue here given the code base seems like mission impossible.