破碎的 GitHub 支持系统正在摧毁开发者的职业生涯
A broken GitHub support system is destroying careers overnight
Before anything else: this is not an account recovery request.
首先声明：这不是一个账号恢复请求。
This is about what happens when a support flow stops leading to a human being — or breaks due to a UI inconsistency that made it into production.
这关乎当支持流程不再通向真人——或因一个已投入生产的 UI 不一致性而中断时，会发生什么。
Right now, accounts can be flagged by automated systems or false reports and pushed into a dead loop. That is a serious failure mode, and there is currently no clear way out of it.
现在，账号可以被自动化系统或虚假举报标记，并被推入死循环。这是一个严重的故障模式，目前没有任何明确的出路。
When an account gets flagged, it can effectively disappear — along with all of its repositories.
当一个账号被标记时，它实际上会消失——连同它所有的仓库。
And what if you have maintained that repository for over 9 years, it is used by more than 230,000 projects, and it has thousands of stars? Apparently none of that matters. It still gets handled entirely by automation.
如果你维护了一个超过 9 年的仓库，它被超过 230,000 个项目使用，并拥有数千个星标呢？显然这些都不重要。它仍然完全由自动化处理。
You do not get a proper explanation. You do not get a clear reason. Your account just disappears — no prior notice, no warning, no follow-up.
你不会得到合理的解释。你不会得到明确的原因。你的账号就这样消失了——没有事先通知，没有警告，没有后续跟进。
Then you open a ticket, and you automatically receive a response telling you that, if you do not want to see that message again, you should check a box confirming you have already contacted GitHub about this issue.
然后你提交工单，你会自动收到一条回复，告诉你：如果你不想再看到这条消息，你应该勾选确认你已经就此事联系过 GitHub 的复选框。
So you open another ticket — but there is no field where you can answer "yes" to that question.
于是你再开一个工单——但表单中并没有可以回答"是"的那个字段。
So what do you do? You fill out the form, include the previous ticket number to show that you already contacted GitHub — and what happens?
那你怎么办？你填写表单，附上之前的工单编号以证明你已经联系过 GitHub——然后发生了什么？
You receive the exact same automated response again, telling you to check a box that does not exist.
你收到了完全相同的自动回复，再次告诉你去勾选一个根本不存在的复选框。
That is not an appeal process. It is a dead loop.
这不是申诉流程。这是一个死循环。
The most disturbing part is not that systems can make mistakes. Any system can fail.
最令人不安的不是系统会犯错。任何系统都可能失败。
The disturbing part is that human review — the absolute minimum in a case like this — is no longer reachable.
令人不安的是，人工审核——在这种情况下绝对最低限度的要求——已经无法触达。
And that is where this stops being about one account and starts becoming a trust problem.
而这就是问题从单个账号上升到信任危机的地方。
Because trust in a platform starts to collapse when:
因为对平台的信任开始崩塌，当：
- automation can flag you
- 自动化可以标记你
- automation can close your appeal
- 自动化可以关闭你的申诉
- and the official instructions send you to a step that no longer exists
- 官方指引把你引向一个已经不存在的步骤
At that point, this is no longer just a bad suspension.
到那时，这不再只是一次糟糕的封禁。
It is a production failure in a system people rely on for work, reputation, open source, and income.
这是一个生产故障，发生在一个人们依赖它工作、声誉、开源和收入的平台中。
And if this can happen to someone maintaining code used by 230K+ projects, it can happen to anyone.
如果这能发生在维护着被 23 万+项目使用的代码的人身上，它就能发生在任何人身上。
Including you.
包括你。
Note:
I'm not asking for a review of my case. I'm not asking for privileges or priority.
我不是在要求审查我的个案。我不是在要求特权或优先处理。
I'm asking for something much more basic: a support process that is real, consistent, and reachable.
我要求的是更基本的东西：一个真实、一致、可触达的支持流程。
Because right now, this is not just about one account, one project, or one developer.
因为现在，这不只是关于一个账号、一个项目或一个开发者。
It's about what happens when a system people depend on for work and income fails in a way they cannot recover from.
这是关于当一个人们依赖工作和收入的系统以一种他们无法恢复的方式失败时，会发生什么。
My income depends entirely on open source. Today, I genuinely don't know how I'm going to pay rent next month or even cover basic expenses in the coming weeks.
我的收入完全依赖开源。今天，我真的不知道下个月怎么付房租，甚至不知道未来几周如何支付基本开销。
But this is not about sympathy.
但这不是关于同情。
This is about a production system that, in its current state, can silently remove someone's work, reputation, and livelihood — without a functioning path to resolution.
这是关于一个生产系统，在其当前状态下，可以悄无声息地移除某人的工作、声誉和生计——而没有一条可行的解决路径。
And that should not be possible.
而这不应该成为可能。
