What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether an API endpoint could be offered so the palettes can be used programmatically.From this comment
- How the color extraction relates to existing published methods for building palettes from artwork.From this comment
- Whether modern or contemporary painters could be added to the collection.From this comment
- Whether the tool is meant for design work or for painting, and which data views painters need.From this comment
What they doubted or pushed back on our summary
- Old varnish makes many palettes brownish, so they may not reflect the painters' intended colors.From this comment
- Automatic page switching while scrolling was disliked and felt unfamiliar.From this comment
- The extraction may miss key colors and their roles, such as a notable accent or a classic primary set.From this comment
- The site and its comments read as machine generated, raising suspicions about authenticity.From this comment
What the maker answered our summary
26 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The tool extracts colors similarly to prior methods but adds prevalence weighting and caps palettes at ten colors.From this comment
- The maker defended scroll-based switching as a way to show more palettes without extra clicks, but will improve it.From this comment
- The maker had assumed the muted tones came from pigment quality and availability, and found the varnish view interesting.From this comment
- The maker agreed ordering artists by first name is wrong and promised to fix it.From this comment
What a builder can take from it: Builders should expect users to demand APIs, accessibility and data-correctness fixes, and be ready to explain or change unusual interaction choices quickly. our reading
The title, taken apart our calculation
This post got 215 points; the median for all 1442 posts is 112.
When it was posted our calculation
Tuesday at 18:00 UTC. Of 2,649 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 84 (3.2%) 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 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