Submit to Hacker News Wed 2026-06-03 ~7am Pacific and monitor thread for 6 hours

[justin808]

Context

The launch event. Submit the chosen HN post draft at the chosen submission window. Monitor the thread for the first 6 hours: respond to questions, fix obvious doc gaps, answer "why not Inertia" substantively.

Acceptance criteria

• Submission time: Wed 2026-06-03, between 6:30am and 7:30am Pacific (peak HN front-page-curation window)
• Submitter logged in with the chosen account (per HN draft issue)
• Title + URL + (if Show HN) body posted exactly as approved
• First author comment within 10 minutes of submission — substantive, not promotional ("One thing worth flagging: X" or "Question I expect: Y — here's why")
• Justin + at least one backup on-thread for 6+ hours; respond to questions in <30 min
• Track key metrics (manually): rank at 1h / 3h / 6h, comment count, demo URL traffic, repo stars delta
• If a question reveals a doc gap, fix it in a follow-up PR within the launch window (visibly maintained = high signal)
• If a question reveals a bug, decide: fix-and-comment, acknowledge-defer, or "you're right, here's the issue I just filed"
• Post-launch (next day): write a short retro comment in this issue with what worked, what didn't, follow-up actions

Files likely touched

• Possibly some same-day doc fixes
• This issue's comments — keep a running log of the day's metrics

Notes / gotchas

• DO NOT ask friends to upvote. HN detects coordinated voting. Penalty is being de-ranked permanently. Worse than not launching.
• If the post stalls (no front page traction in 3 hours): post mortem, NOT a resubmit. Resubmits look desperate. Pick a follow-up angle for a future launch.
• If the post takes off: do NOT get into argument with critics. "Good point, here's the tradeoff" works. "You're wrong, here's why" doesn't.
• Have docs/02-vs-inertia.md open in a tab the entire time
• Have the rendering-mode drawer screenshot ready to paste into the thread if discussion goes deep on the surface split

Wave + dependencies

• Wave: 4
• Owner mode: single-owner (one submitter, one author voice in the thread)
• Blocked by: rehearsal outcome, HN post draft, all Wave 1+2+3 work
• Blocks: nothing — this is the terminal issue

---

Part of the 2026-06-03 HN launch — see internal/planning/3357-react-on-rails-starter-launch.md. This is launch day.

[justin808]

Submission readiness update (2026-05-31 UTC)

Technical launch blockers are cleared from my side:

• Rspack is the default for local and deployed asset builds.
• /rsc-showcase is the public RSC centerpiece and returns HTTP 200 on the live demo.
• Main CI and staging deploy are green for ac3d897.
• The public landing copy now matches the current Rspack/RSCRoute implementation.

This issue should still stay open because the remaining blockers are launch operations:

• Schedule and run 30-min outside-eval rehearsal (Day 6, Tue 2026-06-02) #38 must run the outside-eval rehearsal before the submit/no-submit decision.
• Draft HN post (4 angle options — RSC lead recommended) and pick by end of Day 6 #40 needs the final title/body decision. I recommend the updated Option A centered on /rsc-showcase.
• The submitter account, launch owner, backup responder, and 6-hour monitoring coverage still need to be confirmed.

Before posting on Wednesday 2026-06-03, rerun a short live checklist: home page 200, /rsc-showcase 200, /dashboard login works with demo@example.com / password, browser console clean on the main surfaces, and docs links return 200.