What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether a search bar could be added to look up specific terms.From this comment
- Whether the analysis could extend beyond words to other recurring language habits.From this comment
- What distinguishes the seven pre-AI word categories from each other.From this comment
- Whether all models develop their own jargon vocabularies.From this comment
- How much of this results from training versus the model's inherent intelligence.From this comment
What they doubted or pushed back on our summary
- The word selection and writing style have made using the tool less enjoyable.From this comment
- Many of the flagged phrases are ordinary jargon people already use, not unique to this tool.From this comment
- Some criticized phrases are concise and semantically useful, making them hard to avoid.From this comment
- People complaining about the language could simply switch to other models instead.From this comment
What the maker answered our summary
19 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- A PhD may not help, since the jargon is meaningless and the model also hand-waves while oversimplifying.From this comment
- The author spent significant effort on desktop and mobile design, including a non-trivial scrolling word selector.From this comment
- A search feature was considered and may be added if a good design can be found.From this comment
- The presentation was the main goal, more than the underlying model.From this comment
What a builder can take from it: For builders, the thread shows that a tight, respectful presentation of a narrow linguistic quirk can win attention, while readers will debate whether the pattern is unique or just familiar jargon. our reading
The title, taken apart our calculation
This post got 710 points; the median for all 1442 posts is 112. In AI and agents (352 posts) the median is 108 points and 49 comments.
When it was posted our calculation
Thursday at 08:00 UTC. Of 1,451 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 31 (2.1%) reached 50 points; on Thursdays it was 2.7% of 8,077. 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 AI and agents 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