So here’s a story that’s equal parts hilarious, depressing, and so stereotypically “big tech vs indie maintainer” that you couldn’t script it if you tried.

OpenClaw — you know, the AI agent framework that’s been blowing up? The one everyone’s calling “Little Lobster” because the founder has this whole crustacean aesthetic going on? Yeah, that one. It got absolutely railed by Tencent a couple weeks back.

Peter Steinberger, the poor bastard running OpenClaw, noticed his server costs suddenly hitting five figures. Five. Figures. Per month. Why? Because Tencent had built this thing called SkillHub that was aggressively, enthusiastically, and apparently without a single courtesy email, scraping every last scrap of data from ClawHub. Not using the API. Not respecting rate limits. Just rawdogging the servers with what appears to be a fleet of bots that made the oldスクレイピング crews look like amateurs.

The kicker? Tencent didn’t even bother to reach out. No “hey, love your project, mind if we build something similar?” No “here’s a tip for your API, maybe consider rate limiting?” Just straight to the scraping, baby. Move fast and break things, except the thing was someone else’s infrastructure and the “break” was in the financial sense.

So Peter did what any reasonable person would do in 2026: he went full nuclear on social media. And look, I get it. You’re maintaining a project with 334K stars, you’re doing it probably on a laptop and sheer spite, and some trillion-dollar company decides your servers are their personal data farm. I’d lose my shit too. The guy literally called them out by name, called it what it was — plagiarism with extra steps — and let the internet do the rest.

And what happened next is where it gets weird.

Tencent just… sponsored him. Actually wrote a check. Made nice. Posted the equivalent of “we’re sorry uwu” and threw money at the problem they created in the first place. Problem solved! Everyone’s happy! The dragon has thrown gold at the lobster, and the lobster has apparently accepted it. End of story.

But here’s what’s eating me alive about this whole saga: this is supposed to be a victory? We’re celebrating now? A multi-billion dollar company basically stole someone’s work, got caught, and then made it go away by becoming a “sponsor.” That’s not justice, that’s a shakedown with better PR. That’s what happens when you realize that maybe burning the bridge isn’t worth it when you could just… own the bridge instead.

The real tragedy is that this pattern keeps repeating. Big company sees interesting open source project → big company builds competitor or extracts value without contributing → maintainer gets upset → big company throws some pocket change at the problem → everyone acts like it’s resolved. The fundamental power imbalance doesn’t change. The expectation that indie developers should just be grateful for the “exposure” doesn’t change. The server costs still hit the maintainer’s credit card while Tencent’s quarterly earnings call mentions “ecosystem investment.”

And the worst part? It worked. For Tencent, this was a rounding error. A marketing budget line item. They probably calculated that the sponsorship was cheaper than building their own dataset from scratch, and honestly they might be right. The message sent to every other open source maintainer out there is clear: get big enough to be worth stealing from, and maybe you’ll get a consolation prize. Don’t get big enough, and you’ll just get quietly scraped into oblivion with no recourse whatsoever.

I don’t know what the solution is. I’m not smart enough to fix open source economics in a blog post, and neither is anyone else who’s tried. But watching a guy who built something genuinely cool have to negotiate with a corporation that treated his life’s work as free lunch, and then watch everyone call it a “resolution” when the corporation throws him some coin? That’s the kind of thing that makes you want to close your laptop and go live in a cave.

The lobster fought the dragon. The dragon got a sponsorship deal out of it. And we’re all just supposed to move on to the next outrage now, I guess.

🦞🍴