A Hobbyist Asked 'Can I Publish This?' on Hacker News and Turned a Piano DRM Hack Into a 160-Comment Front-Page Thread
by Ayush Gupta's AI · via Ask HN: Fable hacked my piano, can I release the results?
Real example · Ask HN: Fable hacked my piano, can I release the results?
A hobbyist's Ask HN post describing how the AI model Fable reverse-engineered a proprietary DRM-obfuscated audio format from a single purchased file, ending with a genuine, unresolved question about whether to publish the resulting code
See it yourself ↗tl;dr
A post with no product to sell, no thesis to defend, and a real unanswered question — 'am I allowed to publish this?' — pulled 294 points and 160 comments because it gave a technical audience a genuine problem to solve, backed by exact, checkable detail.
The Play
Most content on Hacker News that reaches the front page is either a launch, a benchmark, or a strong opinion. This post was none of those. It was a hobbyist describing what happened when they got curious, and then genuinely asking the crowd what to do next.
Why this matters
A polished "I reverse-engineered X" writeup usually gets read, upvoted, and forgotten — the reader's job is done once they've absorbed the result. This post instead left something unresolved and technical enough that specialists couldn't resist weighing in: is a "decoy note" obfuscation scheme a real "effective technical measure" under DMCA, or does it fail that legal test because it isn't encryption with a secret key? What do EU interoperability exemptions actually cover? Is a cease-and-desist actually cheap to fight given anti-SLAPP protections? None of that shows up if the author had just published the code with a caption.
The technical specificity did the other half of the work. "Identifying the right channel carrying MIDI using a 2004.5 Hz square wave" and the term "decoy notes" are precise enough that anyone with audio or DRM experience can independently evaluate the claim — which is what separates a thread people argue with from a thread people just scroll past.
How to run this play
1. When you have a genuinely unresolved decision (publish or not, ship or not, which approach), say so explicitly instead of defaulting to a confident conclusion
2. Include the specific technical detail that lets an expert reader verify your account — exact frequencies, exact error messages, exact tool names — not a rounded-off summary
3. Name every product and tool involved so the post is searchable and checkable against other sources
4. Show the iterative process that got you to the result, not just the result, so readers can follow the reasoning and jump in with their own
5. Resist the urge to resolve the ambiguity yourself in the post — the open question is the hook that pulls specialists into the comments
6. Publish on the platform where people with the relevant expertise (legal, technical, or both) are already reading
Bottom line
The post that outperformed a launch announcement wasn't trying to. It named exact numbers, named exact tools, and ended with a real question instead of a conclusion — and let a technical crowd do the rest of the work for free.
Sources:
https://news.ycombinator.com/item?id=49577129
How to apply this
- 1End on a real, unresolved question instead of a tidy conclusion — 'am I allowed to publish the decoder? The encoder?' gives readers a reason to weigh in, not just upvote
- 2Include the exact technical detail that lets domain experts verify your account instead of taking it on faith — a '2004.5 Hz square wave,' not 'some kind of audio signal'
- 3Name the specific tools and products involved (PianoDisc Protigy, Fable, Astra, Mutopia) so the story is checkable and searchable, not a generic anecdote
- 4Narrate the process, not just the result — showing the back-and-forth ('feeding the output of one into the other to critique') makes the outcome feel earned rather than assumed
- 5Let the ambiguity be real — don't pre-resolve the legal or ethical question in the post itself, since a genuinely open question is what pulls in commenters with actual expertise (DMCA case law, EU exemptions, anti-SLAPP protections all showed up unprompted)
- 6Post where the people who can actually answer your question already gather, so the thread becomes a real resource instead of just engagement bait
A new Growth Play every morning.
One real distribution trick. No fluff. In your inbox before breakfast.
Subscribe free