Hacker News, Distilled

Why an IRC client on Kubernetes (and on KubeVirt)

• Several commenters ask why not just run Weechat in a container, or a plain VM, or Proxmox.
• The main justification given: there is already a Kubernetes cluster with distributed storage; using it keeps everything “standard” instead of adding unique one-off systems.
• Another reason: wanting to use Weechat’s soft-upgrade mechanism without rebuilding images; at that point a full VM feels simpler than a tightly versioned container.
• Critics argue this is an anti-pattern since it decouples runtime software versions from container images; suggested alternatives include init containers, Nix-based images, and automated image updates (Renovate, CI/CD, Helm).

Kubernetes as “standard” vs “overkill”

• One camp sees Kubernetes as the pragmatic standard: a single, uniform way to run many different services, even at home (“home-ops”), reducing aggregate complexity versus many bespoke setups.
• Others counter that k8s adds a large operational layer (CNI, DNS, autoscalers, operators), and that simpler tools (systemd, Docker Compose, Docker Swarm, Proxmox) are more appropriate for small, low-load setups.
• Debate centers on “unique vs standard” rather than “simple vs complex”: SRE/operator benefit vs application developer constraints.
• Lightweight k8s “distros” (k3s, Talos, etc.) are cited as making clusters approachable and reproducible, especially with GitOps (Flux, Helm).

Stateful workloads and networking on Kubernetes

• Some claim Kubernetes is ill-suited for stateful, long-lived connections; CNIs and load balancers can introduce hiccups under node failures or rescheduling.
• Others report success with long-running TCP/UDP streams on modern CNIs and argue such issues are more about specific implementations than k8s design.
• Suggestions include dedicated node pools for stateful apps and tools like Agones for game/server-style workloads.

Homelab durability and storage

• A few run geographically distributed homelab clusters; others argue this is overkill compared to a single NAS plus offsite backups (e.g., S3).
• Rook/Ceph is mentioned as the default for distributed storage, but multi-region latency is problematic for strongly consistent POSIX storage; object storage and active/passive designs are suggested.

IRC tooling choices

• Alternatives discussed: IRCCloud (paid hosted), The Lounge (web client), Quassel (client–server), and Weechat relay mode.
• Choice often hinges on scripting support, persistence model (files vs DB), and the “fun” of self-hosting versus convenience.

YAML and tooling humor

• Multiple jokes about writing lots of YAML, Ansible as “bash in YAML,” and configuration as modern “dark magic,” reflecting both fatigue and familiarity with these tools.

Control Panel vs. Settings App

• Many see the classic Control Panel as more powerful, efficient, and discoverable, especially for networking, sound, printers, and advanced device settings.
• The Settings app is criticized as incomplete: some options are missing, neutered, or just redirect back to old applets.
• Single-window design is widely disliked; users can’t open multiple Settings windows for parallel tasks.
• A minority say Settings has improved over the years and now covers most everyday needs, especially for non‑experts.

UX Design and “Tablet-ification”

• Strong sentiment that Windows is being reshaped into a phone/tablet OS: vertical layouts, huge whitespace, low information density, and touch targets on large desktop screens.
• Similar complaints are made about macOS System Settings and GNOME; trend seen as industry‑wide.
• Designers are accused of prioritizing aesthetics, KPIs, and novelty over usability and power‑user workflows.
• Others argue newer, smartphone‑like patterns are more intuitive to younger users who never learned Win95‑style UIs.

Search, Performance, and Reliability

• Windows search (Start, Settings) is widely described as slow, unreliable, and prone to launching Edge/Bing instead of local tools.
• Third‑party tools like Everything, StartAllBack, and EarTrumpet are frequently recommended workarounds.
• Settings and other “modern” apps are reported to stutter, show loading screens, and occasionally freeze, unlike older Win32 dialogs.

Concrete Pain Points

• Networking: new pages often hide or omit key details (DNS suffixes, adapter stats, jumbo frames, diagnostics).
• Sound: users still rely on legacy “Sounds” and audio device dialogs; some features exist only in old or only in new UI.
• Printers: “Windows manages my default printer” and deep‑buried options cause confusion; Server editions share many of these issues.

Deprecation Scope and Timeline

• Official wording now says many Control Panel settings “are in the process of being migrated,” not that Control Panel is immediately removed.
• Some note this “deprecation” has effectively been ongoing since Windows 8.
• Concern remains that advanced options may vanish rather than be fully reimplemented.

Alternatives, Nostalgia, and Broader Themes

• Repeated nostalgia for Windows 2000/XP/7 UIs that “got out of the way.”
• Numerous commenters say Windows is now mainly a gaming platform; Linux (often with KDE/Plasma and Proton) or macOS are preferred for daily work.
• Suggestions include relying more on PowerShell, netsh, registry tweaks, “God Mode,” or even ReactOS components if functionality disappears.

Author-Paid Open Access and Incentives

• Many agree high APCs (author publication charges) are exploitative given publishers’ high margins and minimal added services.
• Pay-to-publish models are seen as fueling low‑quality and spammy journals; MDPI is mentioned as an easy-to-ignore “spam” brand.
• Some argue author-paid OA is not the core problem; it’s the incentive structure that rewards sheer publication and citation counts.

Prestige, Journals, and Prisoner’s Dilemma

• Career advancement, grants, and PhD completion heavily depend on publishing in high‑impact, selective journals.
• This creates a prisoner’s dilemma: everyone knows arXiv/WWW-style publishing could be better, but no one can risk abandoning prestige venues alone.
• In some fields (e.g., biomed), journal brand and editor gatekeeping matter more than reviewers per se.

Peer Review: Problems and Proposals

• Complaints about superficial or misguided reviews, reviewer anonymity, and political/editorial interference.
• Suggestions include:
  • Rewarding peer review more than raw publication counts.
  • Making reviews public and subject to “peer review of peer review.”
  • Double-blind review to hide author identity; disagreement on whether reviewers should remain anonymous.
• Concerns that open, non-anonymous review could lead to favoritism and retaliation.

Metrics, Gaming, and Goodhart’s Law

• Heavy criticism of reliance on paper counts, h-index, and citations as proxies for quality.
• Examples of citation rings, mega-collaborations with thousands of coauthors, and ML/CS papers that are hard or impossible to reproduce.
• Observations that metrics invite gaming, shifting effort from doing good science to optimizing numbers.

Field Differences and Quality Crisis

• Perceived severity varies by field:
  • Medicine/clinical research and epidemiology described as especially plagued by poor design, data dredging, and careerist projects.
  • CS/ML has its own replication issues and selective reporting, despite strong preprint culture.
• Some link systemic flaws to declining public trust in science; others argue denialism would exist regardless.

Proposed Structural Reforms

• Shift evaluation toward importance of questions, rigor, and quality of review rather than volume of output.
• Strengthen society/overlay journals and institutional curation of arXiv.
• Tighten grant and hiring standards to penalize use of dubious venues and metrics gaming.
• A few argue the root problem is broader political/economic pressures (competition for scarce funding, student loan system).

Value Proposition and “Need”

• Many see Vision Pro and high-end headsets as “solutions in search of a problem”; smartphones already solve most day‑to‑day needs.
• Others argue “need” is the wrong framing for consumer electronics; lots of tech is valuable as convenience or entertainment rather than necessity.
• Comparison is made to PCs and smartphones: once niche “nerd toys” that only later found mass‑market killer apps.

Form Factor, Comfort, and Motion Sickness

• Bulky “ski-goggle” headsets are widely viewed as socially awkward, heavy, and uncomfortable for long sessions.
• Several users report eye strain or motion sickness, especially when movement in VR diverges from physical movement; others say newer tracking largely resolves this for them.
• Many believe mainstream adoption requires something like normal glasses or “swim‑goggle size” hardware; current tech is seen as too early.

Price and Market Dynamics

• $3,500+ price for Vision Pro is viewed as a major barrier; many would expect boredom after novelty wears off.
• Sub‑$1,000 (or even sub‑$500) is repeatedly cited as the threshold for a viable mass market.
• Meta’s billions in Reality Labs losses and relatively low monthly active users are used to argue that current VR is a business failure despite technical progress.

Use Cases: Gaming, Media, “Teleportation,” Accessibility

• Gaming is considered the only clearly compelling mass‑market use so far, but constrained by motion sickness and limited genres.
• Some describe profound “teleportation” experiences: immersive natural environments, spatial photos/videos, and VR travel for disabled or elderly people.
• Others find these close to “big photos” and question how often people would actually use such features.
• Productivity/meetings in headsets are widely mocked; most people won’t even turn on webcams, let alone wear goggles.

Ecosystem, Content, and Walled Gardens

• Lack of standout apps and Apple’s tight platform control are blamed for weak Vision Pro appeal; Meta’s ecosystem is seen as somewhat more hackable but still constrained.
• High cost + tiny user base discourage third‑party developers; some argue these devices function as expensive devkits.
• Porn, social VR (e.g., VRChat), and “coomer” demand are cited as real drivers of usage that big platforms publicly avoid but can’t ignore.

Meta vs. Apple Strategies and Future Outlook

• Meta appears to be refocusing from premium MR toward cheap Quests and Ray‑Ban smart glasses; those glasses are seen by some as the more promising form factor, by others as just camera‑glasses.
• Apple is viewed as using Vision Pro to learn, iterate, and maybe eventually ship a lighter, cheaper non‑Pro model.
• Many expect AR glasses + AI to be the real long‑term play; others think both AR and VR will remain niche for decades.

Context and comparisons to other systems

• iOS and Apple Silicon macOS have used 16 KB pages for years; Linux on some platforms (Asahi, some Debian/RHEL flavors, Nvidia Grace-Hopper) also explores 16–64 KB.
• Windows remains on 4 KB base pages (with 2 MB/1 GB “large/huge” pages) even on ARM64, partly to ease x86 compatibility.
• Prior attempts (e.g., RHEL’s 64 KB pages on AArch64) exposed many bugs and were eventually reverted.

Why 16 KB pages / performance arguments

• Larger base pages reduce TLB pressure and page-table overhead, which can be a big slice of runtime; reported 5–10% app speedups are seen as plausible.
• Bigger pages also help VIPT caches and allow larger L1 caches with fewer synonym issues, as seen in Apple designs.
• Huge pages (2 MB, 1 GB) already provide big wins for databases, hypervisors, and managed runtimes; 16 KB is viewed as a more “everyday” compromise.

Compatibility and software breakage

• Apps break when they hardcode 4 KB: custom allocators, direct mmap/munmap use, ELF segment alignment, database formats, and runtimes like jemalloc and Wine.
• File formats and on-disk layouts that assume 4 KB (including mmapped DBs) can become unreadable on 16 KB systems.
• Toolchains and linkers often bake in page-size assumptions; Android NDK apps generally need rebuilding for a higher max page size.
• Some argue code should always use sysconf(_SC_PAGESIZE) etc., but decades of 4 KB ossified assumptions.

Mixed page sizes, CPU design, and kernel strategy

• Proper support for coexisting 4 KB and 16 KB user processes is non-trivial; depends on ARM’s translation granules and TLB behavior.
• RISC-V’s fixed 4 KB base pages plus extensions like Svnapot are debated; some see them as inferior to ARM’s configurable-granule approach.
• Transparent huge pages and newer schemes (mTHP, TAO) show that multi-size support is complex even on desktop Linux.

I/O, flash, and other side topics

• Larger RAM pages likely don’t hurt flash much: NAND internally uses much larger erase blocks and controllers already do wear-leveling and write coalescing.
• Bigger pages increase memory waste (fragmentation, per-thread stacks, page cache granularity); a ~9% RAM overhead is seen as significant but perhaps acceptable.

Skepticism and impact on devices

• Some see this as overdue modernization; others worry it will further penalize low-RAM or older phones by increasing memory pressure.
• Google’s track record on Android compatibility is viewed as mixed: better than some platforms, but willing to break older apps when pushing architecture changes.

Account freezes, KYC/AML, and SARs

• Multiple anecdotes of business and personal accounts at large banks being frozen or closed without explanation, sometimes with six-figure balances or payroll affected.
• Many commenters believe KYC/AML systems and Suspicious Activity Reports (SARs) are the root cause; banks are legally forbidden to disclose SARs, so staff simply say “risk/compliance decided; it’s final.”
• Some note that SARs are often filed defensively (“when in doubt, file”), most are never read, and banks face huge penalties if they under‑report, so they err on over‑reaction.
• Diversifying across banks may not fully help, as flags can propagate via systems like ChexSystems or compliance information sharing.

Lawyers, escalation, and dealing with big banks

• Strong theme: for substantial sums, get a lawyer quickly; demand letters and threats of litigation sometimes unlock stuck processes.
• Others emphasize aggressive escalation: bypass branch staff and Tier‑1 support, write succinct emails to executive offices, regulators, and legal departments, and use physical-world pressure (in‑person visits, even public embarrassment) to get attention.
• Arbitration clauses are common; some see pre‑dispute mandatory arbitration as harmful, though others say arbitration plus a lawyer can still be effective.

Big banks vs. credit unions and community banks

• Many advise avoiding giant retail banks for small businesses and individuals, favoring regional/community banks or credit unions.
• Reported benefits: actual decision‑makers reachable in branch, staff who know customers by name, manual overrides when systems misfire, fewer junk fees.
• Downsides: some credit unions lack international capabilities or strong IT; shared branching networks exist but have limits (e.g., low cash withdrawal caps).
• View that all large banks operate similarly under regulation is common; a minority insist certain brands have been uniquely bad in their experience.

Fintechs, Mercury, and Meow

• Some praise fintech platforms (e.g., Mercury, Meow) as more responsive to startups; specific anecdotes include rapid setup and exception handling when traditional banks failed.
• Others are wary: fintechs are not banks, depend on partner banks, and can be shut down or sanctioned; one commenter reports a Mercury-style fintech abruptly closing a long‑standing account.
• Several criticize mixing a cautionary story with referral links to alternatives, seeing an obvious conflict of interest; others counter that the recommendation came from genuine gratitude.

Crypto as hedge or distraction

• A subset argues that Bitcoin/crypto offers self‑custody and an escape hatch when banks freeze funds, at least for a portion of assets.
• Critics respond that crypto replaces bank risk with key‑management and custodian risk, still requires trust in software/hardware vendors, and is impractical for most business flows today.
• Debate centers on degrees of “trustlessness,” not on any consensus that crypto “solves” banking risk.

Many-eyes theory and bug discovery

• Several comments challenge “many eyes” / Linus’s Law as a security guarantee.
• Empirical arguments: bug-finding doesn’t scale linearly with reviewers; 2–4 focused reviewers may be optimal.
• High-profile bugs like Heartbleed and OpenSSL code quality are cited as counterexamples to the mantra that open source visibility alone yields security.
• Point that “eyeballs weren’t really looking” until incidents force attention.

Open source vs commercial security

• Debate over whether a volunteer-driven project like OpenSSH can match or exceed commercial security.
• One camp: open source is safer; closed vendors have cost pressure, weaker review, and are attractive targets for insider compromise.
• Others counter: corporations with massive infrastructure (cloud providers, etc.) run very advanced, process-heavy security programs and rarely suffer catastrophic breaches; they invest in access control, logging, and multi-party approvals.
• Some argue volunteer-led infrastructure still ends up more secure in practice; others say both FOSS and corporate efforts are essential and complementary.

XZ/OpenSSH backdoor specifics and impact

• Clarification that vanilla OpenSSH does not depend on xz; the backdoor hit Linux distros that patched in libsystemd, which in turn depended on xz.
• Strong view that expecting OpenSSH maintainers to vet transitive dependencies added by distributions is unreasonable; focus should be on distro processes.
• References to analyses of the payload: it hooks SSH RSA handling and uses a crafted “public key” as an encrypted command channel for remote code execution.

Historical backdoors and “bugdoors”

• Examples mentioned: Juniper firmware SSH backdoor, UnrealIRCd, ProFTPD, socat, a 2003 Linux kernel “bugdoor” attempt, UnrealIRCd backdoor challenge, and alleged but unproven OpenBSD IPsec backdoor.
• Consensus that “bugdoors” (malicious bugs) are plausible and may already have been patched unnoticed.
• Observation: backdoors in widely deployed components (like OpenSSH) are extremely high-stakes and may be more about disruption than targeted access.

Process, tooling, and defenses

• Tests and code coverage alone won’t prevent intentional backdoors.
• Suggestions include: better sandboxing/containers with sane defaults, OS-level permission/IAM-style systems, reduced SSH usage in production, and more specialized tools instead of raw shells.
• Desire for formal verification and rigor similar to certain microkernel projects, but recognition that full formal methods are hard; safer languages (Rust, Ada) are suggested as more realistic improvements.
• Concern that compilers and complex dependencies (e.g., init systems) widen the supply-chain attack surface.

Allegations Against RealPage and Legal Theory

• DOJ and commenters frame RealPage’s software as “price‑fixing as a service”: landlords share non‑public, competitively sensitive data (actual rents, concessions, occupancy, lease terms), and RealPage returns coordinated price recommendations.
• Key factors seen as problematic:
  • Use of confidential competitor data, not just public listings.
  • “Auto‑accept” and “compliance” expectations; pricing advisors escalate when managers want to undercut algorithmic prices.
  • Marketing and internal quotes explicitly touting cartel‑like benefits (e.g., “classic price fixing,” “avoid the race to the bottom”).
• Some argue this crosses the line from benchmarking into a centrally enforced pricing scheme that substitutes for explicit landlord‑to‑landlord collusion.

Market Power, Penetration, and Collusion Mechanics

• RealPage reportedly has ~80% of the “revenue management” software segment but far less than 80% of all US rentals; debate over how much share is needed to distort prices.
• In some submarkets (e.g., large multifamily complexes in specific cities or neighborhoods), penetration is alleged to be 30–70%, enough that a single algorithm may effectively set the marginal rent.
• Discussion of how landlords can profit from slightly higher vacancy if higher rents on the rest of the portfolio outweigh lost income, especially in supply‑constrained markets.
• Others note standard game‑theory logic: strong incentives to defect and undercut, questioning whether stable cartel behavior is realistic without strong enforcement.

Role of Housing Supply vs. Software

• Many argue RealPage can only push rents up marginally (a few percent) on top of a deeper structural problem: chronic under‑building, restrictive zoning, NIMBY politics, and post‑2008 construction collapse.
• Counter‑view: even small algorithm‑driven increases matter when millions are rent‑burdened; software can magnify harm where vacancy is already low and demand is inelastic.

Comparisons to Other Industries and Tools

• Analogies raised: airline fare signaling, gas stations watching each other’s prices, KBB/Zillow for cars and housing, compensation benchmarking tools, credit bureaus.
• Distinction drawn: those generally rely on public or regulated data and don’t enforce adherence; RealPage allegedly uses private data plus compliance pressure, making it qualitatively different.

Policy, Enforcement, and Broader Concerns

• Some want harsh remedies: break up RealPage, penalize participating landlords, treat this like classic Sherman Act criminal cases.
• Others are skeptical DOJ can win or see this as political theater that won’t materially move rents.
• Broader debate over:
  • Landlords’ role (productive business vs. parasitic rentier).
  • Price controls, rent control, and “protecting renters” vs. discouraging construction.
  • Alternative fixes: upzoning, land‑value taxes, vacancy taxes, public/social housing, and stronger antitrust against “collusion by algorithm” across sectors.

Mailbox security and PO box vulnerabilities

• Many are surprised PO boxes can be robbed; they assumed back-loaded boxes and robust locks.
• Several note that front-access master-key systems exist for post offices and apartments; a single master key or panel key can open hundreds of boxes.
• Claims that postal master keys are often stolen or duplicated; cheap insert locks can be bypassed with basic tools or lockpicking.
• General sentiment: common locks mostly deter honest people; determined thieves can bypass them easily.

Law enforcement, DAs, and “acceptance of crime”

• Multiple commenters argue low-level crimes are trivially catchable with decoys and trackers, but police and prosecutors often choose not to prioritize them.
• Explanations offered:
  • DAs not prosecuting petty crimes or drug offenses, leading police to see arrests as pointless.
  • Police unions and political dynamics causing “slowdowns” or selective enforcement.
  • Court backlogs, full jails, and resource constraints forcing triage.
• Others counter that claims of DAs “refusing to prosecute” are overstated or selectively framed, citing data where charge-filing patterns are more nuanced.
• Some see policing as more about visible power projection than solving property crimes.

Policy debates: petty crime, incarceration, and comparisons abroad

• One side advocates more consistent enforcement and meaningful penalties, especially for repeat offenders, arguing a small number of people cause disproportionate harm.
• Others note the U.S. already has extremely high incarceration, and point to Nordic countries with low incarceration and low crime as counterexamples.
• Pushback includes arguments about societal differences (size, “monoculture,” history) and that incarceration length, not arrest rate, is the main U.S. outlier.
• Debate remains unresolved; causes of higher U.S. crime are labeled “unclear.”

Porch piracy and delivery practices

• Some non-U.S. readers are baffled by packages left openly; others say it works fine in many U.S. areas and they value convenience over security.
• Suggestions include better front-door/package infrastructure, lockers, or requiring signatures; others warn that crime of opportunity is hard to fully eliminate.

Jurisdiction and response in this case

• Mail theft is noted as a federal crime, but commenters point out that multiple jurisdictions can apply simultaneously, so local sheriffs are still relevant.
• Some think the victim benefited from being in a small town; in big cities, police might ignore even precise tracker locations.

AirTags and technical limits

• AirTags rely on nearby Apple devices for location; they lack GPS and altitude.
• This makes them good for narrowing to a building or area, but not a specific apartment or floor without in-person searching.

Nostalgia and Community Preservation

• Many recall UT99, Deus Ex, and UT2004 as peak FPS experiences, praising their atmosphere, music, and user-made maps.
• Players reminisce about specific modes (Bunny Tracks, Instagib, Onslaught/ONS-Torlan), LAN parties, and strong bot AI that made small gatherings fun.
• There’s broad appreciation for projects that keep classic games playable and accessible on modern systems.

SurrealEngine and Related UE1 Projects

• SurrealEngine is seen as an ambitious, standalone reimplementation of Unreal Engine 1, with the goal of faithfully running games like UT99 and Deus Ex.
• A separate project, Surreal98 (formerly DXU24), aims to run UE1 games inside UE5 with modern features like VR; that one appears commercial and closed.
• Some worry about reimplementations that depend on heavy modern engines versus lean, SDL/OpenGL-style ports that can run on low-end or niche platforms.

Licensing and Third-Party Code

• A side thread debates a “cutesy” license in a third-party audio library (DUMB), with criticism that joke-style licenses create legal ambiguity.
• Others note DUMB is effectively BSD-like and argue that people should choose what makes them happy, while opponents stress licenses are legal tools, not entertainment.

Epic, Open Sourcing, and Old Catalog

• Many wish Epic would open-source Unreal Engine 1 (as id did with older idTech) or at least release code for its classic DOS games.
• An old statement from Epic indicated UE1 open-sourcing might be possible but would require cleanup; commenters note this still hasn’t happened and suspect Fortnite’s success shifted priorities.
• Some argue Epic could just strip proprietary dependencies and let the community patch; others point out Epic already gives limited source access to trusted community projects.

Arena FPS Genre and Modern Alternatives

• Several note that classic arena FPS (Quake/UT style) is effectively a dead or niche genre, supplanted by tactical shooters, hero shooters, and battle royale games.
• A few modern or open-source alternatives are mentioned (e.g., Quake Champions, Xonotic, Titanfall 2, Splatoon 3), but none match the old player counts or “feel” for many.
• There’s skepticism a new Unreal Tournament could justify its cost, despite nostalgia-driven demand.

Perception of the Handbook

• Many recall the 2012 handbook as fun, well-designed, and inspiring, with strong visual presentation.
• Several doubt it was ever a true internal handbook; prevailing view is it was a deliberate public-facing PR/recruiting artifact rather than a “leak.”
• Some question whether Valve ever actually operated as described, or still does, given later reports about internal dysfunction.

---

Flat / Managerless Structure & Internal Politics

• Multiple comments argue Valve’s “no managers” approach produces hidden hierarchies, “pseudo‑managers,” and informal cabals with unclear power.
• Getting meaningful feedback and understanding expectations is described as hard; success often depends on pleasing influential but unofficial leaders.
• Critics say important “normal company” tasks (consistent execution, long-term support) are harder or “impossible” in this model.
• Others counter that by hard metrics (revenue, profitability, user love, Steam’s dominance), Valve’s structure is highly successful, even if unpleasant for some employees.
• Several reference “The Tyranny of Structurelessness” to explain how power concentrates informally when formal structure is removed.

---

Steam, Monopoly Debate, and Competitors

• Widespread agreement that Steam is by far the dominant PC games storefront; users often refuse to buy games elsewhere.
• Disagreement on whether this is a “monopoly”:
  • One side: effective monopoly / “unimpeachable” position reinforced by network effects and weak competition.
  • Other side: not a legal or structural monopoly; Windows is open, many stores exist, and Steam mainly wins by better UX and not abusing power.
• Competitors (Epic, Xbox, EA, Ubisoft, etc.) are criticized as clunky, slow, feature-poor, or focused on exclusivity and dev-side perks rather than user value.
• GOG is often praised (especially for DRM-free) but seen as niche.
• Some view Valve’s slow, consensus-driven culture as a reason Steam hasn’t been “enshittified.”

---

Games vs Platform, “Lifestyle Company” & Incentives

• Several say Valve now behaves more like a platform/hardware company than a traditional game studio; live-service titles and Steam dominate.
• Complaints that new single-player games are rare, some live-service games (e.g., CS2, Dota 2 features) feel under-supported, and promising projects die quietly.
• Bonus structure is criticized as rewarding launching things more than maintaining or improving them over time.
• The company is characterized by some as a “lifestyle company” optimized for a particular internal culture rather than for shipping lots of games.

---

Management, Alternatives, and Comparisons

• One subthread debates whether managers add value; defenders cite shielding teams from politics, securing resources, and resolving conflicts.
• Comparisons are made to Google’s brief experiment with cutting project managers, Gore’s self-organizing teams, and democracy as a structural analogy.
• Some argue the best “answer” is to stay small to minimize politics; growth inevitably increases structural and political complexity.

Role of Science, Trust, and Individual Choice

• Several comments argue that people should not be compelled to “follow the science” as if it had inherent moral authority; individuals should retain autonomy over medical decisions.
• Others counter that complex modern systems (medicine, water, food) necessarily rely on expert institutions and trust; laypeople can’t independently verify most claims.
• There is concern that “freedom” is often confused with freedom from consequences (e.g., job loss, school exclusion, travel limits).

Vaccines, Risk, and Mandates

• One side stresses that vaccines greatly reduced Covid deaths, that disease risk far outweighs vaccine risk, and that limiting exposure to unvaccinated people is a legitimate societal interest.
• Another side points to documented vaccine side effects, specific death cases, and lack of strong transmission-blocking, questioning the justification for mandates if spread isn’t fully prevented.
• Some argue that overstated or false official claims (“zero risk,” full transmission prevention) and censorship erode trust and fuel skepticism.

Liability and Criminalization of Scientific Fraud

• Many support treating willful data fabrication that leads to deaths as akin to manslaughter or fraud, warranting criminal penalties.
• Others warn that liability will chill honest research, is hard to adjudicate (distinguishing fraud vs. error), and could shift blame away from guideline-setters and clinicians.
• Debate over whether responsibility lies more with fraudulent researchers or with institutions that embed fragile, single-study results into guidelines.

Systemic Problems: Replication, Incentives, and Quality

• Widespread concerns about poor statistics, p‑hacking, weak standards in some medical, psychological, and social sciences; physics is seen by some as more rigorous.
• Replication is underfunded, unrewarded, and often absent; citation chains progressively oversimplify nuanced results.
• Suggestions: mandatory replication funding quotas, required citation of replication outcomes, better stats education, detailed record‑keeping with audits, and possibly financial bonding for published results (though many see bonding as costly and exclusionary).

Case-Specific Issues: Beta Blockers and Guidelines

• Commenters note that the huge “death toll” estimate rests on guideline adoption of flawed studies and possibly on a few dominant trials, some themselves partly tainted by fraud.
• Others emphasize that “not acting” is also a choice: clinicians must decide under uncertainty, and trusting the best available (even imperfect) evidence may still minimize harm overall.

Blocklist characteristics

• List covers ~104 “main domains”; commenters expected more given secrecy and lack of court orders.
• Blocking is at DNS level (NXDOMAIN / misdirected responses), not IP blackholing.
• Domains are largely sports, movie, and game sharing/streaming; Sci‑Hub is included, LibGen generally not mentioned as blocked.
• Some frequent pirate/torrent sites used by commenters are notably absent, leading to speculation about selection criteria and enforcement priorities.

Circumvention techniques

• DNS-based blocking is trivially bypassed with third‑party resolvers (e.g., 8.8.8.8), VPNs, or Tor.
• ISPs can interfere by forcing their own DNS (e.g., blocking port 53 or hardwiring DNS in rented routers), but:
  • Users can often use their own routers; in Germany, that right is legally protected.
  • DNS-over-HTTPS/TLS (e.g., Firefox DoH, NextDNS, Cloudflare, DNSCrypt‑proxy) works around port‑53 blocking since it looks like normal HTTPS on 443.
• More advanced approaches include custom routers (OpenWrt, OPNsense), local DNS proxies, Tailscale exit nodes, VPS/seedboxes, and residential-proxy-like setups.
• Some note tradeoffs: VPN/seedbox IPs are increasingly blocked by streaming services; residential exit nodes avoid this.

Who is actually blocked

• View that DNS blocking is a “hard stop” for the vast majority of users with low technical skills.
• Counterview: anyone motivated to pirate can quickly find workarounds or ask a friend; in poorer or more heavily censored countries, such skills are common.
• Consensus: blocks mostly stop “normies” and casual access (e.g., to Sci‑Hub), not determined users.

German copyright enforcement context

• Commenters say torrent users in Germany risk expensive settlement letters (hundreds of euros per movie), based on rights-holders joining swarms and logging IPs.
• Debate over whether the legal hook is “commercial distribution” vs simple copyright infringement, but several report paying substantial settlements.
• Result: many in Germany avoid torrents and use streaming/direct-download or Usenet, often behind VPNs.

Legality, transparency, and scope creep

• Strong concern that a private “clearing” body plus ISP DNS blocking, without court orders, amounts to privatized censorship and weak democratic oversight.
• Austria is cited as a contrast where blocklists and legal bases are published.
• Some argue DNS blocking is chosen precisely because it’s symbolic and easy to bypass, yet normalizes censorship infrastructure that could later expand (e.g., to “misinformation”).
• Others see a Streisand effect: secrecy failed and the published list now serves as a discovery index for piracy.

Capitalism, incentives, and safety

• Many argue the root cause is “dumb”/short‑term capitalism: profit and cost‑cutting prioritized over engineering quality and safety.
• Debate over shareholder responsibility: some blame shareholders and the financial system; others note most shareholders have little direct control and blame executives’ short‑term incentives (pay packages, stock price focus).
• Non‑voting shares and “quality‑first” companies are discussed as possible but rare alternatives.

Responsibility for the 737 MAX failures

• Several commenters stress that management decisions, not individual $9/hr developers, killed hundreds of passengers.
• Others say engineers share some responsibility, especially senior ones, for not challenging unsafe requirements, while still emphasizing systemic QA and process failures.

Outsourcing, $9/hr rates, and quality

• Strong skepticism that low‑cost outsourcing saves money in complex, safety‑critical domains; cited downsides: lower quality, accumulated bugs, reputation damage, and misaligned incentives.
• Some note $9/hr can be a good local wage; what’s “shameful” is using very cheap labor for high‑stakes work, not the absolute number.
• Others argue pay is mostly driven by supply/demand; moral judgments about “shameful” pay are contested.

Professionalization and certification

• Multiple comments support professional licensing or certification for safety‑critical software (aviation, space, finance), distinct from casual or low‑risk software.
• Concern that broad “software professionalism” would be overreach; focus should be on high‑impact domains.

MCAS, design vs implementation

• Several say MCAS issues stemmed from system design and requirements (single AOA sensor, optional safety indicators, inadequate training) rather than coding bugs.
• One commenter notes an article stating MCAS itself was not outsourced; the $9/hr engineers reportedly worked on display and test software, making the outsourcing–crash link unclear.
• Others emphasize the deeper cultural shift at the company from “engineering firm” to “run like a business,” with cost and schedule overriding safety.

Offshoring, culture, and communication

• Discussion of offshoring economics: quality engineers in Eastern Europe/India are not as cheap as many assume; top talent is mobile and may not join “cost‑center” roles.
• Cultural and communication gaps, time zones, and lack of domain knowledge are cited as major risks; “the hard part is communication, not typing code.”
• Some responses push back, arguing that even if offshore teams operate at lower effectiveness, the cost savings can still be attractive, though this may not hold in safety‑critical contexts.

Purpose and Design of Ruroco

• Presented as an improved, cryptographically protected alternative to naive port knocking.
• Client sends a single UDP packet containing encrypted data (time, command, random bytes).
• Server maps authenticated commands to preconfigured actions (e.g., open/close ports, toggle services), not just SSH.
• Author emphasizes convenience for personal, infrequent access and use from restrictive networks (e.g., only 80/443 or DNS 53 allowed).

Cryptography and Key Usage

• Uses RSA; client “encrypts with private key,” server “decrypts with public key.”
• Multiple commenters note this is conceptually “signing” rather than traditional public-key encryption, and discuss hybrid encryption vs signing.
• Some confusion in the docs about terminology (encrypt vs sign) is flagged as potentially misleading.

Replay Attacks and Threat Model

• Encrypted payload includes a high‑resolution deadline; server adds that deadline to a blocklist after first use.
• This makes exact packet replays ineffective: any second packet with the same deadline is rejected, regardless of time.
• However, interception-and-modification attacks are a concern: thread points out that an attacker could replay with a different source IP to whitelist themselves.
• Including source IP in payload is suggested, but NAT and shared networks complicate this; overall protection against on‑path attackers remains limited.
• Author acknowledges some attacks aren’t currently prevented and plans improvements.

Relation to Port Knocking, SPA, and Similar Tools

• Compared with classic port knocking, Single Packet Authorization (e.g., fwknop), Ostiary, and Moxie’s knockknock.
• Distinctive aspects: single UDP packet, arbitrary server-side commands, time-based one‑time use.
• Others note older tools already handle replay protection and use simpler or more formally discussed crypto.

Security Value vs Obfuscation

• Several comments frame it as primarily hiding services and reducing SSH log noise, not replacing SSH hardening.
• Debate over whether this is “security through obscurity” vs legitimate attack-surface reduction.
• Running an extra daemon increases attack surface; reading firewall logs (no open port/sniffer) is cited as safer but less flexible.

Alternatives: VPNs and Zero‑Trust

• Many suggest WireGuard, Tailscale SSH, or “no inbound ports”/overlay networks (e.g., zssh) as more robust for sensitive or multi-user environments.
• Counterpoints: VPNs add operational complexity, may be overkill for a single personal server, and don’t help when the goal is temporarily exposing HTTP to a local network without configuring clients.

Traceroute capabilities and “sorcery”

• Several comments highlight that traceroute/tracert can reveal much more than basic internal routing.
• With good DNS naming and public maps (datacenters, undersea cables, nuclear plants, shipment records), people suggest you can infer physical locations of routers, data centers, energy sources, and AI infrastructure.
• There is interest in advanced traceroute talks (including “weaponized” techniques), but some are hard to locate.

Protocol details and correctness of explanations

• Multiple replies criticize the article’s technical accuracy and diagrams (e.g., odd IP layout, missing subnets, confusing use of loopbacks vs link IPs).
• Debate over traceroute’s packet types: classic Unix traceroute often uses UDP, Windows tracert uses ICMP, and modern implementations support multiple protocols.
• Some note that application traffic rarely uses ICMP, so relying on ICMP-only tests can mislead troubleshooting.

Limitations of traceroute

• Emphasis that traceroute shows where TTL-expired packets elicited ICMP messages, not a guaranteed exact path. Each probe may traverse different routes (ECMP, asymmetric routing).
• Many routers and firewalls drop or deprioritize ICMP, leading to * * * even when connectivity is fine.
• Traceroute does not expose devices below IP (optical amplifiers, DWDM, physical loops) or within encapsulations (MPLS, segment routing, VPNs), so large segments may appear as a single hop.
• Disabling ping only blocks ICMP echo; full ICMP blocking can break networks, yet many organizations still do it for “security.”

Use in operations and better tools

• Network operators report they do care about traceroute anomalies and sometimes adjust routing or complain to vendors.
• Others say consumer ISPs often ignore low-level traceroute-based complaints.
• mtr and more sophisticated tools (e.g., UDP/port-variation techniques, Trippy) are favored for diagnosing ECMP issues and intermittent loss.

Networking knowledge and education

• Strong sentiment that many developers and even senior engineers lack basic networking and DNS understanding.
• Some defend simple traceroute explainers as useful for teaching, while others argue that literature and better talks already exist.
• Several recommend learning beyond the OSI model, including real-world behaviors like GeoDNS, anycast, BGP, and path MTU.

How UK postcodes and PAF work

• UK postcodes are very fine-grained: often 1–15 buildings, sometimes part of a building.
• PAF (Postcode Address File) links postcodes to full delivery points and is maintained by Royal Mail’s constant on-the-ground operations.
• CodePoint Open already provides postcode→coordinates, but not full address lists, which is what many commercial “type your postcode, pick address” services rely on.

---

Arguments for opening PAF

• Many argue address data (without names) is low-risk public infrastructure akin to maps or weather data and should be open like in several EU countries.
• Open address data would lower barriers for e‑commerce, logistics, and public services and reduce duplicated, error‑prone private datasets.
• Some note the profit from selling PAF is relatively small compared to its systemic value.

---

Privacy and abuse concerns

• Several commenters see little abuse potential beyond postal spam, which is already common.
• Others want high barriers to discourage misuse and note risks arise when address data is linked with other datasets, not from the address file alone.
• Consensus in the thread leans toward “privacy risk is minimal compared to the benefits.”

---

International comparisons

• Examples of open or semi-open address systems: France (BAN), Netherlands, Belgium, Czech Republic, Switzerland, parts of Australia (G‑NAF), and detailed datasets in the US and Germany (with different granularity).
• Contrasts: proprietary or licensed systems in UK (PAF), Ireland (Eircode), Australia Post, Canada Post.
• Many highlight that other countries with strong privacy regimes manage open address data successfully.

---

Data quality and real‑world messiness

• Multiple anecdotes show how physical reality defies neat models: multiple buildings or stairwells sharing a number, no unit numbers, overlapping postcodes, entire campuses under one code.
• Commenters stress that “accurate address database” is intrinsically hard; the map is never the territory.

---

Ownership, law, and privatisation

• Strong criticism that PAF was included when Royal Mail was privatised; seen as a “public jewel” sold off.
• Legal debate: UK Parliament can legislate to free PAF, but compensation, treaty obligations, database rights, and precedent for future privatisations complicate this.
• Some suggest nationalisation or buying back PAF; others propose legal changes to database copyright.

---

Recreation and alternatives

• Proposals: rebuild from Ordnance Survey, National Address Gazetteer, OpenStreetMap, crowdsourcing, or big private map providers.
• Skepticism: without Royal Mail’s daily delivery updates, matching PAF’s accuracy and freshness is hard and expensive.
• Alternatives like what3words or Plus Codes are discussed; many dislike relying on another proprietary system and note technical and safety issues with w3w.

Nature of Physical Theories: Truth vs Usefulness

• Recurrent theme: all physical theories are approximations; usefulness depends on domain.
• Debate over whether Newtonian gravity is “wrong” or a very good model in a limited parameter range.
• Distinction emphasized between:
  • “Not wrong” as “predictively useful in its intended domain.”
  • “Not wrong” as “literally true about reality.”
• Some argue physical theories lie on a continuum of correctness; binary right/wrong is misleading.
• Others stress that quantum mechanics upended core assumptions of classical physics, so earlier theories can be deeply false yet still practical.

Quantum Mechanics, Measurement, and Bell’s Theorem

• Some posters downplay “measurement problem” as a philosophical confusion about extending models beyond what is measurable.
• Strong counter-argument: Bell’s theorem and its experimental violations constrain what “true reality” can be; they are not “just math.”
• Debate over what “proof” means in physics vs mathematics; experimental verification is always tentative, unlike formal proof.

What Is Real? Particles, Fields, and Emergence

• Disagreement over whether leptons/fields are “real” or just successful concepts.
• View that particles are excitations of quantum fields; fields might be the deeper ontology—but this too is questioned as possibly just a convenient language.
• Discussion of effective field theory and emergence: macroscopic physics can be largely independent of microscopic details.

Human Cognition, Explanations, and Models

• Several comments stress humans are optimized for “hominid-scale” reasoning, not quantum/relativistic intuition.
• Idea that good explanations are those that compress data and predict well (real patterns, Kolmogorov complexity).
• Emphasis that theories are metaphors for reality, filtered by our perceptual and cognitive limits.

Free Will and Consciousness

• Long subthread arguing whether eureka moments and subconscious processes undermine free will.
• Positions range from hard determinism (“no free will at all”) to compatibilism (“will exists but is not metaphysically ‘free’”).
• Meta-point: our understanding of mind is far less developed than our understanding of fundamental physics.

Role and Practice of Physics

• Some see physics primarily as understanding reality; others emphasize practical benefits (technology, improved life).
• Industrial and ex-physicists note that most working physicists bracket deep ontology questions and focus on solvable problems.
• Mixed views on future breakthroughs: some pessimistic about new “Standard Model–level” advances; others point to current cosmology, quantum, and condensed-matter as highly fertile.

Study design and interpretation

• Some argue the headline (“increases visceral adipose tissue metabolic activity”) overreaches the data.
• The trial was small (30 people with obesity + obstructive sleep apnea) and not designed to isolate GLP‑1’s metabolic effects from caloric restriction.
• Several commenters note we can’t yet distinguish “GLP‑1-specific VAT activation” from “VAT changes that occur with any sustained calorie deficit.”

Visceral fat importance and measurement

• Visceral fat (VAT) is described as metabolically dangerous, strongly linked to insulin resistance and type 2 diabetes, and not always visible in body shape.
• Some argue VAT is physiologically necessary in modest amounts and only harmful in excess.
• Practical measurement suggestions: waist circumference, waist‑to‑hip or waist‑to‑height ratio, and DEXA (DXA) scans.

Mechanisms and metabolic effects

• GLP‑1 agonists (Ozempic/Wegovy and related drugs) reduce appetite, delay gastric emptying, and may slightly increase resting heart rate and basal metabolic rate.
• One view: the VAT changes are a trivial consequence of losing stored triglycerides.
• Another view: if GLP‑1s truly preferentially increase VAT activity, they would offer health gains beyond generic weight loss.

Safety, side effects, and “Ozempic face”

• The drug class is described as well‑researched (decades in diabetes), with known risks like pancreatitis and possible thyroid cancer, but considered worth it for many with obesity/diabetes.
• Weight‑loss formulation (Wegovy) is FDA‑approved; also allowed for pilots, suggesting a relatively clean safety profile.
• Reported side effects include dry skin, vivid dreams, and cosmetic facial changes. Some say “Ozempic face” is just rapid total fat loss; others suspect skin elasticity or buccal fat changes.

Weight regain and long‑term use

• Some claim patients must stay on GLP‑1s indefinitely; others cite data and anecdotes that many keep part of the weight off after tapering, especially with a gradual wean.
• There is concern about tolerance, rebound hunger, long‑term cancer risk, and unknowns over decades.

Root causes, ethics, and environment

• One camp stresses that GLP‑1s treat symptoms, not root causes like ultra‑processed food, sugar, sedentary, car‑centric environments, and marketing.
• Others counter that:
  • Long‑term lifestyle change succeeds for only a small minority.
  • Obesity involves complex hormonal and regulatory systems; for many, diet and exercise alone are not enough without disordered behavior.
  • Drugs can be a bridge to better habits and higher quality of life.
• Broader proposals include banning “junk food,” redesigning cities for walking/biking, and treating refined sugar more like an addictive drug.

Broader potential of GLP‑1 RAs

• Commenters note wide‑ranging effects: possible targeting of visceral fat, reduced cravings (including for alcohol), potential benefits in Alzheimer’s and other conditions (research early).
• Some are excited by the breadth of benefits; others are wary that it seems “too good,” and actively look for underreported adverse effects.

Overview of the Hacker Purity Test (1989)

• Seen mostly as a historical artifact rather than a serious metric of “hackerness.”
• Originates as a parody of earlier “Purity Tests” (social/sexual questionnaires), replacing wild acts with ultra-nerdy activities.
• Many entries are in-jokes; intended for humor and self-mockery, not formal gatekeeping.

Generational Gap and Relevance Today

• Several commenters note that anyone born after the late 70s or early 80s will score “unfairly” low because the hardware, OSes, and practices referenced were already obsolete by the time they started.
• Some frame it as ideal for people who were in university or industry around the late 70s–80s, not for later generations.
• Multiple people suggest an updated test covering 90s–2000s hacker milestones (Linux distros, device drivers, modem and cable hacks, stack smashing, etc.).

Hacker Culture: Nostalgia vs Critique

• Some express nostalgia for old hacker culture: irreverence, deep technical tinkering, elaborate in-jokes (e.g., BOFH, Geek Code).
• Others are turned off by the status games and “chest beating” over obscure knowledge; recall real people who took this attitude seriously.
• Debate over whether hacker culture has “died” or just changed shape into more corporate, regulated, and social-media-driven forms.

Specific Questions and Anecdotes

• People reminisce about: toggling in boot code on front panels, punch cards and lace cards, IPLing mainframes from tape, writing viruses, self-modifying code, telephony “blue box” style tone generation, and obscure hardware hacks.
• Several mention delight at personality and lifestyle questions that now seem mainstream: using a computer more than 8 hours straight, logging in before breakfast, online blind dates, terabytes of storage.
• Some hardware and low-level anecdotes highlight ongoing relevance of certain “ancient” skills (e.g., NMIs, manual bootstrapping, physical hacks to fix timing).

Tools, Mirrors, and Related Artifacts

• The original scoring form is partially broken; working versions exist via archive links, Debian’s purity / purity-off packages, and a GitHub mirror.
• Thread also recalls “Geek Code” signatures and other 90s net-culture questionnaires as similar cultural artifacts.