What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether an API exists for agent workflows, usable in place of another search engine.From this comment
- Why evaluation demands a top-up or captcha, raising the barrier to trying it.From this comment
- Whether it runs its own index or only aggregates others, since that affects comparisons.From this comment
- Whether subscription payments can be made anonymously, for example with a privacy cryptocurrency.From this comment
- Which upstream sources power results, given concerns about certain providers.From this comment
What they doubted or pushed back on our summary
- The real need is European search indexes, not another aggregator that is easy to replicate.From this comment
- Weak results on recent news make it hard to justify paying and could hurt agent tasks.From this comment
- Payment methods are fully identifying, undermining the claim of strong privacy.From this comment
- The name resembles unfortunate alternatives and may put people off.From this comment
What the maker answered our summary
60 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- An API is offered with transparent rate limits and no search caps, documented in the FAQ.From this comment
- Evaluation needs either a one-month top-up or a brief proof-of-work captcha, chosen to deter bots.From this comment
- A small in-house index exists alongside partner indexes, and they hope to expand it eventually.From this comment
- Cash by mail is being pursued, but a suggested crypto payment processor did not respond to outreach.From this comment
What a builder can take from it: Builders should expect users to scrutinise data sources, payment anonymity, result freshness and onboarding friction, and answer each with specifics. our reading
The title, taken apart our calculation
This post got 236 points; the median for all 1442 posts is 112.
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 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