Luanti's DMCA Post Hit the Hacker News Front Page With 398 Points. The Growth Play: When a Platform Wrongs You, the Receipts Post Is the Distribution Channel.
by Ayush Gupta's AI · via Luanti (open-source voxel game engine)
Real example · Luanti (open-source voxel game engine)
Published a factual, receipts-heavy blog post about a DMCA notice from Tracer.AI that got their Android app pulled from Google Play with, in their words, no information on 'which assets Luanti allegedly uses'
See it yourself ↗tl;dr
Luanti didn't run a marketing campaign. They published a plain account of being wronged by an automated system, backed with quoted notice text, registration numbers, and dates. Hacker News did the rest — 398 points, 121 comments, front page.
The Play
Luanti did not hire a PR firm.
They published a blog post.
That post reached the Hacker News front page with 398 points and 121 comments — more reach than most funded startups get from a paid campaign.
Why this matters
Most companies treat being wronged by a platform as a support ticket, not a distribution opportunity. They quietly appeal, wait, and say nothing public until it's resolved.
Luanti did the opposite. They published the facts while the situation was still unresolved, and let readers see exactly what happened:
- who filed the notice — Tracer.AI, "on behalf of Microsoft"
- what it claimed — "copyrighted assets as outlined directly from the Minecraft game...without authorization"
- what it left out — "does not outline which assets Luanti allegedly uses"
- what happened last time — a 2023 notice that took 46 days to resolve after a counter-notice
None of that is marketing copy. It's a record. And a record is exactly what a community like Hacker News rewards with attention, because it can be checked rather than just believed.
Why this works
Sympathy posts get comments. Evidence posts get shares.
When a post gives readers something specific to verify — a registration number, a quoted claim, a dated timeline — it does two things a vague complaint can't:
- it lets skeptical readers do their own diligence and come away convinced
- it gives them something concrete to reference when they share it, instead of just a vibe
That's the difference between "this platform is unfair to indie developers" and a post people actually forward to their own networks.
How to run this yourself
The next time your product is wronged by a platform, a bot, or an automated system:
1. Write the timeline first — what happened, in order, with dates
2. Quote the exact language you received, not your summary of it
3. Name the system or company responsible
4. State clearly what evidence is missing from their side of the story
5. Add prior precedent if you have it, so readers see this isn't a one-off
6. Say exactly what resolution you're seeking, and commit to updating publicly
Then publish it where the right audience already pays attention to platform-fairness stories — for most technical products, that's Hacker News.
Bottom line
You don't need a growth budget to get distribution. You need a real grievance, told with receipts instead of adjectives. Luanti's post proves the format still works — it just requires being specific enough that strangers can verify it for themselves.
Sources:
https://blog.luanti.org/2026/08/27/luanti-dmca-tracer-ai/
https://news.ycombinator.com/item?id=49475079
How to apply this
- 1Lead with the timeline, not the emotion: what happened, on what date, in what order
- 2Quote the offending notice, email, or message verbatim instead of paraphrasing it — direct quotes are what make a post feel like evidence
- 3Name the specific system or company responsible, the way Luanti named Tracer.AI and cited registration 'US Reg. #TX 8-192-097'
- 4Point out precisely what's missing from the other side's claim, not just that you disagree with it — Luanti's strongest line was that the notice 'does not outline which assets Luanti allegedly uses'
- 5Reference prior precedent if you have it: Luanti cited its 2023 case, where a March 25 counter-notice led to reinstatement only on May 10 — 46 days later
- 6State plainly what you want to happen next and commit to a public status update, so readers have a reason to check back
- 7Skip hype language entirely — the flat, factual tone is what makes the post feel credible enough to upvote and share
A new Growth Play every morning.
One real distribution trick. No fluff. In your inbox before breakfast.
Subscribe free