What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the tool handles music vocals, not just speech, for local audio fine-tuning.From this comment
- Whether 64GB versus 96GB memory meaningfully changes fine-tuning behavior or just delays running out.From this comment
- Whether fine-tuning truly needs 15,000 hours of audio data to work well.From this comment
- Whether the accent and language adaptation feature is for text-to-speech work.From this comment
What they doubted or pushed back on our summary
- Running large speech models locally already strains memory on long audio, so fine-tuning seems harder still.From this comment
- A favored speech alternative came later and cannot be fine-tuned on this hardware.From this comment
- An app was criticized for limiting access to system intents and requiring custom plugins for added capabilities.From this comment
- Some model file formats carry serious security risks, so people should prefer safer formats and verify checksums.From this comment
What the maker answered our summary
9 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Memory grows quadratically with sequence length, so shorter sequences during training avoid memory blowups.From this comment
- On a 64GB machine the work is capped at roughly 2,000 input tokens with about 1,000 output tokens.From this comment
- The faster alternative appeared after this project began and cannot be fine-tuned on this hardware.From this comment
What a builder can take from it: A builder should plan around hard memory limits, state token budgets honestly, and answer capability questions directly rather than overselling. our reading
The title, taken apart our calculation
This post got 235 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
Tuesday at 19:00 UTC. Of 2,501 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 67 (2.7%) 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 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