What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Why build native code instead of doing everything in the browser with WebRTC.From this comment
- What throughput it reaches and how latency and jitter affect performance.From this comment
- Whether it works differently or better than an existing device file transfer tool.From this comment
- Whether the underlying library depends on relays and if users can run their own.From this comment
- What the phrase about file sharing for the physical world actually means.From this comment
What they doubted or pushed back on our summary
- The browser case is weak since peers usually still need a relay server.From this comment
- An existing synced folder already covers personal file sharing between devices.From this comment
- The contributor count looks inflated relative to stars, pull requests and issues.From this comment
- A similar tool from the same underlying library already exists.From this comment
What the maker answered our summary
8 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Browser support could be added, and the library is said to work there via relay.From this comment
- The other tool suits existing users of a managed network, while this needs no owner.From this comment
- WebRTC only works in narrow conditions, so a self-hostable relay is the safer choice.From this comment
- Discussions were turned on after a request from someone building something similar.From this comment
What a builder can take from it: Expect tough questions on browser support, relay dependence and prior art, and answer each plainly with what works and what does not. our reading
The title, taken apart our calculation
This post got 148 points; the median for all 1442 posts is 112. In Open source projects (328 posts) the median is 103 points and 38 comments.
When it was posted our calculation
Thursday at 04:00 UTC. Of 1,003 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 30 (3%) 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 Open source projects 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