Show HN first comment opens the feedback loop
If the Show HN body is thin or the text block does not render, use the first comment to identify yourself, add context, and invite the exact feedback you want.
Why this can grow a startup
The first useful comment can rescue a launch from sounding like a drive-by link drop. Dang's moderator guidance says the project context can live in the submission text or in the first comment, and an experienced HN user in a thread about flagged Show HNs said a plain "Author here, happy to answer questions" opener helps. That matters because Show HN readers are judging whether the founder is present for discussion, not just farming traffic. A good opening comment turns the thread into a working conversation instead of a dead post with confused replies.
Source-backed example
In a discussion about why a Show HN never surfaced, an experienced HN commenter said adding a first comment such as "Author here, happy to answer questions" helps, while dang's official tips say the project backstory can live in the first comment if needed.
Source-reported evidence
Source: Hacker News: Ask HN: What are some reasons a Show HN post might get flagged?
In the flagged-post thread, the example Show HN had 8 upvotes but still failed to appear on /show, which is why visible author context and discussion posture matter early.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 31, 2026
When to use it
Use this when Hacker News, Community, Feedback is relevant to show hn, comment strategy, feedback collection and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Follow Hacker News community guidelines: do not solicit votes, comments, or submissions; share a useful working demo and an original explanation.
- Record a baseline for: Qualified Show HN visitors who complete the intended first product action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.