Hacker News Show HN Launch Strategy for Enovari

2. Algorithm, Timing & Ranking Mechanics

The HN Ranking Algorithm

The core ranking formula (publicly documented by Paul Graham and refined over the years):

Score = (P - 1) / (T + 2)^G
Where:
  P = points (upvotes minus downvotes, minimum 1)
  T = time since submission in hours
  G = gravity factor (approximately 1.8)

Fact-check on the formula: This formula was originally published by Paul Graham in a 2009 essay and in the HN source code when it was partially open. The gravity constant of 1.8 is the commonly cited value and has been confirmed by multiple independent analyses (including a well-known 2013 analysis by Amir Salihefendic, founder of Todoist). However, HN's actual implementation has evolved since then:

> - The base formula is correct, but HN applies numerous additional modifiers on top of it that are not public.

- Penalties and boosts are applied multiplicatively, not additively. A flag penalty, for example, divides the effective score rather than subtracting from it.

- The (P - 1) term means the submitter's own upvote does not count. You start at score 1 but the ranking formula uses P - 1 = 0 for the numerator until you get your first external upvote.

- The (T + 2) base (rather than T + 1 or just T) ensures that new posts do not get an infinite score at T=0 and provides a short grace period.

- The gravity factor may be slightly different for different post types. There is indirect evidence that Show HN posts on the /show page use a slightly different gravity than the main page, though this is not confirmed.

- HN has added anti-gaming layers since the original formula was published, including velocity anomaly detection and account-trust weighting.

What this means in practice:

• A post needs rapid early upvotes to climb. The denominator grows fast.
• A post with 10 upvotes in the first hour will outrank a post with 20 upvotes that took 4 hours to get there.
• After about 12-18 hours, even popular posts slide off the front page.
• The gravity factor (G) can be adjusted per-post by moderators. Posts they want to promote get lower gravity (stay longer); posts they want to suppress get higher gravity.

Penalties That Affect Ranking

Flag penalty: If users flag your post, it gets a ranking penalty proportional to the number of flags. Enough flags and it drops off the front page entirely, even with high points.

Vote ring detection: HN uses sophisticated detection for coordinated voting. If accounts that do not normally interact all upvote the same post in a short window, the post gets penalized. This is why "share it in your Slack/Discord and ask people to upvote" backfires.

How vote ring detection actually works (inferred from moderator statements and observed behavior): HN tracks multiple signals: (1) IP address clustering -- multiple upvotes from the same IP range or VPN exit nodes, (2) temporal clustering -- a burst of upvotes in an unnaturally tight time window, (3) account behavior patterns -- accounts that never visit HN suddenly arriving to upvote one specific post, (4) social graph analysis -- accounts that only interact with each other's posts. The detection is not perfect, but false negatives are rare for obvious coordination. dang has stated that the detection system is "quite good" and that the consequences are applied automatically before moderators even see the post.

Overposting penalty: If you have submitted several things recently, your new submissions get a slight penalty.

New account penalty: Very new accounts have less voting power and their submissions start with a slight disadvantage.

Practical implication: If your HN account was created recently, your Show HN submission will start with a handicap. Create your account well in advance (ideally 3+ months before launch) and build some karma by commenting thoughtfully on other posts. An account with 50-100+ karma and a history of substantive comments will have its submissions treated more favorably by the algorithm than a brand-new account.

Controversy penalty/boost: Posts with many comments relative to upvotes (low points-to-comments ratio) may get a ranking boost because HN values discussion. However, posts where comments are overwhelmingly negative may get flag-killed.

The "flamewar detector": HN has an automated system that detects flamewars -- threads where comments are being posted rapidly, getting flagged, and generating more heat than light. When triggered, the post's ranking gets suppressed. This is separate from the flag penalty on the post itself. If your Show HN thread devolves into a heated argument (e.g., about AI ethics, privacy, or open-source licensing), the flamewar detector may suppress your post even if the post itself is good. This is another reason to keep your responses calm and technical.

Velocity Matters More Than Total

The most critical insight about HN's algorithm: velocity in the first 60 minutes determines everything.

• 5 upvotes in the first 30 minutes will get you onto page 1-2 of HN
• 10-15 upvotes in the first hour will get you into the top 10-15
• 30+ upvotes in the first hour is a strong hit that will sustain for hours
• If you get fewer than 3-4 upvotes in the first hour, the post is effectively dead

This is why timing matters enormously.

The "new page" window: When you first submit, your post appears on https://news.ycombinator.com/newest. It stays there for roughly 30-60 minutes depending on submission volume. During this window, HN regulars who browse /newest will see it. These are your critical early voters. If your title is compelling enough to earn clicks from /newest browsers, you have a fighting chance. If not, your post scrolls off /newest without ever reaching the front page. This is why the title is the single most important element of your launch.

Best Time to Post

The data-backed optimal window:

Data sources for timing claims: Multiple independent analyses have converged on this window. Key studies include:

- An analysis of ~1 million HN posts by social media scheduling tools (Buffer, later replicated by others) found that posts submitted between 7-9 AM ET on weekdays received the most average points.

- A 2020 analysis by HN user minimaxir (Max Woolf) analyzing submission timing vs. front-page probability confirmed Tuesday and Wednesday mornings as optimal.

- YC's own internal advice to portfolio companies reportedly recommends Tuesday/Wednesday morning ET launches.

- An important caveat: the optimal time depends on the audience for your specific product. For developer tools targeting a global audience (like Enovari), the 8-9 AM ET window catches US East Coast mornings and European afternoon simultaneously. For products targeting primarily European users, posting at 6-7 AM ET (11 AM - noon in London/Berlin) may be better.

Why these times work:

• HN's primary audience is US-based tech workers, with a strong secondary European contingent
• 8-9 AM ET is when US East Coast opens laptops. By 9 AM, West Coast is waking up too.
• The post needs to build momentum during the US workday (9 AM - 5 PM ET)
• Weekdays dramatically outperform weekends for developer tools
• Tuesday and Wednesday are the highest-traffic days on HN
• Avoid Friday (people check out early) and weekends (much lower traffic)

Times to AVOID:

• Weekends (50-70% less traffic)
• Friday afternoon ET (people mentally check out)
• Very early morning or late night ET (not enough eyeballs for initial velocity)
• Holidays, major tech conference days (competing for attention)
• Same day as a major Apple/Google/Microsoft announcement (you will be drowned out)
• The day of or after a major AI model release (e.g., a new GPT or Claude version) -- the front page will be dominated by discussion of the release and your Show HN will be buried
• YC Demo Day weeks -- a flood of YC company Show HNs will compete for the same attention
For Enovari specifically: Post on a Tuesday or Wednesday at 8:30 AM Eastern Time. This gives you the full US workday to build momentum. If you are in a different timezone, set an alarm. Check the day before that no major tech announcements are expected -- scan TechCrunch, The Verge, and X/Twitter for embargoed announcement hints.

---

5. Failure Case Studies & Common Mistakes

Common Reasons Show HN Posts Fail

5.1 The "Marketing Page" Post

What happens: Founder submits a link to a slick marketing page with "Book a demo" or "Join waitlist" buttons. No way to actually use the product.

Why it fails: HN users want to TRY the thing. A marketing page with no product behind it signals "this is an ad, not a Show HN." It gets flagged quickly.

Example pattern: Many YC companies make this mistake during launch week, submitting their polished landing page instead of a working demo or GitHub repo.

Specific example: In YC W23 and S23 demo days, multiple AI startups submitted Show HN posts linking to landing pages with "Request Access" or "Join Waitlist" buttons. These consistently underperformed relative to companies that had an open product. One commonly cited case: an AI coding assistant that launched with a waitlist despite having a working product -- it got flagged and received comments like "Can't try it, can't evaluate it, not a Show HN." When they relaunched weeks later with open access, the reception was dramatically better.

5.2 The "Ask HN for Upvotes" Post

What happens: Founder shares the HN link on Twitter/X, in their Discord, in Slack groups, and asks people to upvote.

Why it fails: HN detects coordinated voting with high accuracy. The post gets killed silently -- it just disappears from the rankings without any notification. The founder often does not even realize what happened.

How they detect it: Accounts that rarely visit HN suddenly upvoting, multiple upvotes from similar IP ranges, upvotes from accounts with no other recent activity, temporal clustering of votes.

Real consequence examples:

- A well-known developer tools company in 2023 shared their Show HN link in a company Slack of ~200 employees with "please upvote." The post had 50+ points within 30 minutes and then suddenly disappeared from the front page. It was penalized so severely it ended up below page 5 despite the high point count. The founder later posted about this experience, confirming the penalty.

- A crypto project coordinated upvotes through a Telegram group. The post was killed outright (marked [dead]) within an hour, and the submitter's account was flagged.

- The subtle version that also fails: Even "soft" asks like "I just posted on HN, would love your support" or tweeting the link with a wink emoji are risky. HN's detection does not require you to explicitly say "upvote" -- a burst of votes from accounts that all follow you on Twitter is enough.

> What you CAN do: Share the link as "I'm discussing my project on HN" (inviting reading and commenting, not voting). People who genuinely find it interesting will upvote organically. You can also tell friends "I'm on HN today" without linking to the specific post -- if they're HN users, they will find it on /show or /newest.

5.3 The "Defensive Founder" Post

What happens: The post gets initial traction but the founder responds to every criticism with defensiveness. "You clearly don't understand what we're building" or "That's not a valid concern."

Why it fails: Defensive responses get downvoted. Other commenters pile on. The thread becomes toxic. Moderators may intervene by adjusting the post's ranking down.

Example: Multiple AI startups in 2023-2024 had promising Show HN launches that turned sour when founders could not handle the "isn't this just a wrapper around GPT?" question gracefully.

Detailed anatomy of a defensive thread going wrong:

> A common pattern observed across multiple AI product launches:

1. Comment: "This looks like a nice UI but isn't it just calling the OpenAI API under the hood?"

2. Defensive response: "That's a simplistic view. We have proprietary technology and novel approaches that go way beyond a wrapper."

3. Follow-up: "OK, what novel approaches? Can you be specific?"

4. More defensive: "Our architecture is proprietary and I can't share details, but trust me it's much more sophisticated."

5. Pile-on begins: Other commenters start questioning the defensiveness itself. "If you can't explain what makes it different, that's a red flag."

6. Thread devolves: The discussion shifts from the product to the founder's behavior. Flags start accumulating.

> How the same exchange should have gone:

1. Comment: "This looks like a nice UI but isn't it just calling the OpenAI API under the hood?"

2. Good response: "Fair question. At its core, yes, we use LLM APIs -- most AI products do. The value we add is in [specific technical detail]: we do X preprocessing, Y postprocessing, and Z caching that makes the results [specific measurable improvement]. Here's a concrete example: [example]. Whether that's enough differentiation is a valid debate, but hopefully that gives you a clearer picture of what's happening beyond the API call."

> The key difference: acknowledging the premise, providing specific technical depth, and remaining open to the possibility that the criticism has merit.

5.4 The "Wrong Time" Post

What happens: Founder posts at 11 PM ET on a Friday, or during a major tech news day.

Why it fails: Not enough eyeballs for initial velocity. The post never gets the 5-10 upvotes in the first hour needed to reach the front page. Once it falls off /newest, it is dead.

Specific timing disasters observed:

- Product Hunt spillover timing: Some founders post on HN at the same time as their Product Hunt launch (midnight Pacific, which is 3 AM ET). This is terrible for HN -- there are almost no active users at 3 AM ET. By the time the US wakes up, the post has already fallen off /newest.

- Major announcement collision: An AI developer tool launched their Show HN on the same day OpenAI released GPT-4 Turbo. The entire front page was GPT-4 discussion. Their post got 8 points.

- Holiday launches: Several founders have reported launching on US holidays (thinking "less competition") only to find that traffic is so low they cannot get initial velocity. Less competition means nothing when there are 70% fewer eyeballs.

5.5 The "Too Vague" Post

What happens: Title like "Show HN: An AI tool for productivity" or "Show HN: My new SaaS product."

Why it fails: HN users scroll fast. Vague titles get zero clicks. There is no curiosity hook and no technical signal.

Before and after examples of vague vs. specific titles:

- Bad: "Show HN: An AI-powered developer tool" -- what does it DO?

- Good: "Show HN: Cursor -- An AI-first code editor that generates diffs"

- Bad: "Show HN: A better way to manage data" -- meaningless

- Good: "Show HN: DuckDB -- An embeddable analytical database"

- Bad: "Show HN: AI memory for your apps" -- too generic

- Good: "Show HN: Enovari -- Persistent, structured memory for AI assistants via MCP"

> The pattern: good titles name the product, state specifically what it does, and include at least one technical or domain-specific term that signals depth.

5.6 The "Wall of Text" Post

What happens: Show HN text post with 1000+ words covering the founder's life story, the company vision, the 5-year roadmap, and three paragraphs of disclaimers.

Why it fails: Nobody reads it. HN users scan. If they cannot understand what your product does within 10 seconds of reading, they move on.

The 10-second test: Before submitting, have someone who has never seen your product read the first two sentences of your post. If they cannot explain back to you what the product does, your opening is too vague, too long, or too indirect. Cut everything that does not serve the core message. Move backstory and technical details to the first comment.

5.7 The "No Technical Substance" Post

What happens: Product is a GUI over an API (e.g., a ChatGPT wrapper) with no novel technical decisions.

Why it fails: HN's audience is deeply technical. "We call the OpenAI API and display the results nicely" is not interesting to them. You need to demonstrate technical depth: your own models, novel architecture, interesting engineering challenges you solved, or a genuinely new approach to a problem.

The "wrapper" trap for AI products (directly relevant to Enovari):

> In 2023-2025, HN developed "wrapper fatigue" -- a collective skepticism toward any AI product that appeared to be a thin layer over an LLM API. This is the single biggest risk for AI product launches on HN. Products that survived this scrutiny did so by:

> 1. Showing the work that is NOT the API call. Cursor survived by demonstrating their diff model, context management, and editor integration. The LLM call is a small part of what makes Cursor work.

2. Having a novel architecture. Mem0 differentiated by explaining their memory management logic (what to remember, when to update, when to forget). The LLM is one component, not the whole product.

3. Open-sourcing enough to prove depth. When your code is visible, "it's just a wrapper" accusations can be disproven by pointing to the codebase.

> For Enovari: Your defense against "wrapper" accusations is strong: you are not wrapping an LLM API at all. You are building memory infrastructure that LLMs connect to via MCP. The LLM is the client, not the engine. Make this distinction crystal clear in your post.

5.8 The "Vanished Founder" Post

What happens: Founder posts and then disappears for hours. Comments asking questions go unanswered.

Why it fails: Engagement drives the algorithm. Posts with active comment threads get boosted. Posts with unanswered questions stagnate and die.

Quantified impact: Analysis of Show HN posts suggests that founder response rate is one of the strongest predictors of final point count, independent of the product quality itself. Posts where the founder responds to 80%+ of comments within 2 hours average 2-3x more points than posts where the founder responds to fewer than 30% of comments. The likely mechanism: each founder response is an opportunity for further discussion, which generates more comments, which generates more page views, which generates more upvotes.

5.9 The "Premature Optimization" Post

What happens: Founder spends weeks perfecting the HN post copy, A/B testing titles, coordinating a "launch team," and scheduling social media amplification -- but the product itself has bugs, slow load times, or incomplete features.

Why it fails: HN users will immediately try the product. If it is buggy, slow, or broken, the comments will reflect that. No amount of launch strategy can overcome a broken product. The comments "I signed up and got a 500 error" or "The page took 8 seconds to load" will dominate the thread.

Real-world example: A developer tools startup in 2024 coordinated a major Show HN launch with a PR push, influencer outreach, and a polished text post. The product's signup flow crashed under the HN traffic spike. The thread quickly became a discussion of the infrastructure failure rather than the product. By the time they fixed it (3 hours later), the thread had already fallen off the front page.

5.10 The "Open Source Bait" Post

What happens: Title prominently features "open source" but the actual repo is either (a) a thin SDK with the real logic behind a proprietary API, (b) licensed under a non-standard "open source" license that restricts commercial use, or (c) the code was pushed to GitHub an hour before the Show HN with minimal documentation.

Why it fails: HN users WILL check the GitHub repo. They will read the license. They will look at the commit history. If the "open source" claim feels misleading, the backlash is swift and severe. Comments like "This isn't really open source, the core is behind an API" or "The license says you can't use this commercially, that's not open source" will dominate.

Red Flags That Trigger Moderator Intervention

• Title editing by mods: HN moderators (dang) will rewrite titles that are clickbaity, hyperbolic, or misleading. If this happens, do not change it back.
• [flagged] tag appearing: Multiple user flags. Your post is being suppressed.
• [dead] status: Post has been killed, either by flags or by moderator action.
• Rapid drop in ranking despite high points: Usually means a penalty has been applied (vote ring detection or manual moderator adjustment).
• dang commenting on your post: If dang leaves a comment like "Please don't use Show HN for X" or similar, take it seriously and respond graciously. Do NOT argue with the moderator.

How to respond if dang comments on your post:

> If dang comments, it is almost always because something about your post or your behavior in the thread needs correction. The correct response is always:

1. Read the comment carefully. dang is precise with language.

2. Acknowledge immediately. "Thanks for the note, dang. I'll [specific action]."

3. Take the corrective action. If he says your title was changed, accept it. If he says your comment was too promotional, dial it back.

4. Never argue. Even if you think he is wrong. dang has stated that he is happy to discuss moderation decisions via email (hn@ycombinator.com) but not in public threads.

5. Consider it a signal, not a punishment. dang commenting on your Show HN means he is paying attention to it, which means it has traction. A moderator comment that you handle gracefully can actually boost your credibility in the community.

---

Appendix A: Key HN URLs

Appendix B: Tools for Preparation

Appendix C: HN Etiquette Quick Reference

• Do respond to every substantive comment
• Do concede valid criticisms gracefully
• Do share technical details freely
• Do fix bugs reported in the thread in real-time
• Do stay in the thread for 6-8 hours minimum
• Do respond with the same energy to the 50th comment as to the first
• Do save harsh feedback for later analysis -- it often contains the most useful insights
• Don't ask anyone to upvote your post
• Don't be defensive when criticized
• Don't use marketing language in comments
• Don't argue with the moderator (dang)
• Don't post during US holidays or weekends
• Don't submit a link to a landing page with no working product
• Don't create multiple accounts to vote or comment
• Don't repost if your first attempt fails -- wait at least a month
• Don't edit your post after submission to add "EDIT: thanks for the upvotes!"
• Don't reference your HN ranking in the thread ("We're #1 on HN!")
• Don't cross-post your HN link on social media asking for engagement within the first 6 hours

Appendix D: HN Comment Formatting Reference

HN uses its own formatting system, NOT Markdown:

Rank	Day	Time (ET)	Time (UTC)	Why
1	Tuesday	8:00-9:00 AM	12:00-13:00	Peak weekday activity, US East Coast morning
2	Wednesday	8:00-9:00 AM	12:00-13:00	Same pattern, slightly less competition
3	Monday	9:00-10:00 AM	13:00-14:00	Week-start energy, slight delay to avoid Monday rush
4	Thursday	8:00-9:00 AM	12:00-13:00	Good activity, less weekend drain
5	Tuesday	6:00-7:00 AM	10:00-11:00	Catches both EU afternoon and US morning
Resource	URL
Show HN guidelines	https://news.ycombinator.com/showhn.html
General HN guidelines	https://news.ycombinator.com/newsguidelines.html
HN FAQ	https://news.ycombinator.com/newsfaq.html
Current Show HN page	https://news.ycombinator.com/show
New submissions	https://news.ycombinator.com/newest
HN search (Algolia)	https://hn.algolia.com/
HN moderator (dang) profile	https://news.ycombinator.com/user?id=dang
HN Algolia API (for item lookup)	https://hn.algolia.com/api/v1/items/{id}
Contact HN moderators	hn@ycombinator.com
Tool	Purpose	URL
HN Algolia Search	Search past Show HN posts for similar products	https://hn.algolia.com/
HN Trending	See what is currently trending	https://hntrending.com/
Hacker News Rank	Track your post's ranking over time	https://hnrankings.info/
Pinboard Popular on HN	Historical popular posts	Various
HN Who's Hiring	Monthly hiring threads where you can gauge market interest	https://news.ycombinator.com (search "Who is hiring")
What You Want	How to Do It
Paragraphs	Blank line between paragraphs
Italics	text
Code/monospace	Indent with two or more spaces
Links	Just paste the URL -- it auto-links
Bold	Not supported. Use italics or ALL CAPS for individual words sparingly.
Headers	Not supported.
Bullet lists	Not natively supported. Use - or * at the start of lines (renders as plain text with the character).
Blockquotes	Not supported. Use > convention but it renders as plain text.

Important: Test your formatting by posting a comment and then deleting it (you have a short window to delete comments). Formatting that looks good in your text editor may break on HN.

---

Strategy document prepared for Enovari (https://enovari.ai) Show HN launch. Last updated: April 2026 Enhanced with fact-check corrections, expanded case studies, additional examples, failure analysis, and launch-day operations manual.