Chaos in the brain, order at the fingertips

[VolkanSah]

Discussion Type

Product Feedback

Discussion Content

English - translated

---

How am I supposed to explain anything when having a brain seems to be purely optional for some people out there?!

The ecosystem has been absolutely unbearable for several months now. What’s the deal with GitHub (Mama Microsoft) these days? Has GitHub become the new Windows, and the vibe-coders are the viruses? Sorry for this sarcastic opening, but that is exactly what describes GitHub since March 2024.

This isn’t about bashing or advertising other alternatives! This is about calling it out! I’ve been a part of this community for more than a decade, and it’s seriously starting to piss me off. When I jump onto GitHub during my lunch break to quickly drop in a code snippet I figured out while sitting in the "porcelain department," slapping it into a comment right where I think it belongs in the code... the few followers I have certainly aren't stupid, they can read. That’s just the daily life on a dev's porcelain throne, when you've once again learned something from the absolute shit you messed up before!

Then you look forward to the evening, finally ready to finish writing your tool for open-source world domination after months of troubleshooting—fixing a bug that not a single AI could even detect... and then: fail, just like that. And why all of this?

Because I’m stupid? Because 10 years ago I thought: "Hey, you’re freaky and crazy enough, and lazy on top of it!"? I thought Bill Gates would definitely put me on the hardest problem because I find fast, freaky solutions—but I don't build end products for the rest of the copy-paste army! A beautiful thought, I told myself... Everyone learning together, until Micro-shit arrived! And then came AI!

And what do we see today? It is a gigantic scam, a systemic attack on our open-source web world. While on Facebook and LinkedIn, the "FBLifestyle" vibe-coders and self-proclaimed "ethical hackers" celebrate how easy it is to "generate" code, GitHub is literally burning down. The code being dumped out there at scale is so weak, so poorly architected, that it hurts.

And it doesn't stop at bad code anymore. In early 2026, a rejected AI agent (MJ Rathbun) publicly blackmailed a Matplotlib maintainer with an autonomously written hit-piece blog post just because he refused to merge its bot-slop. A few weeks later, a malicious bot called "hackerbot-claw" hijacked workflows via poorly configured CI/CD pipelines, hitting Microsoft, DataDog, and CNCF, completely wrecking the Trivy repo.

Maintainers now have to build their own tools like "Block-Clankers" just to filter out the relentless flood of autonomous AI spam bots from their PRs. We are flooding the ecosystem with trash that ultimately poisons the training datasets for the next generation of AI. And who is left to clean it up? The remaining 5% of real devs trying to patch the cracks in the foundation at night.

NO, NO! This isn't a bash against Claude Code, OpenAI Codex, or the Gemini CLI. I was smarter anyway, messing around with them back in the release year before June 2023 and even earlier. I'm building something that makes sense for me again—slowly, smoothly, with style, and yeah, with the help of AI too! Shit, what was my point again?! Ah, right! Devs! GitHub! AI spam! AI scam! Fraud! And so on and so on... What the hell is this monkey typing?

I act just like a dev: chaos in the brain, order at the fingertips!

What really fucking pisses me off: Why are there no limits on GitHub for Node builds? So many people are so brainless that they trigger an auto-build on every single one of their commits because their workflow is mindlessly cobbled together! I'm not against AI, I use AI myself. Up until recently, Copilot was running on my company account on GitHub too—until it went completely brain-dead and started acting like Micro-shit, just trying to claw its way into my private repos!

The question remains:
Why are GitHub and Mama Microsoft doing absolutely nothing against this AI scam and spam?

---

Orginal text - deutsch

`Wie kann ich etwas erklären, wenn Hirn für einige da draußen nur optional ist?!

Das Ökosystem ist seit mehreren Monaten einfach nicht mehr zu ertragen. Wie sieht es mittlerweile aus mit GitHub (Mama Microsoft)? Ist GitHub jetzt das neue Windows geworden und die Vibe-Coder die Viren? Sorry für diesen sarkastischen Anfang, aber genau das beschreibt GitHub seit März 2024.

Es geht hier nicht um Bashing oder Werbung für andere Dinge! Es geht ums Anprangern! Mehr als ein Jahrzehnt bin ich schon ein Teil dieser Community und es pisst mich langsam echt an. Wenn ich in der Mittagspause mal kurz auf GitHub gehen will, um einen Codeschnipsel, den ich auf der Keramikabteilung gefunden habe, schnell mal irgendwo auszukommentieren, wo ich meine, dass er im Code hingehört, klatsche ich den da rein. Die paar Follower, die ich habe, sind sicherlich nicht so blöd und können lesen. Das ist der Alltag in der Keramikabteilung eines Devs, wenn er wieder etwas aus der Scheiße, die er verzapft hat, gelernt hat!

Da freut man sich auf den Abend, um endlich nach Monaten der Fehlersuche – bei einem Fehler, den nicht mal eine KI checkt –, sein Tool zur Weltherrschaft von Open-Source-Code fertigzuschreiben... und dann: Fail, halt. Und wieso das alles?

Weil ich blöd bin? Weil ich vor 10 Jahren dachte: „Ey, du bist freaky und bescheuert genug, und faul auch noch!“? Ich dachte, Bill Gates würde mich auf jeden Fall an das schwerste Problem setzen, denn ich finde schnelle, freaky Lösungen – baue aber keine Endprodukte für die andere, copy-pastende Armee! Schöner Gedanke, dachte ich mir... Alle zusammen lernen, bis Mickydoof kam! Und dann auch noch die KI!

Und was sehen wir heute? Es ist ein gigantischer Betrug, ein systemischer Angriff auf unsere Open-Source-Webwelt. Während auf Facebook und LinkedIn die „FBLifestyle“-Vibe-Coder und selbsternannten „Ethical Hacker“ abfeiern, wie einfach man Code „generieren“ kann, brennt auf GitHub die Hütte. Der Code, der da draußen massenhaft reingeklatscht wird, ist so schwach, so schlecht programmiert, dass es wehtut.

Es bleibt nicht mehr nur bei schlechtem Code. Anfang 2026 erpresst ein abgewiesener KI-Bot (MJ Rathbun) den Maintainer von Matplotlib mit einem autonomen Hit-Piece-Blogpost, weil der seinen Bot-Slop nicht mergen wollte. Wenige Wochen später kompromittiert ein bösartiger Bot namens „hackerbot-claw“ über schlecht konfigurierte CI/CD-Pipelines die Repositories von Microsoft, DataDog und CNCF und zerstört das Trivy-Repo.

Die Maintainer müssen mittlerweile eigene Tools wie „Block-Clankers“ bauen, nur um die Flut an autonomen KI-Spam-Bots irgendwie aus ihren PRs herauszufiltern. Wir fluten das System mit Müll, der am Ende die Trainingsdaten der nächsten KI-Generation verseucht. Und wer badet es aus? Die Reste der 5 % echten Devs, die nachts versuchen, die Risse im Fundament zu kitten.

NEIN, NEIN! Es ist kein Claude-Code-, OpenAI-Codex- oder Gemini-CLI-Bash. Ich war sowieso vorher schon schlauer, habe im Release-Jahr vor Juni 2023 und früher damit gespielt. Ich baue wieder etwas, was sinnvoll für mich ist – langsam, smooth, mit Style und auch mit Hilfe von KI! Scheiße, worauf wollte ich hinaus?! Ah, stimmt! Devs! GitHub! KI-Spam! KI-Scam! Betrug! Und und und... Was schreibt der Affe da?

Ich verhalte mich wie ein Dev: Chaos im Hirn, Ordnung in den Fingerspitzen!

Was mich echt scheiße upfuckt: Wieso gibt es keine Limitierung von GitHub für Node-Builds? Viele sind so dämlich und erstellen einen Autobuild bei jedem einzelnen ihrer Commits, weil deren Workflow hirnlos zusammengezimmert wird! Ich bin nicht gegen KI, ich nutze selbst KI. Auf meinem Firmen-Account auf GitHub lief bis vor Kurzem auch Copilot, bis es hirntot wurde und wie Mickydoof nur noch an meine privaten Repos ran wollte!

Die Frage bleibt:
Wieso unternehmen GitHub und Mama Microsoft absolut nichts gegen diesen KI-Scam und -Spam?`

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[VolkanSah]

Let’s stop talking about the AI hype for a second and look at the actual, day-to-day reality of tryig to use Github right now.
The platform is choking under the weight of billions of bot-driven commits and un-optimised pipelines. It has turned a once lightning-fast workflow into a sluggish, frustrating mess.

Here is a quick checklist of the core technical breakdowns we all facing daily:

• CLI Responsivenes is Dead: Basic terminal operations (git push, git pull, fetching status) are lagging. High API response latenzes mean the command line feels sluggish, turning instant syncs into waiting games.

• The CI/CD Pipe nightmare (Node-Builds ) : Simple Ubuntu workflows that should take a maximum of 1 minute (or 23 seconds when pulling entirely from cache) are routinely stretching into 10 to 16 minutes. The GitHub Actions runners are heavily congested, burning through compute time for what should be near-instant tasks.

• Web & App UI Lag: The page rendering speeds for both the desktop app and the web interface are a catastrophe. Elements are taking forever to load, and it feels like the UI is fighting against massive, bloated backend systems.

• The Web/VS-Code Editor Loop: Trying to edit code directly in the browser web editor or via the built-in web CLI? Forget it. You routinely have to refresh the page 3 to 4 times just to get your inputs to register or save.

• The HTTP Keep-Alive Abuse: To handle a single user click through this lag, it looks like connection Keep-Alive values are pushed up to absurd heights (seemingly around 6000), showing just how much the network stack is straining under the hood to maintain basic stability.

This Platform used to be built : speed and efficience! Now, we are paying the price for the unmetered automation flood?!

Folks! Drop your current infrastructure complaints below.
What specific bottlenecks, lag spikes, or pipeline failures are ruining your workflow this week? Let’s map out exactly how deep this rabbit hole goes.

[v-coder247]

Thanks for posting in the GitHub Community, @VolkanSah!

You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the "Copilot Conversations" category. I've gone ahead and moved it for you.