# HN posting-hour test before front-page hope

> Choose the Hacker News posting window deliberately because timing can change the GitHub proof a launch earns.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/hn-posting-hour-test-before-front-page-hope/
- Source: [arxiv.org](https://arxiv.org/abs/2511.04453)
- GrowthDex source hub: [arXiv: Launch-Day Diffusion: Tracking Hacker News Impact on GitHub Stars for AI Tools](/sources/arxiv-launch-day-diffusion-tracking-hacker-news-impact-on-github-stars-f/)
- Last checked: 2026-06-10T06:39:08.000Z
- Rarity: rare
- Budget: free
- Channels: Hacker News, Launch, Developer Marketing
- Stages: posting time, launch timing, developer audience, reply window, GitHub proof


## Why this can grow

Founders often treat HN timing like superstition. The diffusion study gives a better reason to care. Its models found posting timing was a key factor, with optimal hours able to mean hundreds of additional stars. The lesson is not to chase a magic minute. It is to pick a window where the relevant technical audience is awake, the founder can reply quickly, the repo is stable, and the team can watch issues, stars, forks, and docs questions together. A good posting hour does not rescue a weak product, but a bad one can waste a rare room full of qualified technical readers.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where hn posting-hour test before front-page hope can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Hacker News and Launch channel.
3. Use the evidence from arxiv.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

The Launch-Day Diffusion study says posting timing appeared as a key factor and that optimal hours could mean hundreds of additional stars for AI and LLM repository launches.

## Adjacent tactics in the same lane

- [HN star-window ledger before launch retrospective](/growth-ideas/hn-star-window-ledger-before-launch-retrospective/) - same source, 2 shared channels
- [HN Show label after substance, not before](/growth-ideas/hn-show-label-after-substance-not-before/) - same source, 2 shared channels
- [HN public API launch tracker before vanity summary](/growth-ideas/hn-public-api-launch-tracker-before-vanity-summary/) - same source, 1 shared channel
- [Show HN runnable surface before announcement page](/growth-ideas/show-hn-runnable-surface-before-announcement-page/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) - Hacker News, GitHub, developer marketing

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.