Most of the discussion on this link is about how Google is being developer hostile. I think that's getting plenty of attention. You are certainly within your r

Most of the discussion on this link is about how Google is being developer hostile. I think that's getting plenty of attention. You are certainly within your rights to state things divisively if it pleases you. I was merely suggesting how you might make your point in a way people will agree with you. If they've flagged this through user reports of the permissions being too wide then they may not actually know which permissions need to be changed. Even if this were true, 1) what about the update that narrowed the permissions, surely Google knew which permissions remained in violation? Remember, it was the rejection of that update that prompted this post 2) user reports of permissions being too wide should also be required to identify the specific permission that is in violation. That would not only help the developer, but also help Google make the decision on whether to ultimately ban the extension 3) Google should have clearly stated in the initial message that they hadn't actually verified that the alleged violations are occurring