What bug reports means
Finding problems with your product reported in public — in a thread, an issue on someone else’s repository, or a complaint that never became a support ticket.
Hacker News · Bug reports
Monitor Hacker News for bug reports
The outage thread and the "is anyone else seeing this" comment — low volume, and the most expensive to miss.
[01] THE JOB/ BUG REPORTS
What it looks like on Hacker News
Hacker News does not produce many bug reports and the ones it produces are the worst kind: public, technical, well-argued and read by everyone in your industry at once. The characteristic shape is a comment under an unrelated thread — "we hit this with X too, it silently drops writes above N" — from someone credible, which then becomes the top reply. The second shape is the incident thread, where your outage is the submission. Both are cases where a fast, honest, technical response from someone who actually knows is worth a great deal, and a slow or evasive one is remembered for years.
What Hacker News will not give you
HN moves fast and is hostile to marketing. A thread is effectively closed within hours, and a promotional reply does more damage than silence. This is the platform where the speed of the alert and the tone of the draft both matter most.
What FishOut collects from Hacker News
Stories and comments, including Ask HN and Show HN.
[02] WHAT TO TRACK/ KEYWORDS
Keyword shapes for bug reports on Hacker News
A keyword tuned for this job on another platform is usually silent here, because the same person writes differently in each place. The example beneath is read the way FishOut reads one: a relevance bar and the label it would carry.
keywords · hacker-news
your product name plus failure language
"broke", "silently", "data loss", "regression". Narrow enough to be manageable and precise enough to catch the comments that matter.
your name in any thread
Volume on Hacker News is low enough that a bare product-name keyword is viable, and this is the platform where a missed mention is most expensive.
your error strings
As on GitHub, and for the same reason — a pasted stack trace is a bug report from someone who did not file one.
Hacker News92
We hit this with AcmeMail too — above roughly 40 messages in a thread it silently drops the oldest rather than paginating. Took us a week to spot.
Has a problem[03] HOW TO SET IT UP/ VIEWS & ROUTING
The configuration that works here
A relevance floor of 60 on a channel with notifications on, routed to engineering rather than to marketing, and escalating rather than drafting. This is the cell where response latency has the highest reputational value in either direction: an engineer replying within the hour with a real answer is worth more than any campaign, and silence under a credible technical criticism is read as confirmation.
And what to do with what arrives
To engineering, with no reply drafted. Write an agent: when a brand post is labelled Has a problem or Complaint, or a label you describe such as "Bug report", assign it to an engineer and send it to a webhook — a tracker, not a brand-voice answer.
[04] THE COMMON MISTAKE/ AVOID THIS
Letting marketing answer
A credible technical criticism answered in a brand voice is worse than one left alone, and Hacker News comments are permanent and heavily read. The response that works is a specific, honest reply from an engineer who actually knows the system, posted quickly. Routing this cell to the same place as everything else is how you get the wrong response from the wrong person.
Questions
Run it from your assistant: Public bug reports to issues.
Other jobs on Hacker News
GitHub
Reddit
Bluesky24 of a possible 40. A job and a platform only make a page when the intersection has something true of it alone.