Hacker News, Distilled

AI, Recommendation Systems, and Profit Motives

• Commenters expect restaurant AI to mirror retail recommendation engines: repetitive, profit-driven, and not genuinely personalized.
• Consensus that AI will primarily steer diners toward higher-margin items, not maximize their enjoyment.
• Some explicitly liken this to how social media is “for our benefit” in name but actually optimizes engagement/profit.

Menu Psychology and Its Validity

• Skepticism that “menu engineering” is overhyped consulting psychology with dubious statistics.
• Others note the restaurant industry has tracked numbers for decades and claims at least some measurable impact.
• One simple, data-backed tactic: frequently remove or change the least-popular dish to increase overall demand.

Choice Architecture, Specials, and “No-Decision” Dining

• Multiple anecdotes of chefs and small places where the cook or server simply decides what you eat (yachts, diners, taco trucks, fixed lunch spots, Indian restaurants).
• Many diners welcome this: it reduces decision fatigue, feels like home cooking, and often yields reliably good meals.
• Staff recommendations can strongly shape what sells; servers effectively “choose” desserts for guests.
• Some treat “daily specials” and asking “what would you eat?” as a reliable strategy and quality signal.

Dietary Restrictions and Allergies

• Concern that “you’ll get what we serve” models clash with modern allergy/dietary patterns, especially in the US.
• Observations (not settled science) that severe food allergies seem more common in the US and younger generations; proposed but unproven causes include pesticides, food processing, or changing child-feeding habits.
• Reports from Japan: restaurants posting signs refusing guests with restrictions, largely targeting foreign tourists.

Salt, Taste, and the Dorito Effect

• Many complain about oversalted restaurant food; some say it’s a dealbreaker.
• Explanations offered:
  • Chefs adapt to customers accustomed to high-salt processed foods.
  • Taste perception varies widely; “supertasters” find normal seasoning excessive while others add more salt.
  • Some chefs’ palates may be dulled (e.g., from smoking).
• Linked idea: the “Dorito effect” of amped-up flavors driving higher seasoning expectations.

Pricing, “Market Price,” and Social Friction

• “Market price” (especially for lobster/crab) deters some diners who dislike asking costs, appearing price-sensitive, or refusing after hearing the number.
• Others explain M.P. as a practical response to highly volatile seafood costs and menu printing expenses.
• Some restaurants post daily prices on chalkboards; others rely on servers to provide M.P. on request, which can still feel awkward.
• Debate over tech fixes (QR codes) vs. high-end norms that avoid phones at the table.

Menu Language, Burgers, and Luxury Signaling

• Discussion of $20–$30 gourmet burgers versus simple $8 burgers; “elevated” burgers seen by some as a genuine niche, not pure scam.
• Trend in upscale menus toward minimal, ingredient-list style descriptions rather than adjective-heavy marketing prose.
• Observation that “fresh” rarely appears on fine-dining menus because freshness is assumed; calling it out can imply other items aren’t.
• Foie gras appears as a stereotypical luxury upsell; some object to its ethics and are surprised it remains fashionable, while others argue the animals are relatively well treated compared to industrial poultry.

Service Tactics and Wine/Menu Tricks

• Noted tactic: giving a table only one wine list nudges people to share bottles instead of ordering individual drinks.
• Some diners report modern servers responding to “what’s good?” with unhelpful scripts like “it’s all good,” possibly due to corporate training or fear of complaints.
• More effective approach described:
  • Narrow to a few items and ask for a preference.
  • Use playful questions (“if X and Y fought, which wins?”) to elicit honest recommendations.
• Several argue the best “menu engineering” is simply: only serve dishes you execute very well with consistently fresh ingredients.

Ethical Concerns About “Tricking” Diners

• Some readers dislike how the article frames psychological tactics—like anchoring with very expensive items—to increase spend as something clever or celebratory.
• They argue menu design could be optimized for satisfaction and happiness rather than revenue alone, and criticize the coverage for not challenging profit-maximizing framing more forcefully.

Scope and Mechanics of Norway’s Wealth / Exit Taxes

• Norway has a long-standing annual wealth tax (~1% on net wealth above a threshold), applied to market value of public assets and book value of private firms, with various discounts and a lower effective rate on unlisted shares.
• An exit tax on unrealized gains (around 38%) also exists for people leaving the country.
• Critics emphasize that founders can owe tax even when companies are loss‑making or illiquid, or after values fall; supporters note credits/refunds and that this is a generic wealth tax, not a “gains-only” tax.

Fairness, Justice, and the Realization Principle

• One side argues taxing unrealized or illiquid wealth is inherently unjust, breaks the realization principle, and forces people to “sell or borrow to pay.”
• Others counter that wage earners and property owners already pay tax on revenue or value, not profit, and that justice doesn’t require waiting for realized profit.
• Some see the tax as class‑targeted: aimed at capital owners who currently avoid income tax via unrealized gains and borrowing.

Entrepreneurship and Practical Impact

• Critics say the tax is anti‑startup, adds uncontrollable risk, and discourages new companies or keeps only the already‑rich in the game.
• Defenders with local experience claim that, if planned for (e.g., structuring dividends or loans from the company), the amounts are modest and only problematic for poorly structured or weak businesses.
• There’s disagreement whether recent rate hikes have materially changed this calculus.

Loans, Collateral, and Tax Avoidance

• Some propose simply borrowing against shares to cover the tax; others note this only delays the problem and can compound via interest.
• A separate subthread debates “buy‑borrow‑die”–style strategies where the ultra‑rich borrow against assets at low rates to avoid realizing gains, with suggestions to either tax such collateralized unrealized gains or even disallow their use as collateral.

Comparisons, Property Tax, and Broader Policy Design

• Several commenters liken wealth tax to property tax, which already taxes value irrespective of realization; others point to property tax horror stories to argue against wealth taxation generally.
• Some say Norway can “afford” such policies because of oil wealth and a strong welfare state; others worry about long‑term diversification and competitiveness, contrasting Norway with Sweden’s abolition of wealth tax.
• Proposed alternatives include taxing capital gains as ordinary income, taxing vacant land and unoccupied property, and closing specific loan‑based loopholes instead of broad wealth taxes.

Background on CEO and project

• Several commenters see the CEO’s prior work on privacy-focused tech (e.g., Zcash, decentralized social research) as credibility for building a user-centric, privacy-respecting network.
• Others distrust Zcash and say they’re “more inspired by Monero,” so the same background makes them wary rather than reassured.
• Some link external writeups praising the CEO’s character and leadership, and like that the CEO is relatively low-profile compared to other social-media figureheads.

Protocol, decentralization, and data control

• AT Protocol’s design (signed posts, relays unable to modify content) is seen as a strength for integrity and spam filtering via trust scores and labeling.
• Concerns remain about:
  • How deletions/edits propagate once content has hit downstream relays.
  • How resilient the network is if the main Bluesky servers shut down, compared to more distributed Mastodon instances.
• Users appreciate that you can self-host a personal data server (PDS) and still participate if banned from the main one, reinforcing “user sovereignty.”

Moderation, free speech, and “censorship”

• Big debate on whether free speech is a narrow legal right (First Amendment vs government) or a broad social principle that should constrain private platforms.
• Some argue platforms have a right—and strong incentive—to exclude abusive or extremist content (the “Nazi bar” problem), and that freedom of speech doesn’t imply a right to an audience.
• Others worry that a culture of deplatforming undermines the broader free-speech principle, even if it’s legally allowed.
• Bluesky’s composable moderation (subscribable labelers, per-label “off/warn/hide” controls, blocklists) is widely praised as innovative, but:
  • Some fear labelers can silently escalate from “warn” to “hide.”
  • There’s controversy over labels like “Intolerance” being applied to right-leaning satire; some see that as proper labeling of bigotry, others as bias.

Comparisons with X/Twitter

• Multiple users report that new or lightly curated X accounts quickly surface racist and bigoted content, often with substantial engagement; others claim they rarely see such material.
• One side frames X as a “free speech” platform where users simply reveal their views; another cites examples of both far-right amplification and selective censorship (e.g., doxxing, specific slurs, or political content) to argue the “free speech absolutism” branding is inconsistent.
• Bluesky is described as feeling like early Twitter: fewer trolls, less ragebait, and better tools for avoiding harassment—though a minority claim it also hosts a “firehose” of low-quality, sneering content.

Enshitification, business model, and future

• Many assume all large platforms eventually “enshittify,” but some hope decentralization, benefit-corp status, and data portability will delay or limit that.
• There is skepticism about the unclear revenue model; a paid subscription offering is mentioned but not yet proven.
• Some are resigned to migrating to a new network every 5–10 years if/when platforms degrade.

Community climate and trolls

• Commenters note that the CEO attracts coordinated trolling and misogyny, visible if you enable hidden comments.
• Several emphasize that Bluesky’s tools (blocklists, nuclear blocks, labelers) make it easier to avoid trolls without banning them from the entire network, though critics see this as enabling echo chambers and coordinated mass-reporting.

Perceived Problems with LeetCode‑Style Interviews

• Many see grinding algorithm puzzles as humiliating and disconnected from real work, especially for senior engineers with long track records or open‑source portfolios.
• Complaints that questions often reward memorization of “obscure” algorithms rather than general problem‑solving or product skills.
• Some note that success is heavily correlated with recent practice; needing weeks of prep for a job you’re already good at feels wrong.
• Algorithmic tests are viewed by some as subtly ageist: older engineers never faced these in school and may be filtered out despite experience.
• For most jobs, actual work is CRUD, systems thinking, communication, and maintainability, not graph algorithms under time pressure.

Defenses and Justifications

• Others argue basic DS/algorithms are foundational, like scales for musicians or drills for athletes; demonstrating them shouldn’t be considered degrading.
• Coding screens act as a “stupid test” in a world of inflated resumes and degrees; many applicants cannot solve even FizzBuzz‑level tasks.
• LeetCode performance is seen by some as correlated with CS fundamentals, grit, and ability to reason from first principles.
• Top companies and saturated markets can afford to filter on both LeetCode and other dimensions.

Alternatives and Modifications

• Suggestions:
  • Short, relevant work samples or take‑home tasks with clear rubrics, PRs, linting, and repo usage.
  • Let candidates submit existing public work (OSS, prior projects) plus written context instead of a canned challenge.
  • Lightweight, realistic coding tasks (“type 2” LeetCode: prototype a solution to a real-ish problem) rather than puzzle‑style questions.
• Some prefer LeetCode over highly stack‑specific grilling or purely subjective “culture fit” chats.

Career Choices and Coping Strategies

• Several report avoiding or leaving traditional SWE roles because of LeetCode, moving into cybersecurity, data analysis, or ops where tests are more job‑aligned.
• Others accept the system pragmatically: grind intensely for a period, secure higher‑paying roles, then stop.
• A minority enjoys LeetCode as a hobby and claims it improved day‑to‑day coding intuition.

Broader Concerns

• Debate over power imbalance: long multi‑stage processes, unpaid lengthy exams, relocation/probation risks vs. employer flexibility.
• Tension between wanting more objective hiring and recognizing that narrow proxies can select for “LeetCode engineers” over well‑rounded ones.

Visualization & Related Tools

• Many praise the “Copper Sushi” map as visually impressive and educational about power flows and grid complexity.
• Several compare it to ElectricityMaps and other dashboards (gridwatch, energygraph, ENTSO‑E, etc.):
  • ElectricityMaps is better for real-time mix and CO₂ intensity.
  • Copper Sushi shows finer-grained transmission networks and simulated power flows.
  • It’s based on PyPSA-Eur with modeled, not actual, plant outputs; some generation and grid elements are missing or outdated.

Grid Physics, Trade, and Measurement

• Discussion on how imports/exports are determined on a synchronized grid:
  • Technically, flows across interconnectors are directly measured (current, voltage, vector product).
  • Market-wise, there’s a regulated trading system; physical flows can differ from commercial trades.
• Europe has multiple synchronous areas; Baltics are leaving the Russian/Belarus BRELL grid to join the continental system.

Nuclear vs Renewables (France, Germany, Costs, Emissions)

• Strong debate around France’s nuclear-heavy mix vs Germany’s renewable-heavy but coal/gas‑backed mix:
  • France: low CO₂ intensity (often cited as ~40–50 gCO₂/kWh), majority of electricity from nuclear; exports to neighbors; some argue nuclear was crucial for Europe’s emissions.
  • Germany: high renewables share but still heavy coal/lignite use, much higher CO₂ intensity; critics call Energiewende slow and dirty, defenders emphasize long-term downward trends and nuclear phase‑out as democratic choice.
• Disagreement on nuclear economics:
  • Some cite LCOE data showing nuclear 3× cost of wind/solar in EU/US; others cite French and Canadian experience with amortized fleets as cheap and stable.
  • New builds like Flamanville EPR seen as cautionary examples (delays, overruns); others argue costs would drop with serial construction and regained expertise.
• Waste and fuel concerns:
  • Critics point to finite uranium and lack of “safe” waste solution.
  • Pro‑nuclear voices respond that current waste practices have had no major accidents and uranium constraints are distant.

Storage, Electrification, and Flexibility

• Some argue we could cut most developed‑world emissions by electrifying heating and transport, if electricity is low‑carbon.
• Counterpoint: large-scale storage is a hard unsolved problem; claims range from needing “weeks” of storage to studies suggesting less.
• Others note:
  • Nighttime EV charging and thermal storage (water, sand, larger boilers) can shift loads without massive grid batteries.
  • Pumped hydro, especially in Alpine regions, already acts as a large “battery,” though good sites are limited.

UI/UX and Technical Feedback

• Mixed reactions to 3D map tilt: some like it, others find it disorienting; workarounds (right‑click drag, key combos, multi‑touch) are shared.
• Performance issues and missing plant names/data (e.g., closed plants still shown) are noted.

Security and Miscellaneous

• Light concern about publishing infrastructure maps; others respond that models ≠ territory and such data is already broadly available.
• Observations on EV uptake in Nordic/Baltic countries, and how cheap, clean electricity and good infrastructure support high adoption.

Scope and definitions

• Law bans platforms from providing accounts to under‑16s; children themselves are not criminalized. Existing under‑16 accounts must be deactivated.
• Large fines (up to AUD 50M) for non‑compliant platforms.
• “Social media service” is broadly defined as services whose primary or significant purpose is online social interaction, linking users, and posting material.
• Exemptions: messaging apps, “online gaming services,” health/education services, and sites like YouTube that can be used without login.
• Commenters note this definition is so generic it could cover many sites (HN, news sites with comments, Google Maps, etc.), with practical scope left to the communications minister.

Enforcement and age verification

• Law bars platforms from requiring government ID (including Digital ID) as the only age‑check; they must offer some alternative, but no method is specified.
• Many see enforcement as practically impossible without ID, likening it to piracy controls or “are you over 16?” checkboxes.
• Some discuss cryptographic or token‑based “proof of age” schemes; others point out they are breakable (e.g., selling tokens/accounts) and complex.

Privacy, surveillance, and ID fears

• Strong concern that this will evolve into de‑facto identity requirements for all online speech, enabling user de‑anonymization and government tracking.
• Others argue privacy‑preserving age proofs exist in principle, but skeptics doubt governments actually want privacy‑friendly solutions.

Child safety vs. harms of the ban

• Supporters cite serious harms from social media for adolescents (addiction, mental‑health issues, bullying, grooming), comparing this to age limits on alcohol or tobacco.
• Critics say evidence is mixed and often overstated; some internal and academic studies are contested in the thread.
• Several worry about cutting off queer, neurodivergent, and rural teens from crucial online support networks, likening it to a human‑rights issue for some.

Parents vs. state

• One camp: parents should set limits; outsourcing to government or platforms is “nanny state” overreach.
• Another: parents can’t realistically compete with trillion‑dollar attention‑optimization machines; collective rules help coordination (like smoking bans).

Circumvention and unintended consequences

• Many expect widespread evasion via VPNs, foreign or “rogue” sites, or using adults’ accounts; law may mostly impact rule‑following families.
• Some fear driving teens toward less regulated, more toxic spaces (e.g., 4chan‑style sites, dark‑web forums).

Politics, media, and process

• The bill was reportedly rushed (24‑hour consultation), with experts opposing a blanket ban.
• Some see it as “performative” pre‑election politics or legacy media lobbying against social platforms.
• Others frame it as a valuable test case: outcome metrics and “what counts as success” remain unclear.

Scope of the change

• US cloud VPS bandwidth included drops from 20TB to 1–8TB (often 1TB), while base prices also rise.
• Overage in US remains very cheap (~$1/TB), and changes hit new instances immediately; existing ones switch in Feb 2025.
• Applies only to US cloud regions; EU and (currently) dedicated servers keep old traffic terms.

Reactions to pricing and “fairness” rationale

• Many see it as a bait‑and‑switch: 90–95% less included traffic plus price hikes, framed as helping low‑usage customers.
• Several point out the stated logic (“low-usage users subsidize high-usage users”) would imply lowering prices for low‑usage customers, which did not happen.
• Others argue the old offer was clearly unsustainable and attracted bandwidth-heavy abusers; this is a correction, not malice.
• Some say the absolute increases (e.g., +€1–2/mo, +$12–19 for 20TB users) are manageable; others emphasize the % jump (400–500%) and short notice as unacceptable.

Regional bandwidth and infrastructure economics

• Multiple comments note bandwidth and peering are cheaper and more competitive in Europe; US IXPs are often for‑profit and pricier.
• Hetzner owns much of its EU network but colo’s/rents capacity in the US, making US traffic more transit-heavy and costly.
• Some speculate US launch pricing was a “honeymoon” market‑share play that backfired once heavy users piled in.

Impact on use cases

• High‑bandwidth workloads cited: DIY CDNs, VPNs, seedboxes/private torrenting, video/PeerTube, container registries, blockchain nodes, file APIs, backups.
• Low‑traffic users mostly unaffected in practice but feel anxious about future flexibility, leading some to evaluate alternatives anyway.
• A few consider shifting bandwidth-heavy workloads back to EU regions and accepting latency.

Comparisons to competitors

• Even after the change, Hetzner’s $1/TB overage is described as 10–100× cheaper than major clouds’ egress.
• Competitors named as alternatives or benchmarks: OVH (unmetered with caveats), DigitalOcean and Linode (pooled transfer but higher per‑TB), Hivelocity, others.

Communication, PR, and trust

• Many criticize the very short notice (days for new instances), email‑only communication, and “fairness” framing as insulting or gaslighting.
• Some argue this is the predictable downside of relying on unusually cheap, non‑contracted pricing; others say abrupt changes still erode trust.

Terminology: “Tariff”

• Significant confusion in US readers who interpreted “tariff” as trade/import tax, not pricing plan.
• Others note “tariff” meaning “price list/plan” is standard in German, UK, and Indian usage, so likely a translation/variety issue rather than political tariffs.

Site UX and Irony

• Many note the irony of an article praising deep reading appearing on a page made “nearly unreadable” by heavy, slow, intrusive ads and pop‑ups.
• Several users say adblockers had hidden from them just how unusable large parts of the modern web have become.

Prose Style, Accessibility, and “Elitism”

• Some find the essay’s language dense, abstract, and full of unclear metaphors, hard to pin down into concrete claims.
• Others defend discursive, reference‑rich prose as normal for literary essays and a deliberate pushback against “lowest‑common‑denominator” internet style.
• One user runs readability metrics and finds the text around US Grade 8–9, arguing that perceived difficulty is more about unfamiliar references than raw complexity.

Print vs Digital Reading

• Broad agreement that long‑form reading and reduced distraction matter; disagreement over whether print is uniquely necessary.
• Critics say the piece unfairly blames “digital” instead of the surrounding attention economy and ad‑driven platforms.
• Multiple commenters argue e‑readers (especially distraction‑free, e‑ink devices) combine most of print’s cognitive benefits with superior search, portability, and accessibility.

Attention, Education, and Short‑Form Media

• Several report younger students struggle to read anything longer than a few pages and constantly seek summaries.
• Debate over whether students using YouTube/podcasts/ChatGPT are equally educated or just “gaming” easier, changed assessment systems.
• Linked research is cited claiming ed‑tech and heavy screen use correlate with declining reading performance; others question interpretation and confounders.

Epistemology, Truth, and Media Ecosystem

• Some embrace “epistemological crisis” as recognition that all information is narrativized; others warn this slides into nihilistic “everyone has their own truth.”
• Strong thread arguing the core problem is tribalism and emotional, identity‑driven consumption, not the screen itself.
• Others highlight how modern propaganda works less by burning books and more by flooding channels with low‑signal content, making truth hard to discern.

Elites, Capital, and Information

• Long sub‑thread argues over whether “elites” have higher‑quality information or simply better tools to profit from a biased information system.
• Financial media are cited as “reliable” for specific market facts but heavily critiqued for narrow class interests and ignoring structural harms (war, inequality, environment).

Historical Parallels and Tech Panics

• Commenters recall past anxieties over writing, print, and TV, noting a recurring pattern: each new medium is blamed for shallow thinking, yet also expands access.
• Others argue the internet’s scale, speed, and personalization make it qualitatively different, not just another iteration.

Books, Self, and Passive Consumption

• Several distinguish immersive reading from “reel”/feed consumption: reading demands active imagination and sustained attention; short‑form feeds encourage fragmented, passive, often addictive use.
• Some frame algorithmic feeds as a kind of “psychological obliteration,” briefly erasing self‑awareness and leaving little lasting memory or understanding.

Scope of “mindfuck” & criticism of the list

• Many feel “mindfuck” is used loosely; the list is seen more as a generic internet-popular sci‑fi/fantasy/top‑books list.
• Several say only a small fraction of titles they’ve read truly fit the label; classics are “good” but not mind‑bending.
• Some want one‑line explanations per book, but others note this risks spoilers.
• One commenter notes that once you’ve read a few genuinely disorienting books, others feel tame by comparison.

Reading preferences & fiction recommendations

• Some readers need strong personal recommendations before investing in a book.
• Frequently endorsed novels include cyberpunk, post‑cyberpunk, culture‑wide space opera, and certain Japanese surrealist works, though opinions split on specific long novels (e.g., “1Q84” is called slow, formulaic, or overrated by several).
• Other praised titles: experimental SF about consciousness and copies (“Permutation City”), identity and social experiments (“Glasshouse”), war‑and‑consciousness stories like “Blindsight,” “There Is No Antimemetics Division,” “Hard-Boiled Wonderland & the End of the World,” and “The Wind‑Up Bird Chronicle.”
• Some mention magical realism and war novels as personally mind‑altering but not necessarily universal “mindfucks.”

Nonfiction & ideological “mindfucks”

• Several posters list religious apologetics, political philosophy, and intellectual history as life‑changing, especially for those raised to distrust “the West” or Christianity.
• Others highlight books on perception and consciousness (“The User Illusion,” bicameral‑mind theories) and occult/epistemology texts as more brain‑twisting than much fiction.
• A side discussion contrasts a popular left‑wing “people’s history” with a conservative “debunking” of it; one side sees the latter as under‑publicized correction, another dismisses it due to its publisher and ideological slant.
• Another commenter enjoys juxtaposing a collectivist history with a strongly individualist novel to “ping‑pong” between worldviews.

Debates on the West, Christianity, nationalism & oppression

• Long subthreads argue over whether critical education about Western atrocities equals “hating the West” or is necessary accountability.
• Germany’s post‑WWII self‑critique is praised by some as a model and condemned by others as self‑destructive “cultural suicide”; there is dispute over Germany’s energy policy and responsibility for emboldening Russia.
• Commenters debate whether modern societies over‑emphasize Western sins while minimizing similar abuses elsewhere.
• A side argument contrasts fictional depictions of gender oppression in Western settings with real, often worse conditions elsewhere; others push back that fictional narratives still validly address local oppression and that dismissing them reflects bias.

Historical figures, philosophy & extremism

• Some argue that major revolutionary or totalitarian texts (from communists and fascists) are obvious omissions because they “mindfucked” entire nations; others say the list rightly avoids them because their influence is catastrophic, not enlightening.
• A heated exchange examines whether certain 19th‑century philosophers meaningfully influenced fascism and Nazism. One side claims strong ideological linkage and “proto‑fascist” themes; opponents argue influence is overstated, misinterpreted, and often second‑hand.
• Comparisons are drawn between how later dictators misused both socialist and existentialist/irrationalist philosophy; participants disagree on how much blame attaches to the original thinkers.

Christianity, cosmopolitanism & patriotism

• Quoted passages from early‑20th‑century essays spark debate about whether modern “good taste” suppresses serious religious/metaphysical discussion.
• One interpretation: earlier liberals freed inquiry to find truth, whereas today truth is treated as trivial, and genuine debate is socially discouraged. Others counter that deep “cosmic truth” discussions remain common.
• Another quotation arguing that deep love of a place or church sets one against the “world” leads to debate over cosmopolitanism vs rootedness.
• One side sees cosmopolitan identity as shallow and illusory compared to rooted patriotism; another sees this rhetoric as close to “blood and soil” nationalism and potentially proto‑fascist.

Meta: list composition & site tech

• Some note glaring omissions (e.g., certain theory, philosophy, and experimental fiction; “The Anomaly”; “Poker Without Cards”) and propose additions like “Fanged Noumena.”
• One commenter criticizes the list as too large and indistinguishable from other “top 100/500” classics lists, making it hard for casual readers to find genuinely unusual works.
• Others defend it as a “pretty decent” set of recommendations that inevitably can’t please everyone.
• Brief meta‑thread comments that the host site is still not mobile‑friendly and uses very old Perl infrastructure, making modernization attempts difficult.

Concept of “abandonment” and nature’s role

• Several comments argue the framing is backwards: “abandonment” is a human perspective; from nature’s side it’s reclamation once human pressure stops.
• Multiple posters stress humans are part of nature, not outside it. The idea of a harmonious, self-balancing “pristine nature” is criticized as mythologized.
• Ecological succession and “climax communities” are described as largely debunked in their deterministic form; real ecosystems are dynamic, with cycles of collapse and regeneration.
• The “baseline problem” in conservation is highlighted: what historical state are we trying to restore, and who decides? Examples like the Salton Sea show that “restoration” depends heavily on which year you choose as the target.

Human impact, sustainability, and future energy

• Some see episodes like COVID lockdowns as evidence that ecosystems quickly benefit when human noise and disturbance pause.
• Others counter that many landscapes have been co-shaped by humans for millennia (e.g., Aboriginal land use), and that complete withdrawal is not automatically beneficial.
• There is extended discussion that industrial civilization is fundamentally unsustainable, having burned through vast fossil energy accumulated over millions of years.
• A recurring claim is that any future civilization after collapse would lack easy-access energy resources, making re‑industrialization much harder or impossible.

Depopulation, fertility, and social tradeoffs

• Ghost towns, abandoned rural areas, and shrinking cities (US Great Plains, Japan, Russia, Bulgaria) are discussed as present-day examples of “the great abandonment.”
• Large subthread on falling fertility: causes mentioned include women’s autonomy, economic precarity, high housing and childcare costs, career penalties, and weak male participation in parenting.
• Some argue low fertility is “self-correcting” via natural selection or cultural selection (e.g., high-fertility religious groups); others strongly dispute this, emphasizing culture, economics, and no observed rebounds.
• Concern is raised that aging populations threaten pension systems, stock-market-based retirements, and care capacity, with grim speculation about euthanasia or cutting elder healthcare.
• Others welcome population decline as ecological relief, while warning about rapid, compounding shrinkage once fertility stays well below replacement.

Abandoned places and wildness

• Personal anecdotes describe why homes end up full of possessions: elderly deaths, low property values, “storage” houses that are never cleared.
• Rail lines and mining towns vanish rapidly under vegetation and animal engineering (e.g., beavers), illustrating how quickly infrastructure is erased.
• DMZ, Chernobyl, and remote rural areas are cited where wildlife becomes abundant and unusually unafraid of humans, contrasting with “zoo-like” nature near civilization.

Purpose and value of rewriting history

• Many see value in rewriting only local or feature-branch history before merging: remove “oops/typo/WIP” commits, group related changes, and make each commit buildable and meaningful.
• Clean history is viewed as critical for git bisect, git blame, and understanding why code changed; small, well-described commits help debugging years later.
• Some use history rewriting to maintain internal forks of upstream projects, splitting local changes into well-isolated feature commits to ease future upstream updates.
• Rewriting may be necessary in corporate setups when author name/email changes must be applied retroactively.

Skepticism and opposition

• Others are uncomfortable with “rewriting history,” worrying it hides the real development path or weakens the audit trail.
• Some prefer “messy but complete” logs, arguing that failed attempts and PR-fix commits can provide useful context or cultural insight.
• There is disagreement on whether main should be perfectly clean vs. using merge commits and log filters while preserving all intermediate commits.

Retcon’s approach and technical aspects

• Retcon is seen as a polished GUI wrapper around git rebase -i, with its main novelty being drag-and-drop reordering and rich undo/redo.
• A key feature: when a move introduces conflicts, users can keep rearranging commits first and resolve conflicts later, all tracked in an in-memory “virtual history” before writing to Git.
• Some want more: true DAG-based drag-and-drop rebasing, better conflict resolution, and powerful commit-splitting (down to line-level, via drag-and-drop).

Comparisons to existing tools

• Alternatives mentioned: Sublime Merge, SmartGit, JetBrains IDEs, GitKraken, lazygit, jj/jujutsu (plus GUIs on top), GitButler, Fork, IntelliJ UI.
• Several note that many of these already support interactive rebasing, drag-and-drop within limits, or advanced conflict handling; opinions differ on how smooth they are.

Pricing and adoption

• Multiple commenters balk at a subscription (e.g., ~$10/month) for something used infrequently and seen as “just a nicer rebase UI,” preferring a modest one-time license.
• The developer argues subscriptions help sustain long-term development; Retcon is also available via Homebrew.
• Some doubt many will pay for a dedicated history-rewrite tool when free or existing paid tools already cover much of this workflow.

Overview

• Project is a Gradio-based WebUI that wraps existing audio/ML tools (Whisper variants, F5-TTS/E2 voice cloning, UVR5 vocal isolation, Edge-TTS, yt-dlp).
• Targeted at “content creators and developers” for cloning voices, dubbing, transcription, and YouTube processing.
• Many commenters see it as mainly an easy front-end; others note that making things easy and integrated is non-trivial and valuable.

Use Cases & Desired Features

• Interest in speech-to-speech: act a line with specific emotion/prosody and re-render it in another voice, preserving delivery.
• Creative uses: audiobooks/audioplays, tutorials where the voice owner can’t talk long, character voices for games/D&D, satire/parody, custom Home Assistant voices.
• Accessibility/identity uses: restoring or preserving voices for people losing speech; letting people uncomfortable with their natural voice (e.g., transgender users) sound closer to how they wish; privacy by masking real voice.
• Dubbing/translation: cross-language voice transfer while keeping emotion and speaker identity; auto-dubbing tools and “babelfish”-style real-time use are discussed.

Ethical Concerns & Misuse

• Strong worry about:
  • Voice scams (especially targeting elderly relatives).
  • Impersonation in spear-phishing and social engineering.
  • Revenge porn and general identity co‑option.
  • Undermining voice actors’ livelihoods and “stealing” their distinctive performance.
• Some argue cloning celebrities or public figures for entertainment is satire; others see it as clearly over a line.
• Several note that voice is a biometric and core part of personal identity.

Regulation, Responsibility & Social Adaptation

• Debate over whether technology creators are morally culpable given known misuse patterns.
• Some argue harms from “rogue actors” justify regulation of tools or compute; others say regulating open-source tools is practically impossible.
• Counter-arguments point to past “impossible to regulate” claims (internet, sales tax, GDPR) that proved false.
• Ideas floated:
  • Strengthening right-of-publicity / likeness laws with private rights of action.
  • Mandatory licenses for cloning third-party voices.
  • Robust caller/authentication mechanisms (ID verification, digital signatures/watermarks on media).
  • Family passphrases or improved caller-ID as practical mitigation.
• Disagreement over whether concern about scams is “doomerism” or necessary risk analysis.

Security, Installation & Openness

• Multiple red flags noted:
  • Windows-only batch installer that asks users to bypass SmartScreen and possibly antivirus warnings.
  • Directory of precompiled .pyd/.dll files; some see this as incompatible with an MIT-licensed “open source” claim.
  • Hidden logic (e.g., one-click installer functions) that can’t easily be inspected.
• Defenders counter that:
  • Similar patterns exist in other popular local ML UIs.
  • Code runs in a conda/venv and mainly installs models and packages.
• Skeptical users emphasize that a venv is not a security boundary and treat the project as untrusted/malware-adjacent until proven otherwise.
• Some resort to running such tools on isolated machines/VLANs.

Licensing, Trial Limits & Business Model

• Despite MIT license, the app reportedly enforces a 30‑minute usage limit and then requires payment, with pricing hard to find (especially in English).
• Some see this as misleading for something promoted as open source; questions raised about patching/removing the limit.

Technical & Platform Notes

• No official Mac/Linux support in the packaged app; others note the underlying stack (Python + CUDA) is portable and “one Dockerfile away” from cross‑platform.
• Questions about low-RAM, CPU-only TTS; interest in alternatives like Coqui TTS, StyleTTSv2, tortoise, elevenlabs, and other open dubbing tools.
• Some suggest this project adds mainly integration and UX on top of existing libraries (“wrappers all the way down”).

Water Use and Environmental Impact

• Debate over whether the machine would use “hundreds of gallons” vs being like a water‑efficient dishwasher.
• Some argue reusing a small volume of water would be unsanitary; others note dishwashers already do this safely.
• Discussion shifts to what’s really “wasteful”:
  • One side: water itself is abundant; the main waste is energy for heating and treatment.
  • Others counter with local water stress, aquifer depletion, and infrastructure costs; abundance at global scale doesn’t help regions with shortages.
  • Several note household use is minor compared to agriculture, but still see moral value in conservation.

Hygiene, Ultrasound, and Safety

• Ultrasonic cleaning is effective on hard objects; unclear benefit on skin.
• Some recall being warned not to put hands in ultrasonic cleaners; others suspect it was mostly to prevent misuse.
• Comments note ultrasound at certain intensities can irritate or harm tissue, but the actual parameters for this device are unknown.
• Added UV/IR for “germ killing” is seen as overkill or even hazardous (especially UVC).

Use Cases: Convenience vs Accessibility

• For able‑bodied people, many see it as a fun gimmick that takes longer than a normal shower and doesn’t wash hair.
• Others think it could be valuable for people with limited mobility, restoring some independence.
• Counterpoint: the 1970 form factor (tall pedestal, water up to the neck) looks risky and hard to access; later/healthcare versions seem more plausible.

Experience, Time, and Hair Washing

• Several note that 15 minutes is longer than most showers, and the device omits hair washing, which is often the slowest part.
• Hair‑care routines vary widely; commenters push back on gender stereotypes about hair‑washing time.

1970s Futurism and Design Culture

• Many are charmed by the optimistic, “space‑age” 1970s vision of automated personal care.
• Some argue we still push human‑machine boundaries, just in different domains (AI wearables, brain interfaces) rather than appliance futurism.

Gender, Models, and Pronoun Choice

• Discussion about why the article used gender‑neutral pronouns for clearly female models.
• One side: neutral pronouns keep focus on the machine; model gender is incidental.
• Other side: omitting that they were women erases historical context about marketing, sexism, and “booth babe” culture.

Maintenance and Practicality

• Concerns that such a device would be a nightmare to clean, similar to jetted tubs.
• Question of whether people would trust or enjoy being “washed like a car,” though some admit it might feel great at first.

Related Ideas: Self‑Cleaning and Automated Sanitation

• Tangent on why we don’t have self‑cleaning public bathrooms everywhere.
• Some note self‑cleaning units do exist, but businesses often find human cleaners cheaper and see restrooms as cost centers, not investment targets.

Aluminum frames and history

• Modern aluminum road frames (e.g., CAAD8/9, Klein) are cited as the peak of light, stiff tubular aluminum design.
• Several posters recall older aluminum and aluminum–carbon frames; many failed at glued joints rather than tubes.
• Historical aluminum bikes from late 19th/early 20th century are noted, raising questions about what exactly was novel in the MIT project.

Magnesium and new alloys

• Classic magnesium frames (e.g., 1990s cast designs) are remembered as crack‑prone; casting is blamed for brittleness.
• Modern extruded or welded magnesium frames exist and some riders report good long‑term use, though welds can look rough and ride quality harsh.
• A new class of extruded nano‑laminate magnesium (LPSO alloys) is discussed: higher strength/stiffness than common aluminum, good damping, but strong corrosion issues and no commercial-scale production yet.
• Joining extruded Mg is an active research area; techniques like friction stir welding, brazing, and adhesives are mentioned with caveats (corrosion, inspectability).

Frame materials: carbon, steel, titanium, bamboo

• Carbon is praised for tunable stiffness/compliance via layup and for aerodynamic shaping; several see it as the best performance option.
• Titanium has a strong fan base but others doubt its comfort claims and note welding difficulties and cracked frames.
• Steel is liked for ride feel and durability; ultra‑light steel builds exist but are expensive and can be flexy/dent‑prone.
• Bamboo is viewed as an interesting “green” option but aerodynamically and weight‑wise inferior to carbon for high performance.

Ride comfort and vibration

• Multiple comments argue frame material contributes little to comfort; tires (width/pressure) dominate.
• Suspension seatposts and exposed seatpost flex are cited as highly effective in reducing vibration.
• Claims that aluminum or titanium “ride harsh/soft” are compared to audiophile myths: strong opinions, little data.

Weight vs aerodynamics and performance

• Repeated theme: on track and most road racing, weight matters far less than aerodynamics and rolling resistance; many modern race bikes are well above the UCI minimum.
• Some insist weight has “almost no” effect in constant‑speed track events; others point out small but nonzero effects from rolling resistance, micro‑accelerations, and center‑of‑mass motion on banked tracks.
• On steep climbs and hill‑climb events, weight is agreed to matter more; for everyday riders, body weight often dwarfs frame differences.
• Heavier riders descend faster (higher terminal speed) is defended; counterpoints mention increased rolling resistance and friction but are argued to be relatively small.

Design, manufacturing, and durability

• Larger diameter, thinner‑wall tubes for stiffness/weight are traced from the MIT ideas to modern bikes, though large tubes are disliked aesthetically by some.
• Many modern carbon design choices (oversized head tubes, press‑fit, flat‑mount, UDH) are framed as manufacturing simplifications rather than pure performance gains.
• Aluminum’s lack of fatigue limit is contrasted with steel; catastrophic failure is rare in classic diamond frames but more of a concern in forks and nontraditional constructions.
• Hiking poles and bike frames are used as anecdotes about aluminum fracture vs carbon or desired steel alternatives.

Sheldon Brown site and web nostalgia

• The linked page triggers appreciation for old‑style, content‑rich, stable websites; some note the presence of modest ads and discuss mobile ad‑blocking solutions.

Apocalypse, self‑sufficiency, and small-scale farming

• Several commenters fantasize or worry about owning a small farm as a backup if infrastructure collapses, but others note:
  • Subsistence farming without modern inputs is very different from commercial farming.
  • Even farmers are vulnerable if power and supply chains fail.
• Some argue non-farmers can adapt to manual labor fairly quickly; others say “gym fit” is not “farmer fit,” but this is disputed with concrete anecdotes.

Housing vs farmland and “subdivisions”

• The article’s reference to farms becoming “subdivisions” is read as residential development.
• Some say many farm owners deliberately aim to sell to developers; land is treated as a capital asset waiting for housing value.
• Others stress the US has a large housing shortage and object to opposing development purely to preserve unprofitable farms.
• Concern is raised about unplanned sprawl consuming prime farmland instead of doing urban/suburban infill.

Why (and how) to “protect farmers”

• One side questions why unprofitable, heavily subsidized farms should be propped up.
• Counterpoints:
  • Domestic food production is seen as national security; over‑reliance on cheap foreign food could be catastrophic if cut off.
  • Tools like subsidies or supply management keep domestic production viable but raise prices.
  • Keeping some rural economic opportunity is viewed as socially beneficial.
• Debate over whether support should favor small farms vs megafarms, and whether current subsidies do that.

Definitions, hobby farms, and tax angles

• Multiple comments note “farmer” often means landowner, not workers; this blurs who is actually struggling.
• Many “farmers” may be:
  • Hobbyists, heirs who lease out land, or high‑income people using farms as tax shelters or property‑tax reductions.
• Questions raised about:
  • What share of “farmers with second jobs” are actually hobby or part‑time operators.
  • Whether, in many cases, farming is the second job, not the first.

Consolidation, economics, and viability

• Several comments link the trend to industry consolidation: “get big or get out.”
• Small family farms struggle to compete with large, efficient operations; inputs rise, commodity prices fall, and more volume is needed just to stand still.
• Some view family farms as socially desirable but structurally undermined by corporate agribusiness, healthcare costs, and land-as-investment dynamics.

API changes and immediate impact

• Spotify shut down several Web API endpoints immediately, while grandfathering existing apps with “extended mode” access.
• Apps still in development mode and all new apps are affected; many hobby scripts used development keys and broke overnight.
• Key losses include access to recommendation endpoints and the “Audio Features” / analysis endpoints used to get per-track attributes (energy, valence, danceability, etc.).
• Some users note this also breaks improved integrations (e.g., HomeAssistant, custom playlist tools, jukebox-style apps).

Developer frustration and access model

• Extended access requires an approval process; multiple commenters say it’s slow, opaque, and often stalls for months.
• Many personal/utility projects never applied because they weren’t commercial, so they’re now locked out.
• People criticize Spotify’s framing of the change as “security,” seeing it instead as reducing user value and third‑party freedom.

Music discovery, recommendations, and lost features

• Several commenters used the API for graph‑style discovery (related artists networks), filtering by audio features, and custom radios; they report better discovery than Spotify’s built‑in tools.
• Others find Spotify’s native recommendations decent or “fabulous,” while some say they became shallow, repetitive, or payola‑like over time.
• LLMs as replacements for these APIs are widely doubted; audio analysis is seen as solvable, but not via generic LLMs, and recommendations are viewed as inherently hard.

Alternatives and self‑hosting

• Suggestions include running personal music servers with tools like PlexAmp, Jellyfin, MusicBrainz Picard, beets, and ListenBrainz, plus buying from Bandcamp or similar.
• Some point to MetaBrainz/ListenBrainz as open, recommendation‑oriented alternatives that are actively trying to fill gaps.
• Reverse‑engineering efforts (e.g., librespot, unofficial clients like psst) are mentioned, but many rely on the now‑restricted endpoints.

Artist compensation and streaming economics

• Long subthread debates whether streaming (especially Spotify’s pro‑rata model) is “terrible” for artists versus merely reflecting historic realities.
• Touring as primary income is both defended and attacked, with detailed breakdowns arguing that mid‑level tours often barely break even.
• Comparisons: Apple Music and Tidal are said to pay more per stream but may be subsidized or unprofitable; labels are repeatedly described as the main power brokers.

APIs, lock‑in, and broader trend

• Multiple commenters link this move to a wider pattern: large platforms shutting or monetizing APIs (Twitter, Reddit, Deezer, YouTube Music) after growth phases end.
• Some see this as classic “enshittification” and value extraction; others frame it as inevitable once unprofitable features are scrutinized.

What’s actually happening to the markets?

• The Corporation of the City of London voted to close Smithfield (meat) and Billingsgate (fish), with compensation for traders.
• A Private Bill is needed in Parliament to remove the Corporation’s legal obligation to run the markets; some think it will easily pass, others hope it might fail.
• Earlier plans to relocate several wholesale markets to a new £1bn site in Dagenham were dropped after large sunk costs; now the markets are to close without replacement.
• There is confusion between “850-year-old market” as an institution vs specific buildings, and between Billingsgate’s historic and current sites; commenters clarify these distinctions.

Governance and the City of London

• Discussion dives into the City of London Corporation’s unusual status: a medieval entity “by prescription,” separate from Greater London, with its own Lord Mayor, police, business votes, and a parliamentary “Remembrancer.”
• Some note Parliament could still abolish or override it; others point to protections like Magna Carta clauses.

Heritage vs redevelopment and housing pressure

• Many see the closures as cultural vandalism and short‑term profiteering, predicting luxury flats and a “plastic” version of London.
• Others argue London’s severe housing shortage justifies redevelopment, and that wholesale markets in prime central locations are outdated.
• Debate over whether high‑end housing actually eases shortages: some cite basic supply-and-demand and “filtering,” others counter with gentrification examples and price spirals.

Role of wholesale markets and food system impacts

• Some stress these markets’ logistical importance for restaurants and small retailers, comparing to central food terminals elsewhere.
• Others argue most restaurants now order via wholesalers/warehouses and that efficiency or freshness may improve without central markets; impact on prices and supply is contested and unclear.

Money, laundering, and global capital

• Several connect the City’s special status to its role in global finance, offshore structures, and alleged money laundering, especially past Russian capital inflows.

Corporate language and public reaction

• The Corporation’s statement about a “positive new chapter” that “empowers traders” is widely mocked as euphemistic corporate spin for eviction and land monetization.
• Some argue this reflects a broader pattern: heritage and working infrastructure replaced by high-rent, investor‑oriented developments and “cultural hubs.”

Local character and emotion

• Multiple commenters share personal memories of working, eating, or partying around Smithfield/Billingsgate and mourn the loss of a gritty, distinctive part of London’s fabric.

Unpatentable / “Simple” Cancer Therapies (Vitamin C focus)

• Major subthread on high‑dose IV vitamin C as an adjunct cancer therapy.
• Pro‑side:
  • Cites mechanistic work and clinical data suggesting cytotoxic effects on cancer cells, especially with IV high doses versus ineffective oral dosing.
  • Points to umbrella reviews, RCTs in advanced pancreatic and colorectal cancer, and many case reports indicating longer survival, slower progression, and better quality of life when combined with standard chemo.
  • Argues research is underfunded because vitamin C is not patentable, not because of lack of promise.
• Skeptical side:
  • Labels high‑dose vitamin C as recurrent “quackery.”
  • Notes vitamin C is broadly cytotoxic at high doses, cancers often evolve resistance, and evidence so far shows at best survival extension, not cures.
  • Cites data that some antioxidants worsen cancer; counters that this is about other vitamins, not C.
• Both sides agree: more and better trials would be needed to settle efficacy; safety of vitamin C itself is mostly established.

Cost, Complexity, and Regulation of Trials

• Many comments emphasize that rigorous clinical trials are inherently expensive and logistically hard:
  • Need for ethical design, monitoring, manufacturing quality, liability coverage, and regulatory‑grade documentation.
  • Phase III cancer trials can run into tens or hundreds of millions, with high per‑patient costs and large, complex dossiers.
• Disagreement over how much of this is genuine scientific/ethical necessity versus bureaucracy, CRO markups, and regulatory accretion.

Hospital‑Led Cancer Drug Development

• The discussed hospital‑run phase III trial (TIL therapy) is seen as a notable proof that large, late‑stage oncology trials can be done largely outside Big Pharma, with charity and institutional support.
• Others note it still relies on existing regulatory structures and isn’t a fully “pharma‑free” model.

Pharma Incentives, Doctors, and Systemic Critiques

• One camp argues: effective treatments can’t be ignored for decades because doctors, patients, and researchers are strongly motivated by outcomes and recognition.
• Counter‑camp:
  • Doctors face debt, institutional pressure, and regulatory risk; they rarely drive unproven, non‑commercial ideas.
  • Big‑trial selection is shaped by patents, profit, egos, and academic incentives, not just science.
  • Many potentially useful but unpatentable or off‑label options never get definitive trials.

Cancer Vaccines and Immunotherapy

• Cuba’s CIMAvax and other “cancer vaccines” are discussed as therapeutic vaccines: they induce an immune response against tumor‑related targets (e.g., EGF/EGFR), rather than preventing initial cancer.

Drug Discovery Limits and Reform Ideas

• Several participants highlight:
  • Poor predictive power of animal and preclinical models (especially in neurodegeneration and oncology).
  • ~10% success rate from phase I to approval; much of the total cost comes from failed candidates.
  • Calls for better mechanistic modeling, AI‑assisted prediction, and alternative funding models, but recognition that regulation and patient safety limit “move fast and break things.”

Ethics, Exploitation, and Underground Trials

• Proposals to run cheap trials on underserved populations or via apps draw strong criticism as coercive and scientifically weak.
• Claims that billionaires run private “underground” trials; not substantiated or deeply explored in the thread, but mentioned as a symptom of mistrust in formal systems.

AI and Future Disruption

• Some expect AI to transform drug discovery, forecasting efficacy from preclinical data and reducing failed trials.
• Others caution that biology’s complexity, ethics, and centralized regulation make “Uber‑style” disruption unlikely.

Anecdotes and Fringe Treatments

• The thread contains personal anecdotes (e.g., alternative protocols for Parkinson’s) and direct promotion of specific clinics/protocols.
• These are presented without corroborating data and implicitly treated by others as outside evidence, not as established therapies.

SemVer “compatibility” debate

• Many argue TrunkVer is only syntactically SemVer-compatible (three numbers + prerelease/build), but not semantically compatible.
• Objection: treating every build as a major version discards SemVer’s core meaning (“major = breaking change”), turning versions into opaque identifiers.
• Supporters respond that for trunk-based/continuous delivery, the safe assumption is “any change might be breaking,” so major-only increments are defensively correct.
• Some note the TrunkVer spec itself acknowledges it does not respect SemVer’s semantic interpretation, only the format.

Intended vs problematic use cases

• Supporters position TrunkVer for:
  • Continuously delivered, trunk-based internal services and web apps.
  • Systems where users have no choice of version and compatibility is managed socially/organizationally (coordination, rollouts), not via version numbers.
  • Tooling that expects SemVer-like strings but only needs a sortable, unique identifier.
• Critics stress it is not suitable for:
  • Libraries or APIs consumed via package managers, where compatibility ranges matter.
  • Products with multiple independent consumers, differing deployment cadences, or data/API compatibility concerns.
• Concern: once promoted, some teams will apply TrunkVer to libraries, making dependency resolution and compatibility reasoning much harder.

Timestamp and build-metadata concerns

• Using build timestamps as the “major” field:
  • Can misorder versions when old code is rebuilt later.
  • Entangles volatile data (build time, CI job ID) with artifacts, harming reproducible builds.
  • Produces long, hard-to-scan identifiers; some say a simple incrementing integer or git SHA plus external metadata lookup is cleaner.
• Git hashes are not inherently ordered; timestamps and commit dates can be manipulated, so monotonicity is not guaranteed.
• The published EBNF for TrunkVer is criticized as inconsistent with its own textual description.

Relationship to SemVer and other schemes

• Several commenters frame it as:
  • SemVer: communication/threat indicator about API compatibility.
  • TrunkVer: audit/engineering identifier for “what exactly is running where.”
• Alternatives discussed: plain sequential numbers, CalVer (calendar versions), git SHA-only, git-height-based schemes (e.g., Nerdbank Git Versioning), PEP 440, SemVer plus separate build IDs.
• Broader thread notes SemVer is valuable but imperfect; it encodes developer intent, not guaranteed reality, and is often over- or mis-applied outside library-like contexts.

Hardware vs. Firmware-Controlled Webcam LEDs

• Many assumed webcam LEDs were hardwired to camera power so they must light when the sensor is on.
• Thread shows this is often false: on the X230 and many others, the LED is firmware-controlled, so malware or buggy firmware can disable it.
• Several commenters argue this is a design failure; others note it’s “typical industry cost-cutting” and UX-driven (e.g., avoiding USB plug/unplug chimes, saving parts).
• Some describe simple hardware designs (LED tied to sensor power plus a pulse-stretcher) that would enforce minimum on-time and be non-bypassable.

Apple and Other “Good” Implementations

• Multiple comments claim modern MacBooks hardwire the LED to camera activity with a custom power-management chip that enforces a minimum on-time (~3 seconds) and prevents dimming via PWM.
• Earlier Macs and many other devices used firmware-controlled LEDs and were exploitable.
• Some are skeptical of vendor claims without independent hardware verification; others trust them due to reputational risk and technical detail shared.

Physical Shutters and Hardware Kill Switches

• Many laptops (ThinkPad, HP, Dell, Framework) now have physical shutters; some also cut power or disconnect USB.
• Framework and some privacy-focused devices add hardware switches for mic and camera, often praised as the “right” solution.
• Users also rely on tape, stickers, post-it notes, or aftermarket covers; these are widely accepted, especially in enterprise settings.

Microphones vs. Cameras

• Strong debate whether cameras or microphones are the bigger risk.
  • Camera risk: revenge porn, extortion, humiliation, persistent online images.
  • Mic risk: passwords, banking info, private conversations, keylogging via acoustic analysis, trade secrets.
• Some argue that once an attacker can access your camera/mic, they likely already “own” the system; others counter that sandboxing and permission models can isolate camera access from broader system compromise.

Trust, Threat Models, and OS/Hardware

• Security-minded users favor devices with libre firmware (e.g., X230 for Libreboot) and hardware switches.
• Disagreement over trusting proprietary systems (e.g., macOS, firmware blobs) vs. open source; some say you can’t meaningfully verify any modern stack anyway.

Practical Takeaways

• Consensus: treat indicator LEDs as advisory, not guarantees.
• Best practice: physical covers for cameras, hardware mic kills where available, and assume compromise is possible.