Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> ... all of this is consistent with an extension that should be kicked off the app store within 14 days.

No, it absolutely isn't. You can't take someone's livelihood off the app store within 14 days when they have every interest in complying with your policy but you just don't feel the need to even tell them what all the policy is. The fact it was approved in the first place is Google's fault, not the app developer, so is totally irrelevant to this saga.

If you can hit the Reject button you can fill in a text box that says why. There's no excuse for that.



I think there's two issues here:

1. should Google provide more context to the developer? Of course.

2. if the extension is a genuine danger to users, should they remove it immediately? Of course

I agree that Google should do #1 as well as #2, but I absolutely believe it's better to do #2 (even without #1) than to do neither.


I mean they can. It's their store. I don't think they should, but still


I'm pretty sure the parent comment understands that they can, and also agrees that they shouldn't.


I’m not at all certain about the latter. They’re pretty consistent in ignoring users and providing shitty service.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: