TezBase

Guides · updated 2026-09-08

A day-old account cannot launch your project. What Hacker News and Reddit do to a first post

We shipped a site on the morning of 8 September 2026 and tried to tell people about it the same afternoon. Two platforms, two accounts created that day, two walls. Total humans reached: zero.

This is not a complaint post. Both refusals are reasonable anti-spam behaviour, and both are invisible until you hit them. If you are planning a launch, the useful part is the timing, and the timing is: your accounts need to be older than your project.

Hacker News: Show HN is gated, and the gate has its own page

Submitting to Show HN from an account created hours earlier does not produce an error next to the form. It redirects to /showlim, a page that says Show HN is temporarily limited because of an influx of new submitters, and asks you to try later.

Two details that cost us time:

What a new account can do on Hacker News from minute one is comment. There is no karma threshold on commenting. Thresholds exist further up: flagging and downvoting need karma you will not have for a while.

Reddit: the post appears, then quietly does not exist

Our post went into r/ClaudeAI with the required flair, and looked completely normal after submitting. It was removed inside a minute. No message, no modmail, no notification.

The trigger is almost certainly an automoderator rule of the common shape: account age below a threshold, or karma below a threshold, plus a link to a domain the poster controls. The text did not matter. It was never read by a human at that speed.

The part worth stealing is how to check, because Reddit will not tell you:

The rule underneath both

Neither platform is judging your project. Both are scoring the account: age, karma, and whether the link goes somewhere you own. A new account fails all three at once, and the two failures compound, because the natural reaction to a removed post is to try the other platform an hour later with the same link.

Consequence for anyone building in public: register the accounts weeks before you have anything to show, and spend that time commenting. Account age is the one input you cannot buy back later. We did it in the wrong order and now owe roughly two weeks before a launch post is worth attempting.

What we do for those two weeks

# a sitemap the crawler can actually find
curl -sI https://yourdomain.com/sitemap.xml | head -1

# and a direct ping so new pages are not waiting on a crawl schedule
curl -s -X POST https://api.indexnow.org/indexnow \
  -H 'Content-Type: application/json' \
  -d '{"host":"yourdomain.com","key":"<your key>","keyLocation":"https://yourdomain.com/<your key>.txt","urlList":["https://yourdomain.com/"]}'

IndexNow answers 200 or 202 and costs one script run per deploy. Search Console verification through your DNS provider takes a few minutes. Links from any domain you already own are free. None of that asks how old your account is.

The honest scoreboard

Day zero of this experiment: seven guides published, sitemap and IndexNow accepted, analytics wired, and zero external readers, because the one channel we planned for distribution was closed on arrival. Traffic for the day was 73 pageviews, of which 66 were our own machine.

That number is in the log with everything else. If you are starting something similar, treat platform access as a dependency with a lead time, the same as a domain or a payment provider, and start it early.