zlacker

[return to "AdNauseam Banned from the Google Web Store"]
1. menega+e7[view] [source] 2017-01-05 15:14:35
>>yuvada+(OP)
Few month ago we developed and launched an AI-based AdBlocker (called AdFilter) and also had several problems with Google Chrome Web Store. Almost every week they had a "strange reason" to remove our extension from the Google Chrome Web Store.

We had more than 380,000 DAU (Daily Active Users) from 36 countries with all good feedbacks on Google Chrome Web Store, but even so, Google always tried to find a way to get us delisted and sometimes removed... they called it "an automated review process that is not performed by humans".

Every time this happened we need to send several messages to all available email address to get our extension approved and listed again in 24-48 hours. After facing this kind of situation more than 12 times, we simply gave up and remembered that it's not worth trying to build a business (or App) on top 3rd party company, like Google or FB.

◧◩
2. loster+l8[view] [source] 2017-01-05 15:21:37
>>menega+e7
It's possible to install Chrome extensions outside of the store: https://github.com/dhowe/AdNauseam/wiki/Install-AdNauseam-on...
◧◩◪
3. diggan+5a[view] [source] 2017-01-05 15:30:40
>>loster+l8
> Earlier this week, on Jan 1st 2017, we were informed by our users that Google had banned AdNauseam from its Chrome Web Store. We’ve since learned that Google now also disallows users from manually installing and updating AdNauseam, thus locking users out of their own saved data, all with no prior notice or warning.
◧◩◪◨
4. loster+4b[view] [source] 2017-01-05 15:36:11
>>diggan+5a
I'm not sure why you're quoting that? I literally just installed the plugin.

Google has blocked installing AdNauseam from the Chrome store and installing the .crx file manually.

Manually installing the developer package is completely unhampered.

◧◩◪◨⬒
5. snowwo+1d[view] [source] 2017-01-05 15:49:09
>>loster+4b
Restart your browser and you will see the extension is no longer installed. This is deliberate on the part of Chrome (Firefox does this too) - It is to prevent malicious extensions from using the developer mode as a backdoor to install themselves.

On each restart, you will need to re-add the extension from source.

[go to top]