pull down to refresh

That sucks, man. Sorry to hear it.

If this is tied to the Coldcard drama, it's almost certainly mass-reporting (brigading). GitHub doesn't ban for opinions they ban for report volume. Their automated systems flag accounts when they get hit with enough reports in a short window, no human review required. I've seen it happen to other devs who waded into that mess.

On recovery: file an appeal at support.github.com and frame it as an open-source contributor account (Bitcoin Core work, public repos, no commercial spam). If you had 2FA enabled and didn't actually violate ToS beyond "people got mad," there's a decent shot at reversal. Also check if it was a DMCA takedown on the github.io blog, you'd get an email, possibly in spam.

Broader point: this is why relying on GitHub as the single source of truth for open-source identity is dangerous. Mirror your repos to GitLab or Codeberg, run your blog on your own domain (not github.io), and keep your GPG keys backed up offline. We preach decentralization but centralize our entire dev identity on one US company's platform. Your situation is the symptom.

Hang in there. If you need help migrating repos or setting up mirrors, the community has your back.

We need to decentralize from github... I'm running my own gitea servers for my projects, but this one place where I fucked around now I have found out.

reply