What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Does storing streams on object storage make write performance slow?From this comment
- Could a large chat application be built on this, and what would it cost?From this comment
- How does it compare with a similar open-source streaming project?From this comment
- Did the maker study other durable stream projects and their semantics?From this comment
- How does it handle rapid node scaling and cold-start recovery latency?From this comment
What they doubted or pushed back on our summary
- Write speed may suffer from using object storage as the backing store.From this comment
- Concern about latency and reliability with object-store-based data systems.From this comment
- It would be better if it could run fully serverless.From this comment
What the maker answered our summary
15 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Advises many small streams per user or device rather than one huge pipe.From this comment
- Streams can act as rooms, and ordered delivery suits chat-style applications.From this comment
- Stateless nodes bring it near serverless, but batching and caching benefits are lost.From this comment
- Works with any S3-compatible store, and fast zonal buckets cut durability latency.From this comment
What a builder can take from it: A builder can learn that clear docs and a single deployable binary lower adoption barriers, but the object-storage write-latency question must be answered head-on. our reading
The title, taken apart our calculation
This post got 159 points; the median for all 1442 posts is 112.
When it was posted our calculation
Monday at 16:00 UTC. Of 3,565 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 146 (4.1%) reached 50 points; on Mondays it was 3.1% of 7,396. 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