GitHub can f..k you and you are forced to love it. or live with it...

Back to stories Open in a window
Article news.ycombinator.com

GitHub can f..k you and you are forced to love it. or live with it...

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.”

Those were his words.

I was on the official Discord, among thousands of players wanting to create servers and mods. Everyone wanted to move fast.

I saw an opportunity. A huge wave I could surf.

So I decompiled the server JAR and started creating comprehensive modding documentation.

Three sleepless nights. Two more days. Twenty coffees. My reverse-engineering skills, boosted by AI, working overtime.

Finally, it was ready. I published it on GitHub and shared it with the community. Developers thanked me. Two people joined the project.

Then I woke up on Sunday morning.

Account suspended.

Both collaborators? Suspended too.

GitHub said my account had been suspended for violating the rules. No specific rule. No explanation.

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.

What GitHub has never explained is WHY that work warranted suspending our entire accounts.

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?

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?

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.

And before anyone tells me to contact support: I HAVE.

I followed GitHub’s official appeal process. I sent appeals and emails. I even emailed the game’s official studio asking for help.

Neither side answered.

From January through September, I waited. It’s October now. Still no account. Still no way to retrieve all my repositories.

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.

I have local clones of some repositories. Not all of them.

But the loss goes beyond source code.

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.

Today, people can look at what you build and casually dismiss it with “AI did that.”

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.

Now I’m supposed to start over, looking like just another account created during the AI boom?

“Create a new account” doesn’t restore a professional history.

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.

It feels like they’re holding a part of my life hostage.

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.

How is this acceptable?

If there was a problem with the documentation, identify it. Explain the rule. Answer the appeal.

But what possible justification is there for keeping years of unrelated repositories inaccessible?

I’ve already spent nine months trying the official channels.

I want my work back.

P.S. I’m not giving my name. If they care about their customers, they’ll find me. Or not…

Discussion 1 comments · 6 points · anonymous_frust · 2h
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. The list is kept in this browser only.

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
]
Read the next story in the same article-reader applet. Back returns to the previous story.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or a story row's Open in new reader window button to compare articles. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.