WeSearch

98% Isn't Much

·2 min read · 0 reactions · 0 comments · 34 views
TL;DR · WeSearch summary

The article discusses how 98% is not a satisfactory percentage for certain aspects of life, such as a restaurant's food safety record or a website's compatibility with browsers. It highlights that 98% can be misleading, as it can still result in a significant number of people being affected, and that truly robust engineering should prioritize handling edge cases. The article concludes that 98% is not enough to be considered widely supported, especially when it comes to basic expectations like website functionality or food safety.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 993 of its stories. Top-voted stories on Hacker News.

Original article
Whynothugo
Read full at Whynothugo →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherWhynothugo
Canonical URLhttps://whynothugo.nl/journal/2026/07/03/98-isnt-very-much/
Publication timeTue, 07 Jul 2026 12:45:14 +0000
Retrieval time2026-07-07T13:05:57.449Z
Last seen2026-07-07T13:05:57.449Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterNone
Cluster logicNot yet clustered, or no peer story found in the clustering window.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

98% sounds like a lot. If someone wins the lottery 98% of the times they play, they are clearly blessed. Getting a top mark (e.g.: 10/10) on exams 98% of the time will likely lead to an honour diploma.But a restaurant where clients don’t get of food poisoning 98% of time is getting people sick on a monthly (or even weekly) basis. If an employer pays their employees 98% of the times, I definitely wouldn’t want to work there. If I pay before leaving a restaurant only 98% of the time, I’ll be in trouble.98% is great for exceptionally good things, like dramatically increasing someone’s quality of life, but very low for basic expectations, like a baby surviving a babysitter taking care of them.If a website uses fancy new browser features and works for 98% of the population, that means that it…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Whynothugo.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Whynothugo