4 ms·
It's pretty sad that getting any of these automated issues resolved requires this. I get the whole need to be able to properly review extensions before they are
by kjrose 6y ago
It's pretty sad that getting any of these automated issues resolved requires this. I get the whole need to be able to properly review extensions before they are in the store. Its such a high security vulnerability.
However. Banning an old app suddenly and not really providing any response to deal with it... that's not a good solution.
- ChuckMcM 6y agoYou know, it sounds to me like a real pain point that could add customer value if it were addressable. As such it suggests that if someone were bright enough to come up with a solution to curating these sorts of things you could add real value that an enterprise customer would pay big money for. It has billion dollar startup written all over it.
- kjrose 6y agoOh absolutely. This is something I chew over all the time. How can we have a large corporation dealing with the number of users that Amazon/Google/etc are dealing with, as well as the number of malicious parties trying to break them without resorting to either systems that create excessive false negatives and provide little to no appeals process of any use, and without having a massive overhead cost for handling the appeals in a judicially reasonable way. Everytime I work on it, it turns into that it requires more people who are properly trained in almost legal theory, and then you end up quickly with the same problem that many policing and court systems have which is very quickly individuals with an axe to grind work to achieve regulatory capture.
- gkoberger 6y agoIt's been fewer than 24 hours since this happened, and they send him an email immediately with steps to fix it. It sucks, but remember that Chrome Extensions have basically unlimited power, and Google is doing their best to protect users. [EDIT: And it's resolved! The extension is back]
- kjrose 6y agoWell I'm glad they resolved it so fast. That's excellent.