TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

After 3 Years of Work, Chrome Killed My Extension and Won’t Tell Me Why

46 pointsby mikobalmost 5 years ago

6 comments

thephyberalmost 5 years ago
{Google, Apple, Steam, etc} all do this with their walled gardens. It&#x27;s sad, but it&#x27;s not unique.<p>Perhaps if there were way to make the rules more programmatic and less ambiguous, these might be easier to resolve (like writing code to fulfill unit tests). But I suppose it probably still gets evaluated by humans on a subjective judgement, even if there is an objective rubric for most of the requirements.
评论 #23587520 未加载
thro1almost 5 years ago
This made me even more depressive.<p>I stopped developing browser extensions when Mozilla killed their only competitive advantage over Google and allowed Webextensions only.
anon4reasonsalmost 5 years ago
This happened to me as well, and my extension was quite popular and very lucrative.<p>What I ended up doing was uploading it to the store under a new category and hoped it would be reevaluated under different people or constraints and it worked. Has been up and running for over a year.
fortysevenalmost 5 years ago
And this is why I stopped developing for Google&#x27;s platforms. Extensions? Android? Forget it. Been abused by their rancid practices too many times, and heard too many similar horror stories. Not worth it.
indigodaddyalmost 5 years ago
Surprised this got no comment traction. This is outrageous. Why on earth can’t Google just identify the exact infraction? Absolutely ridiculous.
jackandamydevalmost 5 years ago
What rejection message ae ou receiving? Maybe I can help Amy