Hacker News, Distilled

Succession, responsibility, and family access

• Several commenters emphasize a hidden risk: if the self-hoster dies or is incapacitated, family and friends may lose access to critical data and services.
• People now plan “home succession”: rsync/USB copies to spouses’ laptops, printed instructions in safes, flash drives with key docs, and notes about what will break (email, domains).
• Many note that most homelab data will never be accessed after death; focus should be on a short list of truly important documents and simple, non-technical recovery paths.

Critical services: what not to self-host

• Multiple participants avoid self-hosting password managers and email, considering them too critical.
• Others report outages on self-hosted vaultwarden that locked them out at bad times, prompting moves to hosted Bitwarden or 1Password.
• Offline backups/exports of password vaults are suggested as a compromise.

Containers vs NixOS/Guix and packaging philosophy

• Big subthread debates Docker vs NixOS/Guix System.
• Pro-Nix side: declarative configs, reproducibility, per-app dependencies, low overhead, one-line service enables (e.g., services.uptime-kuma.enable = true).
• Skeptical side: Nix is opinionated, has a learning curve, and containers remain easier since most self-hosted apps ship Docker images; containers also act as an “escape hatch” when no Nix package exists.
• Some run NixOS but still use containers (podman/systemd) for awkward software.

Economics and practicality of self-hosting

• Mixed views: some find cloud storage (e.g., GCS, Google Drive) surprisingly expensive or cheap depending on workload.
• One example: moving Prometheus object storage from GCS to self-hosted MinIO on a VM cut a cloud bill by ~70%.
• Others stress that for homelabs the real cost is time, power, hardware depreciation, UPS, and cooling—worth it only if learning or control are primary goals.
• “True” self-hosting is debated: some say only on-prem counts, VPS is not; others see that distinction as unimportant.

Ease-of-use, “indie hosting”, and non-technical users

• Thread predicts a split between hobbyist “kit-car” self-hosters and a future “indie hosting” world: turnkey, GUI-first, privacy-respecting, minimal tech knowledge.
• Non-technical users ask for solutions without command line; suggestions include NAS GUIs, /r/selfhosted resources, Yunohost, FreedomBox, Caddy, and GUI-oriented distros.
• Some are building simpler web servers or tunneling services to make exposing home services as easy as installing an app and clicking through OAuth.

Security, email, and exposure

• Self-hosted email is described as increasingly difficult: residential IP blocks, port 25 filtering, reverse DNS requirements, SPF/DMARC/DKIM, and spam blacklists that often distrust home or cloud IP ranges.
• Advice: start on a reputable VPS, use distro packages with unattended security updates, or avoid directly exposing home networks and instead use VPN/overlays like Tailscale.

Home hardware, Proxmox, and infrastructure

• Hardware stacks discussed include Proxmox clusters, ZFS with HBAs, Pi 5s, repurposed laptops, and low-power thin clients (e.g., Wyse 5070).
• Proxmox + ZFS is popular but can be write-heavy on SSDs; tuning logging and ZFS caching can reduce wear.
• VLANs, privoxy, OpenWRT on Mikrotik/Zyxel, and ad-blocking proxies are cited as major quality-of-life milestones.
• Some question using a full three-node Proxmox cluster and off-site object storage (Wasabi) for relatively simple home workloads.

Government and public data on private platforms

• Concern that local governments publish “public” documents via Google Drive, YouTube, or Facebook, forcing residents into big-tech ecosystems or complex DNS blocking exceptions.
• Others argue bureaucratic friction for official web publishing pushes staff toward quick consumer tools.
• Related worries about DMVs and courts outsourcing identity/document handling to private vendors (e.g., ID verification services).

Power, UPS, and reliability

• UPS behavior is discussed; in some environments UPS failures caused more outages than utility power.
• Lithium (especially LiFePO4) vs lead-acid vs emerging sodium-ion batteries are compared: lithium and sodium promising far longer life and cycle counts, but sodium adoption perceived as slow.
• For homelabs, simple Li-ion UPS units are seen as attractive but real-world experience is limited in the thread.

Miscellaneous tools and tips

• Recommended self-hosted apps and patterns: Paperless-ngx for documents, Komga (also for ebooks), calibre-web, vaultwarden, KeePassXC synced via Syncthing, Caddy for auto-TLS, Tailscale for secure remote access.
• Some praise OpenBSD’s integrated services and detailed upgrade FAQs as particularly self-host-friendly.
• VPS-based “dedicated servers” are suggested as a sweet spot: much cheaper than hyperscale cloud, with less ops burden than full on-prem.
• Several report poor reliability and support from specific budget VPS providers, prompting migrations to more reputable hosts.

Living in Phoenix and the “Dry Heat”

• Many residents say Phoenix is “vacation weather” for ~7 months (Oct–May), comparable to coastal climates.
• Summers are described as “surface of the sun”: 100–120°F is common, with dead daytime sidewalks and fully indoor, AC‑to‑AC lifestyles.
• Several compare Phoenix’s dry heat favorably to hot, humid climates (Midwest, Gulf Coast, tropics), but others insist 40°C+ is uncomfortable regardless of humidity.

Health Risks and Infrastructure Vulnerability

• Concern that long strings of 100°F+ days, especially when nights stay hot, are dangerous, particularly if power fails.
• A cited study on combined heat waves and power outages in Phoenix projects massive heat‑illness and deaths.
• Outdoor workers, people without reliable AC, and prisoners are highlighted as especially exposed.
• One-third of US heat deaths reportedly occur in Arizona.

Migration, Economics, and Quality of Life Trade‑offs

• Phoenix’s size (5th largest US city) is seen as a “natural experiment” in how long people will tolerate rising heat.
• Some expect eventual climate‑driven out‑migration and falling home prices; others note continued in‑migration from colder regions avoiding snow.
• Debate over whether 100+ days of extreme heat is more dangerous than snow/ice hazards and snow shoveling.

Urban Design and Mitigation Ideas

• Observations of a strong heat‑island effect and reduced monsoon rains over the growing concrete/pavement footprint.
• Suggested mitigations: more trees, reflective surfaces, covering asphalt with solar, better transit, and even subsurface or semi‑buried buildings.
• Practical barriers include hard caliche soil, developer incentives, and cost of large‑scale earthworks.

Climate Change and Timescale Disputes

• One side emphasizes long‑term natural variability and criticizes “hysteria,” arguing we lack long records and that first‑world impacts may be limited.
• Others stress the rapid, human‑driven rate of change, cite paleoclimate methods (e.g., ice cores) and global temperature records, and highlight disproportionate harm to poorer regions.
• Disagreement centers on how abnormal current trends are and whether large societal changes are justified.

Other Side Topics

• Brief discussion of this year’s hurricane season: some see it as “quiet,” others note strong storms by ACE metrics and Saharan dust suppression.
• Multiple mnemonics and rules of thumb for Fahrenheit–Celsius conversion and subjective comfort ranges are shared.

AI-Focused Marketing and User Perception

• Many note the press release is saturated with “AI” mentions but light on concrete specs or benchmarks.
• Some see this as an “AI fad” akin to 3D TV or blockchain hype; others argue LLMs/diffusion are a lasting, Internet-scale shift.
• A cited study suggests “AI” in product descriptions can reduce purchase intent, yet posters think vendors still emphasize it to impress investors.

Performance, Power, and Efficiency

• Expectation: modest real CPU performance gains; interest is mostly in efficiency and idle power for thin‑and‑light laptops.
• Claimed package power is ~17 W sustained, up to 37 W short‑term; users compare this to Apple’s M-series and Qualcomm’s Snapdragon X.
• Some nostalgia for big single‑thread leaps; others argue we’ve hit practical limits (clock speed, heat) so incremental gains and specialization are inevitable.

Process Node and Manufacturing Strategy

• Noted that Lunar Lake uses TSMC N3B for compute, N6 for platform, and Intel 22FFL for the interposer.
• Some see this as Intel “losing the fab race”; others frame it as a necessary step while Intel tries to catch up (20A/18A) in future products.

NPUs, GPUs, and TOPS Marketing

• Intel advertises “up to 48 TOPS” NPU and ~120 “platform TOPS” (CPU+GPU+NPU). Posters call combined TOPS marketing “word salad” and “a scam” since workloads usually can’t span all units at once.
• Comparisons to Apple’s M3/M4 and discrete GPUs note confusing baselines (INT8 vs FP16, package vs unit power). Real efficiency and usefulness remain unclear until benchmarks.
• Some see NPUs as essential for low‑power “background AI”; others dismiss them as unused silicon on current Windows/desktop workflows.

x86 Legacy and Architecture Changes

• Discussion on dropping 16‑bit real‑mode/older boot paths and the move to x86S plus virtualization for legacy OSes.
• Some highlight how modern x86 is internally very different from the 1980s ISA, yet software compatibility (and performance quirks for old OSes) remains a challenge.

Integrated Memory and Upgradability

• On‑package RAM is welcomed for bandwidth and power in ultraportables, but criticized for killing easy RAM upgrades and the secondary market.
• 32 GB max is seen by some as low for 2024, though others note comparable limits in thin‑and‑light competitors and expect higher‑TDP lines to offer more.

I/O, Use Cases, and Longevity

• Lack of Thunderbolt 5 is seen as limiting eGPU upgrade paths, especially for gaming handhelds/laptops.
• Some want desktop or mini‑ITX variants for efficient home servers; others note this line targets ultraportables only, with Arrow Lake expected for desktops.

Reliability and Support Experiences

• Concerns surface about Intel’s recent quality issues (voltage/“burn out” jokes) and one report of poor RMA handling.
• A few extrapolate from support frustrations to broader pessimism about Intel’s trajectory; others push back, emphasizing the need for real data and upcoming reviews.

Purpose of llms.txt

• Proposed as a small text/Markdown file at site root listing AI-friendly docs and key links.
• Intended mainly for end-users and tools (e.g., IDEs, “projects” features) to assemble good LLM context about a library/site, especially for content created after model training cutoffs.
• Not pitched as a training-data spec, but as a way to curate minimal, well-structured context for inference-time use.

Incentives and Value for Site Owners

• Supporters:
  • Useful for documentation-heavy projects and open source libraries that want LLMs to help users quickly.
  • Might act as a forcing function to write clear, concise summaries that are also helpful to humans.
• Skeptics:
  • Little direct benefit; mostly helps AI products, not authors.
  • Could make original content less visited and more “obsolete” as users stay in LLM interfaces.

Scraping, Control, and Compensation

• Strong frustration that LLM companies profit from scraped content without attribution or payment; some compare it to theft.
• Calls for mechanisms to declare prices or enforce “right_to_be_un_vectorized,” but recognized as aspirational.
• General sentiment that robots.txt / ai-txt-style signals are weak; bad actors ignore them, and even some big AI crawlers disregard crawl delays.

Technical Design Debates

• Many argue this should be a .well-known resource or extension of robots.txt / existing metadata, not another root file.
• Some question why Markdown is used at all; plain text, HTML, or existing formats (OpenAPI, man pages, etc.) already work.
• Concern that LLMs should be able to parse normal HTML/docs; needing llms.txt is seen as a symptom of poor site structure or weak models.

Manipulation, Poisoning, and Security

• Multiple commenters note llms.txt could be abused to poison models or present LLM-only misleading content.
• Others argue this risk already exists via normal pages; llms.txt doesn’t fundamentally change the attack surface.

Broader Web & UX Concerns

• Fear that this further optimizes the web for machines over humans, instead of fixing confusing, marketing-heavy sites.
• Parallels drawn to the Semantic Web and prior machine-readable metadata efforts, with mixed historical success.
• Some would use llms.txt themselves as an ad-free, concise human-readable “real” docs page.

Long-Distance Transmission & Grids

• One path for excess solar is exporting power via long-distance high-voltage transmission, as with China’s ultra-high-voltage lines and proposed Australia–Singapore cables.
• HVDC is argued to be sufficient (≈3.5% loss per 1,000 km, less than AC); superconductors seen as unnecessary and currently impractical (brittle, expensive).
• Continental grids could smooth solar across time zones (e.g., US east–west), but large grid expansions are seen as slow, expensive, politically fraught, and security-sensitive.

Desalination and Water from Excess Solar

• Many see solar-powered desalination as a prime “dump load”: deserts near coasts could gain water and new arable/usable land.
• Counterpoints: brine discharge can damage near-shore ecosystems; evidence of concentrated high-salinity plumes and long outflow pipes is cited.
• Others argue global impact is tiny versus natural evaporation, with effects mostly local and mitigable via dilution, mixing with treated sewage, or further processing.
• Capital cost, not energy, dominates desal economics; plants must run near-continuously. Using only midday surplus demands much cheaper plant construction.

Economics of Solar, Storage, and Incentives

• Debate over whether “too cheap” solar leads to underinvestment: some say negative or low midday prices will self-correct and curb new builds; others say once cheap enough, people buy for direct usefulness, not ROI.
• Excess solar can be monetized via arbitrage and flexible loads (batteries, fertilizer production, CO₂ capture, overcooling buildings, water).
• Battery round-trip efficiency is quoted around 80+%; there is confusion and dispute over how capacity factor and efficiency interact at grid scale.

Rooftop vs Utility-Scale Solar

• Utility-scale solar is broadly seen as much cheaper per MWh than rooftop.
• Rooftop is criticized as heavily subsidized via net metering, shifting costs to non-solar customers.
• Others counter that rooftop only needs to beat retail (not wholesale) prices and can already be rational, especially in high-tariff regions; soft costs and policy design (connection fees, export tariffs) are key.

Batteries, EVs, and Off-Grid Trends

• Home batteries are getting cheaper; some expect them to become widely affordable within 5–10 years.
• EVs with large batteries and vehicle-to-home/grid are viewed as emerging storage assets, especially as used EV prices fall.
• In places with unreliable grids (e.g., South Africa), solar + batteries are already widely used to reduce or eliminate grid dependence.

Environmental & Scale Concerns; Skepticism

• Some worry cheap solar will boost total energy use with unclear long-term effects, though others note solar’s lower climate impact vs fossil fuels despite lower albedo.
• There is skepticism about long-range projections that promise “effectively free” energy, likened to past “too cheap to meter” claims, and about the reliability of some official solar deployment statistics.

Context & Process

• Article is from early 2024 and tied to a UK parliamentary inquiry that has since closed; commenters note UK political turmoil and delays mean little has progressed.
• Some emphasize the title is overstated: OpenAI’s formal position is that training on copyrighted works is already legal and should remain so, not that it needs a special retroactive exemption.

Copyright, Fair Use, and Law

• Major debate over whether training on copyrighted data is fair use:
  • Pro-training side likens it to search engines, caching, libraries, and humans reading books, arguing that only outputs that reproduce protected text or images matter.
  • Critics argue LLMs are built explicitly to commercialize other people’s works and often act as substitutes, which weighs against fair use, especially when outputs are near-verbatim or “in the style of” specific creators.
• Some compare to Google Books and web search; others say those products are more limited (snippets, links, non-substitute use) and so are not good precedents.
• Jurisdiction issues arise (training in one country, use in another; fair use not universal). Several lawsuits (e.g., news and music) are cited as evidence this is unresolved.

Ethics, Economics, and Impact on Creators

• Many characterize current AI as built on “piracy” or uncompensated use of scraped/tor­rented works; they see it as rich firms monetizing small creators’ labor.
• Concerns:
  • Direct substitution (e.g., “Frank Miller-style” comics, stock image generators, AI-written books flooding markets).
  • Erosion of incentives to create high-quality content.
  • Cultural degradation from AI spam and hallucinations misattributed to real outlets.
• Counterviews:
  • People will still follow trusted human voices.
  • LLMs compress and transform data; they don’t store perfect copies.
  • Some creators would keep producing regardless of money.

Policy, Reform, and Possible Compromises

• One camp wants strong enforcement: pay for training data or “don’t exist as a business.”
• Another fears that banning training on copyrighted works would over-expand copyright, hurt open models, and slow Western AI relative to less IP-respecting states.
• Proposed alternatives:
  • Systemic licensing or revenue share for creators (various splits suggested).
  • Focus on sample-efficient models and truly copyright-free/public datasets.
  • Limit outputs (prevent verbatim or substitutive content) rather than training itself.
  • Broader copyright reform: shorter terms, fees to renew, healthier public domain.

Broader Reflections

• Some see this as proof AI should be treated as a public good, not proprietary infrastructure.
• Others doubt LLMs’ long-term importance and warn of rewriting copyright for a technology that might be a dead end.

Basque Country, Spain, and Local Impressions

• Disagreement over Spain’s wealth: some call it “not known for vast wealth,” others stress Spain is highly developed and the Basque Country is among its richest regions, helped by a special tax regime.
• One visitor found Mondragón town drab and DDR‑like, others argue local Basque culture favors practicality over aesthetics and that many Mondragón workers live in nicer nearby areas.
• Some note favorable regional subsidies and tax treatment; others counter that Basque GDP (PPP) compares well to rich EU regions.

Capitalism, Socialism, and Labor Theory of Value

• Strong pro‑labor arguments: “no value without labor,” capitalism framed as extraction of surplus value by capital owners; co‑ops and small/local businesses presented as more “socialist” in spirit.
• Critics respond that mainstream economics rejects a strict labor theory of value and emphasize risk, tools, and capital; argue free markets have raised living standards and that Marxist regimes fared poorly.
• Debate over whether communism has ever truly been implemented; some say failures show human selfishness is incompatible with it, others say all real systems are hybrids of socialism and capitalism.
• Environmental and historical harms are attributed both to “too much free market” and to centrally planned systems; participants clash on which is worse.

Worker Co‑ops: Structure, Ownership, and Governance

• Mondragón’s specific structure: workers invest to join, get profit‑sharing and interest while employed; ownership is tied to current workers rather than tradable shares.
• Some argue this is still real ownership (like partnerships); others see it as conditional profit‑sharing with limited long‑term upside.
• Democratic governance is highlighted as at least as important as formal equity; contrast with conventional firms where employee stock rarely yields real power.

Replicability, Incentives, and Scale

• Supporters see Mondragón (and Italian/Emilia Romagna co‑ops, kibbutzim, food co‑ops, social media co‑ops) as proof large co‑ops can work.
• Skeptics question scalability: co‑ops may struggle to attract top engineers and executives, face financing barriers (reliance on loans vs equity), and may be outcompeted by profit‑maximizing firms.
• Some report internal patronage and “where your dumb cousin works” reputations, suggesting bureaucratic drift over generations.
• Debate over whether ethnic or cultural solidarity (Basques, kibbutzim, Kurds in Rojava) is a precondition; others reject “ethnic purity” arguments as dangerous or overstated.

Policy and Ecosystem Ideas

• Suggestions include tax and legal reforms to ease co‑op formation, co‑op‑focused loan programs, and a “YC for co‑ops.”
• Proposed hybrid models: worker‑only voting shares plus non‑voting profit shares for outside investors; federated co‑op ecosystems rather than monolithic groups.

Accessing the article

• Several commenters share archive links for those paywalled or blocked.
• Some note one archive copy includes photos while another does not.

Was asking her to step out reasonable?

• One camp sees the request to take the baby outside as polite and standard at professional events.
  • Argument: even “soft” baby sounds are evolutionarily hard to ignore and can distract from talks; it’s fair to prioritize a quiet environment for paying/committed attendees.
  • Many parents in this camp say they routinely remove their own kids when noisy and would appreciate a gentle nudge if they misjudge.
• Another camp argues that quiet cooing is a minimal disruption and the response was overkill, especially given the topic and audience.
  • They note parents may be better at filtering baby sounds; non-parents may be oversensitive.

Event context and gender/parenting

• Some stress the irony: a woman-focused event, talk about mother–founder challenges, and yet discomfort with an actual baby in the room.
• Others counter that the topic doesn’t change the basic norm of maintaining a professional environment.
• Debate over whether this is a good example of “systemic barriers” for mothers, or an overinterpretation of a mundane interaction.

Organizer’s response and media framing

• A LinkedIn response from the organizer (linked in thread) claims:
  • The mother was offered alternate spaces where she could still hear the talk.
  • She stayed for the full conference and was not ejected.
• Some readers conclude the article’s framing is selective or sensationalized; others remain sympathetic to the mom’s discomfort and feelings.

Broader attitudes toward children

• Long subthread on rising intolerance toward children in public vs. expectations that society collectively “puts up with” kids because they’re essential to the future.
• Strong disagreement over whether childless people are especially hostile, or whether some parents are simply inconsiderate.
• Cultural comparisons (e.g., China vs. West) on how much disruption from children is socially tolerated.

Proposed solutions

• Suggestions include on-site childcare at events, clearer expectations in advance, and more flexible spaces for parents.
• Some envision more child-inclusive workplaces; others worry about noise in already loud environments.

Landfill Gas, Energy, and Operations

• Several comments focus on landfill gas-to-energy, noting examples powering tens of thousands of homes.
• Back‑of‑the‑envelope power/energy calculations are debated; initial claims that a single truck uses more energy than 70k homes are widely rejected as orders of magnitude off.
• Consensus in the thread: hauling and on‑site equipment consume relatively little energy compared to the methane energy landfills can yield.
• Some landfills reinject leachate to keep waste wet and boost methane production, but must carefully balance gas extraction to avoid underground fires.

Recycling, Plastics, and “Virtue Signaling”

• Strong skepticism about curbside recycling, especially plastics: contamination, single‑stream programs, and exports that end up burned or dumped abroad.
• Some argue that, for plastics, landfilling is often better than “recycling” via export or incineration, since it effectively sequesters carbon.
• Others counter that in some jurisdictions (e.g., parts of Europe, some North American provinces) PET and other materials are actually recycled at significant rates.
• Multiple commenters emphasize the 3Rs hierarchy: reduction and reuse matter more than recycling, and many “green” programs lack honest accounting of emissions and costs.

Incineration vs. Landfilling (Including Plasma/Gasification)

• Waste‑to‑energy incineration is common in parts of Europe and Japan, often tied to district heating and sophisticated flue‑gas treatment; seen by some as preferable to methane‑emitting landfills.
• Critics highlight CO₂ and toxin emissions, arguing incineration is only justifiable where landfill space is truly constrained.
• Plasma gasification and molten‑salt oxidation are discussed as ways to destroy waste and generate syngas; seen as technically promising but currently expensive and energy‑intensive.
• Some suggest these high‑energy processes could use surplus solar/wind and help with “duck curve” balancing; others argue all clean power should first displace fossil generation.

Environmentalists, Policy, and Trade‑offs

• One camp criticizes “environmentalists” as anti‑technology and hostile to nuclear, high‑density housing, and engineered solutions like advanced landfills.
• Others call this a strawman, noting mainstream waste hierarchies and that criticism of landfills often aims to improve or replace them, not deny engineering.

Scale, Impacts, and Engineering of Landfills

• Multiple commenters note that, volumetrically, even centuries of waste occupy modest land area relative to a large country, though a hypothetical single mega‑landfill would be huge.
• Landfills are described as highly engineered systems: liners, leachate collection, gas capture, and eventual reuse as parks or other amenities.
• Concerns remain about methane (landfills are a major human‑related source), leachate chemistry, and microplastics spread by birds. Composting food/yard waste is presented as a key mitigation.

Future Uses and Business Angles

• Speculation about future landfill mining for plastics, hydrocarbons, or archaeological data.
• Some see economic opportunities in local hauling co‑ops, gas‑to‑energy, or even pairing landfill gas with data centers or cryptocurrency mining.

Wave-based picture of mass and the Higgs

• Several comments recast mass in terms of wave equations: a “restoring force” term in the field equation raises the time-oscillation frequency even for spatially uniform waves.
• This extra temporal frequency at zero spatial momentum is identified with mass (via relativistic Klein–Gordon–type equations).
• Massless fields (like EM) lack this restoring term, so spatial and temporal frequencies are coupled directly; massive fields have an offset.
• Lay questions probe whether this extra “frequency” is like kinetic or potential energy; responses frame rest mass as potential energy stored in a standing wave.

What fields are and how they relate to particles

• Recurrent theme: in QFT, particles are excitations of underlying fields; fields are treated as fundamental mathematical objects, not made “of” anything.
• Some argue the wave itself is the only “real” thing, with no separate medium; others stress this is partly interpretive and drifts toward philosophy.
• Discussion contrasts field and medium viewpoints (e.g., wind vs air) and notes we don’t know if there is any deeper “substrate.”

Higgs field, symmetry breaking, and cosmology

• Higgs is described as unique in having a nonzero vacuum expectation value in today’s universe, giving masses to certain fields.
• Early universe: electroweak symmetry unbroken at extremely high temperatures; as it cooled, a phase transition gave the Higgs a nonzero vacuum value.
• A “Mexican-hat” potential analogy: the field value settles into a ring of minima rather than zero; random choice of direction breaks symmetry.
• Comments note this is more like a phase transition than an on/off switch; details of the exact mechanism are acknowledged as technically complex.

Mass, gravity, and energy

• Strong correction to claims that Higgs is needed for gravity: in general relativity, gravity couples to the full stress–energy tensor, not just rest mass.
• Even massless radiation (photons, early-universe plasma) gravitates.
• Some confusion over E=mc² is addressed by citing the more general energy–momentum relation and pointing out that rest mass is not required for energy.

Other mass mechanisms and field interactions

• Neutrino masses likely need extensions beyond the minimal Higgs mechanism:
  • Option with Higgs plus right-handed neutrinos that barely interact.
  • Option with heavy Majorana states giving light neutrino masses via mixing.
• Cross-field effects are mentioned: EM fields in media, superconductors giving photons an effective mass-like behavior, and energy in EM fields gravitating.

Analogies, misconceptions, and aether

• The popular “Higgs as sticky soup / drag” analogy is criticized as misleading and violating basic mechanics.
• Some see the article’s attack on this analogy as perhaps a straw man; others report having seen it often.
• Comparison with historical aether:
  • Aether had a preferred rest frame for light and was ruled out by experiments.
  • Modern fields and spacetime do not provide such a frame, so “aether” is generally viewed as inapt, though some note conceptual similarities to a “structured vacuum.”
• Debate over calling fields “non-physical”: some say that’s just a way of saying “fundamental”; others find it ontologically unsatisfying.

Pedagogy, resources, and precision

• Multiple commenters praise slightly-mathy explanations (wave equations, Klein–Gordon, Dirac) as more satisfying than pure metaphors.
• Several links to lectures, videos, and books are shared that bridge pop-sci and technical treatments.
• One criticism: the article’s mention of a “stationary electron” is flagged as an idealization not physically realizable, though common in theory.

Open conceptual questions

• A late comment asks why fields and particles “keep moving forever” and what underlies perpetual motion/inertia in terms of quantum fields.
• The thread labels this as a “why” question beyond current explanations; no consensus answer is offered.

Overall reception

• Many commenters are impressed by the technical ambition and smoothness of the editor, especially given it’s WebGL-based.
• Several say they’re eager to try it and see it as a promising alternative to existing tools, though some won’t sign up without clear code export options.

Positioning vs incumbents (Webflow, Framer, Figma, Wix)

• Team frames it as Figma-like UX combined with HTML/CSS fidelity, contrasting with Webflow’s perceived clunkiness and Framer’s divergence from “real” code.
• Others note that for simple marketing/landing pages, mature incumbents with built-in analytics, templates, and funnels are still attractive.

Code export, hosting, and “walled garden”

• This is the most contentious topic. Many say lack of HTML/CSS (or React) export is a deal-breaker and call this “digital feudalism.”
• Desired options: static HTML/CSS export, React/component export, Git-based sync, self-hosting, or at least downloadable “frozen” output.
• Motivations: control over infra, integration with existing stacks (Vercel, GitHub Pages), long-term data sovereignty, and avoiding lock-in or price shocks.
• The team is reconsidering, exploring code export and alternative business models but has no concrete plan yet.

Responsiveness, semantics, SEO & accessibility

• Current workflow is desktop-first with breakpoints; some question this vs mobile-first.
• Commenters highlight need for semantic tags, better defaults, and integrated SEO/a11y checks.
• The product already scores decently on Lighthouse but not top-tier; future improvements and per-element tag control are planned.

Rendering engine, WebGL, and text layout

• Many recognize the difficulty of reimplementing CSS and text rendering; there’s detailed discussion of fonts, metrics, HarfBuzz, Skia, etc.
• Team notes brutal effort to match browser text/layout and that they currently focus on Latin script, with ligatures and complex scripts deferred.
• Some question whether WebGL is necessary vs smart caching; others argue GPU-driven editors enable Figma-level smoothness.

Performance & visual quality

• Discussion about FPS: some say 30+fps feels better; others note designers may not need very high frame rates.
• Aliasing at certain zoom levels is observed; suggestions include shader-based AA, supersampling, and accumulation-buffer style techniques.
• Team is open to WebGPU in future and considering a C++/WASM core for performance.

UX, onboarding, and feature requests

• Playground without signup exists but is hard to discover from the main site; several request ungated, more-visible demos.
• Requests include: Figma import, HTML/CSS import, semantic IDs for post-processing, CMS/data integrations, relative CSS units (rem/em/vw/container units), component libraries, SDK, and embedding the editor into other apps.
• Some want the rendering engine itself open sourced as a general-purpose canvas/graphics platform.

Internationalization and input

• Current text system struggles with emojis, IMEs, and non-Latin scripts; users report broken input and missing context menus.
• Team acknowledges it’s Latin-focused so far and treats broader i18n as future work.

Site design, “scrollytelling,” and accessibility

• Some praise the smooth, non-hijacked scrolling and narrative feel; others find the style disorienting, hard to navigate, and unusable with disabilities or on e‑ink tablets/locked‑down browsers.
• Concerns raised: motion and constant animation, low contrast, poor reader mode output, unclear loading states, performance issues (including crashes on iOS Chrome).
• General split: engaging storytelling vs. “gimmicky” and distracting; strong call for plain text + static graphics as an accessible baseline.

Use of the map and data

• Divers and survey groups report using similar wreck data for dive planning and imaging.
• The dataset is also seen as valuable for pollution‑cleanup efforts and underwater cultural heritage work.
• The creator notes the project has taken ~12 years of spare time, motivated by wanting to see spatial and temporal patterns.

Salvage, low‑background steel, and ethics

• Discussion of pre‑1945 “low‑background steel” and centuries‑old low‑background lead for sensitive scientific instruments.
• Several posters say demand has dropped with the decline of atmospheric testing; others recall it being used for medical and physics applications.
• Debate over salvaging wrecks: some call it grave‑robbing and note legal protections for war graves; others argue most human remains are long gone and wrecks weren’t intended as memorials.
• Mention of specific non‑grave wreck sources (e.g., scuttled fleets) and current illegal/under‑the‑radar scrapping operations.

Human cost and modern geopolitics

• Many are struck by the density of dots and the horror of merchant losses, especially unarmed transports.
• Extended debate connects WWII losses to present risks around Taiwan, Ukraine, and the South China Sea.
• Tensions:
  • Whether it is “worth” great‑power war to defend smaller states.
  • Nuclear deterrence vs. appeasement, and whether current Western responses embolden or restrain aggressors.
  • US role as “world’s police” vs. beneficiary of global order; tradeoffs between military and domestic spending.

Shipping, logistics, and historical context

• Context on modern merchant fleet size and ship types; today’s ships are fewer but much larger and more efficient.
• WWII tanker losses pushed construction of long‑distance oil pipelines; attacks on supply lines and merchant marine casualty rates highlighted.
• Users relate personal family stories (merchant sailors, naval crews) and reference books and memorials that deepen understanding of specific battles and the scale of sacrifice.

Patterns in the map and WWII turning points

• Users note how yearly layers visualize the war’s global reach and the Axis–Allied momentum shift.
• 1942–43 “inflection” is linked to multiple factors: major battles (Midway, El Alamein, Stalingrad, Guadalcanal), codebreaking (Enigma, Bombes, Colossus), improved ASW tactics, fixed US torpedoes, and increased production.
• One commenter argues the graph crossing point is just gradual attrition, not a sharp structural break.

Routes, coasts, and open ocean

• Observers are surprised how few ships sank in the deep open ocean; most wrecks cluster near coasts, straits, and supply routes.
• Explanations: great‑circle routing that still follows coasts, concentration near ports and chokepoints, and attackers preferring “target‑rich” areas.
• Links to modern traffic visualizations used to compare contemporary routing patterns.

Scope of the Question and Assumptions

• Central dispute: the TV question mixes probability, adversarial behavior, and interview meta-goals.
• Some note the article implicitly assumes the number is chosen uniformly at random; the TV clip explicitly allows adversarial choice.
• Several argue the article’s title overstates “incorrectness”: the original claim can be seen as about adversarial play and expected value, not pure binary search.

Random vs Adversarial Choice and Expected Value

• With a uniform random secret number and straightforward binary search, multiple commenters reproduce the result that the guesser has slightly positive expected value (around +$0.20).
• If the picker is adversarial but must commit to a number, standard “start at 50” binary search becomes exploitable: the picker avoids “easy” numbers.
• Counter-strategies discussed:
  • Randomizing the initial guess within a band (e.g., 37–64) while preserving worst‑case depth.
  • Randomizing offsets across later guesses.
• Several call for or sketch game-theoretic / Nash equilibrium analysis; consensus is that optimal strategies are mixed, not pure, and the true equilibrium EV is nontrivial and unresolved in the thread.

Cheating vs Adversarial Within the Rules

• Some point out that if the picker can change the number mid-game, they can always win; this makes the puzzle uninteresting unless precommitment (e.g., writing the number down) is enforced.
• Others insist the game is only interesting if “adversarial” means “worst-case choice within fixed rules,” not cheating.

Clarifying Questions and Trust

• Multiple commenters say a strong candidate would first clarify:
  • Is the number an integer?
  • Is it chosen randomly or adversarially?
  • Is it precommitted and verifiable?
  • Can the guesser stop early?
• This is framed as analogous to treating external inputs as untrusted in software design.

Interview and Brainteaser Culture

• Many criticize such puzzles as ego trips that poorly predict job performance, sharing stories of hostile or gotcha interviews.
• Others defend them if used to:
  • Observe reasoning, communication, and ability to say “I don’t know.”
  • Test comfort with ambiguity and clarifying requirements.
• There is broad agreement that delivery and framing matter far more than having the “correct” answer.

Broader Themes

• Discussion touches on:
  • Over-pigeonholing people as “technical” vs “nontechnical.”
  • Cognitive biases (Dunning–Kruger, narrative bias, attribution errors).
  • Binary search as a powerful general debugging and diagnostics tool beyond coding.

Website & Resources

• Several people report the Ninjalab site hanging; workarounds include reader mode, blocking the loading overlay, or using the linked PDF.
• Links to Yubico’s advisory and support article are shared.

Vulnerability Scope & Requirements

• Affects YubiKey 5 series with firmware <5.7 using Infineon’s cryptographic library.
• Exploit is an electromagnetic side-channel on a non-constant-time modular inversion in ECDSA.
• Requires physical access, disassembly of the key, lab-grade EM equipment, and a few minutes of traces.
• Once refined, the attack might not require fully destroying the device; current work didn’t focus on re-packaging.

Impact on Security Guarantees

• Key extraction turns the device from “unextractable secrets” into “very hard-to-extract secrets”.
• Some argue this is mainly a high-end, targeted attack; others note many YubiKey use cases (crypto, defense, banking) are exactly such high-value targets.
• Attestation keys can also be cloned, undermining hardware model enforcement and FIDO attestation in some deployments.

Firmware, Mitigations & Replacement Debate

• YubiKey firmware is not upgradable; old devices remain vulnerable.
• Earlier Infineon issue (ROCA) led to free replacements; several posters are surprised replacements aren’t offered now.
• YubiKey 5.7 switches from Infineon to Yubico’s own crypto library; some are nervous about custom crypto, others say it’s reasonable after multiple vendor failures.

Broader Infineon Ecosystem

• Discussion notes all Infineon secure microcontrollers using the affected crypto library may be vulnerable: TPMs, e-passports, phone secure enclaves, SIMs, some hardware wallets, EMV cards, tachographs, etc.
• There’s debate about how serious this is for each: some see primarily forensic/government use; others highlight passports, banking apps, and payment systems as significant.

FIDO2, PINs, UV & Passkeys

• PIN/user verification can often be bypassed because relying parties may request “user verification not required”; thus the side-channel can be driven without PIN knowledge.
• This can reduce “key + PIN” from two factors to effectively one (possession).
• Resident (discoverable) vs non-resident credentials matter: resident ones can be attacked offline; non-resident need the credential ID, typically learned via a legitimate challenge.

Usability, Backups & Account Management

• Major pain point: no easy way to enumerate where a key is registered; users resort to tagging entries in password managers.
• Many recommend registering multiple keys only on critical services (email, password manager, SSO, cloud) and keeping backups in separate locations.
• Some lament difficulty of securely backing up or cloning keys; proposals for paired/synchronizable keys are debated as too risky/complex.

Crypto Engineering & Certification Critique

• Infineon is criticized for a non-constant-time primitive; modular inversion leaks are seen as a basic failure.
• Common Criteria certifications are questioned since the flaw survived ~14 years and many evaluations.
• Some note this is a known class of attacks; constant-time algorithms, blinding, or using schemes like EdDSA could have mitigated it.

Terminology and “Targeted Individuals (TIs)”

• Some see using “targeted individual” as validating a harmful delusional frame (external persecution, gang-stalking, tech harassment) with real-world risk (self‑defence violence, estrangement from family).
• Others argue the label comes from a self-organized movement and is used to avoid immediately invalidating people whom psychiatry has already failed.
• Several point out that TI-type beliefs are structurally similar to conspiracy theories: impose meaning, assign blame, grant specialness and a sense of (illusory) control.

What It’s Like to Hear Voices

• Multiple detailed first‑person accounts: voices can be external or internal; malicious, commanding, or supportive; sometimes location‑specific (e.g., behind you, in another apartment, in the abdomen).
• Some distinguish hallucinated voices from normal inner monologue by loss of voluntary control, distinct “personality,” and sometimes apparent agency (negotiation, tricks, predictions).
• A few argue benign or guiding voices can be integrated and even helpful; others warn that “good” voices can still mislead and reinforce poor decisions.

Risk, Violence, and Substance Use

• One clinician stresses that psychosis, especially schizophrenia, is associated with higher violence and homicide rates; argues stigma is not the main problem, untreated illness is.
• Another cites a study: most homicides by people with schizophrenia involved substance misuse and/or absence of planned treatment; replies note self‑medication is common and severe cases are more likely to use substances.
• Some emphasize that paranoid frameworks like TI can justify pre‑emptive violence (“kill them before they kill you”).

Medical Model vs. Spiritual/Trauma Models

• “Broken brain” framing:
  • Supporters say it’s accurate, reduces moral blame, and encourages caution about one’s own perceptions.
  • Critics say it’s crushing, encourages total self‑distrust, and drives people into TI/spiritual communities that feel more validating.
• Alternatives raised: trauma‑based models (structural dissociation), “spiritual emergency,” shamanic interpretations, and psychedelic‑like states as protective responses to trauma.
• Strong debate over whether spiritual explanations are open‑minded or just misinterpreting well‑studied cognitive/perceptual glitches.

Treatment Experiences and Practical Responses

• Several describe dramatic improvement on antipsychotics (e.g., Risperidone) after severe paranoid psychosis; others describe years of trial‑and‑error and side effects with limited benefit.
• Some successfully stop meds; others stress lifelong adherence and avoiding alcohol/weed.
• Common ground:
  • Drugs often function as stabilizing “band‑aids,” not cures.
  • In acute crisis, listening without open contradiction and providing practical safety (food, sleep, perceived protection) can reduce paranoia; longer term, psychiatric support is needed.
  • Normalization can reduce shame but may also delay necessary treatment.

Culture, Meaning, and Science

• Cited research and anecdotes suggest culture shapes voice content and valence: more hostile in Western/“WEIRD” contexts, more neutral or positive in some African/Indian settings.
• Debate over whether hallucinations tap into “something real” (spirits, non‑material realities) versus being entirely brain‑generated; both sides accuse the other of overconfidence.
• Several note psychiatry is effective in some ways yet conceptually immature; call for humility, rigorous science, and space for subjective meaning without endorsing dangerous delusions.

Legitimate uses of argv[0]

• Many commenters argue argv[0] is fundamentally just another argument and widely useful:
  • Multi-call binaries (e.g., busybox, toybox, Android tools, rustup, git, clang, coreutils-style shims) dispatch behavior based on the invoked name.
  • Shells use it for “login shell” behavior (leading - in argv[0]).
  • Programs use it in help/error messages and examples, sometimes stripping the path or using __progname.
  • Some tools use it to set or display process titles (with OS APIs like setproctitle, prctl, or language-level wrappers).
  • Scripts and binaries sometimes use it (or related mechanisms) to locate resources relative to the executable.

Busybox and compatibility

• Busybox and similar toolsets are repeatedly cited as strong counterexamples to the claim that argv[0] is “legacy” or unnecessary.
• Removing or restricting argv[0] would break POSIX/Unix expectations, existing scripts, and many systems that rely on multiple names resolving to one binary.
• Suggestions like “just use busybox cmd” or wrapper scripts are criticized for overhead, non-POSIX behavior, and incompatibility with existing binaries and scripts.

Security concerns and criticism of security tooling

• The article’s core concern: attackers can spoof argv[0] to fool logging, detection, or EDR tools, or use very long values to disrupt telemetry.
• Many replies say this reflects flawed security software, not a design flaw in argv[0]:
  • Correct process identification should use OS facilities (/proc/*/exe, executable-path APIs, mapped binaries), not trust argv[0].
  • Treat argv[0] like untrusted user input; escaping/quoting in logs is the responsibility of logging tools.
• Some agree the call site’s ability to set argv[0] is abusable, but think retrofitting restrictions would break too much.

Executable path vs. invocation name

• Strong consensus: argv[0] is the invocation string, not a reliable executable path.
• Several platform-specific APIs for getting the actual executable are mentioned and preferred when that’s the goal.
• There is debate over using argv[0] to re-exec oneself; critics highlight chdir/chroot/PATH issues, others say it’s acceptable in controlled contexts.

Disk space, performance, and “modern design principles”

• Claims that “disk space is no longer an issue” and that argv[0] violates “modern design principles” are widely rejected.
• Commenters cite embedded systems, routers, containers, and large images as cases where multi-call binaries and size savings still matter.

EBITDA and capital‑intensive businesses

• Debate over whether EBITDA is misleading or useful.
• Critics call it “earnings before bad stuff” and say it can obscure interest, tax, and capex needs, especially in capital‑intensive operations like holiday parks.
• Defenders argue it’s just one metric among many, useful for stripping out distortions and approximating operating cash flow, but dangerous if treated as “profit”.
• The article is seen as a case study in how capital intensity makes EBITDA less informative and forces focus on maintenance vs growth capex and cash‑flow statements.

Private equity, debt, and who benefits

• Some see the core problem as PE loading the business with acquisition debt, then having the company service that debt while PE extracts fees/returns.
• Others argue this deal doesn’t look egregious by PE standards and that PE has funded significant upgrades.
• There’s disagreement over whether the same asset, without repeated leveraged buyouts, could deliver lower prices or more reinvestment for customers.

Is this “price gouging” or normal market pricing?

• Many commenters say peak‑holiday price spikes are standard supply‑and‑demand, not legal/ethical “price gouging,” especially as school breaks are predictable.
• Others object to the term “price gouging” being used loosely for any high price, and reserve it for emergencies or monopoly abuse.
• A minority argue families feel exploited because children’s school schedules make off‑peak travel practically impossible.

Customer experience and captive‑resort dynamics

• Several parents like the forest setting, cycling, and pool, but think on‑site restaurants and activities are “eye‑wateringly” expensive.
• Many bring their own food and bikes, treating meals out as rare treats; some note restaurants now sit half‑empty despite full parks, likely due to cost‑of‑living pressures.
• Others counter that guests voluntarily choose a “captive” resort, akin to cruises, so high on‑site pricing is part of the model.
• Specific complaints include lack of laundry, gas ovens seen as unsafe, awkward vehicle policies, and limited options for under‑5s.

School holidays, attendance rules, and demand spikes

• UK rules fining parents for term‑time absences are blamed for concentrating demand in narrow windows and driving prices up.
• Some advocate giving families an explicit right to limited term‑time absences or staggering holidays by region to smooth demand.
• Others argue discretion doesn’t scale, creates perceived unfairness, and adds risk and workload for schools and teachers.

Land, forests, and tax‑driven investment

• Commenters highlight that the business owns large forest tracts in a country with relatively little woodland.
• Some suspect a strategy of revaluing forest land via small‑parcel sales, exploiting planning creep from “temporary” forest lodges toward eventual housing, and benefiting from favorable tax treatment for woodland and farmland.
• Rising forest prices are also linked to inheritance‑tax exemptions and wealthy individuals accumulating land.

Inheritance tax and intergenerational wealth

• Heated sub‑thread on whether inheritance tax should exist.
• One side argues exemptions for land and forests shift the tax burden onto salaries and investments and entrench feudal‑style wealth.
• The other side sees inheritance tax as corrosive to family responsibility and social cohesion, and rejects the notion that inherited wealth inherently produces “unproductive” heirs.

Miscellaneous points

• Some think high occupancy (~80%) indicates pricing is efficient, not exploitative.
• There’s disagreement over how much real competition the brand has (e.g., Butlins, Pontins, independent cottages).
• Minor side‑discussion on branding/spelling (“Center Parcs”) and on whether PE’s expected returns here are even especially high.

Solar economics & negative prices

• Surplus solar and wind can drive wholesale prices to zero or negative.
• Some argue this is “bad for everyone” because producers must recover costs at other times; others see it as a useful market signal.
• Negative prices are linked to inflexible thermal plants and policy designs like guaranteed feed‑in tariffs, not inherent to solar itself.
• Past policies (e.g., German EEG) are debated: credited with global PV cost declines and lower spot prices, but also described as costly for the host country.

Storage, flexible load & market responses

• Many expect negative prices to incentivize storage (home batteries, grid batteries, EVs) and flexible loads (HVAC, industrial heat, data centers).
• Examples: using batteries with dynamic tariffs, bulk resistive heat storage up to very high temperatures, ice or thermal storage for cooling, and demand-response programs.
• Some think we’ve moved from “build more solar” to “build more storage next to solar.”
• Idea of EVs and home batteries acting as virtual power plants is popular, though not yet mainstream.

Grid vs off‑grid and microgrids

• Question raised whether cheap solar + cheap batteries could make the traditional grid partially obsolete.
• Skeptics point to seasonal variation and high-latitude winters: diurnal storage is plausible, seasonal storage with current batteries is not.
• Microgrids and community solar are seen as complementary, not full replacements; cities will still need large shared infrastructure.

Land use & siting

• Concern over solar farms displacing agriculture, especially in SE England.
• Counters: solar land share could be under 1% nationally; agrivoltaics and grazing under panels can coexist with farming; offshore wind and rooftops reduce land pressure.
• Nuclear is far more land‑efficient but faces cost, planning, and political barriers.

Alternative sinks & fuels

• Ideas for soaking up surplus: hydrogen production, synthetic hydrocarbons via captured CO₂, desalination, sewage treatment, industrial furnaces, and compute workloads.
• Debate over hydrogen vs synthetic hydrocarbons: hydrogen is harder to store/transport but zero‑carbon; e‑fuels can use existing infrastructure but reintroduce combustion CO₂ unless feedstock carbon is captured.

Policy, subsidies & market design

• Large energy subsidies in Europe, especially during crises, raise questions about whether markets alone can handle volatility.
• Some see reserve payments for gas plants and connection fees as necessary reliability tools; others want faster phase‑out and better incentives for storage and demand response.

Nuclear, CCS & SAF

• Nuclear is portrayed by some as economically undermined by cheap daytime solar; others point to low‑carbon grids built with nuclear (e.g., France) as proof of concept.
• Carbon capture and storage is criticized as politically unattractive because it doesn’t reduce fossil extraction.
• Sustainable aviation fuel (SAF) exists at modest scale; producing it purely from electricity and air (via CO₂ capture) is seen as technically possible but currently uneconomic and policy‑dependent.

Bitcoin and speculative energy sinks

• Using excess energy for Bitcoin mining is raised and largely criticized as wasteful and socially harmful compared to productive uses like storage, hydrogen, or industrial processing.

Scope and Meaning of the Efficient Market Hypothesis (EMH)

• Several comments stress EMH is narrowly about financial asset pricing, not “markets” or “society” in general.
• EMH is framed as a model/hypothesis: prices rapidly incorporate available information, not that markets are perfectly efficient or “right.”
• Some note the original proponent has always treated it as a model that’s never 100% true.

Information, Prices, and Quality

• Markets are described as information-compression systems: huge complexity → single price.
• Critics say prices are one-way encodings; you can’t decode quality, labor conditions, or externalities from price alone.
• This creates “lemon market” dynamics and pushes quality down when buyers can’t assess it.
• Online reviews and ratings are seen as a crude, easily gamed substitute for objective quality signals; detailed proposals for audit-based rating systems are discussed.

Externalities, Ethics, and Inequality

• One side argues pollution, forced labor, and low quality are “priced in” via consumers’ (often low) willingness to care.
• Others counter that harms fall on people who don’t participate in the relevant transactions and can’t “opt out,” so they’re not truly priced in.
• Ethical options often appear only as high-end niche products; information opacity and lack of regulation mean consumers rarely even get a realistic ethical choice.

Entrepreneurship, Innovation, and EMH

• Several argue perfectly efficient markets would leave no room for entrepreneurs or active investors; EMH would make funding innovation irrational.
• Others reply EMH applies mainly to public markets; private startups and changing conditions still create opportunities and uncertainty.

How Efficient, and For Whom?

• Consensus: markets are not perfectly efficient but not trivially beatable either.
• Some see “markets trend toward efficiency”; critics note there’s no bound on how long that takes and “in the long run” may be irrelevant.
• Distinction is drawn between markets being hard to beat and inefficiencies being structurally unexploitable or dominated by noise.

Economics, Ideology, and Models

• Multiple comments accuse EMH and related ideas of being treated as ideological dogma or political cover, especially in macro policy.
• Others defend economics as increasingly empirical, emphasizing that models are abstractions, not literal reality.

Usefulness of IPMI / OOB Management

• Widely seen as indispensable for remote servers: power control, rebooting, and remote console were crucial in events like large‑scale agent failures requiring many reboots.
• Even in small deployments, tools like ipmitool/ipmiutil are valued for hardware introspection and automation.
• Some boards expose BMC graphics as a simple framebuffer device; usable for basic desktops but too slow for modern GUIs or high resolutions.

Homelab vs Datacenter Trade‑offs

• Homelab users like integrated IPMI but dislike its idle power draw (often ~5–7W even when host is “off”).
• Debate over where that power goes: some blame the BMC, others the PSU’s inefficiency at low load.
• Datacenter‑oriented designs (no ACPI sleep, crude fan control, loud chassis) clash with SMB/homelab expectations, but are seen as acceptable for rack environments.

Security, Isolation, and Long‑Term Support

• Strong consensus: treat IPMI as highly sensitive and potentially insecure.
  • Always isolate on separate VLANs/VRFs, often only reachable via VPN or bastion.
  • Avoid BMCs that share the main NIC; some implementations silently fall back to it.
• Known weaknesses:
  • IPMI 2.0 sends password hashes to clients and limits passwords to 20 chars.
  • Past bugs allowed null encryption or any password to succeed.
  • Some designs expose unauthenticated admin from the host; useful for recovery but expands attack surface.
• Concern that BMC firmware receives poor long‑term updates; many would prefer fully user‑controlled, open firmware.

Vendors, Hardware, and Firmware Quirks

• Supermicro, ASRock Rack, Dell, HPE, Lenovo all have fans and detractors:
  • Supermicro praised for reliability and flexibility but criticized for archaic UIs, fan handling, lack of sleep, proprietary utilities, and recent secure boot key leaks.
  • ASRock Rack praised for modern features and layout, but some report high RMA rates or specific firmware bugs.
• Intel vs AMD:
  • Many see AMD as better value/performance; Intel NICs are generally respected despite some bad driver eras.
  • AMD PSP / Intel ME are acknowledged as necessary low‑level init engines but distrusted due to opacity and past vulnerabilities.

Redfish and Management Standards

• Redfish is promoted as IPMI’s successor (HTTP/JSON, better security model, broader feature set).
• In practice, implementations are inconsistent:
  • Tasks like SSL cert upload or virtual media/boot control require vendor‑specific workarounds.
  • Automation frameworks must carry per‑vendor logic despite apparent standardization.
• Some regard IPMI as a “dangerous, attractive nuisance” and see Redfish as an improvement, but not yet uniformly reliable.

Alternatives to Built‑In IPMI

• External KVM devices discussed for systems without or with untrusted IPMI:
  • PiKVM, TinyPilot, BliKVM, and NanoKVM offer HDMI capture, USB keyboard/mouse, and sometimes ATX power control.
  • Concerns about closed firmware on some devices; enthusiasm rises when vendors promise or deliver open backends.
• Some pair servers with Raspberry Pis or routers running OpenWrt as always‑on serial/KVM controllers, reverting to simple serial management plus out‑of‑band power (e.g., smart plugs, WoL).