A developer with published extensions and thousands of users describes repeated rejections of their adblocker extension by Google Chrome. The company initially flagged it as "spam" then claimed it had "additional functionality" because it modifies network traffic—essential for any adblocker. Despite simplifying the code and including references to similar open-source projects, Google continued rejecting the extension with identical canned responses.

The developer questions whether Google has an internal policy to discourage adblockers, noting their stated rejections seem invalid given that other adblockers exist in the store. With years of extension publishing experience and multiple successful apps, this reviewer encountered unprecedented gatekeeping. The situation appears especially frustrating since Chrome Web Store policies theoretically allow adblockers, yet this developer faces inexplicable obstacles.

The developer seeks advice from fellow developers who may have faced similar challenges in navigating Google's review process. Despite the apparent contradiction between store policies and practical barriers, the post highlights developer frustration with opaque review systems that appear to apply inconsistent standards to competing products within the same ecosystem.