What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- What makes this durable when similar attempts were previously removed by the platforms?From this comment
- How is this different from existing browser extensions that already hide short videos?From this comment
- Does the option to see fewer shorts on YouTube actually reduce how often they appear?From this comment
- What are the long-term implementation implications of building on top of these platforms?From this comment
- What does this offer over patched YouTube clients that already block shorts?From this comment
What they doubted or pushed back on our summary
- A paid app is hard to justify when a free blocklist already removes shorts and reels.From this comment
- Nobody should have to pay simply to avoid parts of apps already on their phone.From this comment
- Blocking elements treats the symptom while the real issue is shortened attention spans.From this comment
- Creating a separate app just to restore an older Instagram experience says something grim.From this comment
What the maker answered our summary
19 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- They concede they cannot know if the platforms will act against the app, and are uncertain.From this comment
- Platform markup changes constantly, so they rely on daily use and active testers to catch breakage fast.From this comment
- Some features need to run inside the app, and the aim is less time spent, not just hidden elements.From this comment
- They argue the platforms tolerate such tools because losing users costs more than lost ad revenue.From this comment
What a builder can take from it: Builders should know that wrapping a platform's interface invites takedown and breakage risk, so honest answers and fast maintenance matter more than grand promises. our reading
The title, taken apart our calculation
This post got 153 points; the median for all 1442 posts is 112. In Consumer apps and tools (48 posts) the median is 104 points and 50 comments.
When it was posted our calculation
Wednesday at 21:00 UTC. Of 1,956 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 55 (2.8%) 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 Consumer apps and tools 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