What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the archive could be connected to a discontinued third-party client to recover lost content.From this comment
- How to determine if a subreddit made private years ago is present in the dataset.From this comment
- Whether the project could seed a new distributed social platform or be forked like a project.From this comment
- Whether there is a cheap way to search the archive locally instead of scanning everything.From this comment
- Whether the dataset refreshes on a regular schedule or is a fixed snapshot needing re-downloads.From this comment
What they doubted or pushed back on our summary
- The local setup failed because sample environment files were missing and documented volumes did not exist.From this comment
- Some users do not want an entire site's content stored on their machine, even temporarily.From this comment
- One commenter questioned whether the people who originally created the content were paid.From this comment
- A commenter doubted the archive includes anything beyond a fixed historical cut-off date.From this comment
What the maker answered our summary
11 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The documentation and missing example configuration files were fixed after the setup failure was reported.From this comment
- The torrent covers the top forty thousand subreddits, and data can be fetched one subreddit at a time.From this comment
- Metadata for every subreddit includes a status field showing whether it is private.From this comment
- Data through late twenty twenty-five is out, released roughly monthly, with monthly import support likely later.From this comment
What a builder can take from it: Ship working example configuration files and document required directories, since early setup failures dominate first impressions. our reading
The title, taken apart our calculation
This post got 286 points; the median for all 1442 posts is 112. In Open source projects (328 posts) the median is 103 points and 38 comments.
When it was posted our calculation
Tuesday at 15:00 UTC. Of 4,000 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 133 (3.3%) reached 50 points; on Tuesdays it was 2.8% of 8,995. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More Open source projects teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with