问HN:如何对被拒绝的Google扩展进行上诉?

2作者: modzu18 天前原帖
我向Google Chrome的应用商店提交了一个扩展程序(一个广告拦截器)。<p>但是Google不断以可疑的理由拒绝它。第一次拒绝的理由是它被称为“垃圾邮件”。当我提出上诉时,审核结果是它包含“额外功能”,因为它“修改了网络流量”。当然是这样!当我询问审核员如何在不使用“declarativeNetRequest”的情况下实现阻止广告的功能时,我只得到了同样的标准回复。<p>我提交了一个全新的更新,简化了代码并添加了注释,以及对其他使用相同机制的开源项目的引用。结果再次被拒绝。在这次上诉中,我询问是否可以升级到一位高级审核员,以便可能得到更多的背景信息。结果还是同样的标准回复和拒绝。<p>我不禁觉得Google内部可能有某种政策,让广告拦截器处于被动状态。显然,我认为这些拒绝的理由并不成立(请注意,我并不是新手——我有几个已经发布多年的扩展,用户数以千计),但我从未遇到过这样的门槛。<p>这种情况令人感到沮丧,尽管并不完全出乎意料。老实说,我很惊讶Google没有将禁止广告拦截器作为官方政策。但他们并没有——显然还有其他广告拦截器已经发布到商店,这让人感到非常沮丧。<p>无论如何,其他开发者们,有人遇到过类似的情况吗?你们是如何解决的?谢谢!
查看原文
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!