What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Could the browser and server examples include a small visual, like device and server icons on opposite sides?From this comment
- Could it explain how images, stylesheets and scripts load from the HTML so people see why pages break?From this comment
- What are the next steps, and will the reflow process get more detail?From this comment
- Should the DNS section be updated for newer record types that may let browsers skip TCP?From this comment
- Could URL parsing cover schemes other than http and https, which browsers still treat specially?From this comment
What they doubted or pushed back on our summary
- On narrow windows the contents panel overlaps the page content, which distracts readers.From this comment
- Over half the page covers network requests, while most browser complexity sits in parsing and rendering.From this comment
- The guide wrongly says browsers turn a bare string into a domain, but they only do so with valid TLDs.From this comment
- It only covers Chrome and Safari and ignores separate search and address bars.From this comment
What the maker answered our summary
6 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- More detailed sections are planned, but feedback was gathered first; the visual suggestion is under consideration.From this comment
- Resource-loading blocks may be added, though the maker worried about making the guide too complicated.From this comment
- Rendering will be covered in more depth; the maker published early to collect feedback on where to expand.From this comment
- The maker accepted that the domain-transformation claim needs fixing.From this comment
What a builder can take from it: Publishing an intentionally simplified guide invites precise corrections and reveals which sections readers most want expanded. our reading
The title, taken apart our calculation
This post got 302 points; the median for all 1442 posts is 112.
When it was posted our calculation
Sunday 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 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 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