What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Why aren't the standard example prompts precomputed and saved instead of regenerated each time?From this comment
- Can the system handle a much bigger dataset than the small fraction currently released?From this comment
- Could conversations be shared and archived, perhaps using readable query links rather than random IDs?From this comment
- Is this just documents loaded into a retrieval database in front of a model?From this comment
- Could the system help audit which redactions were improper or determine what is missing?From this comment
What they doubted or pushed back on our summary
- Commenters warned that answers could be confidently wrong or fabricated given the material.From this comment
- Several noted only a tiny sliver of files has been released and many are redacted.From this comment
- A tester said a search for a lesser-known but connected person missed documents that simple keyword search found.From this comment
- Some said the real problem is prosecution and hard power, not building better analysis tools.From this comment
What the maker answered our summary
11 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The maker admitted forgetting the caching idea, calling it a quick fun project built in a few hours.From this comment
- The maker agreed the tool covers only all publicly available files, not the complete set.From this comment
- The maker welcomed the readable-link sharing idea and said new files would be added promptly.From this comment
- The maker explained coverage gaps caused by weak embeddings for lesser-known names and a keyword search shortfall.From this comment
What a builder can take from it: A builder should state dataset limits up front, precompute obvious example queries, and blend semantic search with keyword matching for obscure names. our reading
The title, taken apart our calculation
This post got 211 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
Wednesday at 01:00 UTC. Of 1,043 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 24 (2.3%) reached 50 points; on Wednesdays it was 2.6% of 8,118. 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