Original Summary

In January, Hytale launched in alpha. The owner said: “We officialy support mod” and “As long as the code isnt obfuscated you can decompile it.”<p>Those were his words.<p>I was on the official Discord, among thousands of players wanting to create servers and mods. Everyone wanted to move fast.<p>I saw an opportunity. A huge wave I could surf.<p>So I decompiled the server JAR and started creating comprehensive modding documentation.<p>Three sleepless nights. Two more days. Twenty coffees. My reverse-engineering skills, boosted by AI, working overtime.<p>Finally, it was ready. I published it on GitHub and shared it with the community. Developers thanked me. Two people joined the project.<p>Then I woke up on Sunday morning.<p>Account suspended.<p>Both collaborators? Suspended too.<p>GitHub said my account had been suspended for violating the rules. No specific rule. No explanation.<p>I’m an introspective person. I can connect the dots. All three collaborators suspended after working on the same documentation project—we know what triggered this.<p>What GitHub has never explained is WHY that work warranted suspending our entire accounts.<p>The game’s owner explicitly said we could decompile unobfuscated code. If GitHub had a concern about permission, why not contact the studio? Why were other documentation efforts still available while ours resulted in three account suspensions?<p>The repository was hosted under a separate organization. Our personal accounts were attached to it. But if one organization or repository was the problem, why block three entire accounts, including unrelated projects?<p>We also wondered whether a competitor had reported us. That remains speculation. I don’t know whether the suspensions were automated. But when nobody explains the decision, you’re left guessing.<p>And before anyone tells me to contact support: I HAVE.<p>I followed GitHub’s official appeal process. I sent appeals and emails. I even emailed the game’s official studio asking for help.<p>Neither side answered.<p>From January through September, I waited. It’s October now. Still no account. Still no way to retrieve all my repositories.<p>Since that day, I host a fucking Gitea instance on a private VPS. I no longer trust cloud platforms with so many customers that your life, your life’s work, and your history stop mattering—unless you’re Elon Musk.<p>I have local clones of some repositories. Not all of them.<p>But the loss goes beyond source code.<p>My GitHub account was a witness to years of my life as a developer. Projects, commits, dates, experiments. Thousands of hours of work, long before ChatGPT and the current wave of vibe coding.<p>Today, people can look at what you build and casually dismiss it with “AI did that.”<p>My history was right there. Years of commits showing that I was already building things before any of this existed. That history could speak for itself.<p>Now I’m supposed to start over, looking like just another account created during the AI boom?<p>“Create a new account” doesn’t restore a professional history.<p>And the worst part is the data retention. As far as I can tell, my account still exists. The work is still there. I just can’t access it or extract it.<p>It feels like they’re holding a part of my life hostage.<p>We’re encouraged to publish, push our work to the cloud, and trust it to survive a dead computer. Then the platform suspends your account, locks you out of unrelated work, and leaves you waiting for nine months after you follow its own appeal process.<p>How is this acceptable?<p>If there was a problem with the documentation, identify it. Explain the rule. Answer the appeal.<p>But what possible justification is there for keeping years of unrelated repositories inaccessible?<p>I’ve already spent nine months trying the official channels.<p>I want my work back.<p>P.S. I’m not giving my name. If they care about their customers, they’ll find me. Or not…

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Hacker News 新项目
  • 发布时间：2026/10/2 12:22:57