Show HN no booster comments or vote rings
Do not import Product Hunt behavior into Show HN: keep friends, users, and teammates from posting booster comments or outside vote asks.
Why this can grow a startup
Hacker News readers are unusually sensitive to manipulated social proof. The Show HN guidelines say not to ask friends to upvote or comment, dang's tips warn that booster comments from friends or users get treated as spam, and a separate Ask HN thread notes that a post can have votes but still fail to surface when the pattern looks like low-quality outside support. That means the wrong launch brief can quietly hurt visibility even if the product itself belongs on HN. Better to send private context to a few thoughtful peers than to trigger a thread that feels campaigned into place.
Source guidance
Dang warns founders to make sure friends and users do not add promotional booster comments, and an HN commenter in a flagged-post thread said 8 upvotes without surfacing often looks like off-site friends voting and leaving.
Source-reported evidence
Source: Hacker News Show HN Guidelines
The guidelines explicitly ban asking friends to upvote or comment, and the flagged-post thread cites an example with 8 upvotes that still failed to reach /show.
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, Communities, Brand is relevant to show hn, community norms, launch hygiene 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.