My Authors
Read all threads
Something not good was going on with the Chrome WebStore since November, but this case is definitely a culmination.

Dashlane password manager (3M+ users) was removed today for who knows what reason:


Thread (1/9)
First of all, the CWS team was trying to solve a really serious issue - tons of malware and adware extensions that were overwhelming the CWS. The obvious solution was to introduce a manual moderation process and that's exactly what they did.

(2/9)
This has lead to increased review times so now we can wait for up to 3 weeks until the extension update is reviewed and allowed to CWS. There's no way to ask for an expedited review so if you shipped a bug, you are f*cked.

(3/9)
To make things even harder, the CWS team took an interesting approach to communication. If there's something wrong with the extension, they exclusively use canned responses and never explain anything in detail. You just have to guess what they mean.

(4/9)
And of course, there are bugs and some obvious flaws that also don't help. If you change one word in the description, you have to go through the full review. If you publish the extension to testers only, you have to go through the full review. Etc, etc.

(5/9)
All that was not enough. They decided to enforce the CWS development policies *as they see them*. The problem is that some of these policies are rather vague and can be interpreted differently.

(6/9)
First, they removed the uBO dev build because of their understanding of the "Single purpose" policy:



Now they remove Dashlane because of how they understand the "Use of Permissions". Maybe their understanding is okay, I don't know, but

(7/9)
The problem is that they do not explain what's the problem. They use canned emails only, remember? This is what extensions devs get: "You're using too many permissions, you have 7 days (in fact, 1) to fix this or your extension will be removed".

(8/9)
I do believe that they're trying to make CWS better. But I honestly do not believe that 3 months is not enough to fix the communication. This would immediately solve half of the issues I mentioned in the thread.

(9/9)
Missing some Tweet in this thread? You can try to force a refresh.

Enjoying this thread?

Keep Current with Andrey Meshkov

Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!