What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether crawl rate, media skipping and partial-site limits can be configured to reduce load.From this comment
- Whether it matches an existing all-in-one single-file archiver rather than duplicating it.From this comment
- Why a local server is needed when output is static, instead of opening files directly.From this comment
- How it handles client-side paywalls and whether browser extensions can be used.From this comment
- How it compares with an existing self-contained archive format for offline reading.From this comment
What they doubted or pushed back on our summary
- Launching the browser without its sandbox is a security risk and seems unnecessary.From this comment
- The README reads as machine-generated text, which raises doubts about the code too.From this comment
- Windows security software flagged a bundled component as potentially unwanted, blocking it.From this comment
- Mirroring a full site may place heavy load on the target server.From this comment
What the maker answered our summary
23 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The tool mirrors an entire site including subpages, unlike single-page savers.From this comment
- Rate and filtering requests were deferred to a tracked issue, since it was late locally.From this comment
- A single-file HTML mode was accepted as a good idea worth implementing.From this comment
- Plain static serving can be done with a simple built-in server instead.From this comment
What a builder can take from it: Assume users will compare your tool to existing options, ask about crawl politeness and security defaults, and judge your docs before your code. our reading
The title, taken apart our calculation
This post got 712 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
Sunday at 17:00 UTC. Of 3,019 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 109 (3.6%) reached 50 points; on Sundays it was 3.4% of 5,343. 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