Ask HN:如何申诉被拒绝的 Google 扩展程序?

2作者: modzu21 天前
我向 Google Chrome 网上应用店提交了一个扩展程序(一个广告拦截器)。 Google 以牵强的理由一再拒绝我的扩展。第一次被拒的理由是“垃圾信息”。当我申诉时,审核结果变成了它包含“附加功能”,因为它“修改网络流量”。当然了,它就是这么做的!当我询问审核员如何在不使用“declarativeNetRequest”的情况下实现广告拦截的既定功能时,我只收到了同样的套话式回复。 我提交了一个全新的更新,简化了代码,并添加了注释,以及引用了其他使用完全相同机制的开源项目。结果再次被拒绝。在这次申诉中,我请求将此案升级给一位高级审核员,希望能得到更具上下文的回复。结果是同样的套话式回复和拒绝。 我忍不住认为 Google 有某种内部政策,故意刁难广告拦截器。对我来说,很明显所谓的拒绝理由并不成立(请注意,我并非初次涉足此事——我已有几个扩展程序发布多年,拥有数千用户),但我从未遇到过如此的阻碍。 这真是一个令人遗憾的局面,尽管并非完全出乎意料。说实话,我很惊讶 Google 还没有正式出台禁止广告拦截器的政策。但他们并没有这样做——显然,网上应用店里还有其他广告拦截器,而这正是令人沮丧的地方。 总之,各位开发者。你们是否遇到过类似的情况?你们是如何解决的?谢谢!
查看原文
I submit an extension (an adblocker) to Google Chrome&#x27;s web store.<p>Google keeps rejecting it for dubious reasons. The first rejection was claim it was &quot;spam&quot;. When I appealed, the review came back that it contained &quot;additional functionality&quot; because it uses &quot;modifies network traffic&quot;. Well of course it does! When I asked the reviewer how I could achieve the stated functionality of blocking ads without the use of &quot;declarativeNetRequest&quot; I simply received the same canned response.<p>I submit a totally new update that simplified the code and included comments, and references to other open source projecs that use the exact same mechanisms. Again it was rejected. On this appeal I asked if it could be escalated to a senior reviewer who could possibly reply with more context. Same canned response and rejection.<p>I can&#x27;t help but think Google has some internal policy to give adblockers a runaround. It is obvious to me the stated rejections are not valid (Note that I&#x27;m also not new to this - I have several extensions that have been published for years with thousands of users) but have never encountered such gate-keeping before.<p>It&#x27;s a sad state of affairs even if not totally unpredictable. To be honest I&#x27;m surprised Google hasn&#x27;t made it an official policy to prohibit adblockers. But they haven&#x27;t - obviously there are other adblockers published to the store, and that&#x27;s what makes this so frustrating.<p>Anyway, fellow developers. Anyone run into a similar situation? And how did you resolve it? Thanks!