TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

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

46 点作者 mikob将近 5 年前

6 条评论

thephyber将近 5 年前
{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 未加载
thro1将近 5 年前
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.
anon4reasons将近 5 年前
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.
fortyseven将近 5 年前
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.
indigodaddy将近 5 年前
Surprised this got no comment traction. This is outrageous. Why on earth can’t Google just identify the exact infraction? Absolutely ridiculous.
jackandamydev将近 5 年前
What rejection message ae ou receiving? Maybe I can help Amy