Hacker News, Distilled

Types as Documentation, Validation, and “First-Line Tests”

• Many commenters endorse using richer types to document data models, aid refactoring, and “make bad state unrepresentable.”
• Domain-specific types (IBAN, AccountId, UserId, Money, Percentage, TempC/TempF, absolute vs delta time/temperature) allow validation at construction and encode invariants once.
• Some describe a workflow akin to TDD but with the type checker: tighten types until a bug causes compile-time failure, then fix.

Newtypes, Value Objects, and Primitive Obsession

• The core pattern is widely recognized: newtypes / strongly typed identifiers / value objects / painted types / “safety through incompatibility.”
• It’s contrasted with “primitive obsession” / “stringly typed” code where everything is string or int.
• Examples span many languages: Go named types, Rust newtypes, C# marker-generic Id, TS branded and template-literal types, Python NewType, Nim/Ada/Pascal subranges, F# units-of-measure, etc.

Range, Refinement, and Dependent Types

• Several want bound integers and refinement types (“int in [0,10)”, array indices guaranteed in range, HTTP-status-to-response typing).
• Ada, Pascal, Nim, ATS, TypeScript tricks, F# measures, Idris, Liquid Haskell, and Wuffs are cited as partial realizations.
• Others warn of undecidability, type-level “puzzles,” recursion limits, and gnarly types that hurt usability.

OOP, Constructors, and Correct-by-Construction

• “Correct by construction” is emphasized: enforce invariants via constructors or factory functions; make it hard to create invalid UUIDs/IDs.
• Debate over exceptions vs Result/Either: checked exceptions viewed by some as powerful type-level contracts, by others as ergonomically “contagious” and noisy.

Costs, Over-Typing, and Dynamic Alternatives

• Skeptics report painful codebases where “everything is a unique type,” leading to boilerplate conversions, awkward interop, and performance worries (heap allocation, excessive conversions).
• Some argue that in many domains good tests, schemas, and dynamic validation (e.g., Clojure Spec/Malli) are more flexible and less brittle, especially for startups.
• Consensus: strong, domain-aware types are extremely valuable, but can be overdone; types, tests, and runtime checks are complementary tools, not substitutes.

Regulation, Red Tape, and Feasibility

• Many readers are shocked by how many separate rules block walkable, “European-style” urbanism, especially in the US/California.
• Some find the list “daunting” and politically unrealistic; others counter that many top items have already been implemented in NYC, LA, Nashville, Austin, etc.
• Several note that the list itself is a useful way to start a public dialogue and reveal invisible constraints (setbacks, parking minimums, height limits, etc.).
• A recurring theme: most items are removing regulations rather than adding new ones, often with no direct fiscal cost.

Developers, Markets, and Regulation

• Debate over “greedy developers”: one side argues this is an unserious trope; another cites fraud and failed projects to justify skepticism.
• One camp: loosen regulations, let developers build more, and prices will eventually fall (citing Austin and long-term underbuilding).
• Counter-camp: “market forces” stop building when prices fall; real affordability needs government-funded/social housing and cost-plus models.
• Further pushback: US housing is deeply financialized; large price drops could destabilize many households and institutions.

Quality Standards vs Affordability

• Example tension: soundproofing in multifamily/row houses. Some want strict noise and fire standards; others argue every mandate raises costs and prices out poorer households.
• Middle ground suggestions include mandatory disclosure/testing of noise performance rather than blanket bans on “lower-quality” units.

Public Safety, Crime, and Disorder

• One viewpoint: walkability is pointless without fixing what’s seen as a “dramatic decline” in public safety (homelessness, public drug use, visible disorder).
• Others respond with crime statistics showing long-term declines since the 1990s, arguing fear is driven by visibility of poverty and media focus on a few neighborhoods.
• Distinction emerges between crime vs disorder: some concede crime is down but feel day-to-day public environments have become less pleasant.

Homelessness, Drugs, and Punishment

• Hardline position: walkability is meaningless unless cities remove drug users, homeless people, litterers, vandals—primarily through punishment.
• Opposing view: punitive cycling between jail and encampments fails; root causes include unaffordable housing near jobs and lack of services.
• Another camp insists drugs and untreated mental illness are the primary drivers of street homelessness, not housing costs alone; without addressing addiction, other interventions are seen as futile.

Cars, Traffic, and Safety

• Several argue cars are the dominant public-safety threat (tens of thousands of deaths), but are culturally normalized while homeless people are treated as the main danger.
• Others highlight specific corridors where reducing car lanes for “walkability” feels dangerous due to heavy regional traffic and emergency access needs.
• Some emphasize design fixes (roundabouts, wider and better-lit sidewalks/bike paths) and note that car congestion itself slows emergency vehicles; dedicated bus/bike/emergency lanes are suggested.

Car-Free Visions, E‑bikes, and Behavior

• Some dream of car-free districts where people walk, bike, or use mobility scooters; others see past denials of “we’re not coming for your cars” as political bait-and-switch.
• E-bikes are praised but also criticized: “unlocked” high-speed models behave like small motorcycles on bike paths, creating new safety problems amid weak enforcement.
• Several note that behavior and social norms matter as much as vehicle type: inconsiderate riding/driving stresses others regardless of mode.

Politics, NIMBYism, and Implementation

• Walkable neighborhoods are in high demand and expensive, yet locals often oppose change that would make more such areas, especially near them.
• Commenters note that those who love walkability may still object when a neighbor’s lot is upzoned or fully built out.
• Some stress that entrenched interests (drivers, existing homeowners, city staff tied to regulation) make reforms politically difficult, even when fiscally cheap.

International Comparisons and Lived Experience

• Multiple references to Dutch, Norwegian, Finnish, German, and Eastern European cities: quiet centers, heavy bike use, frequent small grocery trips, and integrated bike/foot paths.
• People who have lived in walkable areas say it’s hard to go back to car-dependent life; others strongly prefer large private property over urban convenience.
• Several argue that “nice places to be” (clean, safe-feeling, socially cohesive) are what ultimately make walkability succeed; zoning and transit then follow demand.

Purpose of SQLite WAL checksums

• Several commenters argue WAL checksums are primarily to detect partial / out‑of‑order writes, not arbitrary corruption or “bit rot.”
• Checksums let SQLite know when a transaction was fully written and fsynced so it can safely treat it as committed and distinguish complete vs incomplete journal entries.
• SQLite uses checksums on both rollback journal and WAL; database file pages themselves are not checksummed by default (except via optional VFS extensions).

Why truncating at first bad frame is seen as correct

• Once a checksum fails, all subsequent frames are untrustworthy, because:
  • The WAL describes page‑level B‑tree changes; skipping frames can break structural invariants and cause deeper corruption.
  • Later frames may depend on earlier ones (e.g., page splits, pointer rewrites), so applying them without the missing changes is unsafe.
• Chaining checksums means corruption in the middle is treated like a “rockslide”: replay up to the obstruction, then stop; this leaves the DB in a state that definitely existed.
• Many see this not as “data loss,” but as rolling back untrustworthy transactions to the last known‑good state.

Disagreement over “silent” behavior and recovery options

• The article’s author and some commenters want:
  • Errors raised on checksum failure.
  • An option to preserve the WAL for manual / tool‑driven recovery or partial salvage in special cases (e.g., corrupted frames that aren’t logically needed).
• Others counter that:
  • Most applications just want a consistent DB that opens; refusing to start on WAL issues would be worse.
  • Attempts at partial application or heuristic recovery would be arbitrary and dangerous for transactional semantics.

Checksums, algorithms, and corruption scope

• Debate over Fletcher vs CRC:
  • CRCs can sometimes correct 1–2 bit errors and have stronger detection; Fletcher is seen as weaker and somewhat outdated.
  • Counter‑argument: for SQLite’s purpose (detecting partial writes), Fletcher is sufficient; full anti‑bit‑rot protection would also require page checksums on the main DB.
• Some note real corruption can occur in transit (controller, bus, memory) despite SATA/NVMe ECC, though rates and seriousness are debated.

Filesystem and storage assumptions

• SQLite assumes reasonably correct fsync semantics; if fsync “lies” or the filesystem silently corrupts data, SQLite cannot fully defend against that.
• Discussion of ZFS, ext4, btrfs:
  • ZFS’s strong checksumming is praised, but its interaction with SQLite fsync and txg timeouts can cause hangs unless tuned (e.g., sync=disabled), which then risks data loss.
  • Many databases and common filesystems still use relatively weak 16–32‑bit checksums, often disabled or metadata‑only.

Critiques of the article’s framing

• Several commenters think calling this a “PSA” about data loss is misleading:
  • The behavior is intentional, documented, and primarily about crash safety, not end‑to‑end corruption detection.
  • The simulated WAL‑only corruption scenario is considered contrived compared to broader risks (main DB corruption, full sector loss, missing .db‑shm, etc.).
• Some also object to implying SQLite is hard to contribute to or “limping along,” noting that corruption‑detection features (checksum VFS) and clear design assumptions already exist.

How the System Works and What’s New

• Many note that traffic‑actuated lights using inductive loops or radar are decades old; the Flemish system mainly adds app‑based prediction on top of existing “smart” infrastructure.
• Clarified model: navigation apps share approaching vehicles’ positions (and sometimes next turn) so controllers can turn green before cars, bikes or ambulances arrive, smoothing flow rather than just reacting at the stop line.
• Several posters stress this is a protocol integrated into existing apps, not a standalone “traffic light app” that drivers actively fiddle with.

Cost, Complexity, and Alternatives

• Supporters argue app integration is cheaper and easier to retrofit than digging up roads for more loops or cameras, and can be upgraded via a small box at the light.
• Skeptics see it as over‑engineered and fragile over a 20‑year lifecycle, citing IoT products that break when networks or apps disappear.
• Alternatives proposed:
  • Better use of existing loop/IR/camera sensors.
  • Turning or flashing lights off at night with yield/stop signs.
  • Wider use of roundabouts, which self‑balance flow and reduce crashes in many contexts.
• Some question the claimed long‑range prediction: one commenter familiar with Flanders says current practice is ~1 minute ahead and still mostly loop‑driven.

Privacy and Data Concerns

• Strong thread on privacy: continual sharing of location and route intent with government and commercial apps is seen as intrusive, especially when data can reveal origins/destinations and emergency‑vehicle movements.
• Emergency services themselves reportedly balked at similar systems over concerns about tracking and potential misuse (e.g., criminals predicting police/EMS positions).
• Others counter that governments can already track phones via networks, and prefer state access over big‑tech data mining.

Equity, Commercial Influence, and “Pay to Play”

• Concern that only users of certain commercial apps gain priority, disadvantaging others and creating a de‑facto “pay to win” mobility layer.
• Worry about private firms effectively influencing public infrastructure and monetizing government‑backed incentives with little transparency.
• A minority think this is “obviously good”: worst case it behaves like current dumb lights; best case reduces waiting, fuel use, and stop‑and‑go traffic.

Cyclists, Pedestrians, and Usability

• Frustration that many sensor‑based systems ignore cyclists, forcing them to rely on cars or “beg buttons.”
• Some cities report good results with bike‑targeted detection (induction tuned for bikes, radar, or warm‑body sensors) and even bike‑priority apps.
• Multiple commenters emphasize that any system must avoid requiring manual phone interaction while driving.

Diet vs. Exercise as Drivers of Obesity

• Many commenters agree the article’s core message matches their experience: diet changes move weight much more than typical exercise levels.
• Common heuristic: “Diet to manage weight, exercise to manage fitness.”
• Several people report large weight loss from diet alone (keto, low-carb, cutting soda/processed food) with minimal or unchanged activity.
• Others note periods of intense training (martial arts, cycling, manual labor, hiking) where they could eat “anything” and maintain or lose weight, but concede this volume is unrealistic for most people.

Calories, Metabolism, and ‘Outrunning a Bad Diet’

• Strong consensus that long‑term weight change is governed by calories in vs. calories out, with many pushing careful tracking (scales, apps, TDEE).
• Debate over how adaptive metabolism is: some argue bodies strongly adjust expenditure (constrained-energy model), others think that adaptation is limited and deficits still dominate.
• “You can’t outrun a bad diet” is defended as broadly true for average people; critics point out elite athletes and extreme exercisers clearly can, but are rare.
• Timing approaches (intermittent fasting, OMAD, weekly 24h fasts) are described as useful mainly because they enforce lower intake, though some insist insulin dynamics matter independently.

Processed / Hyperpalatable Foods and Food Environment

• Many tie modern obesity to cheap, ultra-tasty, low-satiety foods engineered to encourage overconsumption.
• Some are skeptical of vague labels like “processed”/“ultra-processed,” calling them ill-defined and “vibes-based.”
• Others reply that classifications (e.g. NOVA) do exist and that the real issue is high calorie density, low fiber/micronutrients, and ease of overeating chips, sweets, snack foods, etc.
• Side discussion on food being dramatically cheaper and more abundant than in previous decades, making passive overeating easy.

Diet Strategies, Drugs, and Psychology

• Approaches mentioned: low‑carb/keto, intermittent fasting, strict portion control, calorie counting, higher-protein/low-carb, avoiding snacks and sugary drinks.
• Some emphasize that “eating clean” without measuring portions often fails; hidden calories (oils, nut butters, “just a handful” of snacks) derail deficits.
• GLP‑1 drugs (e.g. Ozempic) are praised by some for eliminating “food noise”; others voice concern about side effects and long-term dependence.
• Several note that different methods work for different people; sustainability and hunger management matter more than macronutrient ideology.

Exercise, Muscle, and Health Beyond Weight

• Commenters stress that exercise has major benefits independent of weight loss: cardiovascular fitness, strength, aging, mood, stress.
• Strength training is widely recommended to preserve/build muscle, improve function, and modestly raise resting expenditure; others caution that the extra calorie burn per pound of muscle is often overstated.
• Light, consistent activity (walking, low-intensity cardio) is seen as more sustainable than high-intensity efforts that spike appetite.

Study Design and Media Framing

• Multiple readers criticize the NPR headline as over-causal for an observational study.
• The dataset excludes athletes and focuses on differences across economic development; interpretation: daily expenditure doesn’t differ enough to explain obesity gaps, so diet/food environment likely dominate.
• Some note similar findings have been published before; this work is viewed as refinement, not a revolution.

What vet does and why it exists

• vet is a wrapper around the curl | bash pattern: it fetches a remote script, shows it (with a pager/diff), and only runs it if the user explicitly confirms.
• Several commenters like it as a pragmatic harm‑reduction measure: you won’t stop people from using one‑liners, so you might as well make the default “inspect first, run second.”
• Others argue it adds minimal real security: you could already curl > file; less file; bash file, and vet doesn’t solve deeper supply‑chain problems.

Risk model: scripts vs binaries

• A recurring argument: if you don’t trust the project enough to run its install script, why do you trust the much larger, opaque binary it installs?
• Counterpoint:
  • Package managers add vetting, signatures, predictable file locations, and a clean uninstall story.
  • Install scripts often run as root, modify system paths, add repos, create users, open ports, or “yolo” into /usr/local or $HOME. That’s a different, more invasive risk than just running a single binary.
  • Even if both are arbitrary code, scripts can be poorly written and non‑standard, breaking systems in subtle ways.

Rust / rustup as a case study

• Rust’s official docs prominently recommend curl --proto '=https' ... | sh for installing rustup.
• One side calls this “crazy” for a language that markets safety.
• Others respond:
  • rustup itself can be (and is) packaged in many distros and Homebrew; the curl‑pipe is just a uniform, low‑friction option.
  • The real toolchain churn is in compilers and crates; rustup is stable enough for repos.
  • If you care, it’s possible to avoid curl|bash entirely by manually installing rustup, using distro packages, or tools like mise.

Server compromise & targeted curl|bash attacks

• People note that servers can detect “curl | bash” and selectively serve malicious payloads only to piped requests.
• Some argue this is mostly theoretical; others share real‑world phishing examples that use this trick.
• Consensus: once you trust a compromised server, both scripts and binaries are suspect; hashes or signatures from a separate channel are the only strong defense.

Sandboxing and alternatives

• Multiple suggestions: run installers in containers, VMs, separate users, or tools like firejail/bubblewrap; inspect filesystem diffs before adopting the result.
• Some point to Nix/Guix, Fedora Silverblue/distrobox, Flatpak, and similar approaches to isolate third‑party software, revert easily, and avoid curl|bash entirely.
• Others mention specific tools (e.g., try, probox) or workflows (devbox + nix, home‑manager) to never need curl | sh.

Culture, usability, and package management

• Many blame fragmentation and lagging distro repositories for the popularity of curl | bash: developers want a single, cross‑distro install, users want the documented “latest,” and packaging everywhere is hard.
• Others counter that this leads back to Windows‑style entropy: ad‑hoc installers that don’t integrate with the system, update weirdly, and rarely uninstall cleanly.
• Debate over “safer behavior”: some insist on “use your distro’s package manager first,” others say real‑world needs and outdated repos make curl|bash or custom repos unavoidable.

Critiques of vet and “security theater”

• Skeptical voices call vet “enterprise fizzbuzz” that mainly prettifies curl | bash without fixing core issues (trust, sandboxing, supply chain).
• Supporters respond that making the default path “review before execute” still meaningfully raises the bar, especially for copy‑paste one‑liner culture.

What WiX Toolset Is and Technical Context

• Thread clarifies this is WiX Toolset (Windows installer tooling), not the website builder.
• Several describe WiX as powerful but extremely complex, with poor or historically outdated docs; others note it exposes the full (ugly) MSI/Windows Installer model, so much of the pain is inherent to Windows.
• Some praise WiX’s build/CI integration and flexibility versus GUI-based commercial tools; others say they’d gladly pay for easier, better-documented alternatives.

How the Open Source Maintenance Fee (OSMF) Works

• Source remains under an OSI license; the fee applies to:
  • Official binaries (GitHub releases, NuGet packages).
  • Using the project’s issue tracker/discussions if you generate revenue from it.
• Non-paying users may:
  • Use the source freely and build their own binaries, including commercially.
  • Redistribute their own builds, subject to the OSS license.
• Fee tiers are low monthly amounts by org size; maintainers frame it as payment for maintenance/support, not for the code itself.

License Compatibility and Enforceability Debates

• Some argue the chosen license allows charging for official binaries but forbids adding extra restrictions to redistribution; others think an additional EULA on binaries is fine.
• Multiple comments note anyone can legally fork, build, and publish binaries, making the fee partially “honor system.”
• Questions are raised about:
  • Whether restricting GitHub “Releases” clicks is compatible with GitHub’s own terms.
  • How this interacts with various OSS/FOSS definitions and with GPL-family licenses (compatibility is asserted but not fully resolved in-thread).
• Skeptics worry the README/EULA wording (“if you use this to generate revenue, the fee is required”) is misleading relative to the actual license rights.

Impact on Users: Indies, Companies, and Contributors

• Concern: small indie developers with tiny revenue might be deterred; responses say they can self-compile or that $10/month is trivial for a real business.
• Some fear a “two-class” system (paid maintainers vs. unpaid contributors); others say almost nobody contributes to boring maintenance anyway.
• Corporate angle:
  • Maintainers report many companies are willing to pay once there is a formal requirement that activates legal/procurement.
  • Others say their legal departments would just ban the tool as too risky/complex.

Broader Views on Funding Open Source

• Supporters see OSMF as a pragmatic, Red-Hat-like model: free code, paid convenience and support, aimed at reducing maintainer burnout and “entitled” users.
• Critics see it as “subscriptionizing” open source, edging toward corporate creep and undermining the “gift economy” ethos.
• Alternative ideas discussed: better corporate culture for donations, bounties, new licenses with profit-sharing or commercial-use restrictions.
• Several note this won’t be a silver bullet but could be one useful pattern; some other projects have reportedly started experimenting with OSMF.

Browser behavior and real-world tests

• Multiple commenters tested fingerprint.com and similar demos:
  • Brave, Firefox, Chrome (even with “hardest” settings) often still yielded stable IDs across normal and private sessions; Tor Browser was the main case that consistently broke tracking.
  • Safari (especially Private mode) often produced different IDs between normal and private windows; some saw it as significantly better than Chrome for privacy.
  • Mullvad Browser + VPN could still be tracked by fingerprint.com for some users.
• Brave’s built‑in fingerprinting protection and Shields were viewed as weaker than advertised; blocking scripts can break demos but may just hide the identifier UI.
• Firefox’s privacy.resistFingerprinting and related privacy modes can reduce leakage but:
  • They break or degrade many sites (timezone forced to UTC, canvas glitches, Cloudflare loops, bot flags, finance sites issues).
  • Several users reported still being uniquely fingerprinted or re-identified, especially when IPs are static.
• Librewolf and plugin-heavy Firefox setups often trigger more captchas and bot checks, indicating that “hardened” profiles themselves become fingerprints.

---

How fingerprinting works and its limits

• Signals mentioned: browser/OS versions, CPU count, screen/viewport size, fonts, codecs, timezone/locale, touchpoints, GPU/canvas/WebGL artifacts, extensions/adblockers, timing/CPU performance, and TLS/JA3/JA4 fingerprints.
• On homogenous platforms like iPhones, fingerprinting is weaker but still possible via regional settings, font sets, rollout timing of versions, and subtle rendering differences.
• IP address:
  • Some see it as a major signal (stable home prefixes, household-level ID).
  • Others note IPv6 rotation and MAC randomization, though home prefixes can remain static for years.
• Stability over time: Fingerprints can ignore fast-changing attributes (like browser version) and rely more on hardware and network invariants; un-hashed/raw attributes let trackers link “old” and “new” fingerprints.

---

Mitigations, tradeoffs, and arms race

• Techniques like spoofing user agents, randomizing canvas/fonts, or blocking JS can:
  • Make you stand out as “privacy-ext user” and increase fingerprintability or risk of blocking.
  • Break legitimate functionality (graphics, terminals, layout adaptation, downloads per-architecture).
• Some argue that removing or heavily gating high-risk APIs (canvas, WebGL, capability queries) would help, but others note modern “web app as VM” design inherently enables fingerprinting.
• Split setups (locked-down browser vs. “clean” browser for banking/government) are a common coping strategy.

---

Legal and regulatory debates (GDPR, cookies, enforcement)

• Several comments assert that under GDPR and ePrivacy, fingerprinting is legally on par with tracking cookies and requires consent; “cookie banners” are in fact broader tracking-consent dialogs.
• Others emphasize:
  • Enforcement difficulty: fingerprinting happens via JS and server-side matching; unlike cookies, there’s no local artifact to inspect.
  • Industry has turned consent UIs into dark patterns to force opt-in and blame GDPR for UX pain.
• Disagreement:
  • Some say doing fingerprinting without consent is “almost certainly illegal” in the EU.
  • Others claim that purely client-side, non-stored, non-shared measurements might be compliant (unclear; multiple “I am not a lawyer” caveats).
• Strong skepticism that regulators will meaningfully act, given corporate lobbying and low political payoff.

---

Legitimate vs abusive uses

• Cited “legit” uses:
  • Bot detection, rate limiting (e.g. JA3/JA4 TLS fingerprints), preventing ban evasion and fraud.
• Abuses:
  • Commercial services that “de‑anonymize” site visitors by merging fingerprints with data brokers and selling identity/PII for retargeting.
  • Vendors marketing this as “privacy-compliant” and skirting GDPR/CCPA spirit while claiming legality.

---

Broader sentiment

• Many view browser fingerprinting as more dangerous than cookies and believe it should be outright illegal, but:
  • Some argue purely legal approaches are weak and we need technical defenses too; others see technical-only responses as an endless arms race.
• There is deep distrust of ad-funded browser vendors and large platforms; several comments frame the problem as structural: tracking is aligned with their core business models.

What “connecting” means and why it matters

• Many agree with the article’s framing: connection = mutual empathy, shared values/experiences, and a sense of safety to say what’s really on your mind.
• One commenter notes that their best life experiences are overwhelmingly about connection, but others caution that this may overfit the past and neglect new, solitary or inner experiences.

Small talk and “How are you?”

• Big thread around “how are you?” as greeting:
  • In the US it’s often seen as a shallow ritual, not a real question; honest answers can be socially punished.
  • Others report that in some US regions it is answered honestly and is a useful context-setting opener.
  • Several European perspectives: equivalent phrases exist but are typically perfunctory; some cultures skip them, which reduces easy openings.
• Some see “how are you?” as an attention-grabber rather than a true question; others dislike it as fake and prefer more open prompts (“what keeps you busy?”, context-based questions, rating your day 1–10).

Small talk vs depth

• One camp defends small talk as the “MVP of connection”: safe, low-stakes, a way to test rapport and gradually build trust.
• Another camp finds it boring, a crutch that avoids real connection and crowds out meaningful topics.
• Several note that “clicking” often happens very fast—within minutes—through cues and mannerisms more than words.

Vulnerability and oversharing

• The “right” level of vulnerability is seen as highly context-dependent: time/place, relationship, and the other person’s signals.
• Some argue you can’t be vulnerable without risk; you learn the line by occasionally crossing it.
• Definitions of “oversharing” vary: for some it’s when the listener clearly isn’t interested; others doubt the concept and emphasize that people mostly don’t care as much as we fear.

Connecting across value gaps and with “bad” people

• Strong disagreement here:
  • One side, inspired by a famous quote about knowing those you dislike and examples of befriending extremists, argues that understanding and empathy can sometimes change harmful views and reduce polarization.
  • The other side (including minority perspectives) insists they don’t owe emotional labor to racists or homophobes; policy disagreements are one thing, but denying someone’s right to exist is another.
  • Debate continues over how changeable “values” really are, and whose responsibility it is to try.

Empathy, social media, and other practices

• Several see empathy as central to connection but argue it’s eroded by anonymous, reward-driven online culture.
• One perspective: the deepest common ground isn’t shared ideology but shared human fragility—our conflicted, irrational minds—so patience and compassion matter more than agreement.
• Social dancing is suggested as a way to practice nonverbal connection; others mention conversation skills and a recent book on “seeing others deeply” as useful tools.

Odds and ends

• A humorous aside reinterprets “connecting” as joining two USB‑C cables with a coupler.

Immediate situation and scope

• itch.io has removed or hidden >20k NSFW games/books after its credit card processors threatened to cut off service.
• Commenters see this as part of a broader pattern: Steam’s recent policy change, Pornhub/OnlyFans pressures, and similar actions against VPNs, Tor, Sci‑Hub, Wikileaks.

Who is driving the censorship?

• Disagreement over the main driver:
  • Some blame a small number of ideologically motivated billionaires and evangelical or “anti‑porn feminist” NGOs like Collective Shout.
  • Others point to government “jawboning” (Operation Choke Point–style pressure) and regulators using banks/cards as indirect censors.
  • A minority argue it’s mostly economics: higher fraud/chargeback rates and legal risk around adult content.
• Several note that advocacy letters alone seem insufficient to move Visa/Mastercard, implying unseen political or regulatory pressure.

Legal vs fictional harm

• Many stress that the banned games are legal, fictional depictions (including coercive/rape scenarios) sold under clear NSFW tags.
• They contrast this with:
  • Porn sites that hosted non‑consensual/trafficked content (seen as legitimately requiring intervention).
  • Violent games and TV (GTA, Skyrim, Game of Thrones) which depict murder and torture but face no comparable payment bans.
• Some are personally “icked out” by rape/blackmail content but insist that fictional depictions should remain lawful and purchasable.

Payment processors as de facto regulators

• Strong concern that a global Visa/Mastercard duopoly has become an unelected moral censor and sovereignty issue: local laws permit content that global processors can effectively outlaw.
• Several call for treating payment infrastructure as a common carrier or public utility: no service denial except for illegality/fraud, with risk priced via higher fees, not bans.

Alternatives: crypto, bank rails, and new systems

• Crypto advocates argue this is a textbook use case for Bitcoin/stablecoins: censorship‑resistant, borderless payments.
• Critics respond that today’s crypto is slow, UX‑hostile, scam‑ridden, and still dependent on centralized exchanges that can be pressured.
• Others highlight national or interbank schemes (UPI, Pix, Interac, SEPA, domestic card networks) as proof that non‑Visa/Mastercard rails are feasible, but note cross‑border gaps and political capture risks.

Policy and political responses

• Some push US bills like the “Fair Access to Banking Act” that would bar financial institutions from inhibiting lawful transactions; others are unsure if the text actually protects marginalized users.
• Suggested structural fixes include: stricter antitrust action, regulating card networks like utilities, or even nationalizing/creating state payment networks to provide neutral competition.

Culture-war and feminism tangents

• Long subthreads debate whether groups opposing sexualized content represent feminism, religious conservatism, or both.
• Related arguments flare around “attractive women” in games, body standards, breast sliders, trans inclusion, and bathroom politics, illustrating how NSFW censorship quickly entangles broader culture‑war disputes.

Tire Wear on EVs vs ICE Cars

• Many anecdotes of rapid EV tire wear (10–20k miles), especially on Teslas, Kia/Hyundai EVs, and some Niro/EV6/EV9 models; others report 30–70k miles or more, even on performance EVs.
• Proposed causes: higher vehicle mass, instant torque, “sporty” large rims with low-profile, soft-compound OEM tires, and aggressive driving (hard launches, fast cornering).
• Several people point to poor factory alignment/camber (notably on some Teslas, some FWD crossovers) and lack of tire rotation. Others blame low-rolling-resistance or shallow-tread “eco” tires.
• Counterpoint: many EV owners say tire life is normal or better than past ICE cars; suggest bad tires, alignment faults, or driving style when sets die at 10k miles.

Brake Dust and Regenerative Braking

• Consensus that EVs and strong hybrids use friction brakes far less due to regenerative braking.
• Multiple stories of pads lasting 50k–250k miles; some hybrids/EVs still on original pads after a decade.
• Some report brake rotors rusting from disuse; manufacturers sometimes deliberately engage friction brakes (or disable regen briefly) to keep discs clean.
• Discussion of blending strategies: many EVs map regen into the brake pedal; some (notably Tesla) rely on accelerator lift-off and use friction only at low speed or high SOC.

Net Particulate Emissions (Brakes, Tires, Road)

• Commenters quote the article’s figure: even adding tire, brake, and road wear, BEVs emit ~38% less particulate pollution than ICE cars before counting tailpipe emissions.
• Skeptics emphasize heavier EV weight (10–20% more than comparable ICE) and suggest tire particles and road wear may scale worse than linearly with mass. Others note delivery trucks for gasoline also damage roads.
• Some worry about tire microplastics and black carbon, but several argue EVs are still much cleaner overall than ICE vehicles.

Hybrids, Engine Braking, and Comparisons

• Hybrids are noted to get similar brake benefits from regen; some see essentially no pad wear on Prius/Yaris/Volvo PHEVs.
• ICE drivers discuss engine braking and careful driving extending pad life, but others point out clutches and drivetrains then take some of that load.

Infrastructure, Policy, and Equity

• Strong advocacy for banning ICE cars in cities vs. others favoring carbon pricing or incentives over bans.
• Major concern from renters and urban dwellers with no home charging: retrofitting garages, street chargers, and grid upgrades is seen as expensive and logistically hard.
• Some argue resources should prioritize public transit, cycling, and fewer cars overall; EVs alone don’t solve congestion, safety, or land-use issues.

US Access to BYD and Role of Tariffs

• Many commenters want BYD‑class cars in the US but see high tariffs on Chinese EVs as the main obstacle.
• One side argues tariffs distort markets, entrench bloated US automakers, and hurt consumers.
• Others see tariffs as strategic industrial policy: preserving domestic manufacturing capacity (and Tesla) even at consumer expense.
• There’s concern that heavy protection will cause the US auto industry to “rot from inside,” becoming uncompetitive globally.

Small Cheap Cars vs American SUV Culture

• Debate over why the US gets electric Hummers instead of tiny EV hatchbacks.
• Some say consumers simply don’t buy small hatchbacks (Fit, Yaris, etc.), and automakers rationally reallocated capacity to more profitable crossovers.
• Others argue regulations, tax code, and classification of SUVs as “trucks” push the market toward larger vehicles, then advertising and culture lock it in.
• Used‑car behavior: many people who want small, practical hatchbacks buy them used, shrinking new‑car demand.

Chinese EV Pricing, Subsidies, and Policy

• BYD’s ~$12k Atto 1 is seen as plausible and in line with other Asian EVs; the Chinese domestic price war pushed some models down to $6–8k.
• Several comments describe a “fantasy land” price war fueled by provincial subsidies and cheap debt, causing bankruptcies and prompting Beijing’s recent crackdown.
• Others note China’s broader pivot from real estate to EVs/clean energy as a national employment and industrial strategy, expecting long‑term price declines.

Prospects for the US Auto Industry

• Some predict much of the US auto sector will be wiped out within a decade by Chinese competition; others think tariffs will simply keep Chinese cars out.
• BYD is repeatedly described as offering Tesla‑class performance and better interiors at roughly half the price, though claims about “Porsche handling” and “Toyota reliability” are disputed.
• US legacy automakers are criticized for financial engineering (e.g., stock buybacks) instead of investing to compete; others emphasize structural constraints from investor expectations and interest rates.
• There’s a side debate over whether the real problem is “expensive labor” or management choices and corporate structure.

Demand for Ultra‑Cheap EVs in the US

• Several argue a $10–15k new EV wouldn’t sell well in America: buyers either move up to better‑equipped crossovers or buy used.
• Examples: the Chevy Bolt and Equinox EV had attractive effective prices (after incentives) but limited uptake; consumers prefer more expensive models.
• Others still ask why no entrant is attempting a truly stripped‑down $10–15k EV; one startup (Slate) is cited as trying exactly that by avoiding “gimmicks” like self‑driving.

Quality of Chinese EVs (BYD, etc.)

• Experiences are mixed but skew positive:
  • In low‑end segments, Chinese cars are described as “best for the money,” though sometimes with rough edges (buggy UIs, coarse driving dynamics, plasticky interiors).
  • Ride‑share users report BYD Atto as surprisingly good for a cheap car; Geely ICE examples reach ~100k km without major failures.
  • Some say China‑domestic BYDs feel flimsier than export versions; others contest this and stress intense domestic competition leaves little room for chronic low quality.
• Consensus that Chinese manufacturers are ahead in batteries (LFP, sodium‑ion, solid‑state ramping) and EV integration; US firms, including legacy OEMs, are seen as having under‑invested here.

Global Market Shifts and Emerging Economies

• BYD’s low‑cost EVs are already reshaping markets: in Brazil, the “Dolphin Mini” is a hit and BYD has reportedly overtaken Toyota in sales.
• Commenters expect Chinese brands (BYD, SAIC, Geely, GWM, Xiaomi, etc.) to dominate developing and emerging markets first, then increasingly pressure Western markets via local factories to sidestep tariffs.
• Some note Indonesia’s lack of a strong domestic auto brand compared with Vietnam’s VinFast, tying this to broader development and “commodities trap” concerns.
• Cheap EVs are seen as democratizing car ownership and thus traffic—but with far less local pollution than combustion cars.

Favorite Cocktails & Experiments

• Commenters latch onto specific standouts (Rabo de Galo, Porto Flip, Bijou, Negroni, Jack Rose, Dirty Martini, Betón, Sgroppino) and share riffs and substitutions.
• Strong emphasis on bittersweet, spirit‑forward classics (Negroni variants, Bijou, Hanky Panky, Rusty Nail).
• Some note that certain “official” cocktails are obscure or regionally skewed (Pornstar Martini popular in UK, White Lady not obscure, Monkey Gland’s odd history).

IBA List, Authenticity & “Every Cocktail”

• Several argue that saying “every cocktail” but using the IBA list is misleading; the list is narrow, rotates over time, and omits popular drinks (Dirty Martini, Gimlet, Jack Rose, etc.).
• Debate over whether you can really claim to have had certain classics when key ingredients no longer exist (Vesper with Kina Lillet; Chartreuse scarcity and non‑substitutability).
• Some feel brand‑specified recipes can be annoying at home; others say certain brands (Green Chartreuse, Kina Lillet) effectively are unique ingredients.

Ingredient Quality, Technique & Home Bartending

• Repeated advice: know when quality matters. Fresh citrus, good vermouth, and good cherries have big payoff; high‑end vodka is usually poor value in cocktails.
• Detailed spirit buying heuristics across gin, rum, tequila, whiskey, rye, vodka; warnings about Canadian “rye” and big‑brand rum/tequila.
• Strong focus on technique: ice quantity, dilution, and temperature as “hidden ingredients”; some recommend a pinch of salt to balance bitterness/sourness.
• Encouragement to make simple syrups and grenadine at home, refrigerate vermouth, and taste ingredients neat.

Alcohol Use, Health & Culture

• Discussion around whether “2 drinks a night” constitutes a problem: answers range from “normal, especially in Europe” to concern about dependence, sleep quality, and HRV effects.
• Nordic participants describe high taxes and state alcohol monopolies; debated as both protective and burdensome.

Learning Tools, Apps & Resources

• Multiple tools shared: a checklist app for the IBA list, open‑source cocktail apps, paid apps that optimize recipes by your inventory.
• Recommendations for books, blogs, and YouTube channels that teach cocktail “grammar” (sour ratios, Manhattan/Negroni families) rather than just recipes.

Reaction to the Blog Post & Broader “Lists”

• Many found the write‑up charming and well‑written, praising the prominent trigger warning about alcohol.
• Several are inspired to adopt similar long‑term “lists” (cocktails, sci‑fi, etc.) as slow, open‑ended life projects rather than speedruns.

Overall reaction & tone

• Many commenters found the idea “adorable”, “wholesome”, and genuinely uplifting; several said it made their day or improved their evening with a partner.
• A minority felt uneasy or saw it as potentially “psychological torture” or “deeply disturbing” that such an app might “need” to exist, though others stressed it’s clearly a parody / fun side project.

Features, UX, and implementation

• Core behavior: choose an album of partner photos; only right swipes, plus swipe-up to share a photo with the partner.
• Built with SwiftUI; no Android version yet (just a waitlist). No backend server; photos are on-device, with Firebase analytics as the only external service.
• Photos must be placed into an album manually (e.g., using Apple’s face recognition in Photos, then selecting that album in the app).
• Bug reports: shared albums not working, setup permissions sometimes failing, UI cut off on smaller iPhones, and issues with “unable to connect” likely related to Cloudflare.

Planned direction

• Author doesn’t plan major new features; intends to open source so others can extend (chat, “poke”, matchmaking, etc.).

Monetization & startup satire

• Long joke chain about needing an AI angle, microtransactions, loot boxes, B2B/SSO, YC funding, and MRR.
• Dark-humor suggestions: premium mode to swipe on others’ spouses, divorce-attorney automation, ex-partner photos that trigger alerts, polycule support.

Legal and branding concerns

• Some expect trademark or patent trouble from Tinder/Match (name similarity, swipe gestures).
• Others argue there’s no obvious trademark confusion and that noncommercial use is less risky, while noting copyright vs trademark are distinct.

Relationship dynamics & use cases

• Several couples tried it immediately and reported it sparked laughter or affection.
• Suggestions ranged from toddler/family albums to narcissist/self-photo mode, to using it as a “boss key” or prank.

Meta & broader ideas

• Meta-discussion about HN vs Reddit humor and “Reddit leakage” into HN threads.
• Tangents spawned ideas for Tinder-like swiping on arbitrary content for private groups, reminiscent of StumbleUpon or group curation tools.

Shallow water and child risk

• Multiple stories describe near‑drownings or deaths in very shallow water: fountains, puddles, bathtubs, mop buckets, and kiddie-pool depths (<30 cm / ~1 ft).
• Several commenters emphasize that drowning can be silent and extremely fast; parents often won’t hear a fall or struggle.
• A recurring theme: kids can drown if they fall unconscious face‑down, get trapped upside down in floatation devices, or simply can’t get their mouth above the surface.

Regulation vs “nanny state”

• One view: any standing water feature below ~1 m high should be fenced if children are expected; Australia is cited as an example of strict fencing laws plus lifeguard requirements, correlated with fewer pool drownings of under‑4s.
• The opposing view: broad fencing rules are overreach, costly, and often based on “if it saves one life” logic without clear causation; parents should supervise and teach swimming instead.
• There is debate over whether strict rules should apply even where no children live or to all bodies of water vs only pools.

Teaching kids to swim & inequality

• Some say early swimming lessons (from infancy) are normal and even part of school curricula in parts of Europe, credited with big reductions in drownings.
• Others argue it’s common in many parts of the US too, especially where water is central to life (e.g., hot climates, high pool density).
• A long subthread covers access barriers: cost, scheduling, geography, and historical closure or segregation of public pools; swimming proficiency correlates with socioeconomic status and race.
• Some argue public provision of lessons is a basic state responsibility; others say access via YMCAs, city pools, churches, etc. is already sufficient and the main gap is parental prioritization.

Recognizing and responding to drowning

• Shared resources stress that drowning is quiet and doesn’t look like movie-style splashing; key indicators include vertical posture, glassy eyes, gasping, and no forward progress.
• Autistic children are noted as having dramatically elevated drowning risk, especially under non-parent supervision.
• Several anecdotes highlight how crucial constant visual supervision is, regardless of flotation aids.

Other water hazards and safety heuristics

• Wave pools, low-head dams, riptides, and floodwaters are repeatedly called out as unusually dangerous and hard to lifeguard.
• Some surfers describe routinely rescuing people from riptides; advice is to understand currents rather than fight them.
• A simple rule offered for child safety focus: “cars, dogs, and water” as everyday things that can kill quickly with little warning.
• Brief tangents debate whether fear of heights is innate vs learned, and poke fun at exaggerated non-water hazards (e.g., garage door springs).

Meta: relevance to HN

• One commenter questions why this story is front-page material; others note HN’s “second chance pool” and broader remit of intellectually interesting, safety-related discussions, especially when comments are substantive.

Google’s incentives and business model

• Many see AI Overviews and “AI mode” as Google’s attempt to keep users on Google pages, even at the expense of outbound clicks and the broader web.
• Debate on monetization: some expect ads/product placement inside AI answers; others say that’s hard to do without destroying trust, which may explain why it’s not fully rolled out yet.
• Some argue this is defensive: Google is trying not to lose search share to standalone LLMs, even if it risks cannibalizing search ads.
• Others note “money queries” (commercial searches) remain mostly link‑based, so ad revenue hasn’t yet crashed, but informational queries are being absorbed by AI.

User experience: why people use or avoid AI Overviews

• A large group finds the overviews convenient for quick factual queries (“what temp is pork safe at”, flight numbers, definitions), avoiding SEO spam, cookie walls, and hostile UX.
• Another group disables or hides overviews (query hacks, udm=14, userscripts, adblock filters) because they prefer raw results or distrust the summaries.
• Many compare AI Overviews to reading Hacker News comments instead of the article: a faster but potentially distorted shortcut.

Accuracy, safety, and hallucinations

• Numerous reports of blatantly wrong answers: fabricated game hints, wrong population numbers, unsafe cooking temperatures, incorrect legal/medical/organizational info.
• Overviews sometimes contradict their own cited sources or misinterpret simple pages; some say they hallucinate more than high‑end LLMs.
• This creates real‑world harm: misdirected calls to businesses, users arguing about event fees or policies based on AI, and confusion in health and legal contexts.
• Some believe non‑technical users over‑trust AI outputs, while others say the general public is more wary than technologists assume.

Impact on publishers, SEO, and the web’s economics

• Many publishers and small sites report traffic drops of ~40–50%, threatening ad‑funded content and niche hobby/educational sites.
• Concerns that Google is “stealing” their work: ingesting pages into models, answering on‑page, and intercepting both traffic and revenue.
• Fear of a “dead internet” loop: less incentive to create quality content → less fresh training data → more AI‑generated slop → overall quality spiral.
• SEO is morphing into “GEO”/LLM‑SEO: optimizing content to be quoted by AI engines instead of merely ranked in blue links.

Workarounds and alternative tools

• Users share tactics to avoid AI: profanity triggers, -ai in queries, udm=14 parameter, custom Firefox search engines, CSS/JS to hide the overview.
• Increasing interest in alternatives like Kagi, Perplexity, Marginalia, library‑style or local LLMs; praise for Kagi’s paid, ad‑free model and per‑site up/down‑ranking.
• Cloudflare’s “pay per crawl” and robots controls are cited as early mechanisms to charge or block AI crawlers.

Long‑term concerns: data, law, and information ecosystem

• Open questions about how future models will get training data if web content becomes paywalled, blocked, or economically unsustainable.
• Worries that AI providers dodge liability by blaming “the algorithm” while now clearly publishing their own synthesized content.
• Legal and ethical debates around defamation, libel, business harm, and whether AI platforms should be treated as publishers rather than neutral intermediaries.
• Some hope this collapses ad‑driven SEO sludge and revives passion‑driven, non‑monetized “small web”; others fear only propaganda and commercial content will remain worth producing.

Cost Premium and Product Impact

• Many commenters are surprised the US-fab premium is only 5–20%, calling it a “bargain” for leading-edge nodes.
• Rough back-of-envelope math suggests that for a ~$350 Taiwan-made GPU die, a 20% fab cost increase adds ~$70, which is only a few percent of a $2,000 retail card.
• Others note margins differ: AI GPUs and high-end GPUs can absorb this easily; commodity CPUs and lower-margin parts feel it more.
• There’s debate over how much manufacturing cost matters versus total development and BOM (HBM, packaging, etc.).

Resilience, Security, and Geopolitics

• Strong support for paying a moderate premium to reduce dependence on Taiwan given invasion/earthquake risk and China–US tensions.
• Some argue that even maintaining 5–10% of global leading-edge capacity in the US is strategically huge: it preserves skills, equipment, and a base to scale in crisis.
• Others counter that for non-US buyers, Taiwan or “anywhere-but-US” is safer given US sanctions, export controls, and tariff volatility.
• A minority worries that more US capacity could reduce US willingness to defend Taiwan; others argue the opposite: the Arizona fab increases Taiwan’s leverage.

Partial Onshoring and Supply-Chain Gaps

• Several point out that wafers from Arizona are often still packaged in Asia; however US-based packaging (Amkor Arizona, Intel NM, others) is ramping.
• Boards, passives, specialty films, and many “low-profit, high-barrier” components remain overwhelmingly Asian; without these, US fabs don’t fully solve dependency.
• Shipping cost and carbon from moving dies back and forth is argued to be minor versus fab energy use; leading-edge chips are often air-freighted anyway.

Tariffs, Subsidies, and Who Pays

• One camp sees this as validation that modest tariffs plus CHIPS-style subsidies can level costs without massive consumer pain.
• Another stresses that any 10–20% cost rise, once passed through layers of the stack and compounded by tariffs, is effectively a large indirect tax on consumers.
• Some insist businesses, not end-users, should bear more of the cost (lower margins, government subsidies), while others argue customers ultimately pay either via prices or taxes.

Intel, TSMC, and Long-Term Industry Structure

• Long side-thread debates whether Intel is “cooked” or can recover; many blame decades of financialization, mismanagement, and fab delays.
• Consensus that TSMC currently dominates state-of-the-art; Samsung is a distant second; Intel’s future as a competitive foundry is uncertain.
• Several note that long term, leading-edge fab economics may support only one or a very small number of global players, making geographic diversification politically but not economically natural.

AccuWeather Change & “Enshittification”

• Many see the end of AccuWeather’s free API as part of a broader pattern: once ecosystems are built on free APIs, the terms shift to paid-only or “rent-only” subscription tiers.
• The announcement’s marketing language (“excited,” “elevate your experience”) is mocked as corporate spin for simple monetization.
• Some defend the move: running an API costs real money and staff; if developers value it, they should expect to pay.

NWS/NOAA, Politics, and Project 2025

• Multiple commenters stress that U.S. National Weather Service (NWS) APIs remain free and are the true upstream source most commercial services repackage.
• There is significant fear that NWS/NOAA will be “sabotaged” or privatized, citing:
  • Longstanding lobbying by AccuWeather to restrict NWS public outputs.
  • Trump‑era budget cuts and appointments tied to commercial weather interests.
  • Project 2025 language attacking climate and weather agencies as supporting “climate alarm.”
• Others push back, calling this fearmongering and noting that a private company charging for its API is not itself government censorship. There’s also skepticism about how predictive Project 2025 is of actual policy.

Public Good vs Privatization & Deficit Claims

• Strong pro‑public-good argument:
  • Weather data underpins aviation, shipping, agriculture, logistics, disaster response, and everyday safety.
  • NWS’s relatively small budget reportedly yields large economic ROI; cutting it is likened to “turning off a light to pay the mortgage.”
  • Examples from the UK and mapping (Met Office, Ordnance Survey) are used to argue that paywalled public data suppresses innovation and soft power.
• Libertarian/deficit‑focused responses:
  • The U.S. debt is unsustainable; everything, including nice‑to‑have APIs, should be on the table.
  • Counter‑argument: recent huge tax cuts and larger-ticket spending make it implausible that gutting public weather is really about fiscal responsibility.

API Quality, Abuse, and Scraping

• Some developers find NWS APIs clunky compared to commercial offerings, which add station networks, preprocessing, and better formats.
• Others note that truly free APIs get hammered by bots and hobby projects; one operator shut down a weather site after a scraper inflated pay‑per‑call costs.
• People discuss rate limiting, bot detection, and even serving fake data to bots. Some announce they will just scrape AccuWeather or its mobile app.

Alternative Weather Data Sources

• Numerous free or low-cost alternatives are shared:
  • Government: NWS (US), Environment Canada, Norwegian MET/yr.no, KNMI (Netherlands), various European services.
  • Open/community: Open‑Meteo (heavily praised), Pirate Weather, wttr.in, RainViewer (radar), plus Home Assistant integrations and personal weather stations (Tempest, Ecowitt, PurpleAir).
  • Commercial with free tiers: OpenWeather, Apple WeatherKit (via paid dev account), others.
• Several projects and libraries aggregate official national services (e.g., UniWeather.js) to bypass commercial middlemen.

Wider Internet & Climate Context

• Commenters link this to a broader trend toward walled and “wallet” gardens, in part accelerated by AI-era mass scraping.
• Climate politics loom large: some see undermining public weather infrastructure as part of a broader anti-science, anti-climate policy agenda; others frame it as ordinary conservative policymaking rather than coordinated conspiracy.

What the article actually claims

• Thread agrees the title is clickbait: the practice of resting isn’t “wrong,” but old explanations are.
• The core claim: resting’s main purpose is managing carryover cooking and hitting target internal temperature, not “locking in juices.”
• Experiments cited show no meaningful difference in perceived juiciness between rested and unrested meat when final slicing temperature is controlled.

Resting: juiciness vs temperature control

• Many commenters insist anecdotally that resting “keeps juices in,” pointing to puddles of liquid when cutting immediately.
• The newer model: juice loss depends on temperature at slicing (vapor pressure/thermal pressure), not on rest time per se. Resting only helps insofar as it changes temperature.
• Some argue the article under‑emphasizes that ideal practice is: pull early, let temperature rise via carryover, then cool somewhat before slicing.

Carryover cooking and practical technique

• General consensus: pull meat 5–15°F (sometimes more) below target, especially for thick cuts, and let carryover finish the cook.
• Thin items (skirt steak, shrimp) need very short rests; large roasts or barbecue can benefit from long, warm holds.
• Several people highlight predictive / multi-sensor thermometers as game‑changers for timing pull and rest.
• Environment matters: air temp, resting surface, and whether you hold in a warm oven or insulated box significantly change the curve.

Sous vide, reverse sear, and BBQ competitions

• Sous vide (and low‑temperature reverse sear) largely eliminates carryover; many say no rest is needed there.
• Side thread on BBQ competitions: many apparently ban sous vide/low‑temp water baths to preserve “authentic” smoked‑meat technique and difficulty, not just flavor.

Science, tradition, and disagreement

• Some see this as a classic case of folk “rules” that worked but had the wrong physics, later corrected by measurement.
• Others say serious kitchens have long used resting explicitly to ride carryover to target doneness, not for mystical “juice reabsorption.”
• A few criticize the article as product-adjacent or rehashing older work; others praise it for clear experiments and for debunking searing/resting myths with data.

Perceptions of the advice

• Several readers see the piece as re-packaged self‑help/networking advice: “grow your network,” “act like the job you want,” “say yes more.”
• Others like it because it frames things as memorable mindsets (curiosity, giving first, airing weirdness), which they feel are easier to recall and act on.
• One critique is that it’s fuzzy and unstructured: you can burn out chasing “microlucks” without real progress unless you’re more strategic about where you look for luck.

Hosting events and social serendipity

• Strong support for “host events”: hosting is seen as higher‑leverage than passively attending, and many note that most scenes lack enough organizers.
• Concrete example: a weekly “project night” where people bring personal projects led to a thriving community and steady inflow of new people.
• Some pushback: coordinating people is exhausting, cancellations are common, and managing others can feel like “herding.”

Curiosity, authenticity, and personality fit

• Multiple commenters credit intense curiosity as central to their success; others feel stuck because curiosity doesn’t easily translate into sharable output or career change.
• “Air your weirdness” resonates: hiding quirks is seen as counterproductive, though there’s a caution against faked eccentricity.
• Introverts worry the model implicitly assumes extreme extroversion; suggested workaround is “role‑playing” an extrovert persona at events.

Luck, privilege, and preparation

• Big thread on structural luck: being born in a rich country with computers is framed as a massive, often squandered advantage.
• Some argue success is mostly about seizing opportunities given your starting point; others insist initial conditions dominate outcomes and Western narratives underplay this.
• A reconciliatory view: luck delivers opportunities randomly; work, skill, and preparation determine whether you can use them.

Risk, failure, and strategy

• Debate over “fortune favors the bold”: one side urges more risk‑taking and not overestimating imagined dangers; another stresses underappreciated catastrophic risks.
• Idea of “bulk positive randomness”: increase variance where downside is small (meeting people, trying projects), reduce it where downside is large (health, safety).
• Some advocate studying failures and “non‑ergodic” dynamics (avoid ruin) rather than obsessing over copying rare success stories.

Concept and origins of “luck surface area”

• Commenters reference an earlier formulation: luck ≈ doing × telling—build real things and talk about them publicly.
• Compared to that, the article is seen by some as drifting toward style and mindset, away from concrete “build in public” and “be visible” tactics.