Hacker News, Distilled

AI powered summaries for selected HN discussions.

Page 522 of 793

Resident physicians' exam scores tied to patient survival

Study design, confounders, and effect size

  • Commenters immediately question whether results are driven by hospital quality, case mix, or specialty choice (e.g., high‑mortality vs low‑mortality fields).
  • Others note the study reportedly compares doctors within the same hospital to partially control for institutional differences and patient populations.
  • Some see the study as observational and potentially fragile: effect sizes are described as “marginal,” and there is concern that exam organizations are both data gatekeepers and study sponsors, creating conflicts of interest and no possibility of external replication.
  • Skeptics ask for more granular statistics (score distributions, classification error between quartiles) before treating the “top 25% vs bottom 25%” difference as practically large.

Residency workload, filtering, and exploitation

  • Large subthread on whether brutal 80–100 hour residencies improve long‑term outcomes or just act as a resilience filter.
  • Several argue overwork harms learning (sleep debt, cognitive impairment) and may worsen care during training; any marginal outcome gains would need to justify serious human costs.
  • Others prioritize patient outcomes over resident comfort but are challenged with fairness arguments and claims that harsh conditions also limit physician supply.
  • Multiple comments frame US residency as partly historical hazing and cheap, semi‑captive labor, with much time spent on administrative “scut” unrelated to learning.

Complexity of medicine and health‑system structure

  • Some argue modern medicine is too complex for any one person; better memory and pattern matching (which exams may proxy) become critical, yet many patients still go undiagnosed.
  • Others emphasize system‑level complexity: huge revenues flowing through insurers, PBMs, and distributors, with multiple middlemen each skimming a little and driving up costs.
  • There is debate over whether eliminating middle layers would simply produce vertically integrated conglomerates rather than true simplification.

What exam scores may actually reflect

  • Several commenters see the findings as intuitive: high scores indicate discipline, prioritization, and sufficient “cleverness” to understand the literature.
  • Others stress that great doctors also need humility, meticulousness, communication skills, and manual abilities (for surgeons), which correlate imperfectly with written exams.
  • Some worry exams may also alter physicians’ confidence and risk tolerance, potentially affecting practice style in ways not directly captured by knowledge alone.

Race, DEI, and standardized testing

  • A contentious subthread links the study to existing gaps in MCAT/USMLE performance among demographic groups and to affirmative‑action‑style admissions.
  • One side argues that if board scores predict outcomes and test scores differ by race, then quality differences by race are “obvious,” even if not measured here.
  • Others reject extrapolating from entrance exams and partial datasets, calling this non‑rigorous and insisting on direct data on board scores and outcomes by race before drawing such conclusions.
  • There is disagreement over whether diversity efforts have “passed bad doctors” or simply expanded opportunity while the same exit standards apply.

Surgical skill variation and system response

  • Anecdotes describe large variability in surgical outcomes, with a small fraction of surgeons perceived as “horrific,” yet often still operating because systems struggle to identify and reassign them.
  • Proposals to remove or redirect chronically poor performers collide with concerns about surgeon shortages and perverse incentives (e.g., surgeons avoiding high‑risk but necessary cases to protect metrics).

AI and test‑taking vs real practice

  • One commenter notes that chatbots can score very highly on medical exams; another counters that real practice hinges on physical examination, incomplete histories, and nuanced judgment, where a text model alone is clearly insufficient.

New maps of the chaotic space-time inside black holes

Nature and Status of Singularities

  • Several commenters object to the article’s “point of infinite density” phrasing as misleading.
  • Distinction is drawn between:
    • Mathematical singularities in general relativity (where equations break down / go to infinity).
    • Physical reality, where quantum effects are expected to remove true infinities, though no complete theory exists.
  • Claims that singularities are “disproven” are criticized as overstatements:
    • A recent Kerr paper is said to invalidate an earlier proof of a specific singularity, not singularities in general.
    • Both video explainers and papers are interpreted as “the classical proof is wrong,” not “singularities don’t exist.”
  • Clarifications:
    • Event horizon ≠ singularity; the former is not a physical singularity and is regular in better coordinates.
    • Singularity in GR doesn’t talk about baryons/fermions; that’s quantum language.
    • From an infalling observer’s perspective, reaching the singularity takes finite proper time, even if external observers never see it happen.

What We Actually Have Evidence For

  • Strong thread arguing: we only have empirical evidence for ultra-compact massive objects whose behavior matches GR black holes.
  • Disagreement over whether we have direct evidence of event horizons:
    • Images (EHT) and tidal disruption events are consistent with horizons but are theory-dependent.
    • Some insist this doesn’t prove all GR features (horizons, singularities, information loss).
  • Hawking radiation is discussed:
    • Standard view: emission is generated just outside the horizon; no ordinary matter or detailed information escapes.
    • Others loosely talk as if matter “passes back out,” which is challenged on information-theoretic grounds.
  • A highly speculative idea of an inner “second horizon” and crystalline core is proposed and largely rejected as unevidenced.

Inside Black Holes and Coordinate Intuitions

  • Lay confusion about “space and time swapping” inside a black hole is addressed:
    • This is a statement about a particular coordinate choice (Schwarzschild coordinates), not a literal physical swap.
    • Physically meaningful questions must be coordinate-invariant (geodesics, causal structure).
  • Cosmologist-style explanation: locally, crossing a large black hole’s horizon feels ordinary; inside, all future-directed paths inevitably lead inward.

GR, Quantum Gravity, and Measurement

  • Several comments note: singularities and horizons are classical GR predictions; quantum gravity is expected to modify them, but details are unknown.
  • Side discussion on:
    • Gravity’s nonlinearity (e.g., Mercury’s perihelion).
    • Competing views on the measurement problem (Copenhagen vs many-worlds vs gravity-induced collapse).

Meta: Tone and Disagreement

  • Small subthread debates snark vs name-calling and how using “you” personalizes conflict.
  • Emphasis on replying to arguments rather than attacking individuals, while still allowing firm correction of factual errors.

Hyperspace

Perceived Need and Value

  • Many see this as most useful on Macs, where internal SSD upgrades are expensive and non‑user‑replaceable.
  • Others argue that on machines with cheap multi‑TB NVMe or NAS, reclaiming a few GB (e.g. 1–10 GB) is “spare change” and not worth the cost or risk.
  • Some users report modest savings (≈1–2 GB on large home dirs) and decide the benefit doesn’t justify the price; others see double‑digit GB savings and are enthusiastic.

How It Works: APFS Clones vs Links

  • Repeated clarifications that this uses APFS copy‑on‑write clones (reflinks), not hardlinks or symlinks.
  • From the user’s perspective, all file paths remain and can diverge later; unchanged blocks remain shared.
  • Multiple questions about “what happens if I edit one copy” are answered: only the modified parts are written separately; the other clone stays unchanged.

Safety, Risks, and Metadata

  • Strong general mistrust of dedup tools: fear of silent corruption and irreversible mistakes; some contributors say they only ever log duplicates, never auto‑modify.
  • Hyperspace is described (via docs/podcast) as conservative:
    • Skips files if it can’t preserve metadata (timestamps, permissions, extended attributes, resource forks).
    • Lets users review proposed changes before committing.
  • Nonetheless, several people prefer to wait and see how it behaves “in the wild” before trusting it with important data.

Why the Filesystem Doesn’t Do This Automatically

  • Discussion of why APFS doesn’t background‑dedupe duplicates:
    • Comparisons to ZFS, Btrfs, XFS, NTFS/Windows Server, ReFS, which can dedupe at block or file level.
    • Trade‑offs mentioned: high RAM usage, heavy I/O, complexity of on‑write vs periodic sweeps, and operational horror stories from backup dedupe.
    • Linux offers kernel syscalls (e.g. FIDEDUPERANGE) that validate ranges before deduping, making userland tools safer.

Alternatives and DIY Tools

  • Multiple free/open‑source options cited: fclones (APFS clones via cp -c), rmlint (with clone mode on Linux), jdupes, duperemove, bees (Btrfs), czkawka, custom SHA‑based scripts, and a macOS CLI tool dedup.
  • Debate over algorithms: use file size, partial content, or full cryptographic hashes; some argue SHA‑256 collision risk is practically irrelevant, others still favor byte‑by‑byte confirmation.

Pricing Model and App Store Issues

  • Pricing is mixed: some praise the “scan free, pay to reclaim” shareware‑style model (one‑month, one‑year, and lifetime unlocks), others say $10–50 is too high for a storage utility.
  • Complaints that App Store hides IAP pricing and that you often must dig to see costs, especially from non‑Apple devices.
  • Supporters argue you’re paying not for the basic idea (which many FOSS tools implement) but for careful engineering, safety checks, and a polished macOS GUI.

Platform, Performance, and Closed Source

  • Requires macOS 15; users on older systems are disappointed and see this as part of Apple’s “hardware treadmill” and SwiftUI’s reliance on new APIs.
  • Side discussion: native SwiftUI/macOS table performance vs HTML/webviews/Electron; several say browsers are now surprisingly faster for large tables.
  • Some hesitate to run a closed‑source, full‑disk utility on work machines; others counter that open‑sourcing would both enable free clones and greatly increase support burden.

Launch HN: Browser Use (YC W25) – open-source web agents

Positioning vs Other Tools

  • Compared to Stagehand, Browser Use is described as higher‑level and “end‑to‑end” rather than step‑by‑step, and compatible with many LLMs (including local ones via Ollama).
  • Versus Skyvern, commenters see Browser Use as an open‑source framework with a simple cloud “one prompt and go” layer, while Skyvern feels more like a closed web app.
  • Some ask how it compares to TaxyAI’s DOM‑based extension; no detailed answer appears in the thread.

Security & DevTools Concerns

  • A substantial subthread criticizes the guidance to attach to a user’s real Chrome profile via remote debugging (CDP) as “inherently insecure,” referencing known Chromium issues.
  • Attack vector: devtools port has no auth and can be exploited (e.g., via XSS) to compromise the browser and potentially the host machine.
  • Alternatives discussed: ChromeDriver, minimal‑permission extensions, WebViews; disagreement over which approach is safer.
  • Several commenters say local use in this mode is “unusable” until addressed; cloud use shifts risk to trusting the provider with passwords instead.

Integrations & MCP Debate

  • Some users want MCP (Model Context Protocol) support to plug Browser Use into tools like Cursor and Claude Desktop.
  • Maintainers initially view MCP as unnecessary “gimmick” vs direct HTTP APIs, but are swayed by repeated user requests and existing community MCP wrappers.
  • Pro‑MCP arguments: standardized tooling, easier integrations, explicit user opt‑in, and better security boundaries than arbitrary HTTP/curl.

Scraping Ethics & Website Impact

  • Concerns about agents driving huge traffic spikes, ignoring robots.txt and rate limits, and increasing hosting bills 100–1000%.
  • Browser Use team mentions possible mitigations: only fetching interactive elements, skipping media, caching via eTags, and a long‑term vision where agents pay for data.
  • Critics highlight marketing claims like “extract data behind login walls” as adversarial to sites and liken it to “breaking into someone’s house.”
  • There’s a request for an easy way for site admins to detect and block Browser Use traffic.

Reliability, Determinism & Speed

  • Mixed reports: quickstart Reddit example sometimes fails, while more complex internal workflows can work surprisingly well.
  • Issues cited: loops while loading a tab, hallucinated form inputs (e.g., fake addresses), lack of a verifiable feedback loop that what was requested actually happened.
  • Ideas: record agent histories, extract xPaths/DOM selectors from successful runs, then re‑run deterministically and use LLMs as a repair fallback.
  • Users want faster execution; maintainers say they’re already significantly faster than some vision‑heavy competitors and discuss specialized inference (e.g., Groq) and custom actions for common flows like WhatsApp.

Use Cases, RPA & Testing

  • Strong excitement from people doing:
    • Legacy web/CRM integration and internal tools
    • RPA‑style workflows, with Browser Use turning agent runs into repeatable scripts
    • Automated web testing and accessibility, especially if xPaths/DOM or accessibility trees can be captured once and reused.
  • There’s interest in extending these ideas to native Windows apps (with pointers to OmniParser, Pig, AskUI) and eventually to mobile device automation.

Licensing & Open‑Source Strategy

  • MIT license draws praise but also warnings: cloud vendors could repackage and undercut them, as allegedly happened with Elasticsearch, MongoDB, Redis.
  • Some predict a future shift to AGPL or a business license; maintainers don’t commit either way in the thread.

Anti‑bot / Platform‑Specific Issues

  • LinkedIn is highlighted as particularly hostile to automation: CAPTCHAs, nested scrollable UIs, detection. Suggested mitigations include using a separate browser profile.
  • A user reports being blocked within seconds by a real‑estate site and asks about stealth measures; no concrete anti‑detection roadmap is given.
  • One commenter distinguishes “agents” (acting as user clones) from traditional scraping bots but acknowledges sites that truly don’t want agents will escalate defenses.

Community Reception

  • Overall sentiment is highly positive: many see Browser Use as a leading open‑source building block for browser agents and RPA.
  • Users share creative demos (e.g., ordering food from smart glasses) and plan to integrate it into products, while recognizing that security hardening, speed, determinism, and site‑friendliness remain open challenges.

Fabric and craft retailer Joann to go out of business, close all of its stores

Loss of a Physical Craft Resource

  • Many lament losing a place to buy a single, specific item (e.g., one skein of yarn, one resistor) instead of bulk online packs they’ll never use.
  • Joann is described as especially valuable for tactile selection of fabric and upholstery materials; people doubt fabric buying works well online because “feel” matters.
  • In smaller cities, options may now be only Hobby Lobby or nothing; dense areas might still have boutique yarn shops, but those often focus on expensive “boutique” yarn rather than cheap basics.

Are Hobbies Dying or Just Changing?

  • One line of discussion claims people are abandoning hands‑on hobbies for passive entertainment and doom‑scrolling.
  • Others strongly push back: board and tabletop games are said to be more popular than ever, RC partly replaced by drones, Lego and miniature kits booming, and kids socializing in new ways.

Online vs. Local: Economics and Friction

  • Shipping makes small orders (like a single resistor) expensive from specialist sites; Amazon’s subsidized logistics warp expectations.
  • Several people cite alternative suppliers (DigiKey, Tayda, McMaster, Grainger) with better catalogs and non-counterfeit parts, but acknowledge shipping and minimum quantities as pain points.
  • Inventory is highlighted as a killer cost: maintaining hundreds of fabric SKUs across hundreds of stores is expensive and risky if stock doesn’t move.

Private Equity, Debt, and Business Models

  • One camp bluntly blames private equity: classic leveraged buyout, heavy debt, inventory cuts to look good on spreadsheets, then customer attrition when items aren’t in stock.
  • Another camp argues Joann’s model was already strained by outsourced textiles, online competition, tariffs, and big-box real estate costs; PE is framed more as “buyer of last resort” than sole cause.
  • Extended debate about whether craft chains truly need high growth vs. sustainable returns, and how leverage turns a flat business into a failure when growth bets don’t pan out.
  • Some note contrasting outcomes: other hobby chains (Michaels, Hobby Lobby, local shops) are still operating.

Covid, Culture, and Store Experience

  • One commenter recalls Joann resisting Covid closures and calls its demise fitting; another counters that during early mask shortages and lockdowns, fabric and crafts were effectively “essential.”
  • Some feel Joann had already declined: dim stores, disorganized fabric, low-quality “junk hobby” focus, and staff unable to give expert advice.
  • Broader concern surfaces that society is losing making and craft skills, with more emphasis on buying than learning how to do things.

ChatGPT Saved My Life (no, seriously, I'm writing this from the ER)

Perceived Role of ChatGPT in the Incident

  • Many commenters see this as a genuine success case: the model noticed “alarmingly low platelets + rash” and strongly urged an ER visit when the physician hadn’t yet reviewed labs.
  • Others stress the key value wasn’t raw medical knowledge but the conversational, persuasive UX: it could interpret labs, connect them to visible symptoms, and tell the patient, in plain language, “this is urgent.”

“AI Win” vs Existing Tools

  • Several argue no LLM was needed: abnormal platelet counts are flagged in lab portals; a simple search like “low platelets red spots” or a call to a doctor/urgent care could have led to the same outcome.
  • Counterpoint: most patients don’t know which numbers matter or what to search for, and often don’t understand radiology/blood reports; LLMs can bridge that gap better than static ranges or scattered web pages.

Healthcare System & Lab UX Failures

  • Strong sentiment that this illustrates systemic failure: dangerous labs should be auto-flagged and rapidly escalated (to doctors, on‑call staff, or even patients), not sit for 2–3 “business days.”
  • Some note many labs and EMRs already have critical-result workflows, but they may not be consistently implemented or surfaced to patients.
  • Several call for better UX: severity indicators (e.g., “critical, seek care”), variance scores, or plain-language summaries instead of only numeric ranges.

Use of AI for Patients vs Providers

  • Many see AI’s near-term role as a “patient-side assistant”: explaining results, suggesting questions, offering differential diagnoses to bring to a doctor.
  • Others describe similar experiences where LLMs helped them frame obscure conditions or interpret complex histories, but emphasize final decisions remained with physicians.
  • Provider-side ideas: AI scribes (already used), triaging radiology and lab reports, prioritizing which results clinicians review first.

Risks, Ethics, and Safety Concerns

  • Multiple commenters warn that saying “ChatGPT is better than doctors” is dangerous: people may skip or delay professional care, or follow incorrect treatment suggestions.
  • Concerns raised about hallucinations, overconfidence, and unequal access to good doctors; plus privacy risks when uploading medical records and genetic data to cloud LLMs.
  • Liability questions: what happens when an LLM misses a fatal issue or gives harmful advice? Some expect models will default to “go to the ER” to reduce risk.

Cost-Effectiveness & Broader Priorities

  • One subthread challenges the claim that “saving one life justifies every cent spent on OpenAI,” comparing billions in AI spending to much cheaper, proven life-saving interventions (e.g., malaria vaccines).
  • Others note survivorship bias: we hear about the dramatic saves, not the silent harms or near-misses.

Authenticity and Skepticism

  • A few suspect the story might be AI-generated or embellished, referencing prior fake “AI saved my life” posts; others point to added photos and an addendum as evidence it’s real.
  • Meta-point: as AI-generated narratives proliferate, it becomes harder to distinguish genuine medical anecdotes from synthetic ones.

DOGE will use AI to assess the responses of federal workers

Perceived Purpose of the AI/Email Scheme

  • Many commenters doubt that millions of responses can be meaningfully evaluated, even with AI, given the diversity and complexity of federal roles.
  • The dominant theory is that this is an obedience test: see who complies quickly, then use that as a basis for future purges and restructuring.
  • Others suspect it’s a political stunt to create a narrative of “lazy bureaucrats” and justify broad cuts, rather than a serious management tool.
  • Several note the phishing-like nature of the emails (odd sender, urgency, sensitive info requests), interpreting that as either gross incompetence or intentional pretext to fire non-responders.

AI, Security, and Gameability

  • Commenters point out that any LLM-based triage can be easily gamed with impressive-sounding but meaningless text, or even prompt injection.
  • Some joke that employees should use AI to draft their own responses, or inject prompts asking for raises or high rankings.
  • Musk-associated AI already having filtered criticism (per a linked report) feeds skepticism that any “DOGE AI” would be neutral.

Impact on Workforce vs Management Goals

  • Many argue this approach will mainly traumatize workers, drive away competent people, and degrade services, not meaningfully cut waste.
  • Others reply that government is enormous and certainly contains waste, fraud, and “ghost payrolls,” and see this as a rough but necessary “turnaround” attempt.
  • Critics respond that real fiscal problems lie in mandatory spending and tax policy, and that random, AI-filtered purges won’t address those.

Comparisons to Corporate Practices

  • A minority claim that “justify your job” demands are normal in startups or big firms; others strongly disagree, saying even in harsh private environments this kind of mass, decontextualized ultimatum is abnormal and toxic.
  • Distinction is made between daily standups to unblock work (within a known org chart) and having a politically connected outsider or ad hoc office evaluate everyone via a one-off email.

Wider Political and Culture-War Context

  • The move is widely framed as part of a broader project to weaken or dismantle the administrative state and normalize a CEO-style, near-monarchical executive.
  • Long subthreads argue over whether this is a right-wing authoritarian turn, a reaction to earlier “woke” excesses, or both.
  • Some discuss civic responses (calling representatives, anti-gerrymandering efforts, protests) but also voice deep pessimism about eroded democratic accountability.

Signal to leave Sweden if backdoor law passes

Military and national security views

  • Commenters highlight that Sweden’s armed forces formally oppose the backdoor proposal, explicitly warning it would introduce exploitable vulnerabilities.
  • The military has recently encouraged staff to use Signal for non-classified communication to reduce interception risk; a backdoor would undermine that.
  • Some debate whether it’s wise for a military to rely on a foreign-hosted messaging app, but others note it’s only for routine, non-secret traffic and a complement to existing military systems.
  • Parallel is drawn to TOR and SELinux originating in military/intelligence contexts, illustrating that modern armed forces often prefer strong encryption for their own security.

Backdoors, crime, and “think of the children”

  • Supporters of tougher laws cite Sweden’s serious gang violence and “crime as a service,” often organized via encrypted apps, and argue backdoors are needed to reach organizers.
  • Opponents respond that criminals will simply migrate to other channels, while the backdoor remains as a permanent mass-surveillance and espionage risk.
  • Several insist “backdoor for good guys only” is technically impossible; any weakness will be discovered and abused by hostile states or criminals.
  • Distinction is made between targeted warrants (reading diaries, intercepting specific lines) and scalable, automated surveillance of everybody by default.

European politics and surveillance trend

  • Many see this as part of a broader European shift: chat control proposals, France’s “Narcotrafic” amendment, Denmark’s blasphemy laws, etc., framed as anti-terror/child-protection but eroding privacy and other rights.
  • Explanations offered include: technological ignorance of bureaucrats, desire for population control, fear of terrorism and social fragmentation, lobbying by a “surveillance-industrial complex,” and influence from Five Eyes partners.
  • A minority express trust in Scandinavian governments and even support scanning systems for child pornography, while acknowledging technical challenges.

Centralization, open source, and alternatives

  • Centralized services like Signal are seen as uniquely vulnerable: one legal lever (servers + app stores) can compromise everyone; updates to closed mobile clients are a single point of failure.
  • Free software and decentralization (XMPP/Prosody, Matrix, Jami, Briar, SimpleX, home-hosted “server under the stairs”) are proposed as more resilient against state pressure but acknowledged as niche and less user-friendly, especially on mobile.
  • Some criticize Signal’s own governance (e.g., MobileCoin episode, non-reproducible builds) as “trust us” security, though others still see it as one of the best practical options.

Corporate reactions and jurisdiction

  • Signal’s stated willingness to leave Sweden is contrasted with Apple’s partial retreat on UK iCloud features and Google’s exit from China.
  • Debate centers on whether companies “can” defy laws at real scale, given boards, shareholders, and local enforcement.
  • For Signal specifically, commenters argue Sweden’s practical tools are app-store pressure, ISP blocking, and potential legal risks to staff traveling in cooperating countries, rather than direct fines on a US non-profit with no local presence.

What do people see when they're tripping? Analyzing Erowid's trip reports

Subjective Effects Across Substances

  • 2C-x series: 2C-E described as intensely visual with heavy body load and nausea but relatively “sober” headspace; 2C-B and similar reported as mostly visual (tracers, pattern enhancement) with only mild mood lift and short duration.
  • LSD: recurring themes of time distortion, difficulty reading (letters become meaningless symbols), extreme visual enhancement (breathing walls, morphing textures, fractals), and occasional full amnesia for parts of the trip. Some compare it to temporary psychosis or schizophrenia.
  • Mushrooms: often less overtly visual and more introspective; “popping out” or sharpening of perception more than new objects appearing. Experiences range from mild pattern movement to deep emotional insight and major depression relief.
  • DMT: very rapid onset, intense geometric or entity-filled spaces, sometimes “VR headset”–like replacement of reality; some users never reach the more famous “breakthrough” state.
  • Ketamine: powerful dissociation, ego separation, and immersion in music; some report long‑term softening of depression, others mostly novelty.
  • Salvia: repeatedly described as uniquely strange and often frightening (becoming objects, living as a plant or inanimate thing for “years”). Several warn strongly against it.
  • Datura and other deliriants: almost universally condemned as dangerous, unpleasant, and insight‑free, with high risk of poisoning and prolonged psychosis.

Profundity, Insight, and Meaning

  • Many describe seemingly world-shattering insights (about time, self, or reality) that later read as gibberish; others report enduring, life-improving realizations about empathy, relationships, and personal patterns.
  • Meta‑insight: feeling that something is profound is not evidence it truly is, but realizing this can itself recalibrate one’s sense of meaning.
  • Debate over whether psychedelics are better for “EQ problems” (emotions, empathy) than “IQ problems” (technical creativity), though some cite research and anecdotes suggesting creativity boosts.

Risks, Set/Setting, and Mental Health

  • Reports of persistent visual disturbances (visual snow, subtle movement) and HPPD; others note long‑term panic and cognitive issues, especially from misrepresented or DOx‑type drugs.
  • Strong advice that people with anxiety, bipolar, psychosis risk, or fragile mental states can be badly harmed; some say trips that dredge up trauma can still be healing, but only with preparation, support, and willingness.
  • Emphasis on set and setting, sober or trusted sitters, cautious dosing, and having benzodiazepines as an “emergency brake.”

Patterns, Commonalities, and Theory

  • Discussion of “form constants” (grids, spirals, tunnels) and recurring motifs like spiders on certain drugs or cigarettes on datura, suggesting shared neural mechanisms.
  • Mixed reactions to the article’s claim that different psychedelics don’t differ much visually: some think this reflects analysis limits; others insist the character of LSD, psilocybin, DMT, salvia, etc. is dramatically distinct at experiential level.

Erowid, AI, and Culture

  • Some want to mine Erowid trip reports with LLMs for better taxonomies and harm reduction; Erowid’s anti‑scraping stance is respected but seen as a lost opportunity by some.
  • Light speculation on whether AI could “trip” via perturbations of its own parameters, and broader surprise at how common serious drug use is among technically inclined people.

Tell HN: Y Combinator backing AI company to abuse factory workers

Overview of product and reaction

  • Thread centers on a YC‑backed startup using AI + cameras to monitor factory workers and line performance, illustrated by a widely criticized promo video.
  • Many commenters view the product as dystopian worker surveillance; a minority see it as a standard productivity tool with terrible marketing.

Ethical concerns & worker abuse

  • Strong view that this is “AI micromanagement”: enabling harassment, unrealistic quotas, and dehumanization (workers reduced to numbers, “who’s working and who’s not”).
  • Comparisons to Amazon-style warehouse monitoring and “pee bottle” conditions; fear that reducing friction for abuse will amplify existing bad behavior.
  • Several argue that tools which primarily help abusive managers are themselves unethical, not neutral.

Capitalism, power, and surveillance

  • Long subthread on whether this is “peak capitalism” or more like neo‑feudalism: extreme power imbalance, weak unions, blurred lines between corporate and state control.
  • Some argue real capitalism requires voluntary, non‑coercive exchange, which doesn’t exist under such power asymmetries; others say this is just “true capitalism in practice”.
  • Concerns about ubiquitous AI cameras in workplaces and beyond, and parallels to social credit / “good behavior” systems.

Arguments defending/normalizing the tool

  • Defenders compare it to long‑standing performance tracking: punch clocks, quotas, simple output metrics, and existing “bossware” for office workers.
  • They say the real issue is management intent; software merely provides data that could also be used to reward high performers or optimize bottlenecks.
  • Some with factory experience report that careful, humane analysis can improve operations without abuse; others with similar experience strongly disagree and call the product inhumane by design.

Marketing, culture, and optics

  • The video is widely seen as amateur, cruel in tone, and revealing of founders’ lack of empathy—especially the “worker as number” framing and scolding scene.
  • A few note that hierarchical, scolding management styles are common in parts of India, but argue that’s precisely the problem, not an excuse.
  • Multiple commenters suggest it could have been framed around process improvement and worker training/rewards rather than policing “slackers.”

YC and VC ethics; meta‑HN

  • Debate over YC’s moral stance: some say it will “back anything that makes money,” others counter with examples of YC rejecting or ejecting unethical startups.
  • Side discussion on VC investments in adware, crypto, and weapons, with differing views on whether these are inherently unethical.
  • Meta thread about HN ranking: staff clarify the story tripped an automated “flamewar” penalty, not manual censorship, and restate a policy of moderating YC‑related threads less, not more.

Troubleshooting: A skill that never goes obsolete

Value of Troubleshooting vs Building

  • One camp argues that spending “more time troubleshooting than building” is a red flag: it can distort your reward system, make you complacent, and trap you in low-status “support” roles.
  • They emphasize opportunity cost: time fixing a bug for 5% of users might be less impactful (and less career-rewarded) than building a new feature for 50%, depending on context.
  • Others strongly disagree, saying troubleshooting has been the foundation of successful, well-paid careers (e.g. SRE, ops, consulting, retainers) and is often exactly what management and teams value most in crises.

Career Dynamics and Perception

  • Several commenters describe getting stuck as the “support/troubleshooting person” while colleagues who ship fast (often buggy) features get promoted.
  • Advice: if an org only rewards flashy feature work and ignores maintenance, that’s a systemic problem—either change how work is measured (reliability metrics, leading indicators) or change jobs.
  • Conversely, being the “go-to firefighter” can create credibility, leadership opportunities, and promotions—provided the org respects reliability and quality.
  • There is concern about burnout and single points of failure; some intentionally step back so others develop troubleshooting skills.

Nature and Teachability of Troubleshooting

  • Many see troubleshooting as a distinct, generalizable skill: systematic hypothesis testing, questioning assumptions, ruling out confounders, narrowing scope.
  • Some claim it’s largely an innate mindset/curiosity that can’t be taught past a certain career stage; others counter it’s teachable but attitude- and interest-dependent.
  • It’s compared to the scientific method and to ITSM “problem” vs “incident” analysis, and framed as broader than just reading code.

Practices, Tools, and Techniques

  • Common recommended practices:
    • Start simple; don’t assume the problem is complex.
    • Change one thing at a time; avoid fixation.
    • Clarify the problem and shared assumptions with the team.
    • Increase observability/telemetry; gather more data when stuck.
    • Keep careful written notes of hypotheses, experiments, and results.
  • There’s debate over heavy use of debuggers vs fast iteration with logging/print statements; platform and codebase size matter.

Analogies, Pay, and Organizational Incentives

  • The “reliable car mechanic” analogy is hotly debated: some say such mechanics are underpaid; many reply that the reliable ones are busy and well-compensated.
  • Parallel in software: feature work is “sexy” and visible; maintenance and reliability are treated as cost centers, despite being crucial.
  • Several note that good diagnostic ability includes knowing what not to fix and where effort has real business impact.

Meta: Article and Site

  • The article resonated strongly with many who enjoy troubleshooting and see it as their comparative advantage.
  • The site was “hugged to death”; discussion touched on hosting limits, cache strategies, and ironic need to troubleshoot the article’s own availability.

US court upholds Theranos founder Elizabeth Holmes's conviction

Purpose of Imprisonment and Alternatives

  • One camp questions why Holmes, seen as non-violent and not an immediate physical threat, must be in prison rather than on house arrest or doing community service.
  • Others respond that this logic would apply to many incarcerated people and that “threat to society” is not the only justification; punishment and accountability also matter.

Deterrence, Especially for White-Collar Crime

  • Several argue that long sentences for high-profile white‑collar criminals are needed to deter future fraudsters, especially wealthy elites who otherwise feel untouchable.
  • Critics counter with research suggesting longer sentences don’t clearly deter crime and note that overall U.S. incarceration rates are already extremely high.
  • Some nuance: deterrence may be weak for impulsive street crime but more relevant for deliberate, multi‑year financial schemes.

Nature and Severity of Holmes’s Crimes

  • Commenters emphasize the scale of investor fraud (hundreds of millions to nearly a billion) and compare it to major bank robberies.
  • Many see a miscarriage of justice in her acquittal on patient-related counts, arguing her fake tests endangered lives, even if not legally proven.
  • Others stress she was convicted strictly for investor fraud, not patient harm, but note that fraud would not have been possible without misrepresenting test accuracy.

Fairness, Class, and Race in the Justice System

  • Some say her imprisonment is a “litmus test” that the system can still punish well-connected “nepo kids,” in contrast to impunity for bankers after 2008 or some political figures.
  • Others point out racial double standards: drug offenders of color get harsh time while there’s visible sympathy for a wealthy white woman.

Prison Conditions and Holmes’s Narrative

  • Holmes’s description of prison as “hell and torture” is met with skepticism, given reports that her facility is a relatively comfortable minimum‑security camp.
  • Several view her statements as self‑pitying and consistent with a manipulative persona.

Holmes and Future Prison Reform / Broader Comparisons

  • A few speculate she could leverage her profile for prison reform; others strongly reject a convicted fraudster as movement figurehead.
  • Side discussions compare her treatment to crypto fraud, Trump’s civil and criminal cases, and potential future scrutiny of other tech leaders.

Tesla sales in Europe down 45% in January

EV Market vs Tesla’s Performance

  • Commenters note that while overall EU car sales dipped slightly, battery EV sales actually rose ~34–37% YoY; BEVs went from ~10% to ~15% market share.
  • BEV units: ~92k → 124k YoY, while Tesla dropped from ~15k to ~7.5k units, sharply losing share of a growing market.
  • Several see this as a very poor Tesla result masked by aggregate “car sales down” headlines.

Competition, Product, and Pricing

  • European, Korean, and Chinese brands now offer a wide EV range (small city cars to family SUVs), often cheaper, with more conventional designs and local dealer networks.
  • Tesla’s lineup is seen as aging: no truly new mass models for years; incremental refreshes not obvious from the outside.
  • In Europe, Tesla lacks small/cheap EVs; Model 3 is now roughly twice the price of entry‑level EVs cited.
  • Some argue the current Model Y refresh and removal of French incentives explain part of the January dip; others think that’s insufficient to explain a ~45–57% fall.

Musk’s Politics and Brand Damage

  • Large subthread claims Musk’s far‑right alignment, Nazi‑adjacent signaling (salute, “14 words” references), and open meddling in European politics (e.g. AfD support) have made Tesla ownership a political statement.
  • Multiple Europeans say they now avoid Tesla specifically to not “fund” or be associated with Musk; some owners report embarrassment, “I bought this before he went crazy” stickers, and fear of vandalism.
  • A minority argue this is overblown “virtue signaling” and that most buyers don’t follow politics closely; they doubt the salute was intentional or meaningful.

Reliability, Quality, and Ownership

  • Links to German TÜV data show Model 3 near the bottom of 2–5‑year reliability rankings, with issues in lights, brakes, and suspension; supporters counter with UK data where Model Y ranks highly.
  • Debate over whether inspection failures measure reliability or just maintenance behavior and service practices.
  • Several Europeans describe Tesla build as “cheap” vs incumbents; others say feature‑for‑price (software, range, superchargers) is still strong.

Tariffs, Trade, and Geopolitics

  • EU tariffs on Chinese‑built EVs (including made‑in‑China Teslas) are flagged as another headwind, but some commenters oppose these barriers, preferring cheap Chinese EVs to accelerate decarbonization.
  • Broader geopolitical worries (US reliability as partner, Musk’s role in US administration, SpaceX/Starlink leverage) color attitudes toward buying US products generally.

Stock, FSD, and Tesla’s Future

  • Many see Tesla’s valuation as meme‑like, disconnected from fundamentals; repeated “FSD in 12 months” promises are widely called out.
  • Some expect brand damage plus fierce competition to erode Tesla’s position, especially in Europe; others point to still‑high global deliveries and argue it’s premature to call decline.

Ask HN: Recommend resources that helped your game dev journey?

Design, Vision & “What Is Your Game?”

  • Several comments push the idea that design starts with a strong vision: what feelings, story, or “space” you want to create.
  • Some suggest the project may be more of a social “space” or sandbox than a traditional goal-driven game; expectations differ depending on how it’s labeled.
  • Others emphasize separating “play” (pure delight) from “game” (goals, constraints, winning conditions) and being clear about which you’re building.

Feedback & Playtesting

  • In-person, empathetic feedback from experienced players is seen as far more useful than anonymous message-board critiques.
  • Recommended approach: small, trusted alpha group → iterate → slightly larger group → only then expose to harsh public venues like Reddit.
  • Feedback should be filtered: not all gamer opinions are right; it’s up to the creator to decide what to adopt.

Scope, Practice & Game Jams

  • Strong consensus: make lots of small games, prototypes, and clones; don’t expect the first big idea to work.
  • Game jams (Ludum Dare, itch.io jams, private 48‑hour jams) are praised as the best way to practice finishing games and discovering what’s fun.
  • Multiple people warn against oversized first projects and stress being willing to abandon ideas that aren’t fun.

Mechanics, Fun & Studying Other Games

  • Advice to deeply study games you love (including board games) and write down what works, how it feels, and why.
  • Board games are highlighted as great lessons in minimal, clearly communicable mechanics.
  • Comments discuss “skill ceiling,” systemic mechanics, and the importance of polish (e.g., “game feel,” screenshake, responsiveness).

Marketing, Onboarding & Accounts

  • Strong criticism of forcing sign-up before play; many say they immediately close the page.
  • Recommendation: instant playable demo, guest mode, and a landing page that sells the core experience rather than technical features.

Tools, Engines & Technical Resources

  • Popular technical starting points: Godot (plus its docs), LÖVE, PICO‑8, CS50’s game dev course, tabletop design books, open-source game code, game mods.
  • Links to specialized resources: redblobgames, Game Programming Patterns, low-level graphics (OpenGL/WebGL), Game Boy dev, shaders, and simulation-heavy games.

Books, Talks & Video Resources

  • Often‑recommended design books include:
    • Designing Games: A Guide to Engineering Experiences
    • The Art of Game Design
    • Game Feel
    • Challenges for Game Designers
    • “Game Thinking,” “Save the Cat,” various essays and blogs (e.g., lostgarden, Liz England).
  • Suggested talks/videos: devlog analyses, “art of screenshake,” systemic design talks, classic FPS commentaries, game design YouTube channels, veteran postmortems.

Communities & Career Realism

  • Suggested communities: itch.io, Discord servers (general gamedev and specific creators), new sites like gamedev.city, subreddits focused on feedback.
  • Several comments stress that solo gamedev requires many disciplines and long-term motivation; commercial success is statistically rare, so intrinsic motivation and realistic expectations are important.

AI Tools & Information Diet

  • Some encourage experimenting with AI tools; others argue new devs should first learn fundamentals (art, code) themselves.
  • Sharp criticism of over-consuming startup/VC “thought leaders”; recommendation to “clean up your information diet” and focus on making and testing games instead of absorbing hype.

Spotify's Beta Used 'Pirate' MP3 Files, Some from Pirate Bay (2017)

Early Spotify and Pirate MP3s

  • Multiple early users say beta-era Spotify clearly contained pirated files, often matching known scene/BitTorrent rips (same glitches, bad encodes, inconsistent bitrates).
  • Some recall the beta catalog being a superset of employees’ and testers’ private libraries, with huge breadth and many obscure or bootleg releases.
  • Early clients reportedly scanned local drives, uploaded missing tracks to Spotify’s backend, and even shared local music on the network—enough for some workplaces to block it.

Legal and Copyright Nuances

  • Central question: if Spotify was paying labels, does the pirated origin of the file matter?
    • One side: if rights holders are compensated, using a convenient pirated copy is practically and morally minor.
    • Other side: if they were downloading from public torrents and seeding, that’s still infringement, regardless of later licensing.
  • Discussion of US vs EU law: ripping your own CD vs downloading an identical MP3; some jurisdictions treat “illicit lineage” of bits as legally significant.
  • RIAA/MPAA are seen as lacking formal enforcement power but wielding huge practical power via ruinous lawsuits and license blackmail (e.g., playlist and trademark disputes).

Startups, Crime, and Survivorship Bias

  • Many frame Spotify as part of a broader pattern: early success via piracy or regulatory arbitrage (YouTube, Crunchyroll, Uber, Airbnb, various file lockers).
  • Viewpoint A: “Don’t worry about regulatory—if you get big enough, you can clean it up later.”
  • Viewpoint B: this is corrosive; most who try this fail or get crushed (Grooveshark, Megaupload, Kim Dotcom, FTX, Theranos), and we only remember the winners.
  • Several draw parallels to modern AI training on copyrighted data: same “break rules first, legalize later” dynamic.

User Reactions, Lock-In, and Self-Hosting

  • Many fondly remember beta Spotify as “magical” compared to today’s more restricted, label-driven catalog; lots of playlists were gutted once licensing went legit.
  • This pushed some users permanently back to “files on disk,” NAS setups, or services like Bandcamp, Tidal, or self-hosted music lockers.

Spotify vs YouTube and the Rogan Factor

  • Some resent a perceived fixation on Spotify’s sins while YouTube, with much larger cultural and infringement impact, is treated as inevitable infrastructure.
  • Others single out Spotify for aggressively platforming and paying Joe Rogan, describing personal harm from COVID discourse and vowing to boycott Spotify regardless of YouTube’s behavior.

Artist Compensation and Alternatives

  • Several argue the real immorality isn’t the early piracy, but that Spotify’s mature model still underpays artists while aligning tightly with labels.
  • Proposed alternatives include:
    • Donation/“pay what you want” layers where users direct most of their subscription money to chosen artists.
    • Decoupling distribution from payments: use any files (even torrents) but report plays to a payment system that compensates rightsholders.
    • Relying on human-curated radio (KEXP, KCRW, others) plus Bandcamp purchases instead of algorithmic playlists.

How Core Git Developers Configure Git

Global ignores and editor/IDE files

  • Several people like a global ignore file ($XDG_CONFIG_HOME/git/ignore), e.g. for .DS_Store or personal .envrc, so they don’t pollute project .gitignores.
  • Others warn that hiding files only locally can surprise collaborators, since those files aren’t ignored in the repo.
  • Strong disagreement over committing editor/IDE directories like .vscode:
    • Pro: shared debug/launch/tasks settings benefit all VS Code users; VS Code config is hierarchical and composable.
    • Con: repo clutter, tool-specific noise, and lack of similar treatment for other IDEs; prefer .editorconfig or global config.

Local-only ignores

  • .git/info/exclude is highlighted as a useful per-repo ignore that doesn’t touch tracked files or shared .gitignore.
  • Some just put such patterns in their global ignore and force-add when needed.

Diffs, conflict styles, and tooling

  • Many readers immediately adopted diff-related settings: diff.algorithm=histogram, diff.colorMoved, merge.conflictStyle=zdiff3, whitespace highlighting, etc.
  • Strong praise for three-way conflict styles (diff3/zdiff3) as making some conflicts solvable or at least mechanically resolvable.
  • Third-party tools get lots of love: difftastic, delta, diff-so-fancy, bat as pager, kdiff3, etc.
  • A few reverted from delta back to plain diffs because pretty output complicates copying patches or small terminals, though piping/redirecting is noted as a workaround.

CLI vs GUI

  • Some mostly use VS Code’s Git UI and find it covers 99.9% of needs; graphical diffs and merge UIs are praised.
  • Others argue you should gradually learn the CLI because GUIs hide model details and fall short for complex history surgery and debugging.

Branch naming: master vs main

  • Sarcastic and serious complaints about the main change: breaks aliases and scripts that assumed master, adds noise in logs/CI, and is viewed by some as unnecessary “word policing.”
  • Specific technical pain around mirrors and symbolic HEAD refs when upstreams rename/delete default branches.
  • Counterpoints: Git only changed defaults for new repos; any repo has always been free to use other names; robust tooling shouldn’t hardcode master. Some simply prefer “main” as shorter/nicer.

Config philosophy, safety, and defaults

  • Many share custom configs and aliases (lg fancy logs, out for unpushed commits, “quick push” functions).
  • Divided views on “clearly better” options:
    • fetch.prune / pruning: fans want remotes to mirror reality; critics fear losing recoverable data and insist deletions stay manual.
    • push.autoSetupRemote: some like auto-publishing branches; others insist this should remain explicit.
  • Wishes for versioned “modern defaults” profiles instead of touching long-stable defaults.
  • Safety suggestions include always using --force-with-lease (often via alias) and enabling commit/tag signing with SSH-based GPG.

Git’s evolution

  • One commenter assumes Git is unchanged in 15 years; replies point out that many highlighted configs are fairly recent quality-of-life features, and that deeper changes like a new hash algorithm are in progress.

What would happen if we didn't use TCP or UDP?

SCTP as “better TCP” and why it failed on the Internet

  • SCTP offers message semantics, multiple independent streams, and optional reliability; it underlies WebRTC data channels and is heavily used in mobile/telecom cores.
  • Despite technical merits, it’s “effectively unsupported” on consumer devices: kernel implementations are rare/slow, userland needs raw sockets, and middleboxes/NATs often drop or mangle non‑TCP/UDP protocols.
  • Many see SCTP as an example of protocol ossification: new L4 protocols (SCTP, MPTCP) are blocked by middleboxes that only understand TCP/UDP.

QUIC vs SCTP/TCP and why QUIC exists

  • QUIC chose UDP precisely because UDP is widely passed by routers and NATs; SCTP over bare IP generally can’t traverse home NATs.
  • QUIC integrates TLS to cut round trips and improve TTFB, especially on high‑latency links, and provides multiplexed streams like SCTP/MPTCP.
  • Some ask why we don’t “just use QUIC instead of TCP”: answers note QUIC is young, has implementation bugs (e.g., HTTP/3 in some browsers), uneven language/OS support, and far less operational experience than TCP.
  • Viewpoint: QUIC is a powerful third option between TCP and UDP, but unlikely to fully replace TCP; protocol choice will remain application‑specific.

Middleboxes, NAT, and protocol behavior

  • Consumer NATs multiplex based on transport‑layer ports; they’re usually only aware of TCP/UDP (and a few special cases like ICMP). Unknown protocols may consume scarce IPv4 addresses or just be dropped.
  • One report: a Netgear router “zeroed” the first 4 bytes of custom packets, apparently assuming they were TCP/UDP ports.
  • Discussion clarifies layering: IP has protocol numbers, not ports; ports live in TCP/UDP/SCTP headers and are protocol‑specific.
  • Speculation about the article’s “single packet got through” cliffhanger: likely a firewall created a flow for the first packet, then dropped later ones when it couldn’t match them.

DNS over TLS vs HTTPS and censorship

  • DoH is described as primarily an anti‑censorship and anti‑ISP‑logging measure: port 443 traffic is hard to block wholesale, whereas DoT/853 is trivially blockable.
  • Others argue both DoH and DoT rely on encryption for privacy; DoH’s “obscurity” undermines network operators’ ability to manage DNS on their own networks.

IPv6 design and deployment friction

  • Some wish early IP had stronger header integrity, forcing earlier IPv6 and cleaner protocol evolution; others note IPv6 was initially over‑engineered (mandatory IPsec) and hard to implement.
  • Debate over SLAAC vs DHCPv6, /64 vs /56+/48 allocations, and Android’s lack of DHCPv6 complicating home subnetting; many ISPs don’t follow best‑practice prefix delegation.

Raw sockets and other stacks

  • Raw/packet sockets (AF_PACKET, AF_INET+SOCK_RAW) let you bypass TCP/UDP to experiment with custom transports, but require elevated privileges and generally don’t survive through NAT/firewalls.
  • Thread briefly mentions alternative or historical stacks/protocols (IL, IPX, UUCP/NNCP, Plan 9’s flexible addressing, Infiniband, Ethernet WAN) as reminders that TCP/UDP/IP were not inevitable.

Dogs may have domesticated themselves because they liked snacks, model suggests

Plausibility of dog self-domestication

  • Many commenters doubt that wolf domestication was purely “self‑driven,” arguing humans must have strongly shaped which animals survived and bred.
  • Core objection: why would early humans keep feeding wolves if they didn’t yet provide value (hunting help, protection, alarm system)?
  • Others counter that humans aren’t purely transactional: surplus after big kills, children feeding cute animals, and general human enjoyment of feeding wildlife are enough to start the process.
  • A common scenario offered: bolder but less aggressive wolves scavenge on middens and feces at the edge of camps; aggressive ones get killed; over generations this selects for tamer, more human‑tolerant animals without an explicit “breeding program.”

Mutualism and ecology

  • Several comments propose early wolf–human hunting cooperation: humans bring tools and cognition, wolves bring speed, senses, and tracking; both gain more food.
  • Wolves near camps may deter more dangerous megafauna (big cats, bears), making their presence indirectly valuable.
  • Analogies are drawn to “problem bears,” raccoons, baboons, and urban coyotes already adapting to human food and proximity.

Cats, other species, and domestication constraints

  • Side debate over whether cats mostly hunt birds or rodents; anecdotes show it varies strongly by individual cat and environment.
  • Discussion that successful domestication usually requires preexisting social structures (packs, herds, colonies); this is used to argue cats and dogs fit, bears and snakes mostly don’t.

Food motivation and behavior

  • Long thread on what “food‑motivated” means in dogs and cats: not “likes food” but “will reliably work for food despite distractions.”
  • Many examples of animals more motivated by play (balls, work) or attention than by ordinary treats, though high‑value foods can override that.
  • Parallels drawn to humans’ variable “food drive.”

Ethics and meaning of domestication

  • One line of discussion expresses remorse that dogs’ bodies and minds were reshaped for human purposes, creating a sense of moral debt to treat them well.
  • Others respond that domestication is a mutually beneficial evolutionary strategy: dogs as a species exist and thrive only because of humans, and humans were also reshaped by dogs.
  • Broader concern that humans have been poor stewards of both domestic and wild animals, despite the deep emotional connection many people feel.

There isn't much point to HTTP/2 past the load balancer

gRPC and HTTP/2 inside infrastructures

  • Several commenters note a major in-datacenter use case the article barely touches: gRPC.
  • Teams have invested heavily in HTTP/2 internally to get gRPC’s multiplexed, binary, streaming RPCs, with clear performance wins over JSON/HTTP APIs.
  • Others clarify that this is mostly a non-browser story; browsers don’t expose “native” gRPC over HTTP/2, so you still need specialized clients or fall back to WebSockets/other transports.
  • Load balancing gRPC can be tricky: if you use only L4 balancing with long-lived connections, traffic can skew heavily to a subset of backends; proper HTTP/2-aware L7 proxies avoid this.

Do you even want a load balancer?

  • One camp argues: if your framework and language are good, you shouldn’t need a reverse proxy; it adds another protocol, failure mode, and attack surface.
  • The dominant response: production app servers are not hardened for direct Internet exposure (slowloris, malformed headers, DoS), and most docs assume a fronting proxy.
  • Common reasons given for load balancers/reverse proxies: TLS termination, central security enforcement, static asset performance, URL rewrites, multi-service routing, graceful deploys, failover, hiding private resources, and solving DNS/TTL and multi-IP issues.
  • Strong disagreement over where TLS should end: some insist on end-to-end encryption (post-Snowden), others terminate early and rely on internal network controls or VPNs.

Is HTTP/2 past the load balancer worth it?

  • Article’s claim: inside the DC, low latency and long-lived connections mean HTTP/2’s multiplexing gives “little benefit,” and encryption/TLS handling adds complexity, especially in Ruby where parallelism is weak.
  • Pushback:
    • Header compression and fewer connections can matter at scale; one comment cites measurements where headers were a huge share of bandwidth.
    • Multiplexing can mitigate ephemeral port exhaustion and reduce syscall overhead by coalescing many small responses.
    • Some see large speedups even on localhost and question the lack of benchmarks supporting “no benefit.”
  • Others side with the article: implementing HTTP/2 end-to-end (HPACK, flow control, stream state) is significantly more complex than HTTP/1.1, and for most typical LAN workloads the gain is marginal.

Streaming, HTTP/2 vs HTTP/3, and browser gaps

  • HTTP/2’s bidirectional streams are praised for long-lived, duplex communication (especially service-to-service), but browsers don’t expose this cleanly to JS; WebSockets and now WebTransport are the de facto options.
  • Some note HTTP/2 can perform poorly on lossy mobile networks due to TCP-level head-of-line blocking; HTTP/3/QUIC improves this but currently costs more CPU and relies heavily on userland stacks.

Security and correctness

  • End-to-end HTTP/2 substantially reduces classic HTTP request-smuggling issues; downgrading to HTTP/1.1 at the proxy reintroduces risk.
  • A few operators disable HTTP/2 on load balancers until they’re confident implementations are free of such vulnerabilities.

How to change your settings to make yourself less valuable to Meta

Ad Targeting vs. “Value” to Meta

  • Some wonder if turning off personalization just makes Meta show “highest-paying” generic ads and thus increases user value.
  • Others with ad-tech experience argue the opposite:
    • Advertisers bid more for well-targeted impressions, so less targeting → lower bids, more repetition, worse engagement.
    • Meta might compensate only by increasing ad density, not by magically making you more valuable.
  • Consensus: these settings can reduce how precisely you’re targeted, but don’t make you more profitable.

“Just Quit Meta” vs. Practical Constraints

  • Many say the only real way to be less valuable is to stop using Facebook/Instagram/WhatsApp altogether.
  • Counterarguments:
    • Meta still tracks via embedded JS, pixels, and SDKs on third‑party sites and apps; shadow profiles persist even without an account.
    • In many regions and communities, Facebook/WhatsApp are the de facto infrastructure for local business, school sports, parenting groups, special‑needs support, hobby groups, and marketplace. For these users, “just quit” is costly or unrealistic.
    • Partial harm reduction (settings, blockers, containers) is defended as a reasonable compromise.

Technical Tactics to Reduce Tracking

  • Common advice:
    • Use uBlock Origin (and extra privacy/social lists), Firefox containers, NextDNS, or similar.
    • Block social widgets, avoid social logins, and disable/limit Meta-owned domains.
    • Use browser instead of apps; on mobile, consider patched APKs (e.g. ReVanced) where feasible.
    • Extensions like Consent‑o‑Matic to auto-reject tracking in cookie banners; some use AdNauseam to click all ads.
  • Notes that blocking Meta apps at network level can be surprisingly hard, and server-side tracking by partner sites still leaks data.

Within-Facebook Settings & Workarounds

  • Use Meta’s ad settings / ad topics page to opt out of categories and see what they’ve inferred about you.
  • EU users discuss the new “pay or be tracked” model, with some in a “less personalized ads” middle ground and even interstitial ad timers that help break doomscrolling.
  • Tips shared for:
    • “Friends only” chronological feeds via hidden parameters.
    • Clearing off‑Facebook activity and minimizing engagement.
    • Language switching (e.g., to a less-supported language) to drastically reduce ad inventory.

Broader Reflections

  • Some treat these tweaks as moral/political resistance to Meta’s business model; others see them as self-delusion that masks continued dependence.
  • Debate over whether society should rely on regulation (especially in the EU) rather than individual technical workarounds.