Hacker News, Distilled

Impact of Comedy Central Site Shutdown

• Users lament loss of 25+ years of Daily Show, Colbert Report, and other CC late-night material, seeing it as erasure of political and cultural history.
• Some note specific interviews and convention coverage now apparently unavailable anywhere official.
• A few point out that some Comedy Central clips still exist on YouTube, but coverage is fragmentary and inconsistent.

Paramount+, Finances, and Business Strategy

• Many see the move as “belt-tightening” by a heavily indebted company betting everything on Paramount+.
• There’s disagreement whether “all” content will eventually be on Paramount+: some argue that’s the clear strategic goal; others cite past removals and missing seasons as evidence it likely won’t be.
• Users question how much hosting old clips really costs and suggest alternative monetization (YouTube ads, keeping an ad-supported archive) might be better than deletion.
• Management is criticized for short-termism, poor streaming execution, and destroying goodwill and brand value.

Archiving, Piracy, and Data Hoarding

• Strong sentiment that individuals should download what they love; “torrenting as moral imperative” is a recurring theme, framed as cultural preservation rather than theft.
• Some describe private tracker communities and “packrat” archivists who maintain huge NAS collections as de facto distributed archives.
• Others worry that uncoordinated personal hoarding is inefficient but concede it may be more resilient under current legal regimes.

Copyright, Public Domain, and Reform Proposals

• Extensive debate on whether copyright should lapse if works aren’t kept reasonably available (“use it or lose it”).
• Multiple proposals: much shorter terms (5–20 years), renewable with fees; compulsory licensing with guaranteed payment but no veto; loss of protection when originals are altered and originals suppressed.
• Several argue current long terms and takedowns harm the historical record; some counter that creators’ rights and trade secrets matter.

Technical and Long-term Storage Issues

• Discussion of how “hard drives are cheap” breaks down at scale when you factor in RAID, backups, monitoring, and power.
• Ideas for ultra-long-term media (M-Discs, quartz/5D optical storage) are mentioned; others suggest institutional “copying monasteries” as more realistic.

Broader Reflections

• Many see this and similar MTV News takedowns as symptoms of enshittification, late-stage capitalism, and misaligned incentives.
• Concern that 21st-century digital culture may be less accessible to future generations than earlier centuries due to fragility of digital archives and corporate control.

Valuation Context & Comparisons

• Thread notes SpaceX’s rumored $210B valuation and compares it to Bytedance (~$268B).
• Some argue Bytedance would be worth more without geopolitical risk and potential US bans.
• Debate over whether a US IPO with majority US ownership would prevent bans; others claim US policy is political and “goalposts move,” citing past TikTok data-onshoring/Oracle arrangements.
• Concern that minority (49%) ownership plus control structures could still leave real power outside the US.

Asteroid Mining, Gold, and Macroeconomics

• One view: $210B seems low if SpaceX can eventually mine “trillion‑dollar” asteroids.
• Counterpoints:
  • Historical analogy: Spanish New World gold caused inflation rather than broad national wealth.
  • Adding huge amounts of gold would likely crash gold prices or devalue money.
  • Real wealth is goods and services, not nominal money or bullion.
• Some suggest space resources could still be transformative for non-gold materials or in‑space construction, but others call asteroid mining and moving asteroids to LEO “pure sci‑fi” for centuries.

SpaceX Business Model, Starlink, and Future Demand

• SpaceX reused rockets and created Starlink partly to fill launch demand; Falcon 9 is seen as likely profitable on its own, while Starship investment keeps overall profits down.
• Disagreement whether Starlink is “profitable” without fully allocating rocket costs.
• Ideas for future demand:
  • Moon bases (tourism, science, manufacturing, resource extraction).
  • Orbital fuel depots selling high‑margin propellant.
  • Commoditized launch services (“Expedia for space”) enabling many small satellites.
  • Possible space‑based industry (e.g., data centers).

Starlink Market vs Terrestrial Networks

• Starlink revenue reportedly concentrated in wealthy, populated regions.
• Some say fiber upgrades (e.g., 1 Gbps in parts of Australia) will undercut Starlink; others argue many rural and semi‑rural areas will never get fiber or only at very high cost.
• Niche use cases highlighted: RVs, boats, second homes, remote workers, redundancy alongside fiber/cable/5G.

Mars, Colonization, and Terraforming

• One camp: Starship’s “real” market is Mars settlement; people will pay for one‑way or semi‑one‑way migration.
• Skeptics: no meaningful Mars market for centuries; current tech cannot support safe, self‑sustaining habitats or terraforming; life there would be harsh and fragile.
• Proponents emphasize frontier mentality and long‑term terraforming concepts; opponents call terraforming a largely unproven, poorly constrained “pipe dream.”

Financing, Ownership, and Risk

• Some speculate tender offer proceeds could help reduce margin pressure from loans collateralized by other holdings.
• Concern that control over “world internet” or an orbital fuel monopoly could invite political pushback similar to TikTok’s experience.

Disillusionment with Tech & Big Companies

• Many relate to leaving big tech or “the industry” due to cynicism, rent‑seeking, and value extraction over solving real human problems.
• Several contrast the 90s’ techno‑optimism (“enough tech to help, not enough to dominate”) with today’s attention harvesting, surveillance, and platform monopolies.
• Some still see this as a “golden age” (fertility tech, self‑driving taxis, LLMs, VR, open source), arguing pessimism may reflect aging more than tech itself.

AI, Automation & the “Laundry vs Art” Meme

• Long debate over the quip: “I want AI to do my chores, not my art.”
• One side: It captures frustration that tech automates joy (creative work) instead of drudgery (housework), and symbolizes misaligned incentives.
• Others: Call it clickbait, note laundry/dishwasher machines already exist, and argue AI isn’t stopping anyone from making art—only changing paid markets.
• Class issues surface: wanting to escape menial labor is seen by some as “classist,” others reject romanticizing such work while affirming dignity for workers.

Labor, Inequality & Capitalism

• Multiple comments tie modern tech to shifting income from labor to capital and eroding the middle class, citing falling labor share of income.
• Others counter that technology historically enabled a middle class and that inequality itself isn’t necessarily harmful; policy and access to capital are key.
• Discussion of gig economy and “platformization” as mechanisms to underpay workers, sidestep labor laws, and concentrate power.

Advertising, Platforms & Surveillance

• Strong sentiment that computing has become an arm of advertising and psychological manipulation, with attention and data as primary extractive targets.
• Blame variously placed on ad‑funded models, search/SEO, smartphones, app‑store policies, and global platforms’ winner‑take‑all dynamics.

Integrity, Meaning & Leaving the “Bullshit Industrial Complex”

• Many resonate with the author’s moral exhaustion: producing PR/BS, not believing in their work, or doing “corporate drudgery” like press releases.
• Some argue integrity means not just exiting but actively exposing manipulation patterns so others can resist.
• Others are pragmatic: they admire leaving for ethical reasons but admit they’d stay for financial security.

PR, Hype & Ethics

• PR is variously described as propaganda, “highly optimized bullshit,” and necessary brand strategy.
• One camp says good marketing co‑creates products and visions (e.g., charismatic founders and brand narratives).
• Critics stress the thin line between aspirational storytelling and outright fraud (invoking cases where marketing long preceded working tech).

Overall impressions & model comparisons

• Many commenters find Claude 3.5 Sonnet extremely strong, often preferring it over GPT‑4/4o for coding, data-heavy tasks, and “human-like” language.
• Others report the opposite: GPT‑4o feels more capable, especially for assistant-style reasoning and calculus/physics; experiences are clearly mixed.
• Some see Sonnet as slightly ahead of GPT‑4o on coding and extraction from long documents; Gemini is mentioned for much larger context windows.
• Benchmarks are viewed skeptically: several note that leaderboard scores don’t match their day‑to‑day experience.

Coding ability & tools

• Strong praise for Sonnet 3.5 as a coding assistant: “junior engineer or better,” very fast at prototyping, refactors, infra planning, Dockerization, tests, docs, etc.
• Works especially well on greenfield tasks or small to medium codebases; less reliable when deeply entangled with large existing systems or modern idiomatic framework patterns.
• Users mention workflows with IDE integrations and agents (Cursor, Cody, Aider, Sweep, custom bots) and note that semi‑autonomous PR agents are still mediocre (~25% success on SWE‑bench).

Reasoning, math, and consistency

• Some say Claude is better at careful, step‑by‑step reasoning and ambiguity handling; others show math/physics prompts where Claude fails and GPT is correct.
• A recurring theme is Claude 3.5’s improved consistency: fewer wild swings in quality once a good prompt style is found.

UX, pricing, and limits

• Claude Pro’s opaque usage limits frustrate users; message caps are token‑dependent and capacity‑dependent, which feels unpredictable.
• OpenAI’s consumer products also have caps and dynamic throttling; both sides are criticized for lack of transparency.
• Projects (persistent context with files/instructions) and Artifacts are seen as major productivity features; some wish for repo integration and voice interfaces.
• Account creation friction: phone-number requirement and blocking of Google Voice numbers turn some users away.

Safety, bans, and reliability

• Some accounts are auto‑banned with little explanation; appeal flows exist but are slow or inconsistent.
• Claude’s safety filters are stricter than GPT’s in some areas (e.g., code obfuscation), which some see as overreach.
• Occasional dangerous suggestions (e.g., rm -rf on keyring data) show that safety and caution are still imperfect.

Broader impacts

• Strong sense that modern LLMs dramatically accelerate experienced developers, especially on side projects.
• Debate over whether this threatens software jobs or mainly raises the bar for developers who can direct and verify AI‑generated code.

Article / Arbitrage Setup

• Thread revisits a 2020 story about exploiting a pricing mismatch between a pizzeria’s prices and DoorDash’s scraped menu.
• One update: the mismatch occurred during a DoorDash “demand test” period with no platform fees, which significantly increased arbitrage profits.

Legality and Fraud

• Some question whether intentionally sending dough-only pizzas would be fraud or even wire fraud.
• One view: it would be fraud against DoorDash, which paid for full pizzas.
• Others argue the restaurant could plausibly treat a DoorDash “customer” like any other caller changing an order, but counterpoints note restaurants typically only accept changes from the original caller, so this workaround likely wouldn’t fly.

Delivery Quality, Equipment, and Food Safety

• Multiple complaints about drivers lacking proper insulated bags, especially for pizza, leading to lukewarm food.
• Experiences vary by country and over time; some report branded bags earlier, fewer now, possibly as cost-cutting.
• Questions raised about how this passes food safety rules; responses note regulations usually apply to businesses, not end customers.

Gig Work Economics & Driver Pay

• A driver refusing to return a bag “because of rent” is cited as emblematic of the business model: squeezing time and pay.
• Many posters think drivers miscalculate earnings by ignoring fuel, maintenance, depreciation, and insurance.
• Some acknowledge a minority may profit by working only peak times or with special advantages.

Platform Profitability, ZIRP, and Data

• Discussion on whether food-delivery platforms are still unprofitable; consensus: losses are driven by driver payouts and aggressive growth/marketing, not dev costs.
• Uber’s recent profit is noted but seen as fragile, driven by price hikes and worse driver economics.
• Several commenters argue trip and personal data are far less valuable than commonly believed; lacking a large ad network, companies like Uber can’t easily monetize it at scale.

Capital, Inequality, and “Subsidized Convenience”

• Debate over whether VC-funded losses merely waste capital or represent a form of regressive wealth redistribution.
• Some see delivery apps as “broken window”–style economic activity: they employ people but divert capital from more socially useful investments.
• Others argue that, at least, money flows from investors to workers and customers via subsidies.

Impact on Restaurants and Reputation

• Significant concern about platforms listing restaurants without consent, mispricing menus, and delivering poor-quality or wrong orders that customers blame on the restaurant.
• Examples given of ghost kitchens operating under real restaurants’ names, creating reputational damage.
• Some wonder why more restaurants don’t sue; others think they fear retaliation or are too small to fight.

Customer Behavior, Convenience, and Responsibility

• One camp blames consumers for sustaining an “unsustainable” model instead of cooking or picking up food.
• Another counters that consumer behavior is shaped by capital, advertising, and what options exist; people rationally trade money for time and convenience, especially without cars or with demanding jobs.
• Several note that third-party delivery has degraded both traditional pizza delivery and in-restaurant or pickup experiences, as operations skew toward app orders.

Security and governance failures

• Commenters highlight that AU10TIX allegedly left a high‑privilege portal without 2FA and failed to fully revoke known‑leaked credentials for ~18 months, calling this typical rather than exceptional in the industry.
• Many see these vendors less as “high‑trust specialists” and more as generic software shops and “blame‑outsourcing firms” that let consumer‑facing brands offload risk and PR.

Data retention and “why do they keep IDs?”

• Strong criticism that full images of IDs and biometrics are retained instead of deleted after verification.
• Defenses raised: KYC/AML and other regulations often require storing verification evidence for years; firms also want an audit trail in case of disputes or court cases.
• Others argue retention could still be done in heavily restricted cold storage, with strict minimization, but isn’t.

User distrust and pushback

• Many now assume any ID or biometric shared online will eventually leak, and avoid services that ask for more than legally required—or drop transactions entirely.
• Examples include intrusive flows via Stripe or AirBnB‑style “liveness” videos; some see liveness checks as legitimate anti‑fraud tools, others as dystopian overreach.
• Breach statements like “no evidence of exploitation” are widely interpreted as “we didn’t or can’t really look.”

Law, liability, and lack of consequences

• Skepticism that anyone will face prison or serious financial penalties; past breaches (e.g., credit bureaus) are cited as proof that modest settlements are just a cost of doing business.
• Lawyers in the thread note it’s hard to prove duty of care, gross negligence, and concrete damages under current law; many call for explicit legislation and statutory damages.

Identity systems and alternatives

• Multiple comments advocate government‑run or government‑standardized digital ID / verification APIs (postal services, tax authorities, DMV‑style systems), citing Europe and Canada as partial models.
• Others strongly oppose centralized state ID power on civil‑liberties grounds, especially in the US context.
• Bank/carrier‑based OAuth‑like identity in Poland, Finland, Canada, etc. is cited as working better than ad‑hoc ID uploads; US adoption is limited by fragmentation and mistrust between banks.

Geopolitics and data export

• Concern over US citizens’ IDs and biometrics being processed in or by entities linked to Israel and other countries; some advocate boycotts, others argue for more targeted, evidence‑based divestment.
• It’s noted that US financial and tech firms routinely offshore access to sensitive data (e.g., India, Poland), so global exposure is already common.

Structural fixes and professionalization

• Some propose licensing / certification for software handling PII, akin to civil engineering, to give security‑minded engineers leverage and attach clearer liability.
• Others worry licensing would expand broadly, add rent‑seeking and bureaucracy, and may not meaningfully improve outcomes without stronger enforcement and incentives.

Subjective experience of brain “waste” and naps

• Many describe a tangible “brain fog” after intense mental work, with short naps (10–20 minutes) restoring clarity, focus, and a sense of “release.”
• Some feel skipping such naps is unhealthy; others note naps don’t fully replace a full night’s sleep.
• Polyphasic sleep and power naps are mentioned (e.g., solo sailors), but long‑term learning and decision‑making are reported as worse under chronic fragmentation.

Sleep’s roles beyond waste clearance

• Several argue that if waste clearance were the main point of sleep, 15‑minute naps would make 8 hours unnecessary; others counter that sleep also supports memory consolidation, motor learning, and physical recovery.
• Evolutionary arguments: sleeping less might not be advantageous because of higher energy needs and predation risk.
• Some note chronic short‑sleepers who can’t extend sleep despite good habits, pushing back on simplistic “just go to bed” advice.

Glymphatic system, 40 Hz stimulation, and skepticism

• Confusion noted over the article title, since the glymphatic system has been known for about a decade; the new element is 40 Hz light/sound entrainment in mice.
• Enthusiasm about potentially inducing waste clearance via noninvasive stimulation (light, sound, TMS), perhaps improving or partially substituting for sleep.
• Others emphasize:
  • Sleep likely has many functions; waste removal is just one.
  • Mouse models, including “humanized” mice, often fail to translate to human disease.
  • Frequencies effective in mice may differ for humans.

Binaural beats and auditory/light tools

• Multiple commenters connect the 40 Hz findings to binaural beats, Dreamachines, and phase‑targeted auditory stimulation products aiming to enhance deep sleep or power naps.
• Reports of mixed subjective effects: from refreshed to headaches or no noticeable change.
• One company building phase‑targeted auditory stimulation devices engages in technical discussion (slow‑wave targeting, ERPs), but explicitly says it’s not an insomnia cure.

Sleep optimization practices

• Suggestions include melatonin (with jurisdictional/legal caveats), vitamin D, magnesium, blue‑blocking glasses, dim/warmer lighting, screen avoidance, and exercise.
• Debate on melatonin and hormone manipulation vs. addressing underlying sleep issues.

Societal and ethical implications

• Concern that any technology improving sleep efficiency could become de facto mandatory in competitive workplaces.
• A controversial proposal to use prisoners as medical test subjects in exchange for reduced sentences is widely criticized as unethical and prone to abuse.

Malware incident and technical uncertainty

• KT, a major South Korean ISP, allegedly planted malware on customers using Webhard’s P2P “Grid Service,” in the context of a commercial dispute over network fees.
• Commenters highlight that the judiciary partly sided with KT, criticizing Webhard for unpaid “network usage fees” and poor disclosure of its grid operation.
• Many ask how the malware was actually delivered. Hypotheses include:
  • ISP MITM of unencrypted downloads (e.g., .exe or .torrent files).
  • Abuse of ISP-distributed “value‑add” software (antivirus, parental controls, TV access tools).
  • A honeypot torrent or a proprietary P2P protocol weaker than BitTorrent.
• It’s repeatedly noted that standard BitTorrent content is hash‑checked and MITM‑resistant; no clear technical explanation is given in the thread.
• Korean TV reporting and TorrentFreak are cited, but translations suggest only that KT planted malware that interfered with Webhard’s system, not that it propagated via BitTorrent itself. Overall: mechanism remains unclear.

Law enforcement and accountability

• Some are impressed that Korean police traced the malware to KT’s data center and charged 13 employees/contractors; they contrast this with perceived U.S. reluctance to criminally pursue large firms.
• Others are skeptical that any executives or chaebol leadership will see real consequences, expecting blame to fall on low‑level staff and subcontractors.

South Korean internet quality and policy shifts

• Several recall South Korea’s early 2000s reputation for ultra‑fast, cheap broadband and advanced mobile services.
• Many argue that privatization and an ISP oligopoly turned this into an under‑invested, high‑price system, with “sender pays” interconnect rules discouraging peering and driving services offshore.
• Opinions split on whether Korean internet is still “extremely fast” or now merely average as other countries caught up.

Cultural, regulatory, and software ecosystem issues

• Recurrent criticism of legacy requirements (banking tied to Internet Explorer/ActiveX, domestic crypto algorithms, cumbersome security plugins).
• Broader complaints that Korean consumer software (banking, mapping, chat, streaming) lags global peers and is constrained by regulation and protectionism.
• Discussion of strict laws on online speech, “cyber defamation,” and pornography/obscenity; some defend these as culturally grounded, others see them as overreach that chills criticism and entrenches state–corporate power.

Market structure and oligopoly dynamics

• Multiple comments frame telecom as a “natural monopoly” or de facto cartel: high entry barriers, weak competition, political capture, and cartel-like pricing behavior are seen as core drivers of both technical stagnation and abusive practices.

Contract and Choice of SpaceX

• NASA selected SpaceX to develop and deliver a U.S. Deorbit Vehicle for the ISS, with a single-award contract up to $843M; launch services will be procured separately.
• Some view $843M as very high for what sounds like a one-off tug; others note inflation, heavy mission assurance, and that the NASA Administrator had cited ~$1.5B earlier, making $843M look like a “bargain.”
• Commenters argue that if SpaceX can do it for $843M, other vendors would likely be even more expensive.
• SpaceX’s schedule slips (e.g., Starship) are acknowledged, but many see them as still more capable and reliable than alternatives like Boeing or Russian providers.

What the Deorbit Vehicle Might Be

• Ideas range from a modified Cargo Dragon to a Starship-based tug, or a dedicated propulsion module.
• One calculation notes NASA’s requirement of ~3236 N thrust for a 60-minute burn; Dragon’s 16 Draco thrusters could theoretically provide ~6400 N, but fuel mass and engine duty cycles are concerns.
• Suggestions of using multiple tugs, staged fuel, or orbital refueling arise, but are flagged as technically unproven at this scale.

Why Not Preserve or Re-orbit the ISS?

• Many wish it could be dismantled and returned in pieces (e.g., via Starship) for museums, or boosted to a long-term “graveyard” or Lagrange/Lunar orbit.
• Counterarguments emphasize:
  • Huge delta‑v and fuel needed to move a 450‑tonne station from low orbit to graveyard, lunar, or solar trajectories.
  • Limited ISS power-to-mass ratio for ion propulsion; multi-decade spirals estimated.
  • Structural aging: aluminum pressure shells, thermal cycling, fatigue, contamination (mold/dust) make indefinite use risky.
  • Ongoing drag at current altitude; without reboost it will naturally deorbit in an uncontrolled way.

Extend vs Retire

• Some argue for keeping and incrementally refactoring the ISS, attaching new modules and eventually cannibalizing old ones.
• Others note another decade might cost on the order of tens of billions, and NASA wants to redirect funding to lunar programs and rent space on smaller, private stations instead.
• There is concern that once deorbited, a replacement large, cooperative station may never materialize.

Environmental and Heritage Concerns

• Reentry is linked in the thread to atmospheric/ozone impacts; sending the ISS into the Sun is raised and then rejected as delta‑v–prohibitive and more polluting due to many extra launches.
• Some lament the loss of a historic asset and imagine preserving it as a “space landmark”; others say safety and cost override sentiment.

Pharmacology and Mechanism

• Xenon is described as an NMDA receptor antagonist and GABA potentiator, giving dissociative/anesthetic effects similar to ketamine and nitrous oxide.
• Despite being a noble gas, it can dissolve in lipids, interact via van der Waals forces, and compete at receptor sites (e.g., displacing glycine at NMDA receptors).
• Other noble gases can be anesthetic at high pressure; nitrogen is narcotic at depth (diving), consistent with lipid-solubility-based anesthesia.

Hypoxia vs Psychoactive Effects

• Some argue xenon’s effects are “just hypoxia” from breathing an inert gas.
• Others counter that:
  • Xenon’s subjective effects appear within seconds, faster and qualitatively different from simple oxygen deprivation.
  • In medical and responsible recreational contexts xenon is mixed with oxygen, and still clearly psychoactive.
• Consensus: asphyxiation risk is real and separate from its receptor-level drug action.

Medical Uses and Safety Concerns

• Xenon is already approved as an anesthetic in some countries; advantages cited include rapid onset/offset and minimal metabolism.
• Strong pushback on claims that it’s “perfectly safe”:
  • Any inert gas can rapidly cause fatal hypoxia if oxygen blending is wrong.
  • Long‑term effects of frequent recreational use are unclear.
• Analogies stress that a substance can leave the body unchanged yet still cause profound biological changes.

Comparisons to Other Substances

• Comparisons made to nitrous oxide, ketamine, dextromethorphan, classic psychedelics, and benzodiazepines.
• Debate over definitions of “psychedelic” vs “dissociative”; some classify xenon‑like drugs as dissociative psychedelics.
• Nitrous risks (hypoxia, B12‑related neuropathy) are discussed as cautionary parallels.

Cost, Supply, and Clinics

• Xenon is very expensive; medical/research-grade xenon is cited as extremely costly, limiting use.
• Confusion and corrections around quoted argon prices and purity grades.
• Xenon clinics reportedly exist in parts of Europe and Russia, but seem niche and hard to find.

Consciousness Theories and Speculation

• A side thread debates speculative quantum/microtubule theories of consciousness and anesthesia.
• Some see these as promising; others dismiss them as unproven or pseudo‑scientific, noting anesthesia mechanisms are still not fully understood.

Enthusiasm for the Forth Deck mini & discrete CPU

• Many are delighted by a hand‑built Forth machine with a discrete, microcoded CPU.
• The minimal ALU (single‑bit NOR, multi‑cycle 8‑bit ops) and tiny chip count are praised as elegant engineering.
• People see it as a fun, educational platform for playing with algorithms, games, and small tools directly on hardware.

“AlphaSmart for programmers” / Model 100 successors

• Several want a modern, distraction‑free portable like an AlphaSmart or TRS‑80 Model 100:
  • Real keyboard, low‑power reflective display, long battery life, no internet.
• The Model 100 is repeatedly cited as near‑ideal: great keyboard, ROM tools, AA batteries; main complaints are tiny 8‑line display and clunky data transfer.
• Some propose a $200 modern unit; BOM constraints (especially display cost) are discussed.

Ultra‑low‑power “zorzpad” and longevity goals

• A related project aims at a solar‑powered, batteryless notebook (zorzpad) with:
  • Sub‑milliwatt consumption, 53‑year design life, no charging ports, no commodity key switches.
• Emphasis is on survivability without industrial supply chains: no replace‑often batteries, minimal moving parts, heavy use of redundancy and potting.

Displays: e‑ink vs memory‑in‑pixel LCD

• E‑ink is seen as attractive but probably too power‑hungry and slow for continuous editing on microwatt budgets.
• Sharp memory‑in‑pixel monochrome LCDs are championed:
  • True bistability, ~100 µW level, fast refresh, good sunlight readability.
• Proposals for hybrid designs (small “live” LCD line + large e‑ink page) are compared; memory LCD is argued to be superior overall except for grayscale and size.

Batteries, energy storage, and reliability

• Strong criticism of batteries for ultra‑long‑life devices:
  • Limited shelf life (~10 years), frequent failures (swelling, leaks, thermal issues), and dependence on future markets.
• Others suggest using standard, easily replaced cells (AA/AAA/coin) to gain practicality.
• Alternatives discussed:
  • Supercaps with careful derating and encapsulation.
  • Mechanical or pneumatic charging (pull‑string, bike pump, compressed air) as external, replaceable modules.

Programming models: Forth, UXN/Varvara, CHIP‑8, Lisps

• Forth is valued for interactivity and bootstrapping, but many find it hard to read at scale.
• UXN/Varvara gets praise as a frugal, portable VM with a growing, self‑hosting ecosystem, but:
  • Critics argue it’s CPU‑inefficient (interpretive overhead ~20×), limited to 64K RAM, and unfriendly for complex, data‑heavy tasks (e.g., Norvig‑style spell corrector).
  • Varvara’s 2‑bit planar graphics don’t match 1‑bit memory LCDs well; full GUI at 60 Hz is seen as incompatible with ultra‑low‑power goals.
• CHIP‑8/Octo are noted as fun but IO‑poor and community‑fragmented.
• There is an extended side discussion on Lisp vs Python:
  • Trade‑offs between flexibility, readability, dynamic typing, and collaboration; Lisp seen as powerful but socially and technically challenging for large shared codebases.

Other hardware & prior art

• References to:
  • AlphaSmart, TRS‑80 Model 100, Psion 5, Oric‑1, Jupiter Ace, Open Firmware machines, OLPC XO, GEOS on C64.
  • Modern ESP32 devices: M5Stack Cardputer, Devterm, meshtastic boards; some already have Forth ports.
  • Commercial “distraction‑free writers” (e.g., Freewrite) viewed as too expensive or ergonomically off.

Design trade‑offs & UX

• Debates over GUI vs pure text:
  • Argument that with modern low‑power MCUs and reflective LCDs, efficient GUIs are feasible even under 1 mW; historical “text is cheaper” assumptions may no longer hold.
• Text editors:
  • Benchmarks show wide power gaps: ultra‑minimal editors can be ~1000× more instruction‑efficient than feature‑rich IDEs.
  • Discussion on designing new editors specifically for tiny, slow, 1‑bit screens, including block editors, single‑symbol views, and strategies to minimize screen updates.

Process & Capabilities

• Uses electrochemical additive manufacturing (ECAM): room‑temperature electrodeposition from aqueous/ionic metal feedstock instead of powder + laser/furnace.
• Key hardware idea: a microelectrode array “printhead” that parallelizes deposition (area-based, like DLP/LCD resin versus point-scanning).
• Current “pixel” size is ~33 μm; minimum features around ~50 μm are claimed.
• Can print directly on flat substrates such as PCBs, ceramics, and silicon; curved surfaces are “trickier” but not ruled out.

Speed, Energy & Environmental Aspects

• Traditional electroplating is very slow; commenters report ~1 μm/min.
• Company claims 100–1000× faster than typical electroplating while maintaining properties.
• Electrolytic processes are inherently high-current; however, low voltages keep power moderate.
• Claims of lower CO₂/energy versus powder-based AM because: no powders, no lasers/furnaces, and feedstock is upstream of refined metal powder.
• Some skepticism remains about true energy intensity; faradaic efficiency and upstream feedstock production are flagged as key variables.

Material Properties & Comparisons

• Room‑temperature deposition avoids melting, shrinkage/warpage, and typical porosity issues of sintering/laser-based methods.
• Claimed microstructure: nanometer-scale, equiaxed grains with isotropic behavior and high purity, attractive for thermal/electrical conductivity.
• Compared with powder-bed methods (SLM/DED) and binder-based systems (e.g., Desktop Metal), ECAM is positioned as:
  • 100% dense vs more porous for some binder/sinter routes.
  • Especially strong on pure copper, which is challenging for infrared-laser SLM due to reflectivity and thermal conductivity.
• Others note that modern SLM can also print near‑pure copper with high density using optimized lasers and parameters; debate remains unresolved.

Applications & Use Cases

• Lead application: complex copper cold plates/waterblocks with micro‑/nano‑channels; some think this market is already well-served, others see big gains in conformal cooling and heat exchangers.
• Suggested niches: RF and laser cooling, lab‑on‑a‑chip devices, controlled porous wicks, integrated metal on PCBs/ceramics, possibly molds/dies.

Safety & Materials Handling

• Safer than powder-based systems: no flammable metal powder, no high‑power lasers, no special gases.
• Still industrial: metal salt solutions and resulting acids require responsible handling and disposal.

Business Model & Accessibility

• Company plans to offer print‑as‑a‑service rather than selling printers initially, targeting batch/volume manufacturing.
• Some users want a “SendCutSend for ECAM” and consumer‑level access; others note PCB manufacturing is already extremely cheap by comparison.

Prior Art & Open Questions

• Commenters link decades of prior work on micro‑electrodeposition and laser‑assisted deposition; patents and prior art are actively discussed.
• Open issues: true throughput and cost per kg, long‑term anode wear and compensation, achievable alloy range, crystallization control, and whether this will reach hobbyist pricing.

Overall reaction

• Many are enthusiastic, especially those already making decks in Figma; they see Slides as a natural “first‑class” version of an existing workflow.
• Others find the beta underwhelming so far, saying it mostly replicates decade‑old slide software and looks like “PPT on the web.”

Why Figma Slides appeals

• Designers and some devs already favor Figma for architecture diagrams and “serious” decks due to:
  • Precise alignment, layout, and visual control.
  • Components, auto‑layout, and reuse of existing design systems.
  • Better typography and brand consistency than Google Slides, and often better than PowerPoint.
  • Strong real‑time collaboration and infinite canvas.
• Presenter mode, notes, and a simple AI “tone selector” are seen as key missing pieces now added.
• Some expect it to “murder Google Slides” in design‑centric teams that previously tolerated Slides only for remote collaboration.

Comparisons to existing tools

• Frequent benchmarks: Google Slides, PowerPoint, Keynote, Canva, Pitch, IA Presenter, Penpot, LibreOffice Impress, draw.io, Excalidraw, Typst, Inkscape+Sozi.
• Google Slides is criticized for poor typography, object alignment, font limitations (no custom corporate fonts), lack of SVG support, and weak or buggy animation.
• Keynote is widely praised for animation, vector handling, and polish but knocked for weak collaboration and ecosystem lock‑in.
• Text‑first tools (IA Presenter, Typst) appeal to those who prioritize content over design.

Current limitations and concerns

• Beta feedback: animation is slide‑level only, with few transitions and limited timing control; advanced animation from Figma Design is not yet exposed.
• Advanced design tools inside Slides require a paid Figma Design seat; casual users may get less than in free desktop tools.
• Reports of poor Firefox support and worries about offline reliability for conference talks.
• Accessibility gripe: FigJam still lacks dark mode while new products ship.

Pricing, lock‑in, and strategy

• Slides will be free on Starter; otherwise $3–5/seat/month. Using full design capabilities requires a paid design seat.
• Some see this as sensible expansion of a popular use case; others see ecosystem lock‑in and data capture for AI, plus continuation of perceived “dark patterns” in Figma pricing.
• Debate over whether this further silos designers away from PPT/Slides‑centric organizations vs. simply letting each discipline use the best tool.

Gameplay, Inspiration, and Feel

• Players consistently note strong Old School RuneScape vibes: click‑to‑move, camera angle, chat style, and 600ms tick rate.
• Described as self‑directed: explore, fight monsters and players, solve puzzles, complete quests, and level various skills (fishing, cooking, mining, smithing, woodcutting, farming, crafting).
• Current content includes NPC quests and riddles, a goblin boss and quest, and a lever‑door puzzle. Some players still feel “not much to do” yet.
• Several comments highlight nostalgia for early‑2000s web games and “when the internet was fun.”

Controls, UX, and Platform Support

• Movement is via click‑to‑move; right‑click handles special interactions.
• Some users struggle to move or see clicks register, especially on poor networks.
• Mobile: movement works, but limited “right‑click” functionality prevents accessing inventory and chat; pinch‑zoom on iOS feels “funky.”
• Firefox/WebGL issues reported on some hardware; workaround involves toggling a browser flag. Developer plans better WebGL detection and error handling.

Networking, Performance, and Architecture

• Server tick is 600ms, chosen to match movement pacing and similar games.
• About 200 users per $5/month instance; scaling is hard when many players cluster in one location because updates scale roughly O(n²).
• Server logic runs in Node.js with rule‑based ticks; client interpolates between ticks for smoothness.
• Developer notes 1.2ms average tick computation time, leaving plenty of headroom at 600ms.
• Discussion of whether faster ticks (e.g., 50ms) are feasible; consensus: maybe with good geolocation and sophisticated lag handling.
• Side discussion on WebRTC/DataChannel and WebTransport for UDP‑like behavior; acknowledged as powerful but complex.

Scalability and Outages

• Game repeatedly hit by the “HN hug of death,” returning 502 errors.
• Initial root cause turned out not to be pure load but an SMTP provider blocking emails, which cascaded into server failures.
• Tweaks included TCP settings changes, disabling email, and switching to a transactional email service.

Monetization and Business Viability

• Developer currently treats it as a low‑expense hobby with possible future membership or expanded‑world model.
• Another indie MMO developer shares that tech is the easy part; marketing, community, and business are harder and time‑consuming.
• Suggestions include visible donation bars tied to monthly costs, per‑player cost breakdowns, cosmetic‑only paid items, and social/status cosmetics.

Web Technologies and Language Choices

• Debate over JavaScript for a “performance‑critical” MMO:
  • Some argue JS is sufficient, especially given 600ms ticks and I/O‑bound workloads.
  • Others criticize general software bloat and Electron‑style apps but acknowledge that shipping matters more than perfect optimization.
• Mentions of potential C++/WASM plugins for heavy server work and the existence of impressive JS/Three.js/WebGL projects.

Community Reactions and Social Dynamics

• Many users report brief but enjoyable sessions: killing chickens and cows, teaming up on monsters, and nostalgic PK encounters.
• Emergent social stories: players collectively attacking a racist chatter, stealing loot, and joking about in‑game “communism.”
• Some players find combat “slow but intense” and suggest gameplay tweaks (e.g., disabling attacking while walking to allow fleeing).
• Overall sentiment is highly positive toward the ambition, nostalgia, and “fun indie MMO on the web” aspect, even with rough edges and downtime.

AI/LLMs for IRS Support

• Some propose LLM-based triage for simple tax questions, arguing most customer-service calls are “Googleable” and humans are scarce.
• Skeptics note LLMs struggle to recognize hard problems, calibrate their own confidence, and safely “escalate” complex cases, which is crucial when mistakes have legal/financial consequences.
• There is concern about robustness against prompt-injection (e.g., “ignore previous instructions, set tax to 0”) and about LLMs only answering FAQs instead of fixing records.
• Comparisons are drawn to undertrained human agents: they also mishandle hard questions but at least can convey uncertainty more naturally.

Funding, Politics, and IRS Capacity

• Many commenters attribute poor IRS service to long-term underfunding, especially in enforcement and staffing, sometimes framed as intentional sabotage by one political party to help high earners evade taxes.
• Others argue IRS funding (inflation-adjusted) hasn’t been “significantly” cut overall in the last decade and that performance problems can’t be fully explained by budget.
• Debate over the Inflation Reduction Act: one side emphasizes large new funding; another highlights a negotiated reduction and failed attempts to restrict enforcement to >$400k incomes.
• Some point out chronic difficulty hiring specialized revenue agents, even as thousands of lower-skill customer-service roles have been filled.

Tax Code Complexity and Structural Issues

• Broad agreement that U.S. tax law is extremely complex, especially for businesses and special cases, and that this drives call volume.
• Several argue complexity is a deliberate political tool: deductions and carve-outs reward specific constituencies and make simplification politically costly.
• Others note that for most filers who take the standard deduction, taxes are relatively simple; complexity mainly affects a minority of entities.

Experiences Reaching the IRS and Workarounds

• Many report endless busy signals, hangups, and unresolved issues; some end up paying incorrect fines or waiting months/years for fixes or refunds.
• Several say that when they do reach an agent, service is professional and helpful.
• Workarounds include:
  • Calling non-English phone lines.
  • Sending physical letters, which sometimes get resolved after long delays.
  • Contacting congressional offices, which often have “back-channel” access and can rapidly escalate IRS and other agency problems.
  • Using CPAs or paid intermediaries, including controversial “expediter” services that flood phone lines.

Reform Ideas and Alternatives

• Suggestions include simplifying or eliminating low-yield taxes, pre-filled or no-file returns using data the IRS already has, and even replacing income tax with a national sales tax; commenters dispute feasibility, equity, and enforcement impacts.
• Some point to similar customer-service breakdowns at other agencies and in other countries (e.g., UK tax authority), suggesting a wider pattern of state underinvestment in frontline support.

Addiction, Agency, and Responsibility

• Strong debate over whether addiction should be treated primarily as a disease vs. a matter of personal responsibility.
• One side stresses that addiction, like depression, often involves neurodevelopmental or psychological disorders; relying only on willpower is seen as unethical and ineffective. They emphasize therapy, medication, support systems, and societal responsibility.
• Others argue that people with diseases still have agency and must take active steps (e.g., as with diet changes, chemo, avoiding gluten). They worry that framing addiction as “not my problem to solve” fuels passivity and issues like obesity.
• Several note that while external help is crucial, only the person affected can ultimately initiate change.

Latency and “Dilution” as Digital Self-Control Tools

• Many find added latency or friction psychologically powerful: it makes impulsive visits less rewarding, similar to “diluting” the internet.
• Comparisons are made to ancient practices of diluting wine or to living where basic tasks require walking, introducing beneficial effort.
• Some prefer using underpowered hardware or clunky official apps as a natural latency source that reduces usage.

Phone and App-Level Friction Techniques

• Popular tactics:
  • Grayscale display + minimalist launchers to make phones visually dull and less compelling.
  • App-level delays like “one sec” that force a pause and track avoided usage.
  • Hiding recommendations and history on YouTube to intentionally worsen the algorithm and reduce rabbit holes.
  • Stripping home screens to essentials and limiting notifications to calls/SMS.
• Reported outcomes include large drops in screen time and a more “sterile,” less tempting device.

Browser/Network-Level Approaches

• Suggestions include: disabling prefetch and URL bar suggestions; heavy adblocking; default JS off; sandboxing browsers; console-only Sundays; offline article printing.
• Some want router- or proxy-level latency controls per device/domain, but note it would require custom setups; feasibility is unclear.
• One commenter warns that imposed family-level throttling may provoke frustration unless paired with attractive offline activities.

Social Platforms, Engagement, and Ethics

• Multiple comments link personal overuse to intentional engagement optimization by tech companies, likening “addictive features” to digital drugs.
• Reddit and YouTube are cited:
  • Clunky official apps and UI changes have, for some, incidentally broken their usage habits.
  • Others deliberately use “old” interfaces or limit features.
• Some express discomfort with platforms monetizing user-generated content and behavioral data, especially for AI training.

Alternative Communities and Offline Reading

• Several express nostalgia for old-style, high-effort forums, sometimes paid, as a healthier alternative to modern feeds.
• Offline reading (printed articles, TTS-to-podcast, audiobooks) reportedly shifts attention away from the browser toward books and long-form content, perceived as higher quality.

Scope of the Ruling

• Decision: Federal statute 18 U.S.C. §666 covers bribes to state/local officials, not post‑hoc gratuities (“gifts” after an official act).
• Bribery vs. gratuity: Bribe = quid pro quo for a specific official act; gratuity = reward after the fact, possibly unethical but not a §666 crime.
• Several commenters stress:
  • Federal officials remain covered by separate anti‑gratuity law (18 U.S.C. §201(c)).
  • States and cities can (and often do) have their own anti‑gratuity laws.
  • The ruling is about statutory interpretation, not declaring gratuities “good.”

Concerns About Corruption

• Many see this as “legalizing bribery in slow motion”: you just pay after the favor.
• Fear of a culture where nothing moves in government without “tips,” likened to highly corrupt states.
• Emphasis on the loss of the norm that even the appearance of impropriety is disqualifying; now even overt impropriety often carries no consequences.
• Some suggest radical transparency instead: all gifts/bribes publicly logged, with penalties only for non‑reporting.

Supreme Court Ethics and Perceived Bias

• Thread heavily links the ruling to undisclosed luxury gifts to current justices, arguing they are personally biased toward normalizing “gifts.”
• Others counter that the case legally affects state/local officials, not federal judges, and mostly harmonizes treatment of federal vs. non‑federal officials.
• Strong moral view in the thread: there is no real ethical difference between bribes and gratuities, only a legal one.

Federalism, Drafting, and Statutory “Bugs”

• Some are sympathetic to a federalism angle: states should police their own corruption rather than relying on federal prosecutors.
• Others see the bribe/gratuity split and penalty disparities as a drafting mistake or “tech debt” in the statute that the Court is now locked into.

Broader Systemic Issues

• Comparisons to campaign contributions, super PACs, post‑office jobs and speaking fees as de facto bribery already.
• Debate on whether the Court is properly interpreting law vs. overstepping and remaking policy, amid a wider loss of trust in democratic institutions.
• Meta: some wish political stories like this could be filtered out of HN; others say that’s unrealistic.

Readline usage and configuration

• Many commenters only recently realized how configurable Readline is and express enthusiasm about customizing it system‑wide.
• Common keybindings praised: history search (Ctrl‑r/Ctrl‑s), line killing (Ctrl‑u, Ctrl‑k), yanking (Ctrl‑y, Esc‑y), and last‑argument recall (Alt+.).
• Several advise against rebinding core keys like Ctrl‑k, arguing that standard bindings transfer across many tools and machines.
• Users share .inputrc tricks: showing current mode in the prompt, changing cursor shape per mode, and vi/emacs mode strings.

Vi vs Emacs modes and ergonomics

• Vim users are often disappointed by set -o vi in shells; they prefer Readline/Emacs-style bindings in most places and Vim only in the editor.
• Others say vi mode becomes usable if the prompt indicates mode and cursor shape changes.
• There is light debate over whether Emacs-style keybindings contribute to RSI; anecdotes support both “no evidence” and “Vim helped my RSI”.

GPLv3 licensing concerns

• Several participants worry that Readline’s GPLv3 license prevents its use in proprietary or embedded products and can “sneak in” via dependencies.
• Others counter that this mainly matters for distributed, especially proprietary, software, not internal tools.
• There is disagreement about whether giving GPL‑using binaries to contractors counts as distribution; some cite FSF guidance that it does.
• Some companies reportedly ban GPLv3 code entirely; others happily ship GPLv3 and see it as enabling use of more libraries.

Alternatives and wrappers

• rlwrap and socat readline are highlighted as ways to add Readline‑like editing and history to programs lacking it (e.g., sqlplus, Prolog REPLs, ed).
• Non‑GPL alternatives such as libedit/tecla are mentioned; some shells (dash, busybox ash) can use libedit or provide partial Readline‑like features.
• Windows tools like Clink and BusyBox ports are recommended for gaining a modern, Readline‑style shell experience.

Quality-of-life, bugs, and maintenance

• Users describe how painful non‑Readline CLIs (old Oracle tools, psql --no-readline, early MS‑DOS) highlight how much Readline improves UX.
• One commenter reports helping diagnose and fix an O(n²) performance bug in Readline when pasting long inputs.
• There is concern that critical tools like Readline are maintained by very few unpaid individuals, raising sustainability and security worries, with calls for better funding.

Overall reception

• Widely described as fun, satisfying, and “global fidget toy”–like, despite (or because of) its pointlessness.
• Many users report losing several minutes to it; others bounce off due to performance or chaos.

Design and UX choices

• Key choice: grid width is fluid, not fixed.
  • Some dislike this because drawings and words only align at specific viewport widths.
  • Others enjoy “scanning” for images and treating width as a secret “cipher key.”
• Some want sound effects (e.g., bubble-wrap pops) and clearer keyboard navigation.
• Suggestions include locking width, using primes for rows/cols, or adjacency rules (only check boxes next to already-checked ones).

Technical implementation and scaling

• Backend described as multiple tiny Flask servers, a bitset in Redis, and WebSockets broadcasting updates.
• Frontend uses windowed rendering to avoid drawing all 1M checkboxes at once.
• Initial implementation sent too-frequent updates; later switched to batching for performance.
• Hug-of-death issues, white screens, and lag are common reports; developer added more servers and reintroduced faster rate limiting.
• Reported cost so far is on the order of tens of dollars, expected to rise with bandwidth.

Scripting, bots, and emergent gameplay

• Numerous scripts shared to check, uncheck, randomize, or defensively re-check boxes.
• A client-side alert (“CHILL LOL”) appears when clicking too fast.
• Clear “factions” emerge: checkers vs uncheckers, with localized “wars” over specific boxes or regions.
• Some enjoy the chaos; others feel bots ruin the human, manual aspect.

Content moderation and abuse

• Users quickly notice swastikas and genital drawings, echoing the known “swasticock problem” in UGC.
• Some argue for detection or shuffling algorithms; others see moderation as paternalistic or futile.

Bugs, compatibility, and issues

• Reports of problems on Firefox, Safari, and mobile: slow loads, counts not updating, or non-functioning UI.
• Occasional state inconsistencies, including total-checked counts exceeding one million.

Related ideas and extensions

• Comparisons to r/place, bubble-wrap apps, milliondollarhomepage, pixelflut, and collaborative canvases.
• Ideas floated: levels, SHA-256 hash challenges, stats dashboards, time graphs of checked count, microtransactions, ads, or even physical flip-disc displays.

Purpose and Design of the Tax

• Many frame the levy as pricing in a previously ignored negative externality: methane and CO₂e from livestock, especially in Denmark where agriculture is said to be the largest emissions source.
• Supporters argue that if emissions targets aren’t met, the tax level is simply too low; higher prices should reduce demand for beef/dairy and incentivize lower‑methane feeds.
• Critics call it political theater or “grandstanding,” arguing many other externalities remain unpriced and that Denmark’s action alone has negligible global climate impact.

Climate Science and Methane Debate

• One side stresses that methane is much more potent than CO₂ (roughly 25–80x over common time horizons) and that livestock (with huge global biomass) significantly contribute to warming.
• Others argue cattle are part of a short carbon cycle: plants absorb CO₂, cows emit methane that oxidizes back to CO₂ in years, so with roughly constant herd sizes, net long‑term GHG doesn’t increase.
• Counterpoints note that current livestock numbers far exceed many natural baselines and that what matters is the present “delta” in total GHGs, not geological timescales.
• There is dispute over whether domesticated herds merely “supplanted” past wild ruminants, making their net climate effect minimal; this remains contested and described as unclear in the thread.

Economic, Social, and Political Effects

• Broad agreement that producers will pass costs to consumers, raising prices for meat and dairy, with disproportionate impact on low‑income households.
• Some see this as acceptable or desirable to drive dietary change; others fear reduced nutrition for poorer families.
• Concerns about farm bankruptcies and consolidation favoring large players.
• Worries that higher domestic costs will shift production to countries with laxer standards, hurting Danish/EU competitiveness unless policies are coordinated and border‑adjusted.
• Several predict political backlash, bolstering right‑wing parties promising to roll back such taxes.

Food Systems, Alternatives, and Values

• Debate over whether the real problem is ruminants themselves or industrial monocrop and feedlot systems.
• Some emphasize benefits of pasture‑based or regenerative livestock systems and argue that all food production has environmental trade‑offs.
• Others view reduced meat (especially beef) consumption as necessary, suggesting taxes fund subsidies for lower‑emission plant foods.
• Ethical arguments appear at the fringes: animal suffering, fairness of taxing “moral goods,” and class divides in access to meat.