What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the slop detector's source code and method appear in the public repository.From this comment
- What exact test questions and labels the benchmark actually contains.From this comment
- How task distribution is managed so the benchmark does not favor tuned models.From this comment
- Whether models can be submitted and how entrants get added to the benchmark.From this comment
- Whether any small local models exist that can run through common tooling.From this comment
What they doubted or pushed back on our summary
- An existing similar benchmark shows different results and covers different model sets.From this comment
- A funded model matches a quick browser baseline yet costs more, raising suspicion of misleading claims.From this comment
- The site text reads like generated interface copy rather than human-written product writing.From this comment
- The comparison lineup omits an obvious classic zero-shot classifier baseline.From this comment
What the maker answered our summary
4 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The maker said the underlying code is openly available in a repository.From this comment
- The maker agreed the missing classic zero-shot baseline should be included in the next run.From this comment
- The maker asked entrants to file an issue with endpoint, license, and training disclosure, all run through one harness.From this comment
- The maker conceded coverage is limited to text decisions and said image and screen tasks are planned.From this comment
What a builder can take from it: Builders should expect tough scrutiny of baselines, cost claims, and task coverage, so publish methods openly and accept missing comparisons early. our reading
The title, taken apart our calculation
This post got 154 points; the median for all 1442 posts is 112.
When it was posted our calculation
Tuesday at 13:00 UTC. Of 3,788 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 112 (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 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