No. 03 · The observatory
Startup Opportunities from Hacker News
A year of Hacker News. Read for the problems people hit themselves and the possible openings among them.
- Status
- Open
- Read
- 605,125 comments, sampled from 3,991,507
- Span
- 28 Sep 2025 to 28 Sep 2026
- Cost
- $22.51, classified by TypeSafe Jev

Six findings
Tap one to see the proofAI coding complaints jumped from 2.7% to 5.9% in one quarter, then held.
Chapter 3 →17.1%Consumer tech is 6.9% of talk but 17.1% of complaints.
Chapter 2 →60%60% of people whose paid products got worse already pay, switch, or quit.
Chapter 4 →8×Rebuilding small tools draws 8 times more launches than its share of complaints.
Chapter 5 →$22.51TypeSafe Jev did all the classifying for $22.51. Staying current costs about $1.60 a month.
How we know →$184–$2,930Mainstream LLMs would cost $184 to $2,930 for the same calls.
How we know →Founders ask one question first. What hurts, for whom, and is anyone fixing it? Hacker News is a year-long public log of people hitting problems. We read it at scale.
Every number here is a share of firsthand complaints on HN. It is not market size. No comment text or usernames appear. Each finding links to its evidence instead.
We answer six questions. Each one tests something a real opportunity needs.
- Many people hit it
- It hurts more than the talk suggests
- It is growing, not fading
- People already spend money or time to cope
- Existing fixes fall short
- Few people are building for it
The raw material
The 58% on cards is the map.
HN produced 3,991,507 comments between 28 September 2025 and 28 September 2026.
A cheap classifier, TypeSafe Jev, read a probability sample of 605,125 of them. It asked one question first. Does the writer describe a problem they hit themselves? About 6.4% do.
That projects to roughly 235,000 firsthand problems across the year. We then sorted each problem into 149 need cards. 58% fit a card cleanly. The other 42% are real problems too specific for any card.
About 6.4% of comments describe a firsthand problem; 58% of those fit a need.
Comments at each step, from every HN comment to problems matched to a need card. 28 Sep 2025 to 28 Sep 2026. A square is 1,000 comments, then 100 from step 4.
- Kept at this step
- Left out at this step
- Matched to a need card
- Bars: comments per month
How to readEach field keeps part of the one before it. At step 4 the squares zoom in tenfold. Hover a field or a month for its numbers.
NoteThe monthly rate stays between 5.5% and 7.1% of comments. Steps 4 and 5 are estimates for all eligible comments.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
The monthly rate barely moves. It stays between 5.5% and 7.1% of comments. So HN does not get angrier. What changes is what people complain about.
What people complain about
Know who writes the complaint. That is who you would sell to.
Thirteen groups of needs cover the map. No single need dominates.
Thirteen groups cover the map, and the biggest single need holds only 2% of problems.
Share of all firsthand problems, 28 Sep 2025 to 28 Sep 2026. Each cell is one need; its area is its share. Colour is its group.
- One need, coloured by its group (keys below)
- Faded: thin evidence or a wide range
- Not matched to a need
How to readTap a cell for its need. Tap a group below to highlight it. Faded: thin evidence or a wide range.
Note42% of problems matched none of the 149 needs: real, but too scattered to group. They sit in the pale sector.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
- Developer tools lead at 11.0% of firsthand problems.
- Devices and operating systems follow at 9.3%.
- Consumer apps come third at 6.3%.
- The two AI groups add 9.9% together.
The biggest single need is broken, slow websites. It holds only 2.0% of problems.
The biggest single need, broken and slow websites, holds only 2.0% of problems.
Share of all firsthand problems, with 50% and 95% ranges. The top 30 of 149 needs, plus 9 whose range reaches them. 28 Sep 2025 to 28 Sep 2026.
- Share of problems
- 50% range
- 95% range
- Tab colour is the need’s group (key below)
- Faded: thin evidence or a wide range
- Paler row: outside the top 30, but its range reaches it
How to readEach row is one need. The dot is its share; the bars show where it plausibly sits. Tap a row for the need.
NoteThis is a long tail. The top 20 needs hold about 22% of all problems. Counts are sampled problems, writers and threads.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
This is a long tail. The top 20 needs hold about 22% of all problems. The words people use show each group's texture.
Each group has its own words: claude for AI coding, slop for AI’s effects.
The words each group’s firsthand problems use most, up to 8 per group. Measured as times as often as in other groups (odds ratio). 28 Sep 2025 to 28 Sep 2026.
- The group’s colour
- 95% range: how much more often the group uses the word
- Estimate
How to readEach column is one group, its most typical word first. A bar further right means a more typical word.
NoteOnly words that pass a correction for testing many words at once (q < 0.05). The scale is logarithmic.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Who complains also differs sharply by group. The bars below show who wrote each group’s complaints.
Who complains differs by group: engineers write 81% of AI coding complaints.
Stated role of the writer, among matched problems whose writer states one. Bar thickness is the group’s share of matched problems. 28 Sep 2025 to 28 Sep 2026.
- End user or consumer
- Software engineer
- Ops, SRE, or IT
- Data or ML practitioner
- Founder or executive
- Student
- Other roles
- Small bar: its dark part is the share who state a role
- Hatched: thin evidence
How to readEach bar is one group, as thick as its share. Its colours show who wrote the complaints.
NoteOnly problems matched to a need card, 58% of all. Roles count only where the writer states one.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
- Software engineers write 81% of AI coding complaints.
- End users write 60% of chatbot complaints.
- Cloud problems split evenly between ops staff and ordinary users.
- Students write 58% of learning complaints.
- Founders and managers show up in hiring and management.
Loud versus quiet
Broad needs suit platforms. Narrow needs suit a focused wedge product.
Talk and pain are different things.
Some topics are all talk. We compared each topic's share of all comments with its share of complaints.
Consumer tech is 6.9% of talk but 17.1% of complaints; legal runs the reverse.
Each topic’s share of complaints divided by its share of all comments. For 20 topic domains, 28 Sep 2025 to 28 Sep 2026.
- Bubble area: share of all talk
- Bubble: complaints outrun talk
- Bubble: complaints trail talk
- Complaint share ÷ talk share, with its 50% range
- 95% range
- All topics together
- Faded: thin evidence or a wide range
How to readEach row is one topic. Right of the dark line, a topic draws more complaints than talk.
NoteAI is 14.7% of talk but only 12.2% of complaints. The scale is logarithmic.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Consumer tech is 6.9% of all talk but 17.1% of complaints. That is 2.5 times. Product design runs 1.9 times. Infrastructure and ops run 1.7 times.
Legal and government topics are the opposite. They are 12.7% of talk, 1.9% of complaints. AI is 14.7% of talk but only 12.2% of complaints. People discuss it more than suffer it.
Some needs live inside one domain. Others appear everywhere.
Some needs live inside one domain; others appear almost everywhere.
How evenly each need’s firsthand problems spread across 20 topic domains, in bits. The 115 needs with at least 100 problems. 28 Sep 2025 to 28 Sep 2026.
- One need, coloured by its group (key below)
- Faded: thin evidence or a wide range
- Joins a named need to its dot
How to readHigher means a need’s problems spread over more domains. Zero means one domain only. Tap a dot for the need.
NoteSpread is the Chao-Shen entropy estimate, in bits. The 34 needs with under 100 problems are left out.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Hostile discussions, unreachable support, and arbitrary moderation span many domains. Version control pain and database tuning stay inside software.
What changed
The AI toolchain is where new pain appears fastest.
Six months is enough to see the ground move. AI rose from 9.0% of problems in the first half to 13.0% in the second.
AI coding complaints jumped from 2.7% to 5.9% in one quarter, and stayed.
Each group’s share of all firsthand problems in each quarter, in percent. Colour compares it with the group’s share for the whole year. All 13 need groups, 28 Sep 2025 to 28 Sep 2026.
- Cell colour: the quarter’s share against the group’s share for the year
- Tab colour is the group
- Hatched: thin evidence
How to readEach row is one group, the biggest risers first. Red cells sit above the group’s yearly share; blue cells below.
NoteA quarter’s shares are of that quarter’s problems. The colour scale is logarithmic.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
- 2.7%28 Sep to 28 Dec 2025
- 5.9%28 Dec 2025 to 29 Mar 2026
- 5.5%29 Mar to 28 Jun 2026
- 5.3%28 Jun to 28 Sep 2026
AI chatbot complaints kept climbing all year. From the first quarter to the last, developer tools fell.
| Group | 28 Sep to 28 Dec 2025 | 28 Jun to 28 Sep 2026 |
|---|---|---|
| AI chatbots | 3.7% | 6.6%, rose |
| Developer tools | 13.9% | 8.9%, fell |
| Cloud and ops | 5.2% | 2.8%, fell |
The fastest-rising needs are all AI; developer tools and desktop pains faded.
Change in each need's share of firsthand problems between two halves, in percentage points. First half: 28 Sep 2025 to 29 Mar 2026. Second half: 29 Mar to 28 Sep 2026. 15 needs changed by more than chance.
- Rose
- Fell
- 95% range
- Raw change
- Mostly from three threads
How to readThe dot shrinks small samples toward zero; the tick is the raw change. Tap a need for its detail.
NoteOnly needs whose change survives a correction for testing all 149 needs (q < 0.05). Each keeps its direction when its biggest thread is dropped.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Desktop Linux gaps and steep languages fell the most. The fastest risers are all AI.
- Coding costs and usage limits nearly doubled.
- Changing AI plans and terms nearly tripled.
- Models that flatter and pad more than doubled.
- Slow or fiddly local models grew 2.7 times.
Pay, hack, or quit
Payment means a budget exists. Workarounds mean the pain is real but unmet.
A complaint is cheap. Paying, hacking, or quitting is a stronger signal.
For paid products getting worse, 60% of writers already pay, switch, or quit.
Each need’s mix of three responses: the writer paid, hacked a workaround, or quit. The three shares are rescaled to sum to 100%. The list ranks needs by the share that pay, switch, or quit. The 136 needs with at least 50 problems, 28 Sep 2025 to 28 Sep 2026.
- One need, coloured by its group (key below)
- Dashed: two responses tie. Each region’s corner is its largest response.
- Joins a named need to its dot
- List bar: share of problems where the writer paid, switched, or quit
- Faded: thin evidence or a wide range
How to readEach corner is 100% of one response; the side across from it is 0%. A dot sits in the region of its largest response. Tap a dot or a name for the need.
NoteSwitching counts in the list, not in the triangle. Smart home cloud lock-in and switching AI tools both hit 66% workarounds.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Paid products getting worse leads. 60% of those writers already pay, switch, or quit.
- Costly care and junk reviews follow near 58%.
- Subscriptions replacing purchases reach 50%. Three in four name a money cost.
- AI plans and terms reach 43%.
- AI coding costs reach 41%.
Other needs get hacked instead of bought. Smart home cloud lock-in and switching AI tools both hit 66% workarounds. People rebuild small tools themselves in 59% of those complaints.
Time is the cost named most in 10 of 13 groups; reliability leads the rest.
Share of each group’s problems naming each cost, in percent: money, time, reliability, or customers. A group weights its needs by their share. The 142 needs with enough evidence, 28 Sep 2025 to 28 Sep 2026.
- The group: share of its problems naming each cost
- Dashed shape: average of the 13 groups
- Bar: share of the group’s problems naming the cost
- Tick: average of the 13 groups
- 95% range
- Tab colour is the group
How to readEach cost runs from 0% to 50% of problems. On a radar, 0% is the centre and 50% the outer ring.
NoteA cost counts when the classifier reads that the writer lost it. Money leads nowhere; it peaks at 24%, in money, housing, travel.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Some needs hurt more than others when they land.
- Banned accounts with no appeal are the harshest. 66% reach a real cost or worse.
- Third-party outages follow at 60%.
- Hacked accounts reach 54%.
Is anyone solving it
Pain with few launches is the gap. Crowded needs are a warning.
We checked three things. Replies, named tools, and product launches.
Replies rarely close the loop: 68 of 100 problems got no reply naming a fix.
Share of each need’s problems where no reply named a fix, in percent. Beside it, the share whose author said it was fixed. The 40 biggest needs, whose replies were read, 28 Sep 2025 to 28 Sep 2026.
- Squares: no reply named a fix
- Squares: a reply named a fix
- Share of problems
- 50% range
- 95% range
- Tab colour is the need’s group (key below)
- Faded: thin evidence or a wide range
How to readThe squares stand for 100 problems, weighted by need size. Each row is one need. The author column’s scale stops at 5%; the other runs to 100%. Tap a row for the need.
NoteAuthors almost never come back to say a fix worked. That happens under 1% of the time.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Replies rarely close the loop. In the 40 biggest needs, 68 of 100 problems got no reply naming a fix. Authors almost never come back to say it worked. That happens under 1% of the time.
- Bad management and hostile discussions are nearly never solved in replies, at 97%.
- False chatbot facts sit at 85%.
- Scams and spam sit at 85% too.
Popular tools get blamed and recommended; uBlock Origin, uv and Jujutsu stand out.
Fix share: threads recommending the tool as a fix, over fix and complaint threads. Against the threads naming the tool, on a log scale. The 261 tools with 10 or more threads, 28 Sep 2025 to 28 Sep 2026.
- AI model
- Developer tool
- OS or device
- AI coding tool
- Consumer app
- Cloud or hosting
- Business software
- 95% funnel: where a tool at the overall rate would fall
- Overall fix share, 8.0%
- Joins a named tool to its dot
How to readDots above the funnel are recommended more often than chance allows. Dots below it are blamed more often than chance allows. Hover a dot for its numbers.
NoteBeing named in a complaint does not mean the tool caused it. A reply counts as a fix only when it recommends the tool.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
The same tools appear on both sides. The popular ones get blamed and recommended. A few small tools are recommended unusually often. uBlock Origin, uv, and Jujutsu stand out.
Then we asked where builders actually launch. We assigned a sample of 8,001 Show HN launches to the same 149 needs.
Rebuilding small tools gets 6.1% of launches but only 0.8% of complaints.
Each need’s share of sampled Show HN launches against its share of firsthand problems. Both in percent, on log scales. 8,001 of 46,081 launches were sampled; 47% fit a need. All 149 needs, 28 Sep 2025 to 28 Sep 2026.
- One need, coloured by its group (key below)
- Faded: thin evidence or a wide range
- Diagonal: launch share equals complaint share
- Shaded: under a tenth as many launches as complaints
- On the bottom rail: no launch in the sample
- Joins a named need to its dot
How to readAbove the diagonal, a need draws more launches than complaints. Below it, fewer. Tap a dot for the need.
NoteShow HN is mostly software, so hardware needs draw few launches anyway. Labels name the most underbuilt needs.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Builders crowd some needs. Rebuilding small tools gets 6.1% of launches but 0.8% of complaints. That is eight times more launches than complaints.
Other needs get almost no launches. Early hardware failure with no repair got none. Broken websites and updates that break devices got almost none too.
Where the openings are
Pick one need. Follow its evidence. Then go talk to those people.
Now we combine all six tests into one score.
You choose the weights. The ranking updates live.
With equal weights, five needs lead, and their order is not stable.
Opportunity score: each need’s weighted mean percentile across the tests, in percent. Needs with at least 200 problems, 73 of them. Only the 40 with replies read while Unsolved counts. The top 20, 28 Sep 2025 to 28 Sep 2026.
- Size: share of all problems
- Growth: change in share
- Paid: writers who pay, switch, or quit
- Unsolved: no reply named a fix
- Severity: a real cost or worse
- Underbuilt: few launches for the pain
- Reliability cost: writers lost reliability
- Customer cost: writers lost customers
- Dots: its rank across resamples, at equal weights, among 136 needs
- 80% of its resampled ranks sit within three places of their middle
How to readPick a preset or move a weight, and the ranking updates. The dots show how far each rank drifts, at equal weights. Stable: most resampled ranks sit within three places.
NoteA test with no data for a need is left out of its score. The underbuilt preset leans on the Show HN sample. Read it as a lead.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
With equal weights, five needs lead. Their order is not stable.
- Early failure with no repair
- Data taken without consent
- AI agents that write bad code
- Clumsy login and two-factor flows
- Broken, slow websites
Switch to the underbuilt preset. Bad management and buggy car software rise to the top.
Some needs cluster: 5 bundles hold up, so one product could serve several.
Bundles group needs the classifier judged to describe related problems. Each holds 3 to 12 needs. Its share is its needs’ combined share of firsthand problems, in percent. All 149 needs, 28 Sep 2025 to 28 Sep 2026.
- One need, coloured by its group (key below)
- Link: two needs in a shown bundle, darker when more alike
- Dashed link: in a fragile bundle
- Outside the chosen bundle
- Joins a named need to its dot
How to readTap a bundle to light its needs on the circle. Needs sit around the circle by group. Hover or focus a dot to draw its links in dark lines. Tap it for the need.
NotePersistence is the share of two other cut heights where the bundle still forms. Fragile bundles, under 50%, stay hidden until you show them.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Some needs cluster, so one product could serve several.
- Metered cost pain joins AI coding costs, cloud bills, and subscriptions.
- Platform power joins changing AI terms, platform dependency, and devices losing support.
- Everything-goes-down joins code hosting, AI, and third-party outages.
Broken, slow websites: 2.0% of problems, no clear change, and 68% get no fix named.
One need’s evidence, the largest by share, in percent. Size is a share of all firsthand problems. The rest are shares of its own problems. 28 Sep 2025 to 28 Sep 2026.
- Estimate
- 50% range
- 95% range
- Faded: thin evidence or a wide range
- Dot alone: no range published
How to readEach panel has its own scale. Tap any need on the page for its full profile.
NoteLaunch ratio is its share of Show HN launches over its share of complaints. Under 1× means few launches.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
How we know
A cheap classifier works if you measure its errors honestly.
This whole study cost $22.51 of classifier credit, over 501,082 calls.
That bought 547 million input tokens and 116 million output tokens. The same tokens on general LLMs, at September 2026 list prices:
- GPT-5 nano, batched: about $37. Untested on this task.
- GPT-5 mini, batched: about $184.
- Claude Haiku 4.5, batched: about $563.
- Claude Sonnet 5: about $1,460 batched, $2,930 at standard prices.
- Claude Opus 5.5: about $5,860 at standard prices.
Our 50% confidence rule also needs probabilities. Many LLM APIs do not return them. A monthly refresh with Jev costs about $1.60.
The whole study cost $22.51 of classifier credit, over 501,082 calls.
Classifier credit in US cents, by phase of the study. Then each phase’s share of calls and of cost. Every classifier run, from the pilot to the launch sample.
- Screen: is it a firsthand problem
- Facets: topic, role, costs, coping, severity
- Assign: which need card
- Rewording reruns: instructions phrased differently
- Verify cards and merge duplicates
- Replies: was a fix named
- Builders: which need a launch serves
- Named fixes: which tool a reply recommends
- Other: pilot, a stopped verify run, checks
- Line: joins a phase’s share of calls to its share of cost
- Joins a name to its phase
How to readEach square is one cent. The left bar splits the calls; the right bar splits the cost.
NoteCosts are exact, from the usage ledger. A monthly refresh costs about $1.60. The median call took 260 milliseconds.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
The median call took 260 milliseconds. The main screen took 2 hours 19 minutes. We checked the classifier four ways.
In a blind audit, the classifier’s need card fit 95% of the time.
Four checks of the classifier, each as correct cases out of 100. Then how results move under two rewordings of its instructions, in percent. Samples from the study year.
- Square: the card fit, or the case was right
- Square: it did not
- One run: the original wording or one rewording
- 95% range
- Spread between the two rewordings, not a range
How to readEach square is one case in 100, rounded to whole cases. The two wording panels each use their own scale.
Note226 invented comments tested the screen. Rewording changed the need card for about 8 to 9% of problems.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
What could be wrong
Trust the needs that survive every check. Then verify them in interviews.
Our choices shape the ranking. So we reran it under five other choices.
The top needs mostly hold their place under five other analysis choices.
Each need’s rank by share of firsthand problems, under the main analysis and five alternatives. Rank 1 is the largest. The 28 needs in the top 20 under any choice. 28 Sep 2025 to 28 Sep 2026.
- Rank in the main analysis
- Rank under one alternative
- Bar: best to worst rank across all six
- Darker bar: fragile, one of the three widest
- Its rank depends most on the choice
- Tab colour is the need’s group (key below)
How to readA short bar holds its rank under every choice. A long bar depends on the choice. Tap a row for the need.
NoteAlternatives: a stricter card match, one per thread, one per writer, and two reworded instructions.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
The top needs mostly hold their place. A few are fragile and marked. Some needs rest on a few threads or a few loud people.
42 needs lean on one thread or one writer; treat them as leads.
Share of each need’s problems from its top three threads, in percent. Then the same for its top three writers. Both against its number of problems, on a log scale. All 149 needs, 28 Sep 2025 to 28 Sep 2026.
- Flagged: one thread holds over 30%, or one writer over 10%
- Not flagged
- Untested: under 30 problems
- Grey bar: where the top-three share falls by chance, 95%
- Joins a named need to its dot
How to readHigher dots lean on fewer threads or writers. A dot above its grey bar is more concentrated than chance. Tap a dot for the need.
NoteThe flag tests the single biggest thread and writer, a rule set before the analysis. Flagged needs are leads, not findings.
SourceHacker News comments, 28 Sep 2025 to 28 Sep 2026; a probability sample of 605,125 comments classified by TypeSafe Jev. Analysis: Hansel.
Those are flagged. Treat them as leads, not findings. Other limits matter too.
Credits
- Classifier
- TypeSafe Jev did all the classifying. It answers typed questions and writes no text. No affiliation with TypeSafe. I paid for all usage.
- Naming
- Need and group names were proposed with help from Claude and approved by me.
- Analysis
- Hansel, from Hacker News comments posted 28 Sep 2025 to 28 Sep 2026.