Hacker News, Distilled

Regulation and “red tape”

• Many comments argue that most securities regulations exist because of past abuses (“written in blood”); reducing them likely increases investor risk.
• Others note “red tape” can also be genuinely excessive or misdesigned, and that starting from a cleaner slate might improve efficiency if done thoughtfully.
• Several point out that, regardless of TXSE rules, federal SEC law still applies; exchange-level deregulation has limits.

Listing quality and investor risk

• A dominant worry: an exchange marketed on “fewer rules” may become a “market for lemons,” attracting firms too weak or sketchy for NYSE/Nasdaq or relegated to OTC/pink sheets.
• Some contrast this with Canada’s venture exchanges that at least serve a clear economic niche (e.g., speculative junior drillers).
• Others counter that not every company seeking lighter requirements is low quality and that NYSE/Nasdaq themselves host dubious listings.

Ideology, culture war, and DEI

• Multiple comments see TXSE as an ideological project: a home for “anti‑woke” or culture‑war companies (e.g., Truth Social–like firms) and investors hostile to ESG/DEI.
• Nasdaq’s board diversity rule and DEI materials are cited as catalysts; TXSE is expected not to adopt similar requirements.
• Some welcome an exchange “less politicized” in this sense; others see this as dismantling useful guardrails under a partisan banner.

Comparisons: other exchanges, SPACs, crypto

• Commenters note there are already many U.S. exchanges and specialized venues; the main differentiator is listing standards, not where shares trade.
• The LTSE is mentioned as a prior “CEO‑friendly” innovation exchange with minimal traction.
• SPACs and crypto are repeatedly used as cautionary analogies: light regulation invited fraud, pump‑and‑dumps, and retail losses until reality caught up.

Texas context: economy, grid, secession

• Some see this as another step in Texas’s broader low‑regulation, pro‑business strategy, noting its large corporate base, strong GDP, and comparatively low electricity prices.
• Others counter with Texas’s grid failures and climate vulnerability as examples of how deregulation and under‑regulated markets can backfire.
• A side thread debates Texas secession; opinions range from “viable and desirable” to “politically and militarily unrealistic.”

Open questions

• Unclear which specific NYSE/Nasdaq listing rules TXSE will relax and whether major firms will actually list or switch, beyond ideological signaling.
• Unclear whether TXSE becomes a serious competitor or a niche outlet for speculative or politically motivated listings.

Detectability of warp signatures & Fermi context

• Several comments note that we will likely be able to detect warp-like phenomena long before we can build them, analogous to early radio astronomy vs radio transmitters.
• Others argue this doesn’t obviously solve the Fermi paradox: even if warp traffic is common, our position in a galactic spiral arm and the low probability of random routes crossing near the Solar System make detection uncertain.
• A “dark forest” framing is raised: detectable warp use might be strategically avoided; detecting such signatures would partially falsify that hypothesis.

Energy, distance, and gravitational-wave behavior

• Multiple comments discuss that warp-drive–like gravitational signals would fall off with distance, limiting detectability unless the energies are enormous.
• There is debate and correction over scaling laws: energy goes as 1/r², but gravitational-wave strain amplitude as ~1/r.
• Implication: only very energetic or relatively nearby events would be observable, especially with current detector sensitivity bands.

Audibility and local effects of gravitational waves

• A long subthread explores whether gravitational waves could “wiggle” eardrums and be audible.
• Back-of-the-envelope calculations (later partially corrected) suggest a binary black-hole merger might be audible roughly at Earth–Moon distance, but lethal at that range.
• Participants debate whether differential motion between bone and soft tissue creates pressure differences vs everything moving together in curved spacetime; details remain somewhat unclear.
• Frequency content can fall into the human audible range (~hundreds of Hz), making “hearing” such events conceptually possible in principle.

Technosignatures, advanced life, and behavior

• The paper is likened to Dyson-sphere technosignatures: modeling signals from speculative tech to guide searches.
• Some argue there’s no particular reason to expect life elsewhere, or that it would be technologically advanced; others note that at least one of “life common” or “life rare” must be mundane, once known.
• Competing views on civilization behavior:
  • One side: evolution favors expansionist species; non-expansionist ones get outcompeted.
  • Another side: advanced societies might become non-expansionist; infinite growth is neither natural nor necessary, and selection pressure for expansion could vanish.

Sci-fi, culture, and meta-discussion

• Many comments enjoy the Star Trek nods (Prime Directive, acknowledgments, “cute” tagline) and joke that now sci-fi “whooshes in space” could be gravitational.
• Some highlight that paying people to simulate exotic spacetimes is delightful.
• A substantial tangent critiques StackExchange moderation, duplicate-closing behavior, and outdated answers, comparing it to interacting with LLMs; some prefer LLMs’ patience despite their unreliability.
• One resource for learning numerical relativity (NRPy) is mentioned for those wanting to simulate such spacetimes.

Scope of Israel’s Online Influence Campaign

• Article describes Israeli-run fake social accounts targeting US lawmakers and US audiences; many commenters say this is unsurprising and fits modern information warfare.
• Some see it as part of a broader, organized “hasbara” ecosystem (AIPAC, public diplomacy units, previous social media efforts); others stress that many states, including allies, run influence operations.

Effectiveness and Targets

• Several argue such bot campaigns are likely ineffective on members of Congress, who delegate social media and respond more to lobbying, calls, and donations.
• Others counter that the true targets are:
  • Staffers, consultants, and pollsters.
  • “Low-information” voters who shape the climate around lawmakers.
  • Social media platforms where volume can manufacture apparent consensus.
• There is disagreement on whether current Israeli propaganda is sophisticated or “obvious and clumsy.”

Comparisons to Other Countries

• Many draw parallels to Russian, Chinese, Iranian, Qatari, and British WWII propaganda.
• Some say US interference abroad dwarfs others, and that “everyone does it”; others respond that doing it to your top ally’s lawmakers (while receiving large US aid) is different in kind.

Lobbying, Dual Loyalty, and Antisemitism

• A large subthread debates:
  • AIPAC’s outsized role in US primaries and donations.
  • Whether any US lawmakers are dual US–Israeli citizens (several say current evidence points to none).
  • Israel’s Law of Return vs. actual citizenship.
• Some see criticism of AIPAC and “dual citizens” as veering into antisemitic “dual loyalty” tropes; others insist the core issue is foreign influence, not Jewish identity.

Broader Propaganda & Information-Warfare Context

• Commenters link this to:
  • Cyber commands and “fifth-generation warfare.”
  • Historical media manipulation (Manufacturing Consent, Iraq War coverage, Bernays/PR).
  • The ease, scale, and low cost of social media propaganda vs. earlier eras.
• Several stress that propaganda often leverages existing strong opinions rather than changing minds from scratch.

HN Moderation & Meta

• Multiple comments note Israel/Gaza threads getting rapidly flagged.
• A moderator explains that:
  • Political stories, especially on this conflict, are frequently flagged by users.
  • Mods selectively unflag some when there’s significant new information and potential for substantive discussion, to keep HN from being overwhelmed by politics.

Overall user reaction

• Many commenters are upset; Timeline on web was heavily used for:
  • Remembering places from trips and past years.
  • Reconstructing purchases, holidays, and work-related mileage/tax logs.
  • Browsing life history on a large screen instead of a phone.
• Some say this is the first Google “kill” that personally hurts them.
• A minority welcome the change if it truly means less server-side storage.

---

Privacy, “on-device” model, and data retention

• Google frames the shift as “more private, on-device, per-device.”
• Skeptics argue:
  • Google still harvests/infer location for ads, Photos, etc., so privacy gain is limited.
  • It may be “privacy from the user” (less visibility/export) rather than from Google.
• Supporters counter:
  • If precise, unified location history is no longer stored in the cloud, that’s a real improvement.
  • Location is particularly sensitive; keeping exhaustive server-side logs is risky.
• It remains unclear whether Google will truly stop retaining equivalent location data in other backends.

---

Law enforcement, liability, and regulation

• Several comments suggest a key driver is avoiding:
  • Geofence warrants and bulk law-enforcement requests.
  • Long-term liability of holding years of detailed location trails.
• Others note the article doesn’t clearly guarantee deletion, only the end of web access.
• Some discuss GDPR/right-to-be-forgotten tensions, but legal applicability and enforcement are viewed as uncertain.

---

Data export, migration, and lock-in

• Users rush to Google Takeout; some report:
  • Raw Location History exports (e.g., GPX) have been restricted for about a year.
  • Current exports may be JSON with limited format choices.
• Concern that:
  • Historical data may become effectively unexportable.
  • Device-bound histories complicate switching phones, platforms, or using multiple devices.
• One commenter reports the new on-device Timeline offers JSON export, but others note older data is hard/impossible to fully retrieve.

---

Alternatives and self-hosted options

• Suggested replacements include OwnTracks, Traccar, uLogger, and custom GPS logging setups, often self-hosted.
• Users note tradeoffs:
  • Higher battery usage, lower resolution, or weaker semantic “place snapping” compared to Google.
  • Complexity of running servers, app-store hurdles, and device power-management issues.

---

Why Google kills features

• Theories include:
  • Cost cutting, degrowth, and infrastructure churn making understaffed features hard to maintain.
  • Privacy/liability concerns outweighing value of the feature.
  • Strategic refocus away from non-core, low-revenue offerings.

Production-ready Lisps & Real-world Use

• Common Lisp, Clojure, ClojureScript, Racket, Scheme, LFE, Janet, Emacs Lisp, and various custom dialects are reported in production.
• Use cases mentioned: blockchain/smart-contract-like systems, financial streaming/realtime analytics, algorithmic trading, web publishing, tunnels and transport control, airline booking, aerospace, cybersecurity, and other backend services.
• Some shops report tiny teams in CL delivering output that makes them look much larger to clients.

Productivity: REPL, Image-based Dev, Macros

• Many argue Lisp’s REPL + image-based workflow is still a unique advantage: live modification of running systems, redefining functions without restart, tracing and debugging with resumable stack frames.
• Comparisons say Python/Jupyter REPLs feel more like shells; Clojure/CL REPLs integrate tightly with editors and entire codebases.
• Macros and homoiconicity are seen as key: easy DSLs, code generation, graph/DAG builders, autodiff, numeric DSLs; Julia is cited as a “lispy” example where macros saved thousands of LOC.
• Others warn macros and heavy metaprogramming can hurt readability if overused; some style guides advise restraint.

Types, Structure, and Maintenance

• Pro-static-typing voices stress that types and rigid structure help large teams, long-lived code, and onboarding; dynamic Lisps can feel like “unlabeled tubes” that require runtime probing.
• Counterpoints: CL has optional but powerful types; Typed Racket, Coalton, and Clojure’s Spec/Malli add advanced constraints; REPL debugging can be faster than chasing static types.
• Several note that design quality and developer skill dominate language choice for maintainability.

Ecosystem, Tooling, and Hiring

• A recurring criticism: CL’s library ecosystem is thinner, less standardized, and less documented than Python/Java, which hurt past deployments (e.g., web rewrites).
• Others say in regulated or niche domains, external libraries rarely fit well anyway, so writing your own in Lisp is fine.
• Tooling debates: Emacs is loved by some and viewed as clunky by others; alternative integrations exist for VSCode, JetBrains, Vim/Neovim, etc.
• Hiring is harder; Lisp tends to attract experienced, niche developers, which can be a strength (high ROI per hire) but limits team scaling.

“Beating the Averages” and When to Use Lisp

• Supporters say Lisp still “beats the averages” for:
  • Greenfield, exploratory, and rapidly changing specs.
  • Complex domains where DSLs and live refactoring matter.
  • Small, high-skill teams optimizing feedback loops.
• Skeptics argue:
  • Many Lisp ideas (GC, first-class functions, FP, REPLs) are now common elsewhere, reducing its relative advantage.
  • Popular software and big organizations mostly use other languages; ecosystems and hiring often outweigh language power.
• Several commenters conclude there’s no single “top of the power curve”: pick the language (or DSL in Lisp) that best fits your specific problem and constraints.

RealPage and Alleged “Collusion-as-a-Service”

• RealPage is described as rent‑setting/property‑management software that ingests market data (rents, vacancies, time on market) and returns recommended prices.
• Several commenters argue it effectively coordinates large landlords: many in a city use the same tool and agree not to undercut its algorithmic price; there is mention of a “policing agent” that ejects clients who don’t follow it.
• Critics see this as algorithm‑mediated price fixing: a cartel with one level of indirection and “data‑washing” of collusion.
• Others say it just helps landlords find “what the market will bear” and may only add a small (1–2%) uplift.

Supply, Demand, and Market Power

• One camp: rents are fundamentally driven by supply and demand; you can’t charge Los Angeles prices in Atlanta regardless of software.
• Counterpoint: in markets where RealPage clients control most rentals (Atlanta cited, ~80% coverage), the market becomes oligopolistic and prices are no longer set by competitive forces.
• Discussion dives into microeconomics: monopolies/oligopolies still face demand curves but can move price toward profit-maximizing levels, creating deadweight loss.

Is There a Housing Shortage?

• Many assert the core problem is insufficient construction, blocked by restrictive zoning and NIMBY politics; places that build more see rents soften.
• Others dispute a true shortage, claiming total housing roughly matches households and blaming demand shocks (money printing, higher incomes) or units held vacant.
• There is disagreement over how common deliberate vacancies are versus financially unsustainable for most landlords.

Inelastic Demand and Tenant Leverage

• Housing is framed as highly inelastic: people “must” rent when their lease ends and cannot stockpile or easily delay.
• This weakens classic supply‑demand discipline and amplifies the harm of any cartel‑like behavior.
• Some report rapid intra‑week rent swings (10%) attributed to pricing software.

Legal and Policy Views

• Multiple commenters characterize RealPage-enabled coordination as a textbook antitrust/Sherman Act issue: illegal even if it only modestly raises prices or is economically clumsy.
• Others stress that even if RealPage is punished, broader fixes require:
  • Loosening zoning and embracing YIMBY policies.
  • Addressing financialization (housing as an investment asset).
  • Better alignment of immigration/population growth with housing and infrastructure capacity (contested point).

Natural vs. Surrogate Primary Keys

• Many argue you “almost always” want an internal, synthetic primary key (int or UUID) and treat natural identifiers as regular columns with unique constraints.
• Recurrent theme: every “obviously stable” natural key eventually changes or is reused (emails, usernames, SSNs, government IDs, license plates, VINs, gamer tags, phone numbers, addresses, etc.).
• Opposing view: natural keys are essential for modelling real‑world identity and forcing you to think about what really makes an entity unique; surrogate keys don’t save you from messy external reality.

External IDs and Evolving Reality

• Multiple horror stories: systems using external IDs (SSN, national IDs, stock codes, journal ISSNs, Discord usernames, PSN/Steam logins, phone numbers) as PKs, later broken by policy changes, duplicates, format changes, gender changes, or recycled numbers.
• Strong advice from many: never use IDs you don’t control as your primary key; treat them as data + unique indexes and keep a stable internal ID.

Practical Schema Design Patterns

• Common compromise: synthetic PK + natural “business key” enforced via UNIQUE, possibly composite.
• Natural keys often work fine as alternate keys and for human‑facing lookups, but not as PKs that propagate everywhere via foreign keys.
• Some note you can refer to alternate unique keys in foreign keys (not just PKs), though ORMs often push toward a single synthetic PK.

Performance and UUID Debates

• Pro‑surrogate camp highlights:
  • Smaller, fixed‑size integer PKs make indexes and joins cheaper.
  • Sequential or k‑sortable keys (auto‑increment, UUIDv7, Snowflake‑style) avoid B‑tree fragmentation; pure UUIDv4 can hurt at scale.
• Some like dual IDs: internal int PK + public UUID or short random string (Stripe‑style), to prevent enumeration and “German tank problem” info leakage.

Security, Privacy, and PII

• Natural keys that contain PII (emails, SSNs, national IDs) “infect” every referencing table; complicates compliance (HIPAA/GDPR).
• Debate over whether surrogate IDs themselves count as PII; some standards treat any linkable identifier as sensitive, others carve out internal codes as non‑PHI.

Distributed Systems and Integration

• In SOA/microservices, data warehouses, job queues, caches, and external integrations, changing a PK becomes extremely painful.
• Partitioned systems may need natural‑ish keys for dedup across partitions, but most still recommend an internal surrogate plus natural uniqueness where needed.

Overall Takeaways

• Broad (but not unanimous) consensus:
  • Use surrogate PKs under your control.
  • Enforce real‑world uniqueness with natural keys via constraints.
  • Expect natural identifiers to change; design so that change has minimal blast radius.

Scope of Google’s Contribution

• Many readers initially assume this is a 3D container packing problem; others point out the API targets higher-level network design: port visit order, schedules, and container routing.
• Some note time can be treated as an extra “dimension,” making routing/scheduling itself a bin-packing–like optimization.
• Google’s work is seen as an incremental improvement using established OR ideas (shortest paths, LP/MIP, heuristics), not a wholly new methodology.

Complexity of Real-World Container Operations

• Physical stowage is highlighted as a separate, very hard problem: weight and stability, reefer power access, hazardous-goods separation, unloading order, and multiple cranes working in parallel.
• Ports/terminals add their own constraints: different local practices, union rules, regulations, berth and crane availability, and safety requirements.
• Several practitioners stress that capturing all constraints and edge cases is harder than the math itself.

Adoption Challenges and Industry Culture

• Strong skepticism about using a research API in production: no SLAs, Google’s deprecation history, and the risk of lock-in.
• Terminal-side voices describe fragmented, low-quality software, heavy reliance on spreadsheets and phone calls, and very heterogeneous operations even within the same company.
• Private equity involvement is described as pushing modernization, but also increasing political friction and fear of automation among workers.

Optimization vs. Reality

• Debate over difficulty: some see “just combinatorial optimization” and approximations as tractable; others emphasize enormous state spaces and constantly changing constraints.
• There is interest in combinatorial optimization, constraint programming (CP-SAT), and metaheuristics (Markov chains, ant colony), with disagreement over how competitive OR-Tools is versus specialized solvers like Gurobi or LKH.
• Multiple comments stress that robust, explainable, “good enough” plans that handle disruptions and human constraints are often more valuable than provably optimal ones.

Related Domains and Tools

• Similar scheduling/optimization issues are discussed in restaurants, healthcare, manufacturing, and transportation.
• Accessibility is a recurring theme: modeling tools and OR concepts remain too technical for many real-world users, who default to Excel and manual tweaks.

Access to the Study and Data Sources

• Commenters share direct links to the JAMA paper and to a ResearchGate copy, noting the article does not list the specific 28 physicians analyzed.
• The U.S. Open Payments database is highlighted as a key tool for checking financial ties between physicians and industry.
• Example searches show some prominent media doctors receiving six‑figure consulting payments, while others have only small “food and beverage” entries.

Magnitude and Nature of Payments

• Related coverage cites $12.1B in payments to U.S. doctors over 2013–2022.
• Some argue the average (~$12k/doctor/year) sounds modest; others say that much is effectively “a month’s salary,” and thus a powerful incentive.
• Clarification that free drug samples are not included; reported items range from brief paid consulting to high‑paid speaking and advisory roles.

Transparency, Disclosure, and Regulation

• Debate over whether U.S. rules adequately mirror social‑media advertising standards requiring clear, in‑context sponsorship disclosure.
• Some see Open Payments as sufficient transparency; others call it a “pretend solution” because most patients don’t know it exists or won’t check it.
• There is disagreement about what is currently illegal: some assert doctors must disclose conflicts and that prescribing under undisclosed influence is unlawful; others say enforcement is weak or unclear.
• Comparisons are made to stricter advertising rules in other countries (e.g., no direct‑to‑consumer Rx ads).

Ethical Concerns and Patient Trust

• Many argue that being paid to endorse drugs is inherently in tension with a physician’s duty of loyalty to patients, especially given information asymmetry and patient vulnerability.
• Some call for revoking licenses for undisclosed endorsements and criminal penalties for company “bribery.”
• Others accept paid roles if conflicts are clearly disclosed, both publicly and to individual patients.

Influence on Prescribing and Public Messaging

• Cited evidence and discussion agree that marketing does influence physician behavior, even when framed as “education” about new approvals.
• Direct‑to‑consumer ads are criticized for prompting patients to demand specific drugs, which some fear doctors may prescribe rather than re‑fight lifestyle battles.
• A personal anecdote describes a doctor’s office saturated with a single drug’s branding and strong pressure to stay on that drug despite serious side effects, interpreted as evidence of distorted incentives.

Broader Skepticism and Health Culture

• Several comments express broad distrust of the pharmaceutical–medical complex, calling the system “corrupt” and focused on wealth extraction.
• Others distinguish between skepticism of companies and trust in specific treatments (e.g., vaccines), noting that corruption in promotion does not automatically mean a drug is ineffective.
• A side discussion explores how culture, urban design, and diet interact with heavy reliance on pharmacologic solutions, especially around obesity, with disagreement over whether lifestyle or drugs should be emphasized.

Ownership Change & Trust Concerns

• Users report Bartender auto-updating with a new, unknown signing identity, triggering immediate distrust.
• Main concern: a popular, privileged utility (screen recording, menu access) is an ideal target for malicious takeover or “poisoned” updates.
• Many criticize the new owners’ vague, delayed communication and lack of clear identification, describing it as “shady” and tone-deaf.
• Later posts note that the buyer is now stated to be applause.dev and that the original developer published a statement, but several commenters say the reputational damage is already done and they remain worried.

User Responses & Mitigations

• Common advice:
  • Disable automatic updates in Bartender.
  • Revert to last version signed by the original developer.
  • Block network access for Bartender using tools like Little Snitch or LuLu.
• Some uninstall Bartender outright and look for alternatives, saying they’re very reluctant to trust the new owners.

Alternatives & Workarounds

• Open‑source / free menu bar managers: Hidden Bar, Ice, Dozer; several are reported as abandoned or buggy, especially with notched MacBook screens.
• BetterTouchTool can partially replicate Bartender’s icon-hiding behavior via menu-bar triggers.
• Some use system tweaks (defaults write commands) to reduce menu bar icon spacing instead of using a third-party app.
• Other unrelated but similar “should be built‑in” utilities frequently mentioned: Rectangle, AltTab, Alfred/Raycast, Mos/UnnaturalScrollWheels, window managers, mouse utilities, etc.

macOS Design, Notch, and Built‑In Support

• Strong sentiment that menu bar management should be native to macOS, especially with notched displays where icons can be hidden with no overflow indication.
• Some argue it’s a niche need; others say virtually every power user they see has a cluttered menu bar.
• Discussion that Apple gives more management options only for first‑party icons (via Control Center), reinforcing perceptions of special treatment.

Broader Security & Ecosystem Reflections

• Thread links this case to other app acquisitions that ended badly (e.g., OTP app issues) and to the general risk of relying on many third‑party utilities.
• Questions raised about the practical value of Apple’s code-signing and team IDs if users can’t easily verify who actually controls a widely‑installed app.

iPhone security, Lost Mode & Activation Lock

• Many commenters see the story as an implicit ad for Apple’s security: once a phone is passcode‑protected, put in Lost Mode, and remotely erased, thieves can’t access data or activate it without the owner’s Apple ID.
• Key point: remote erase does not remove Activation Lock; only explicitly removing the device from the iCloud account does. Several warn never to do that under pressure from scammers.
• Some confusion appears about whether devices can be cracked; consensus is that working exploits exist but are rare, expensive, and not used for random street theft.

How thieves contact the owner

• Multiple theories:
  • Phone number from a physical SIM (not applicable to eSIM‑only US iPhone 14s).
  • Contact info displayed via Lost Mode’s custom message.
  • iCloud email address revealed on the activation prompt, then used as an iMessage address.
• One commenter notes that Apple partially obfuscates the email; others think Lost Mode or emergency contact messages are the more likely leak. Overall, the exact mechanism in this case is viewed as unclear.

Value of stolen iPhones & parts pairing

• Thieves still steal iPhones despite Activation Lock, likely to strip for parts or gamble on victims being phished into removing the lock.
• Shenzhen’s Huaqiangbei market is mentioned as a major recycler / parts hub where locked phones are broken down and components reused.
• Strong debate over Apple’s parts pairing:
  • Pro: reduces resale value of stolen phones and thus theft incentives.
  • Con: functions as anti‑repair, locks out third‑party fixes, and is environmentally harmful.
  • Several propose a middle ground where legitimate owners can securely unpair / re‑pair parts or where stolen components are tracked in a database.

Law enforcement & international angle

• Repeated claims that both Chinese and US authorities largely ignore this type of cross‑border phone theft, focusing instead on regime stability or higher‑priority crimes.
• Suggestions that Apple or third‑party sites could aggregate “Find My” locations to identify US‑side fencing operations; others doubt police would act on such data.

User reactions, strategies & ethics

• Many recommend: immediately mark as lost, erase, keep device on the account, and then block all scam messages; threats are seen as copy‑pasted intimidation.
• Some discuss replying with censored Chinese political phrases to scare scammers; others doubt effectiveness and warn against provoking states.
• A side thread argues over harsh punishments as deterrence, with strong pushback that proportional, humane penalties matter more than maximal efficiency.

Debian’s /tmp-on-tmpfs and cleanup policy

• Debian is switching the default /tmp to tmpfs and enabling timed cleanup of /tmp and /var/tmp via systemd-tmpfiles.
• Some see this as overdue alignment with other distros and a net win: fewer disk writes, automatic cleanup, consistency across installs.
• Others stress it breaks long-standing expectations: /tmp as large, disk-backed scratch space; /var/tmp as “temporary but persistent across reboots,” per FHS and historical Unix practice.

Performance, RAM, SSD wear

• Proponents: RAM is fast, SSD wear is finite, and temp data is ideal to keep off SSDs. For many desktops with ample RAM, /tmp in RAM is beneficial.
• Critics: RAM is “precious,” especially on smaller/cheaper laptops and servers. Large temps in tmpfs force swapping and can destabilize systems; for big builds or ISOs, disk is faster than swap-thrashing tmpfs.
• Some argue modern filesystems and cache already keep hot /tmp data in RAM, so explicit tmpfs brings little speed benefit.

Usage patterns and breakage concerns

• Many users and tools already rely on /var/tmp or even /tmp as semi-persistent storage (long simulations, browser profiles, caches, tmux/ssh-agent sockets).
• Automatically reaping files while the system is running (based on last access time) is seen as risky; fear of partially deleted app state and subtle failures.
• Others counter that using temp dirs for important or long-lived data was always fragile; affected users should move to proper cache/data paths or site-specific dirs.

XDG directories and ~/.cache on tmpfs

• XDG base dir spec is widely discussed: half-adoption leads to cluttered $HOME and inconsistent behavior.
• Some put ~/.cache on tmpfs to save SSD wear; others say this breaks workflows that rely on persistent caches or large ML models stored there.

Swap, memory policy, and tuning

• Extensive side discussion on swap size, zswap/zram, swappiness, and early OOM killers.
• Opinions split between preferring slowdown with swap vs. aggressive killing to avoid thrashing.

Backwards compatibility, configurability, and systemd’s role

• Some argue changing long-standing semantics violates user expectations; defaults should favor compatibility, with new behavior opt-in.
• Others emphasize Debian’s configurability: /etc/fstab, masking tmp.mount, and tmpfiles.d allow reverting behavior, and admins are expected to adapt.
• There is unease about systemd owning more policy knobs (mounts, tmp handling), but also acknowledgment that its tmpfiles mechanism is powerful and central to this change.

Overall reception and use cases

• Many find the CLI useful as a quick audit step on inherited or legacy code to gauge “how much pain” to expect from secret leaks.
• Several see it as a “last line of defense” rather than primary protection; it should complement, not replace, strong secret-management and credential rotation.
• Some worry such tools could give a false sense of security, but others argue any extra layer helps given how low the baseline often is.

Comparison to existing tools

• Multiple alternatives are mentioned: tartufo, trufflehog, detect-secrets, semgrep-secrets, PyWhat, noseyparker, gitleaks, ggshield.
• Some commenters think specialized, battle-tested secret scanners outperform naive entropy-based tools, though entropy is more general.

How “high entropy” is calculated and limits

• The tool appears to estimate entropy from per-line character frequency (Shannon-style). High-entropy lines (hard to compress) often indicate random-looking tokens and secrets.
• Weak or human-like passwords and passphrases (e.g., multiple words) may evade detection since they have lower character-level entropy despite good overall security.
• Several criticize treating “entropy of a known string” as mathematically loose, suggesting what’s really approximated is Kolmogorov complexity via compressibility.
• There’s discussion of better methods: dictionaries tuned to natural language/source code, shared compression dictionaries, or statistical randomness tests.

Alternative detection strategies

• Some propose using file or repo-level compression ratios (gzip, zstd, xz) as a proxy for entropy instead of per-line character counts.
• Others suggest language-model–based approaches that flag tokens or spans that are highly “surprising” in context, which could distinguish true secrets from common constants like Base62 alphabets.

Security, distribution, and performance concerns

• Skepticism about running random precompiled binaries for a security tool; some prefer building from source or running inside containers.
• Discussion about packaging: Homebrew taps, Docker images, static Go binaries, and ignoring or handling compressed archives.

Feature ideas and limitations

• Requests for: reading .gitignore, scanning full git history, and more sophisticated strategies (e.g., complexity-based metrics).
• Acknowledgment that binary/compressed files must be ignored or specially handled, or results will be meaningless.

Clarifying the 70 Ω example

• Several commenters note the article’s last example seems numerically wrong: 33 Ω + 47 Ω = 80 Ω, not 70 Ω.
• Common view: it’s likely a typo and should be 22 Ω + 47 Ω ≈ 69 Ω.
• Others joke that 80 Ω is within common loose tolerances anyway, as are 68 Ω and 75 Ω.

---

Tolerance, statistics, and design practice

• Formal derivation: when adding resistors with the same percentage tolerance in series, the resulting percentage tolerance stays the same; absolute error adds, denominator (nominal resistance) also grows.
• Parallel combinations with identical percentage errors also retain that percentage; mixed high/low errors can partially cancel.
• Strong debate over “tolerance vs statistics”:
  • One side stresses tolerance is a worst‑case contractual bound; good engineering designs to that, not to probability.
  • Others note that random errors statistically average out (central limit theorem), so large series/parallel networks can have smaller expected relative error, though real distributions may be skewed or bimodal.
• Distinction drawn between tolerance (spec) and measurement uncertainty (instrument error).

---

Manufacturing, binning, and resistor technologies

• Discussion of resistor types: carbon film, metal film, wirewound, thin‑film, foil; choice affects accuracy, tempco, inductance, and cost.
• Some recall the idea that “5% parts are 1% parts that failed binning”; others argue this is usually uneconomic for very cheap parts and often a myth today.
• For tight tolerances and low tempco, manufacturers use different materials, geometries, and laser trimming; very high‑precision parts become extremely expensive.

---

E‑series preferred numbers and Renard numbers

• Commenters restate that E‑series values form geometric/logarithmic sequences rounded to two digits.
• The key idea praised: “tolerance overlap” — adjacent preferred values’ ±tolerance bands just touch, ensuring any target value is within a fixed relative error of some series value.
• Some point out the article blurs “usage tolerance” (acceptable design error) with fabrication tolerance of real parts.
• The Renard cable story is recognized as the same geometric / overlap principle applied to mechanical sizes.

---

Practical usage and power ratings

• Many say E12 (or even E6) plus 1% resistors is enough for most work, especially digital; analog and metrology may need finer series and matched networks.
• Trimmers and digital calibration are common where precision beyond basic resistors is needed.
• Power rating is usually inferred from package size; designers often standardize on the highest rating they expect to need in a footprint.

Overall framing of the study

• Commenters note the main finding: elevated CO2 increases survival and infectiousness of viral aerosols by buffering droplet pH closer to neutral, where many respiratory viruses fare better.
• Several argue this does not “challenge” ventilation doctrine but strengthens it: CO2 remains both a proxy for air quality and now appears to have a partial causal role in infection risk.

---

Mechanism: CO2, droplets, and pH

• Clarification that viruses are in tiny water droplets; CO2 dissolves into these, forming carbonate/bicarbonate and shifting pH, similar in principle to ocean acidification.
• One commenter was initially skeptical because “air isn’t a liquid,” but accepts the explanation once the droplet context is described.

---

Ventilation vs CO2 scrubbing

• Strong consensus that the practical solution is ventilation with outdoor air, possibly via ERV/HRV systems or cross-ventilation (opening multiple windows/doors).
• CO2 scrubbers are noted as mature tech in submarines and space (e.g., hydroxide sorbents, zeolites, Sabatier reaction), but seen as uneconomic or impractical for homes today.
• Activated carbon prefilters are clarified as targeting VOCs, not CO2.

---

Houseplants and biological CO2 removal

• Widespread skepticism that houseplants can meaningfully offset human CO2 emissions indoors; estimates of hundreds of plants per person, with plants needing to gain substantial mass daily.
• Soil microbes can emit CO2, sometimes worsening levels.
• Closed-loop plant–human systems are described as extremely hard, referencing large-scale experiments.

---

CO2 levels, health, and “good air”

• Shared guideline ranges: ~400 ppm typical outdoor; 400–1,000 “good”; >1,000 linked to drowsiness and poor air; >2,000 to headaches and cognitive effects.
• Some argue these thresholds are too lenient and that impairment starts around 600–800 ppm.
• Disagreement over whether CO2 is “self-modulating” via photosynthesis; others rebut with observed steady global increases.

---

Indoor monitoring experiences

• Multiple commenters report using CO2 monitors at home/offices:
  • Find CO2 an effective proxy for “stuffy” air and timing window opening.
  • Surprised at how long it takes to purge CO2 and how sharply levels rise with added occupants.
• Notes that cheap devices may infer CO2 from VOCs or have dubious algorithms; higher-quality NDIR-based sensors are preferred despite higher cost.

What “encryption at rest” actually protects

• Many commenters stress it mainly protects against loss of physical control of storage: theft of servers/laptops, misplaced drives, shipping incidents, improper disposal, broken disks being resold, etc.
• It also simplifies device lifecycle: crypto‑erase by destroying keys instead of physical shredding or complex wiping, especially on SSDs.
• For always‑on servers, it doesn’t stop attackers who already have OS/DB‑level access; once the system is booted, the data is effectively decrypted.

Disk / volume encryption vs application- or field-level

• Full‑disk or volume encryption is easy to deploy, mostly transparent, and good for physical threats and backups.
• Application/field/row‑level encryption can protect specific sensitive data even when the DB or VM is compromised, but is harder to design and implement safely.
• Some products (e.g., database TDE, Salesforce-style field encryption) sit in between, raising questions about whether they’re implemented correctly.

Online attacks, authorization, and “security theater”

• A recurring theme: encryption ≠ authentication/authorization.
• If an app will decrypt any record it’s given, confused‑deputy style attacks can let one user read another’s data despite “encryption at rest.”
• Several argue it’s “security theater” when used as a checkbox against online attacks (SQL injection, API abuse) instead of fixing access control.
• Others push back: it’s not theater if it genuinely mitigates the defined threat (e.g., stolen disks) or is required by customers/regulators.

Threat models: cloud, insiders, and subpoenas

• Some treat the cloud provider (and its staff) as a real adversary; others accept trusting the provider and treating misuse as a legal issue.
• Bring‑your‑own‑key and external HSMs are discussed as ways to ensure subpoenas must go to the data owner, not just the cloud.
• Multi‑tenant isolation and VM co‑residency risks are mentioned but considered low probability on major clouds.

Performance, functionality, and searchable encryption

• Client‑side/field encryption often breaks indexing, filtering, and sorting; workarounds (deterministic encryption, blind indexes, Bloom filters) leak patterns or require deep data‑shape knowledge.
• Commenters note that for many workloads, app‑level encryption must be selective and carefully designed to be practical.

Compliance and key management realities

• HIPAA, PCI 4.0, SOC2, and large‑enterprise questionnaires are major drivers; often controls are adopted “for the checklist” but still yield real improvements.
• Key management, rotation, boot‑time decryption, and RTO/RPO trade‑offs are repeatedly cited as the hard part.

Remote work and its effect on commutes

• Many argue remote-capable roles should stay remote to eliminate daily commutes, reduce traffic, and effectively “upgrade” infrastructure for those who must travel.
• Others note that only a subset of jobs (mainly office/professional) are remote-capable; many critical roles (healthcare, education, service, infrastructure) are not.
• There’s disagreement on how large that remote-capable share really is; some cite “more than half” of jobs being office/professional, others challenge that interpretation.

Impact on non-remote workers and inequality

• Rising housing costs in desirable areas push low- and mid-income “support” workers farther out, lengthening commutes.
• Several comments stress that remote work by higher-paid workers can indirectly help: less traffic, less central-office demand, weaker price pressure in city centers.
• Others argue this doesn’t solve problems like long distances, car dependence, and the inability of many low-wage workers to move or drive.

Housing, land use, and suburbanization

• Long commutes are tied to housing affordability: people accept longer drives or train rides for lower housing costs or larger homes.
• Some moved farther out once they became remote, trading a short urban commute for rural or suburban living.
• There’s debate about whether remote work stabilizes people in place (due to low-rate mortgages) or encourages moves to exurban areas.

Environmental impact of remote work

• Pro-remote comments emphasize reduced vehicle miles and traffic as a major emissions win.
• Skeptics note that larger suburban homes, more driving for occasional office visits and errands, and dispersed land use can offset or reverse benefits.
• Several argue moderate-density, transit-oriented cities are more eco-friendly than sprawl, even with office commutes.

Worker preferences, office culture, and fairness

• Some prefer offices for productivity and social interaction; others see mandatory in-person work as punishing introverts.
• One view: companies will choose whatever mix (remote/office) best retains their desired workers; neither introverts nor extroverts have a moral “right” to their ideal setup.

Measurement and policy angles

• Hybrid work complicates commute statistics: a longer one-way commute may still mean fewer total hours commuting per week.
• Some see longer commutes and weakened informal social spaces as factors that reduce worker organizing and solidarity.

Forced Microsoft Accounts & Blocked Workarounds

• Many report Windows 11 installs now insisting on an online Microsoft account, with earlier loopholes being closed.
• Some still succeed with workarounds:
  • Disconnecting networking at a specific step.
  • Using the OOBE\BYPASSNRO command in setup to re‑enable local accounts.
  • Using tools like Rufus to pre‑configure an image that skips the account requirement.
• Several users say they were tricked into converting a local account to an online one when resolving license/activation issues.

Perceived User Hostility, Bloat, and UX Degradation

• Strong sentiment that Windows is becoming more user‑hostile: ads, dark patterns, telemetry, Candy Crush‑style bloat, and pushy OneDrive/Microsoft 365 prompts.
• Complaints about sluggish UI (e.g., context menus taking ~1s, sound delays), sometimes attributed to third‑party shell extensions, cloud storage integrations, and OEM crapware.
• Some defend forced updates as good security for typical users; others want full control, especially in paid “Pro” versions.

Accounts, Data, and Business Model

• Widely believed that mandatory accounts support:
  • Data collection/telemetry and ad targeting.
  • Driving subscriptions (OneDrive, M365, app store).
  • Easy license management, device sync, and “just works” backups for non‑technical users.
• Some argue these benefits are real; others see them as pretexts for lock‑in and future subscription gating.

Secure Boot, TPM, and Remote Attestation

• Disagreement on Secure Boot:
  • Pro: real security benefits, integrity of boot chain.
  • Contra: negligible protection vs modern threats, centralizes control with Microsoft, enables attestation‑based DRM and game anti‑cheat, complicates open computing.
• Concerns about TPM hardware IDs, Pluton, and “trusted computing” as anti‑user infrastructure.

Alternatives: Linux, macOS, ChromeOS

• Many say Microsoft is effectively pushing power users toward Linux or macOS, though acknowledge an “echo chamber” effect and that most users don’t care or feel stuck.
• Linux:
  • Praised as increasingly usable (KDE, Mint, Fedora, Steam/Proton).
  • Still criticized for hardware/driver rough edges, specialized apps missing (DAWs, Adobe, some games, VR), and needing terminals for troubleshooting.
• macOS:
  • Seen as more privacy‑respecting and polished, tied to expensive hardware, and increasingly pushing services.
• ChromeOS and Android/iOS are noted as also pushing cloud accounts, though sometimes with slightly more graceful opt‑outs.

LTSC, Piracy, and Workarounds

• Windows 11 LTSC is highlighted as still supporting local accounts and shipping without most consumer bloat, but officially targets volume/enterprise licensing.
• Some recommend using unauthorized activators or repackaged ISOs to get a debloated, local‑account Windows; others flag security risks and ethical concerns.

Windows 10 EOL and E‑Waste

• Anxiety over Windows 10 end‑of‑support in 2025 given many devices fail Windows 11’s artificial requirements.
• Expected outcomes: extended support, paid LTS channels, or mass use of unsupported systems; some hope it nudges more people to Linux.

Falun Gong, Epoch Times, and Shen Yun

• Many commenters were surprised or disturbed to learn/recall that Epoch Times is closely tied to Falun Gong and also runs Shen Yun.
• Several describe the paper as far‑right, conspiratorial, and full of bigoted or hateful rhetoric, especially in Chinese-language editions targeting diaspora communities.
• Others note that Falun Gong members also peacefully protest CCP repression, and that both “cult-like” behavior and genuine persecution (e.g., organ harvesting allegations) may be true.
• There is disagreement over how much to trust Falun Gong claims, given both CCP disinformation campaigns and Falun Gong’s own propaganda and political alliances.

Alleged laundering scheme details

• Key mechanism described from the indictment:
  • Fraudsters obtained prepaid debit cards funded by crimes, e.g., unemployment benefits using stolen identities.
  • These “crime proceeds” were sold at a discount for cryptocurrency.
  • Epoch‑linked entities allegedly bought the cards, pushed funds through many accounts (some opened with stolen identities), and re‑introduced them as donations/subscription revenue.
• Some see it as straightforward, unsophisticated money laundering that was bound to be caught.
• Others stress Epoch didn’t appear to commit the original benefit fraud but knowingly bought tainted funds, which still constitutes money laundering.

Debate on money laundering laws and anonymity

• One side argues AML/KYC is overbroad, ineffective (citing claims of <0.1% impact), and mainly harms innocents (e.g., small businesses locked out of accounts), while enabling prosecutions without proving an underlying crime.
• The opposing view:
  • Using stolen identities and anonymous accounts is itself the crime.
  • AML is analogous to anti‑fencing laws; it’s legitimate to criminalize handling obviously tainted funds.
  • Transparency and prosecuting launderers help maintain confidence in the financial system.
• There is philosophical disagreement over whether anonymous bank accounts should be legal and how far responsibility for crime chains should extend.

Crypto’s role: scams vs legitimate use cases

• Several commenters claim crypto’s only real functions are scams and money laundering, seeing this case as another example.
• Others list uses traditional finance allegedly serves poorly or censors:
  • Buying drugs or performance‑enhancing substances online in structured marketplaces.
  • Payments to controversial figures (e.g., whistleblowers) or to people in sanctioned/hostile jurisdictions.
  • Protecting savings or business operations in high‑inflation or capital‑controlled countries; some from such countries say crypto is indeed used in practice, others say locals prefer USD/EUR and standard remittances.
  • Hedging against central bank policy or “oppressive” financial surveillance.

Technical and regulatory debate: crypto vs banks

• Pro‑crypto arguments:
  • Fast, cheap cross‑border transfers (on some chains).
  • Better self‑custody, hardware‑key security, and avoiding SMS‑based 2FA and card‑number leaks.
  • T+0 settlement and asset tokenization as innovations.
• Skeptical responses:
  • Many of these are already solved or nearly solved in well‑regulated banking systems (e.g., UK/EU instant payments, chip‑and‑PIN, chargeback and fraud protections).
  • Crypto transaction costs, UX complexity, and irreversibility make self‑custody risky for normal users.
  • Permissionless blockchains are seen by some as technically inferior and vastly more resource‑intensive than permissioned consensus, with their main differentiator being the ability to bypass regulation and law enforcement.

Miscellaneous

• Some note that importing “a crazy cult” predictably leads to shady business activity.
• The indictment’s narrative style is criticized by a few as over‑dramatizing ordinary financial flows; others respond that using stolen identities and laundering is inherently harmful.
• The thread attracted obvious spam posts advertising “crypto recovery” services.

Scope of the new result

• Paper improves a classical 1940 bound on how many zeros of the Riemann zeta function can lie off the critical line.
• One commenter clarifies: the improvement is in an upper bound on the number of zeros with imaginary part < y; the exponent in that bound was improved from 3/5 to 13/25.
• This is about zero density, not proving zeros are absent in any region; it nonetheless tightens information relevant to the distribution of primes.

“Breakthrough” vs incremental progress

• Some see the result as a major breakthrough because:
  • It’s the first substantial improvement on a long-standing bound in ~80 years.
  • The blog author (a leading mathematician) calls the techniques “clever and unexpected”.
  • Progress on such a hard problem is rare and may inspire further improvements.
• Others are skeptical of the “breakthrough” label:
  • They argue it’s a sharp technical advance but not an obvious path to a full proof of RH.
  • The methods are seen by some as sophisticated uses of existing ideas rather than the “new kind of machinery” many expect will be required.
• Several commenters note that the ultimate importance depends on what subsequent work can build on this.

Practical implications and cryptography

• Multiple comments emphasize: this is pure math; no immediate real‑world impact is expected.
• If RH or its extensions were proved, potential consequences mentioned:
  • Faster deterministic primality tests (e.g., improving asymptotic complexity over unconditional algorithms).
  • Turning many heuristic assumptions in analytic number theory and cryptanalysis into theorems.
• However:
  • Modern crypto already uses extremely reliable randomized primality tests; deterministic speedups are seen as “nice to have,” not transformative.
  • Cryptanalysts already assume RH (and stronger conjectures) informally when it’s convenient; a proof wouldn’t suddenly “break encryption” based on what’s known.

Explanations, intuitions, and resources

• Several ELI5‑style explanations describe:
  • RH as a statement about where the zeros of ζ(s) lie and how that controls errors in prime‑counting approximations.
  • Connections to Fourier analysis and visual analogies (e.g., building a jagged “prime-counting” step function from oscillatory components).
• Commenters link to videos, popular books, and personal visualizations of the zeta function to build intuition.

Philosophy of math and logic

• Sub‑threads discuss:
  • The status of the many theorems proved “assuming RH”.
  • Constructivist vs classical views: excluded middle, truth vs provability, and Gödel’s incompleteness.
  • Model‑theoretic issues around finiteness, first‑ vs second‑order logic, and nonstandard models of arithmetic.

Meta‑discussion

• Some complain about non‑experts overconfidently commenting; others defend the discussion as largely thoughtful.
• There is side conversation about mathematical “greatness,” major prizes, and how math culture values ideas vs authority.