Hacker News, Distilled

Plug‑in Hybrids, Size, and Use Cases

• Many commenters want more PHEVs, especially small cars and midsize/light trucks (Tacoma, Ranger/Maverick‑like, small hatchbacks), not just SUVs and crossovers.
• Some argue small PHEVs “don’t make sense” due to packaging and cost; others rebut with examples like Chevy Volt, BMW i3 REx, Prius Prime showing compromises are manageable.
• PHEVs are praised as “best of both worlds” for mostly‑short trips with occasional long drives: daily EV‑like use, no road‑trip anxiety.
• There is interest in modular/upgradable battery packs, but skepticism that manufacturers will ever support this.

Toyota’s Strategy: Hybrids vs EVs

• One camp sees Toyota’s hybrid‑first, evolution‑not‑revolution approach as smart, leveraging decades of hybrid experience while waiting for better batteries (including solid‑state).
• Another camp argues Toyota squandered its early lead, came late to PHEVs, and its main EV (bZ4X) is inefficient and underwhelming compared to Tesla and others.
• Some highlight that Toyota hybrids are extremely reliable and easy to maintain; others note certain hybrid implementations from other brands (e.g., older Honda systems) have been problematic.

EV Charging Infrastructure & User Experience

• Several reports of painful non‑Tesla road‑trip experiences: multiple incompatible apps, broken or slow chargers, brand‑locked networks, poor locations, and difficulty charging to 100%.
• Strong dislike of app‑only charging; some say they will avoid EVs until they can pay with a card at any station, like gas today.
• Tesla’s Supercharger network is described as “just works,” but also criticized as a proprietary, data‑tracked system.

Battery Life, Tech, and Cost

• Debate over battery cycle life in PHEVs vs BEVs; some worry PHEVs’ smaller packs will wear faster, others cite long‑lived Prius packs and buffer strategies (not using full capacity).
• Noted that PHEV failures are cheaper than EV pack failures, but some early hybrids had expensive battery replacements.
• Several commenters point to high EV prices (often ~$60k) as a key reason they choose hybrids instead.

Competition and Market Dynamics

• Some predict Toyota will remain dominant; others think Chinese makers like BYD will “steamroll” legacy brands due to scale and battery capacity.
• Honda is criticized as strategically lost in cars and EVs, contrasted with more aggressive Korean manufacturers.
• There is disagreement about EV vs ICE demand trends: some say EV sales are slowing and ICE demand is steady; others insist ICE demand will decline as EVs get cheaper and concerns about oil persist.

Scale of Kim Dotcom and Megaupload

• Many reject framing him as “small folk”; he had a mansion, dozens of luxury cars, ~$175M in cash, and 64 bank accounts.
• Others argue wealth alone doesn’t prove serious criminality, just that Megaupload was a huge cash-generating service in its era.

Cash, Assets, and Suspicion

• Debate over whether holding massive physical cash is inherently suspicious.
  • Some see “two tons of $100 bills” as cartel‑level behavior.
  • Others say distrust of banks and fear of asset seizure (especially by the US) is a rational motive, not proof of crime.

Nature and Severity of Alleged Crimes

• Charges go beyond copyright infringement: conspiracy, racketeering, money laundering, wire fraud.
• Key prosecution claims cited:
  • Megaupload allegedly deduped files; DMCA takedowns removed links but left infringing files accessible via other links.
  • Internal communications allegedly show active encouragement of piracy and paying uploaders for popular copyrighted content.
  • Strong counter‑claim: they did have takedown tools and shouldn’t be liable for what users upload if they comply.

Extradition, Jurisdiction, and US Power

• Many object to extraditing a non‑US citizen for acts done abroad, seeing it as US “world police” behavior and a chilling precedent for foreigners.
• Others note NZ–US treaties, US‑hosted servers, and international copyright treaties; argue this is “boring international justice,” not imperialism.
• Long delay (12+ years) seen by some as “punishment by process,” by others as the natural result of extensive appeals.

Piracy, Copyright, and IP Legitimacy

• Strong split between:
  • “IP is legitimate, artists and studios deserve protection; Kim knowingly built a piracy business.”
  • “File sharing isn’t theft; damages are wildly overstated; current copyright regime and term lengths are abusive.”

Comparisons to Other Platforms and Figures

• Frequent comparisons to YouTube, Spotify, RapidShare, Google Drive, Plex:
  • One side: all bootstrapped via piracy, but YouTube et al ultimately built strong takedown systems and partnerships; Megaupload doubled down on infringement.
  • Other side: differences are mainly political power and lobbying; big US firms are tolerated where Dotcom is made an example.
• Broader analogies to Assange, Snowden, Ross Ulbricht; many see disproportionate, example‑making prosecutions for tech‑enabled offenses.

Broader Political and Geopolitical Threads

• Discussion of US influence over NZ and Australia (Assange case, AUKUS subs), five‑eyes, and copyright lobby power.
• Side debates on Russia/Ukraine, Gaza, and accusations that Dotcom amplifies Russian/CCP narratives; others warn against dismissing dissent as “on the payroll.”

Is Google a monopoly and how does it compare to others?

• Many see Google as having de‑facto monopolies in search, ads, and key gateway services (Android, Chrome, YouTube, Gmail).
• Others argue it has competitors for every product (Bing, iOS, DDG, etc.) and switching is “trivially easy,” so “monopoly” is misapplied.
• Several commenters say if Google is targeted, Microsoft, Apple, Amazon, Meta and others should also face antitrust scrutiny; some call for breaking up all large tech conglomerates.
• Debate over whether Apple and Microsoft are actually more coercive (Windows bundling, iOS walled garden) than Google.

Antitrust theory and legal framing

• Clarification that in the US, having a monopoly isn’t illegal; abusing it or leveraging it into other markets is.
• Google’s payments to be the default search engine, and use of Chrome/Android to protect search and ads, are cited as possible abuses.
• Some see Google’s market share and default status as classic harm to competition; others say users repeatedly choose Google even when asked, so harm is unclear.

Proposed remedies

• Forbid paying to be default search; require real choice screens on major browsers/OSes.
• Structural split of Google Ads from Search/YouTube/other properties, or at least separate “buy side” and “sell side” of ad tech.
• Spin off Chrome, Android, YouTube, Gmail/Docs, Maps, Cloud, etc., possibly as independent firms or non-profits; more radical versions extend similar splits to all FAANG and major game platforms.
• Mandate shared or public crawling/indexing infrastructure so new search engines can compete on ranking, not on raw crawl scale.
• Softer remedies: consent decrees, bans on exclusive deals, constraints on self‑preferencing.

Concerns and unintended consequences

• Fear that breakups would kill cross‑subsidized “free” services or force subscriptions (e.g., Gmail, Chrome), with unclear net consumer benefit.
• Some worry about simply handing power to other giants (Apple, Meta, Microsoft) or creating a “hydra” of smaller but still ad‑driven entities.
• Technical complexity of disentangling Google’s monorepo and deeply integrated systems is seen by some as a practical barrier, though others say that’s Google’s problem, not regulators’.

Ads, utilities, and structural critiques

• Many view the core problem as surveillance advertising and vertical integration: Google controls browser, OS, search, ad exchange, and inventory.
• Suggestions range from treating search, browsers, and email as public utilities to banning or radically constraining targeted ads.
• Others argue the deeper issue is decades of lax merger policy and a system that structurally rewards building firms only to sell or dominate.

Role of Markdown: Visible Syntax vs Rendered Output

• Strong split between those who want to always see raw Markdown and those who prefer styled text with syntax mostly hidden.
• Many argue Markdown’s philosophy is that the plain text itself should be readable, so hiding it undermines a key benefit.
• Others see Markdown primarily as a storage / interchange format that should be rendered WYSIWYG for comfort and aesthetics, especially for long‑form writing and notes.

Editing UX: Modes, Live Preview, and “Reveal Codes”

• Popular compromise: hybrid editors (Obsidian, Bear, Typora) that render formatting but reveal raw syntax around the cursor. Some find this jarring due to text reflow; others say it becomes natural.
• Users want easy toggles between “source” and “preview” and keyboard shortcuts for mode switching.
• Several reminisce about WordPerfect’s “Reveal Codes” and want similar explicit control boundaries to avoid WYSIWYG “magic” backspaces that unexpectedly reformat blocks of text.

Portability, Storage, and Tooling

• Markdown as backend storage is praised: plain text, portable, diff‑friendly, and safer than opaque rich‑text formats.
• Some apps intentionally present pure WYSIWYG while persisting Markdown underneath to get both user‑friendliness and long‑term data safety.
• Others complain about apps that adopt Markdown but then hide it entirely or make preview mandatory, undermining its value to power users.

Markdown Overreach and Alternatives

• Several argue many apps reach for Markdown by default when richer, custom markup or true rich‑text would be better (e.g., complex word processors, wikis).
• Alternatives like djot and formats that output JSON are mentioned, but Markdown’s ubiquity and tooling support are seen as hard to displace.

Formatting Details and Ecosystem Frictions

• Disagreement over keyboard efficiency (* vs Ctrl/Cmd‑I) and interaction patterns for italic/bold.
• Confusion and frustration with inconsistent Markdown‑like syntax across apps (e.g., * as bold vs italic in chat tools).
• Debate over HTML semantics (<b>/<i> vs <em>/<strong>) and whether Markdown is “meant” primarily for HTML generation or direct reading.
• Prettier and similar auto‑formatters are criticized for mangling human‑oriented whitespace and heading styles in Markdown.

Non‑Technical Users and Product Decisions

• Reports that non‑technical users perceive Markdown as “coding” and strongly prefer Word‑like WYSIWYG.
• Some products (e.g., Trello, various wikis) moving away from visible Markdown or disabling it entirely draws backlash from users who rely on raw syntax.

Reticulum & NomadNet Capabilities

• Built on the Reticulum network stack, which can run over many media (LoRa, BLE, packet radio, Tor/I2P, HF, etc.) as long as bandwidth > ~5 bits/s and MTU ~500 bytes.
• Demonstrated over HF radio with ~90-mile separation, bridging an HF node to a TCP-based testnet so off-grid nodes can reach wider peers.
• Ecosystem includes desktop (NomadNet), mobile (Sideband), browser client (MeshChat), and microcontroller firmware.

Routing, Announces, and Flooding

• Reticulum uses “announces” that are flooded only for routing information. Nodes store next-hop info; data packets then follow a single path using hop-count.
• To mitigate flooding, only a small fraction (~2%) of channel bandwidth is used for announces, with priority for lower-hop ones, which biases routes toward faster paths in practice.
• Skeptics question resilience against Sybil-style attacks (e.g., generating vast numbers of fake addresses/announces). Mitigations mentioned: announce caps and rate-limiting per interface, but comprehensive source-flood protection and a formal threat model are described as unclear.

Blockchains, Sybil Resistance, and Alternatives

• Explicitly no blockchain is used. Some argue that mesh + blockchain are ill-matched (consistency vs partition tolerance).
• Long side-thread debates whether blockchains or other consensus schemes are necessary or useful for Sybil resistance; views range from “all blockchain is useless” to “various non-blockchain distributed approaches can work.”

Transports, Radio, and Legality

• Reticulum can be used over ham bands, but US rules generally prohibit encryption on amateur radio; ISM bands (e.g., LoRa, WiFi) avoid this issue.
• Discussion of HF legality, CB restrictions (voice-only, no digital), and FCC’s slow reconsideration of “no encryption” rules.
• Concern over potential loss of 900 MHz ISM spectrum to commercial interests.

Hardware, Performance, and Sneakernet

• Python implementation seen as heavy for very old hardware, but there is a C++ microReticulum for ESP32 and RNode firmware for LoRa boards.
• Supports very low bandwidth and even “sneakernet” via printed QR messages that can be scanned and injected into the mesh.

Security, Auditing, and Usability

• Software is beta and not externally audited; some see that as acceptable for non-commercial projects, others worry about privacy-breaking bugs.
• No clearly documented, formal threat model yet; interested readers are pointed to the manual and community forums.
• Usability critiques: long hex identities are hard to handle; suggestions include decimal/base32 and better grouping. Users must understand what “trust” levels mean.
• Concerns that true privacy also requires trusted input devices and minimal, auditable software stacks, not typical mobile OS keyboards.

Scope of the Proposal

• Policy: make tips (fully or partly) exempt from income tax; some versions include income caps and anti-abuse rules.
• Seen as politically attractive because many service workers would benefit and it sounds novel, even if revenue impact may be modest.
• Some view it mainly as vote-buying or a meme-friendly slogan rather than serious tax reform.

Loopholes, Abuse, and Fairness

• Major concern: businesses and high earners could reclassify normal compensation or performance fees as “tips” to avoid tax.
• Examples raised: independent contractors billing $1 and collecting the real amount as a “tip”; hedge fund performance fees labeled as tips.
• Skeptics doubt “strict requirements” can prevent widespread gaming; enforcement would be complex and uneven.
• Objection that untaxed tips are unfair to non-tipped workers (“back of house,” non-service jobs) whose income remains fully taxed.
• Some argue all income should be taxed similarly; preferential treatment distorts behavior and increases compliance costs.

Tipping Culture Critique

• Many commenters dislike tipping culture and see this proposal as entrenching it further, especially with touchscreen prompts before service.
• View that tipping has become a way for employers to underpay workers and shift labor costs and moral pressure onto customers.
• Several argue for eliminating or restricting tipping, raising minimum wages (including ending the lower “tipped wage”), and making prices all‑in.
• Others note non-US countries where tipping is rare or modest and wages are straightforward, and prefer that model.

Administrative and Edge Cases

• Questions about definitions: what counts as a “tip” vs. bonus; who is a “service worker”; how to handle corporate expense reimbursements.
• Concerns that credit card processors and fraud systems limit large tips, complicating any widespread conversion of pay into tips.
• Some suggest partial exemptions (e.g., first $10k of tips for lower-income workers), or only cash tips tax-free with daily caps.

Broader Tax & Governance Themes

• Debate over whether income should be taxed at all vs. taxing consumption, capital, or land.
• Significant discussion of government waste, fraud, and complexity; many argue simplification and efficiency should precede any new tax carve-outs.
• Others emphasize that taxes fund public goods and that under-taxation or misaligned incentives contribute to societal problems.

Overall view of the Las Vegas Loop / Boring Company

• Many see tunneling as a mature, optimized industry; they argue Boring Company has not delivered real innovation beyond slightly smaller, less-equipped tunnels.
• Defenders say it’s too early to call it a failure: founded 2017, first contract 2019, system delivered as specified and cheaply versus competing local bids.

---

Cost and construction comparisons

• One side claims the LVCC tunnel was more expensive and slower per km than major rail tunnels; others counter with numbers showing the LVCC per‑mile cost far below the Channel Tunnel and typical US subway costs.
• There is confusion over exact LVCC/Vegas Loop costs (52.5M vs ~106M, 1.7 vs 2.2 miles, additional stations); commenters note a lack of transparent breakdown of tunnel vs station vs vehicle costs.
• Several point out station construction usually dominates total cost, so savings on tunnel diameter may not matter much.

---

Capacity and geometry

• Strong criticism: small pods/cars in single-lane tunnels are inherently low throughput compared to trains in similarly sized tunnels, which can move tens of thousands of passengers per hour.
• Multiple back‑of‑the‑envelope comparisons show needing enormous tunnel length or many parallel tunnels to match a single high‑frequency subway line.
• Supporters respond that:
  • More numerous, cheaper tunnels can offset per‑tunnel capacity limits.
  • Point‑to‑point service and smaller stations may be better for many US use cases than “crush‑loaded” subway trains.
  • The system is more comparable to light rail or commuter links than to top-tier metros.

---

Automation and operations

• Many are surprised the cars have human drivers; some assumed Autopilot would be used in this highly constrained environment.
• Skeptics argue that reliable automated control is hard and safety‑critical, even on rails; supporters say metro automation was “solved” decades ago.
• A small, unimpressive operations control center is noted; some see this as penny‑pinching, others say it’s typical of municipal control rooms and not a major cost.

---

Safety, fire, and worker protection

• The operations manual reportedly devotes more space to scripts about the company and its flamethrower than to fire procedures, which some read as emblematic mis‑prioritization.
• Concerns:
  • No emergency egress corridors; single-lane tunnels with no easy way around a disabled vehicle.
  • Lithium‑ion battery fires in enclosed tunnels.
  • Reported construction injuries and chemical burns; debate over whether this is unusually bad or typical of construction.
• Others argue risk is mitigated by:
  • Small, isolated passenger vehicles rather than mixed heavy trucks and cars.
  • Vehicle features like HEPA‑filtered, pressurized cabins (as claimed in the thread).

---

Public vs private transit and equity

• Several criticize the concept as a “luxury” or marketing‑driven system for convention visitors and high‑end tourists, not serious mass transit.
• There is philosophical pushback against privatized urban transport infrastructure, with comparisons to high‑toll private roads near US cities.
• Supporters counter that:
  • It doesn’t displace public transit and uses private capital.
  • It could evolve from Tesla taxis into higher‑capacity rubber‑tired metro‑like service over time.

---

Conceptual critiques

• Repeated comparison to just “roads in tunnels with taxis”: many argue this reinvented concept can’t match rail’s geometric efficiency.
• Others, drawing on personal rapid transit experience, claim that dense networks of small automated vehicles can be competitive on seat‑mile efficiency up to the scale of major urban rail, while offering direct, no‑transfer trips.

Reactions to Google Disabling uBlock Origin on Chrome

• Many commenters say this confirms their decision to keep or switch to Firefox or other non-Chrome browsers.
• Several state they will not use the web without a strong ad blocker and will abandon any browser that weakens ad blocking.
• Some frame this as a core usability/security feature, comparable to removing the back button.

Manifest V3 and uBlock Origin Lite

• uBlock Origin Lite is described as MV3-compliant but significantly less capable: no dynamic filters/scriptlets, limited heuristics, and filter lists only updatable via extension updates controlled by Google.
• Concern that YouTube and “bait URL” anti–ad-block techniques can’t be countered effectively under MV3.
• Some users with basic needs report seeing little practical difference; others emphasize that limitations will show up on more adversarial or complex sites.
• Enterprise/managed-policy flag (ExtensionManifestV2Availability) can delay MV2 removal until June 2025 for some users.

Browser Choices and Built‑In Ad Blocking

• Alternatives mentioned: Firefox, LibreWolf, Orion, Vivaldi, Opera, Brave, Edge, future projects like Ladybird.
• Firefox praised for continuing MV2 support, containers, and extensibility, though some distrust its dependence on Google funding.
• Several want ad blocking baked into the browser “guts” rather than via extensions; Vivaldi and Brave are cited as examples with built-in blockers.

Ad Blocking, Funding Models, and Adoption

• Many find today’s ad-heavy web unusable, especially for less technical or elderly users at risk of scams.
• Debate over how many people actually use ad blockers; some claim 30–50%, others argue actual usage is far lower based on Chrome/uBO numbers.
• Discussion of non-ad funding models: paid services, government-funded services, non-profits, and hobbyist-supported sites.

Security, Extensions, and Workarounds

• Some welcome MV3’s restrictions on remote code as protection against malicious extensions; others call this threat overstated and note Google’s review is imperfect.
• Manifest V3 is criticized for breaking many long-tail extensions whose authors may never update them.
• Suggested workarounds include DNS-level blocking (e.g., Pi-hole), local proxies (e.g., privoxy), and eventually forking or replacing Chromium.

Overall reactions to “trainwreck / hive design”

• Many see “trainwreck design” as natural evolution: systems accrete features and hacks, stay “good enough,” and only rarely get rebuilt.
• Some compare the author’s “hive design” to “bazaar but with shared vision,” and ask for concrete large-scale examples; only small projects (Hare, suckless, etc.) are mentioned.
• Others argue that strong, single-leader design (benevolent dictators) is the only way to avoid long‑term chaos.

CLI usability: df, mount, ip and friends

• Strong agreement that defaults for df, mount, and ip addr are noisy and confusing, especially with many tmpfs, system, and container mounts.
• Several argue the defaults should prioritize the most common human task: “how much disk space do I have?” or “what are my real interfaces?”
• Counterpoint: the “raw, ugly truth” is valuable; changing long‑stable outputs risks breaking scripts and dumbing tools down for power users.

Systemd, containers, and filesystem clutter

• Multiple comments blame systemd and containerization for polluting mount and network views (e.g., many tmpfs, /var/credentials, debugfs).
• Others distinguish between the tools themselves (df/mount) and the underlying “mess” they now have to reveal.

Workarounds and alternative tools

• Suggested commands: df -h /, df -h ~, df -t ext4, or long aliases excluding tmpfs, overlay, etc.
• Alternatives: findmnt for filtered mount views; Rust replacements like fd/sd; GUI tools like gparted for partition resizing.
• Some prefer GUI file managers and display tools on Linux desktops, noting they “just work” for everyday tasks.

LLMs and the shell

• One group claims LLMs already make obscure commands and parsing less relevant; future shells may embed them.
• Skeptics note that asking an LLM for commands and parsing is still more friction than a sensible default like “df that’s readable.”

Governance, funding, and cohesion

• Comments lament lack of funding for refinement of core tools; complexity and strict gatekeeping make drive‑by fixes unlikely.
• There is speculation about new governance models (“human staking,” vote-based “queen bees”) but it remains theoretical.

Aesthetics and web design

• Many like the blog’s ASCII/terminal aesthetic (figlet-style headings, monospaced text, CSS-only animation).
• Others criticize poor semantic HTML, footnotes as plain URLs at the bottom, and monospaced body text as a readability and usability regression.

Outage scope and impact

• Large, global outage: users report failures across North America, Europe, Australia, New Zealand, Hong Kong, Dominican Republic, etc.
• Not just the web UI: git operations (push/pull), API, mobile app, GitHub Pages, Actions, Packages, Issues, Copilot, and Pages-hosted sites all affected.
• Some users continued working locally or exchanged patches via git format-patch, git am, or git bundle. Others simply stopped work or used it as an excuse to end the day.

Status page and communication

• Status page initially showed all green for several minutes while most users saw “angry unicorn” errors.
• Many criticize this lag as making the status page “effectively useless” during real incidents.
• Others note that external status dashboards are usually manually updated, internally approved, and influenced by SLA/liability concerns, so delays are expected.
• Some argue for automated, faster, end‑to‑end monitoring; others point out false positives, complex routing, and “not 100% fidelity” as reasons for caution.
• GitHub’s X/Twitter status feed is also criticized as hard to use when not logged in.

Suspected cause

• Official status later attributes the incident to a “database infrastructure related change” being rolled back.
• Users joke about misapplied configuration changes, database hot patches without transactions, and kubernetes rollbacks, but details remain unclear beyond the DB-change note.

Centralization, reliability, and alternatives

• The outage highlights heavy industry dependence on GitHub as code host, CDN for artifacts, package registry backend, CI/CD, and Pages host.
• Some view GitHub’s recurring incidents as evidence of declining reliability post‑acquisition; others note outages are inevitable at scale.
• Several advocate mirroring to GitLab, Gitea, Codeberg, self‑hosted forges, or keeping offline mirrors; some report excellent uptime with self-hosted Gitea or GitLab.
• Others remind that git itself is distributed and works fine locally; the real problem is centralizing collaboration, CI, and distribution on one service.

UI, culture, and reactions

• The whimsical “unicorn” error page divides opinion: some find it unprofessional during serious outages, others prefer it to sterile corporate language.
• Thread repeatedly uses HN itself as an ad‑hoc “real” status page, praised for speed but acknowledged as informal.

Perceived value and usefulness of news

• Many say modern news is “infotainment”: high volume, low signal, little that’s actionable in daily life.
• Some report dropping news entirely (except maybe weather or very local info) without noticing any downside.
• Others argue journalism is a public good: essential for democracy, corporate oversight, and local accountability, even if individuals don’t feel direct benefit.

Price, paywalls, and subscription fatigue

• Common complaint: individual subscriptions are too expensive relative to usage and competition for attention (e.g., $300+ /year per outlet).
• Friction and “dark patterns” around cancelling are a major deterrent.
• Many want per-article purchase or small occasional payments but almost no outlet offers this in a simple way.

Fragmentation and desire for bundling

• People discover articles via aggregators (HN, Reddit, social media), then hit random paywalls. Subscribing to every source is unrealistic.
• Frequent wish for a “Spotify/Netflix for news” or an Apple-News-like megabundle that covers most major outlets.
• Some suggest usage-based allocation from a single monthly “bucket” rather than per-site subscriptions.

Micropayments debate

• A group wants true micropayments (cents per article) integrated at browser level.
• Others argue this has been tried for decades and fails: low revenue share for publishers, high sales friction, and cost of operating many tiny transactions.

Advertising, business models, and history

• Several point out that cheap print papers were always ad- and classifieds-funded; readers mostly “paid with attention”.
• Loss of classifieds and failure to capture digital ad value (ceded to Google/Facebook) hollowed out news finances.
• Some argue newsrooms also failed to adapt product-wise (data products, better digital formats).

Public funding vs independence

• One camp favors tax/fee-based models (like BBC, CBC, ABC, NPR) or ISP-level “media fees” to create a funding floor for many outlets.
• Critics fear state capture and propaganda; cite politicized public broadcasters as examples.
• Proponents reply that support can be diversified (multiple jurisdictions, indirect subsidies, legal notices), not a single “Ministry of Information”.

Quality, bias, and trust

• Strong complaints about bias, clickbait, shallow or incorrect reporting, especially where journalists lack domain expertise.
• Some see public broadcasters and a few business-focused outlets (e.g., FT, Economist, WSJ) as relatively higher quality; others consider them captured by elites.
• There’s broad agreement that all outlets have biases; dispute is whether any remain sufficiently factual to be worth funding.

Local vs national news

• Many lament the collapse of local papers: loss of city council coverage, investigative work, and cultural listings.
• Evidence is cited that areas without local papers see more corruption and worse governance.
• Yet local subscriptions are often very expensive for thin, wire-heavy products, so even sympathetic readers hesitate.

Alternative formats and platforms

• Several praise Wikipedia for complex, evolving stories: clear overviews, extensive references, and transparent edit histories and talk pages.
• There’s interest in news orgs adopting “Wikipedia-like” living pages for major stories instead of endless disconnected articles.
• New startups aim to aggregate verified journalists into feeds and monetize headlines, but are still experimenting with funding.

Mental health and opting out

• A noticeable subset avoids news entirely for anxiety and mood reasons, seeing it as a stream of negativity they can’t affect.
• Others argue at least some citizens must stay informed for democracy to function, but concede current formats over-emphasize engagement and outrage.

What the breach contains and how “real” it is

• Leaked data appears to come from a US data broker branded as “National Public Data.”
• Core dump: two huge ssn.txt files (~300 GB uncompressed, ~2.7B lines) with US-only records; fields include name, DOB, address history, county, state, ZIP, sometimes phone and aliases, and SSN as last field.
• No email addresses in the SSN files; separate bundled “breach” packages on forums mix this with other datasets that do have emails, causing confusion (e.g., non‑US people getting HIBP notices).
• Users checking themselves and family report: often correct names, addresses, SSNs; sometimes DOBs or addresses are partial or wrong; occasionally the SSN matches but everything else is nonsense.
• Consensus: not a “full” leak of all broker data, but a large, real, and now-irreversible public exposure.

Impact of exposed SSNs and “identity theft”

• SSN is widely used in the US as both identifier and de‑facto password. With DOB and address, attackers can: open credit lines, take loans, impersonate for password resets, commit tax-refund fraud, etc.
• Some argue SSN “security” has been dead for years; real problem is institutions still treating SSNs (and past addresses, mother’s maiden name) as authenticators.
• Several commenters frame “identity theft” as rebranded bank/creditor fraud, shifting blame and cleanup costs from companies to individuals.

Data brokers, privacy, and opt‑out services

• Strong hostility toward data brokers: seen as aggregating and monetizing sensitive data without meaningful consent, enabling discrimination, stalking, and exploitative profiling.
• Suggestions that adding fake/noisy data is dangerous: even fictitious profiles can skew aggregate stats used for pricing, insurance, and policy decisions.
• Multiple opt‑out tools mentioned (commercial and nonprofit). Experiences:
  • They can reduce “people search” visibility somewhat.
  • Effect often decays; data reappears via new feeds and broker‑to‑broker sharing.
  • Some removal services are owned or influenced by the same brokers.
  • Consumer Reports testing found modest effectiveness at best; no solution is close to 100%.
• Technical debate over how brokers could honor permanent opt‑outs (hashes, Bloom filters, shared services) vs claims it’s “impossible” and that brokers have no incentive to try.

Regulation, liability, and legal angles

• Many call for GDPR‑style federal privacy law or stronger CCPA‑like protections: explicit consent, clear limits on use, and real penalties.
• Popular proposal: make aggregators and relying businesses strictly liable for misuse and breaches—e.g., large per‑person statutory damages paid directly to affected individuals.
• Others suggest:
  • Outright banning or tightly constraining data brokers.
  • Prohibiting SSN use outside Social Security.
  • Making SSN legally invalid as authentication; any fraud relying on it is prima facie the company’s problem.
  • Taxing data storage/centers to disincentivize hoarding.
• Counterpoint: in the US, broad bans on collecting and sharing factual information collide with First Amendment protections; advocates suggest focusing on liability instead.
• Some debate whether HIPAA/GDPR‑style regimes do more good than harm; others say industry “HIPAA/GDPR is too hard” complaints are mostly foot‑dragging until real enforcement appears.

Technical notes on accessing/inspecting the leak

• Dataset is distributed via public torrent; contents are unencrypted text once extracted.
• Users describe using command‑line tools (grep/equivalents) to search for SSNs or names; searches over 100–200GB text can take minutes but are feasible.
• Separate web tools (e.g., npd.pentester.com) allow quick checks against the SSN files without downloading them, though legality/ethics of using the raw torrent is debated.

Debates around HIBP and breach‑notification services

• Some appreciate HIBP as a trusted, audited service with rate‑limited APIs and offline password‑hash datasets; others distrust any intermediary collecting emails/IPs “in the name of helping.”
• Critics see monetization (paid APIs, partnerships) as profiting from breaches; defenders argue the scale and ongoing work need funding and are better than opaque corporate handling.
• Important nuance: HIBP only shows email presence in a breach package; given this NPD bundle stitches multiple sources, being “pwned” here does not necessarily mean your SSN is correct or present.

Identifiers, national ID, and future fixes

• Several suggest moving away from SSNs toward stronger, cryptographic identity systems:
  • Government‑backed PKI on smartcards or NFC IDs (as used in parts of Europe).
  • Wider use of login.gov or similar federated identity, possibly open to private sector.
• Others warn that universal, easily checked IDs can also supercharge surveillance and oppression; debate centers on whether better IDs reduce harm or mainly make bulk tracking easier.
• Examples from Australia and Europe: bans on repurposing government ID numbers, digital‑ID initiatives with chips and signatures, and mixed public acceptance.

Practical defenses individuals discuss

• Recommended actions:
  • Freeze credit at the major bureaus; consider IRS IP PIN for tax filings.
  • Avoid giving SSN when not strictly required; refuse optional SSN fields.
  • Use unique email aliases and, where possible, fake names/virtual cards for low‑trust vendors to limit linkage.
  • Periodically search for and manually request removal from people‑search sites; use opt‑out tools to automate some of this.
• Many feel resigned: between this and earlier mega‑breaches, they assume their SSN and core PII are effectively public; focus shifts from secrecy to limiting institutional misuse.

Overall reaction to the write-up

• Many found the post fun and well-written, especially the detailed reasoning and math around contest odds.
• A minority found it tedious or over-validated, arguing that it might be faster to just enter more contests than to analyze one heavily.
• There’s some meta-discussion about Hacker News norms: shallow dismissals vs constructive criticism, and apologies from commenters who felt they were too harsh.

Strategy, odds, and “gaming” contests

• Several readers praise the systematic approach: reading rules carefully, exploiting judging criteria, picking contests with multiple prizes, and allowing multiple entries.
• Others argue that if someone wants to be good at contests, volume and practice (many “good enough” entries) would likely beat deep analysis of a few.
• Multiple parallels are drawn to art shows, engineering competitions, grant applications, and hackathons: closely following the brief/rubric and nailing paperwork often beats superior raw “art” or engineering.
• Some note that revealing detailed tactics risks eroding the author’s advantage if many others adopt the method. Contest discovery is deliberately kept as a “trade secret,” which some see as making the post less reusable and closer to a soft ad for consulting.

AI use and the “enshittification” debate

• Supporters see this as a good example of using LLMs and AI TTS to turn skills into income, reduce friction, and speed tedious parts (voiceover, music) while keeping human scripting, filming, and editing central.
• Critics worry it exemplifies incentives that favor AI-assisted “pipelines” over human-centered art, potentially diverting money from traditional artists and contributing to a “dead internet” full of low-effort content.
• Others counter that the entries were still substantively human-made, that AI here boosted individual productivity rather than replacing creativity, and that the real edge was rule-reading and multiple entries.

WD‑40: lubricant or not, and environmental optics

• Large subthread debates whether WD‑40 is “really” a lubricant versus mainly a solvent/water-displacer.
• Consensus: it does lubricate but is often a mediocre or short-lived choice compared to specialized products; misuses (locks, bike chains, bearings) can wash out better lubricants.
• Some note niche cases where it excels (e.g., machining aluminum).
• Spraying it on a stump/tree in one losing video raises concerns about environmental impact and brand optics; several speculate that this may have hurt that entry’s chances despite its production quality.

Value of participation and side benefits

• Multiple anecdotes show that simply “showing up and trying” often wins in low-competition or poorly-followed contests.
• Commenters frame contest-entering as a hobby or “video game” rather than pure income maximization, with benefits like portfolio building, learning tools (e.g., Playwright), and personal enjoyment even when payouts aren’t high.

Medical slang: “crump” vs “crash”

• Multiple medical commenters say “crump” means rapid deterioration, usually less abrupt than “crash.”
• “Crashing” implies immediate, dramatic decline needing instant action; “crumping” can be a more gradual but serious worsening over hours.
• Some use the terms interchangeably; nuance and severity are somewhat debated.

Flow vs procedure, and crisis leadership

• Central theme: “flow is king” in mass casualty events—reducing bottlenecks (CT, meds, triage) to maximize lives saved.
• Commenters stress that many safety procedures (double checks, radiologist reads, strict narcotics control) are optimal in normal operations but harmful when volume makes catastrophe the default outcome.
• Key leadership behaviors highlighted: anticipating chokepoints, rapidly descoping roles, trusting professionals’ judgment, constantly scanning the big picture, and being willing to deviate from protocol.
• Some worry about over-glorifying “move fast and break things”; they emphasize that in normal times, meticulous procedures prevent errors and are preferable.

Procedure vs results tension (including in tech/aviation)

• Extended discussion on when it is acceptable to break rules.
• Some argue that rules exist precisely because not everyone judges risk well; others note that all procedures are written for typical cases and must bend in true emergencies.
• Aviation is cited: pilots may violate rules in emergencies by design.
• In software, anecdotes show both successful and disastrous rule-breaking; distinguishing justified exceptions from overconfidence is hard.

CT/X-ray and throughput optimization

• Several commenters dissect how pairing radiologists with techs and bypassing EMR/billing can vastly improve throughput and latency.
• Trade-off noted: skipping proper labeling and integration creates downstream chaos, but in an MCI, immediate care outweighs future documentation burdens.

Mass casualty planning, triage, and ambulance distribution

• Some systems (e.g., in Europe, U.S. trauma networks) have explicit plans for hospital load balancing and MCI workflows, though improvisation is always needed.
• Triage tags, simple identifiers (even marker-on-forehead), and predesignated roles are discussed as crucial tools.

Other themes

• Interest in disaster psychology/planning books and “swarm leadership” concepts.
• Brief debate on using AI to second-guess doctors; some see empowerment, others see serious risk.

Overall Reception

• Very positive reaction; many describe it as “addictive,” “mesmerizing,” and “surprisingly compelling” once tried.
• Several say it’s the best thing they’ve seen in a while and bookmark it for repeated use.
• A minority explicitly dislike the TV‑like experience or find it equivalent to “doomscrolling” with less control.

Nostalgia and UX

• Strong nostalgia for 80s/90s channel surfing: limited choices, serendipitous discovery, and shared “everyone’s watching the same thing” feeling.
• People enjoy dropping into the middle of videos, skipping intros and “like/subscribe” fluff.
• The “always running” streams and FOMO of missing content make it feel more like real TV and, paradoxically, more relaxing than on‑demand choice.

Channel Model & Curation

• Channels are topic‑based (science, travel, food, documentaries, music, etc.), with videos hand‑picked and scheduled so all viewers see the same thing at the same time.
• Some worry manual curation may not scale or will stagnate; others suggest search‑based or community‑driven channel lists.
• Users request more genres (sports, kids, DIY/maker, game shows, local/hobbyist, cartoons).

Desired Features vs. Simplicity

• Common requests: TV guide/schedule, channel labels, per‑channel permalinks, direct links to the current YouTube video, captions, volume and quality controls, keyboard/remote controls, app versions (TV, Roku, Fire TV, PWA), language filters, and personalization (e.g., based on subscriptions or keywords).
• Several argue against feature creep; they value the minimal, non‑interactive, non‑algorithmic feel.

Technical / Implementation Notes

• Implemented as static HTML/CSS/JS with YouTube iframes; no backend beyond a file server.
• A list.json file provides per‑channel schedules and is refreshed when needed.
• Static “snow” transition is widely liked for atmosphere but criticized for tiling, repetition, and eye strain; some want it tunable or removable.
• Some report issues with autoplay blockers, certain browsers, SSL errors, or buffering.

Comparisons and Alternatives

• Compared to old broadcast/cable, SiriusXM, radio, Netflix’s former “shuffle”/linear channel, Pluto TV, Shudder linear channels, Plex/Jellyfin + ErsatzTV/DizqueTV/QuasiTV, retro TV sites, and TikTok/Shorts.
• Many see it as a better discovery layer on top of YouTube’s catalog than YouTube’s own UI.

Concerns & Broader Reflections

• Worries about ads, monetization pressure, and possible YouTube policy conflicts or blocking.
• Some raise ethics of crediting creators more clearly and relying on YouTube’s ad/compensation system.
• Thread includes broader reflections on decision fatigue, recommendation algorithms, loss of shared culture, and the appeal of “turn it on and don’t choose” media.

Overall reaction to the Texas v. GM lawsuit

• Many are strongly supportive, hoping other states target GM and other automakers doing similar data sales.
• Some praise Texas for once “being on the right side,” while others highlight perceived hypocrisy given Texas’s broader record on privacy (e.g., medical and library data).
• A minority is skeptical that big settlements meaningfully help victims, seeing them as windfalls for the state rather than systemic fixes.

Legal and policy questions

• Commenters note Texas’ privacy law (TDPSA) appears to require consent for this type of data sharing; others compare it to CCPA/CPRA and GDPR.
• Debate over whether insurers’ use of improperly obtained data should itself be illegal; some argue you should not be allowed to profit from illegally acquired data, others question what specific insurance rules would be violated.
• Several want GDPR-like or HIPAA-like protections, especially for location data, with strong fines or private rights of action and treble damages.

Vehicle telematics, tracking, and user control

• Multiple people report trying to disable cellular or telematics modules via fuses, antennas, or dummy loads; often this breaks other features (hands-free calling, GPS, etc.) or triggers warning lights.
• Some deliberately buy older or simpler cars, or pull data-communication fuses on new ones, to avoid tracking.
• Others like connected features (remote lock/unlock, “find my car”) but only if data isn’t sold; subsequent digging into policies (e.g., Ford) suggests such data is often shared or sold by default with opt-outs buried.

Insurance use of driving data

• One camp argues more granular data makes pricing fairer: unsafe drivers should not be subsidized by safer ones, and high-risk driving should become more expensive.
• Another camp stresses privacy, noisy/biased metrics (hard braking in bad infrastructure), and the social role of insurance as risk-pooling rather than hyper-individual pricing.
• There is extended argument over whether “too efficient” risk segmentation increases uninsured driving, worsens outcomes for poor and rural drivers, and undermines the social safety function of mandatory liability insurance.

Accountability and penalties

• Broad agreement that fines must exceed the profits from illicit data sales; cited figures (cents per car) make GM’s behavior seem especially egregious.
• Many call for personal accountability: jailing executives, clawing back board compensation, even revoking charters, rather than only fining corporations and indirectly harming workers.
• Others warn about over-penalizing to the point that big employers become “too big to punish,” reviving bailout dynamics.

Broader themes

• Strong sense that almost all modern automakers are doing similar tracking; GM is seen as a visible example, not an outlier.
• Some tie the issue to US car dependency: as long as cars are unavoidable, people are effectively coerced into pervasive surveillance.
• There is tension between wanting modern safety/efficiency electronics (ABS, EFI, ECUs) and rejecting always-connected infotainment and data monetization.

Corporate ownership and data-broker questions

• Commenters find it suspicious that “National Public Data” is a subsidiary of a film/TV production company (Jerico Pictures), questioning what business model connects media production and mass personal data brokerage.
• Some argue it may be just a holding structure; others think there’s “more than meets the eye.”

SSNs: identifier vs. authenticator

• Broad agreement that SSNs were never designed to be an authentication secret but are treated as one.
• Many see SSNs as useful unique identifiers but inappropriate as proof of identity.
• Several argue that once all SSNs are effectively public, using them as an authenticator becomes impossible (which some consider a good forcing function).

Pervasive leaks and “already compromised” mindset

• Many assume all SSNs were effectively leaked long ago via breaches at DMVs, credit bureaus, federal agencies, employers, schools, etc.
• Some say they “don’t care” anymore and behave as if their SSN is fully public.

Responsibility, liability, and “identity theft” framing

• Strong sentiment that current regimes externalize fraud costs onto individuals via the “identity theft” narrative, instead of treating banks and lenders as primary victims of their own lax verification.
• Disagreement on how burdens of proof work in practice: some say banks effectively make you prove you didn’t take the loan; others say it’s an adversarial but conventional legal process.

Regulation and punishment proposals

• Calls for new laws imposing personal criminal liability on executives (not just CISOs) for negligent data retention and bulk-extraction vulnerabilities, plus heavy financial penalties.
• Skepticism this would work in practice due to shell companies and perverse incentives.
• Others argue the real problem is lack of economic incentives to secure data, not impossibility.

Replacement identity systems and national ID debate

• Suggestions: cryptographic ID systems (public identifier + private secret), PKI-based schemes, or government-issued chip-based cards similar to many European systems.
• Counterpoints: identity is more than credentials; keys can be lost; strong root-of-trust systems can also be abused for surveillance.
• US attempts at better IDs face political resistance (fears of government tracking, “mark of the beast” rhetoric), despite de facto national identification via SSNs and Real ID.

Practical user defenses

• Common advice: freeze credit with major bureaus (and sometimes ChexSystems) and use IRS tax filing PINs.
• Frustrations with credit monitoring as a default “remedy” and with bureaucratic friction around freezes/unfreezes.

Anecdotes illustrating misuse of SSNs

• Past widespread use of SSNs as student IDs, printed on transcripts and grade sheets, and as driver’s license numbers.
• Ongoing practices where businesses demand copies of driver’s licenses and other ID documents, potentially adding more attack surface.

Overall view of the book

• Many commenters label the book as charlatanism or near-fraud: unsophisticated, full of vague stories and hype, with very little concrete, actionable guidance.
• Several say the main person who got rich from it is the author, via book sales, seminars, and brand-building.
• Others argue it was influential for naive readers at the time of publication, especially those with no exposure to business or investing, by challenging “get a job, stay in school” as the only life script.
• Some see it primarily as a motivational/self-help text, not a technical finance manual.

Real estate, leverage, and risk

• The most-criticized advice is aggressive use of mortgage leverage and “rental pays for everything” real-estate schemes, which many call unrealistic or dangerous, especially in today’s housing markets.
• Commenters note that real-estate success depended heavily on time and place (e.g., past booms), and that many landlords underestimate vacancies, maintenance, legal risk, and management effort.
• Several point out the role of leverage: apparent high returns often disappear once interest, taxes, and downturns are accounted for.

Ethics, “fraud,” and rich behavior

• A disputed anecdote about inserting a “partner approval” clause where the “partner” is actually a pet is cited by some as straightforward fraud; others note the book itself frames this as a didactic exaggeration.
• There is broader debate over whether most rich people necessarily use borderline-fraudulent tactics, with strong disagreement on how common unethical behavior is on the path to wealth.

Mindset vs. mechanics

• Supporters emphasize useful high-level themes:
  • Focus on assets that generate income and appreciate.
  • Avoid lifestyle creep and consumer debt.
  • Aim for ownership or business-building rather than only wages.
• Critics say all of this could fit on a page, and the book offers no real “how.” It encourages risk-tolerance and optimism without teaching risk management (e.g., variance, downside scenarios).

MLM and guru ecosystem

• Multiple comments link the book’s popularity to multi-level marketing networks, where it was pushed as motivational material to keep recruits engaged.
• The book and its spinoffs are seen as part of a broader “get rich”/self-help industry where selling the dream is itself the main profitable business model.

Alternatives and better resources

• Many recommend basic index-fund investing, high savings rates, and simple, diversified portfolios over real-estate speculation.
• Other personal-finance and business books, plus freely available guides (e.g., index-card/three-fund style advice), are cited as more concrete and trustworthy.

Personal experiences with parenthood

• Several commenters have kids and describe them as the most meaningful, transformative part of life; some wish they’d had more, others would not repeat the choice given current conditions.
• A number of people want kids but feel blocked by finances, housing, career timing, health issues, or country conditions.
• Some parents report strained relationships or deep struggles (e.g., disabilities, autism) and say they would not choose parenthood again.
• Childfree commenters say they simply don’t believe kids would make them happier and appreciate that it has become a genuine choice.

Economic and structural factors

• High housing costs, unstable jobs, long work hours, and expensive childcare/education are repeatedly cited as major deterrents.
• Some argue weak worker protections and fear of retaliation around pregnancy or caregiving make family formation risky.
• Others note that low fertility persists even in countries with strong social safety nets and parental protections, so economics alone is insufficient.

Cultural and psychological factors

• Perception that today’s parenting standards are impossibly high, with overprotective norms and intense social/media judgment.
• A pervasive sense of “doomism”: climate change, inequality, political instability, and loss of an optimistic future narrative make people hesitate to bring children into the world.
• Some compare humans to overcrowded rat experiments where stressed environments change behavior in lasting ways.

Ethics and “selfishness” debate

• One side: not having kids while benefiting from society is framed as free‑riding; reproduction is seen as contributing to future taxpayers and social systems.
• Opposing side: having kids is inherently self‑interested (desire for love, legacy, old‑age care) and adds to environmental strain; it’s not a noble act.
• Many agree that motives for kids (or not) are often rationalizations and that both regret having kids and regret not having them exist but are unevenly voiced.

Demographics, policy, and immigration

• Discussion of sub‑replacement fertility as a “demographic collapse” vs a desired easing of overpopulation; strong disagreement on which is the bigger risk.
• Some predict immigration will be used to offset low birthrates; others argue immigration both results from and reinforces high costs and can form a feedback loop.
• Video data point highlighted: a large share of the US fertility drop is due to fewer births among 15–19‑year‑olds, an intended outcome of better contraception and norms.

Future outlook

• Speculation ranges from “this is the best time to be alive” to “I wouldn’t want my hypothetical grandchildren facing the 2060s.”
• Unclear how societies will adapt: possibilities include greater reliance on immigrants, slower growth, or painful adjustment to aging, smaller populations.

Overall reaction

• Many commenters are delighted by the creativity; repeatedly described as “wild”, “ridiculously smart”, and a “wonderful abuse” of OpenType.
• Others see it as a “horrible hack” or “atrocious” in principle, but still impressive as an experiment.
• Several predict niche but real adoption (e.g., blogs, CMS textareas, presentations), and joke about big tools rushing to add it.

How it works and expressiveness

• Uses OpenType contextual alternates (calt) plus color glyph tables (COLR/CPAL) to recolor glyphs based on surrounding characters.
• Clarification that colr is not an OpenType layout feature, and calt is usually on by default; the CSS font-feature-settings line is mostly unnecessary.
• Base rule system is simple: match single characters or character classes in context.
• Multiple commenters argue it’s more powerful than the article suggests: you can effectively drag a finite-state machine along via chained substitutions (including reverse chains), allowing regular-language–level logic.
• Concrete examples show how to implement quoted-string highlighting and escaping purely with substitution rules.

Performance and behavior

• One informal benchmark on ~20k lines of CSS: enabling calt made a font-size change reflow take ~1.6s vs ~100ms with calt off.
• Large documents feel laggy when layout depends on heavy shaping, since it affects scrolling, resizing, and selection.
• Some browser bugs/quirks noted (partial highlighting in Chromium when typing, Safari regressions for COLR support in certain versions).

Tooling and automation

• Font editors mentioned: Glyphs (with Python scripting), FontForge (harder UI), emerging browser-based tools; any editor that allows manual OpenType feature code can, in principle, support this.
• Ideas to:
  • Generate fonts automatically from grammars (e.g., TextMate, tree-sitter) and color themes.
  • Embed fonts via base64 @font-face.
  • Build an online generator for “syntax-highlighted fonts”; blocked somewhat by tooling (e.g., opentype.js missing calt support).

Use cases, strengths, and limitations

• Big advantages: no JS, no DOM span explosion, works in plain <textarea>, can be used wherever only a font is configurable (e.g., Notepad, terminals in future, some PDFs/editors with OpenType support).
• CSS @font-palette-values and font-palette (with override-colors) allow recoloring without regenerating the font, at least in supporting browsers.
• Major limitations:
  • Not language-aware enough for full IDE-grade highlighting: keywords inside plain prose, strings, or embedded languages can be miscolored.
  • No bracket-depth coloring; hard to robustly handle multi-line comments/strings given limited context and partial repaints.
  • Needs different fonts (or variants) per language and, in some environments, per background/theme.
• Some see it as neat but impractical compared to traditional highlighters or CSS Highlight API; others argue it’s perfect for static publishing where any JS is undesirable.

Security and broader implications

• Several note this illustrates why fonts are a real attack surface: they can embed complex behavior; past font-related exploits are cited.
• One commenter refuses to load the demo out of concern about malicious ligature logic.
• The project prompts broader appreciation of how overpowered font technology is (e.g., prior work like games or even LLMs embedded in fonts).