Hacker News, Distilled

Project purpose and motivation

• curl-impersonate is a curl build whose TLS and HTTP/2 handshakes mimic major browsers (Chrome, Firefox, etc.), bypassing servers that gate content on “real browser” fingerprints.
• Several commenters note this is specifically about TLS/HTTP fingerprinting; simply setting User-Agent and headers with stock curl does not suffice.

TLS/HTTP fingerprinting and bot detection

• Fingerprinting derives from protocol details (cipher suites, extensions, ordering, TLS library quirks), not an explicit “fingerprint” field.
• Using NSS/BoringSSL lets curl-impersonate match browser TLS behavior closely enough to get through systems like Cloudflare’s JA3/JA4-based detection.
• Some suggest Chrome should “send less fingerprint,” others argue that practical interoperability and differing TLS stacks make a single universal fingerprint unrealistic.

Responsibility, abuse, and costs

• One camp blames companies that fingerprint and discriminate against non‑mainstream clients, seeing this as gatekeeping that harms openness and privacy.
• Another emphasizes massive abuse: aggressive scrapers, LLM crawlers, and DDoS‑like traffic that can swamp small sites or commercial services, arguing that operators must use stronger detection.
• There is disagreement over how costly scrapers really are: some claim typical blogs can’t realistically be “swamped,” others cite concrete cases of severe load and CI/free‑trial abuse.

Technical nuances and remaining fingerprint vectors

• Discussion covers JA3/JA4, JavaScript challenges (DOM, screen size, WebGL), and behavioral fingerprinting as layered defenses.
• IP/TCP stack fingerprinting (e.g., initial TTL, TCP options) is noted as another potential signal, though harder to use than TLS/HTTP fingerprints.
• Some speculate about “official Chrome verification” via attestation; others argue that without hardware-backed schemes, anything Chrome does at the byte level can be replicated.

Use cases, forks, and ecosystem impact

• Reported uses include red‑team recon, accessing Cloudflare‑guarded APIs from scripts, and making non‑browser clients viable in a fingerprint-hostile web.
• A more active fork and Python bindings are mentioned; integration with Python requests is available.
• Several express sadness that such tools are necessary at all, framing them as part of an arms race that makes life harder for alternative browsers, CLI tools, and non‑conforming clients.

Landing page and documentation

• Many commenters are blown away by the interactive landing page and describe it as one of the best they’ve seen in years.
• The scroll-driven 3D “engine” demo and the overall smoothness, even on some mobile and niche Android browsers, are repeatedly praised.
• The docs themselves are praised as “a work of art”: clear API design, interactive examples, and especially good explanations for timers and breaking changes (shown as diffs).

Scroll-driven animation & UX

• Several people normally dislike scroll-based “story” sites but find this implementation unusually smooth and appropriate as a product demo.
• Some argue scroll should only move the page, not drive animations; others push back, saying the web should be “fun” and that this is a natural evolution of scroll.
• It’s noted that the page doesn’t truly “hijack” scroll: body content scrolls normally while scroll position drives background animation, which helps usability.

Performance, compatibility, and crashes

• A number of users see only a black page or WebGL errors (Lockdown Mode on iOS, Firefox ESR, some Linux/Chromium setups, webgl blocking).
• Some Firefox + uBlock Origin users report reproducible tab crashes on specific docs pages.
• Others report extreme CPU usage and lag on older/virtualized hardware or Ubuntu Firefox; some see nearly perfect performance even on phones.
• Discussion centers on hardware acceleration: GPU availability, browser flags, and tradeoffs between client GPU usage vs bandwidth and energy efficiency.

Library design and integration

• People like that it’s plain JavaScript with type annotations and small compiled bundles, and that it leans on efficient CSS transforms and WAAPI.
• The API is perceived as thoughtfully designed and approachable; v3 users say v4 feels like a major refinement.
• React integration is documented; it works “outside React” post-render, which makes some patterns (e.g., exit animations on component removal) harder.

Comparisons and alternatives

• Mentioned peers include GSAP, Motion, Pixi, Lottie, WAAPI, Rive, Godot, and Flash/DHTML-era effects.
• One commenter strongly favors Anime.js over GSAP on performance, size, and code quality; others ask for an explicit “brag page” vs GSAP/Pixi.
• Some see this as a spiritual successor to Flash-era creative web experiments.

Authoring tools and learning

• Multiple people ask for higher-level authoring tools akin to Lottie or a WYSIWYG for non-coders; some lament that Flash still lacks a true replacement.
• The library author commits to creating a course on recreating the landing page, with a waitlist signup, which receives enthusiastic interest.
• There are questions about how the 3D model was made and whether CAD-like workflows or CAD-to-web pipelines exist; this remains unclear.

Use cases and philosophy

• Some see heavy visual UX as impractical for most professional work, but valuable for art, landing pages, crypto/marketing, and self-expression.
• Others caution developers not to overuse such heavy animations due to accessibility, hardware, and energy concerns.
• Several note this release as an example of how mature and polished modern web/JS libraries have become.

Site and Layout Design

• Many readers found the layout novel and “slick”: inline side panes/tiles with animations that open next to the text kept context and were more pleasant than modals or new tabs.
• Others found it distracting or confusing: right-aligned content felt odd, the bright inline buttons broke reading flow, and the blur on floating UI elements drew unwanted attention.
• Several people initially thought the triggers were normal links and were briefly disoriented; suggestions included different styling, icons, hover states, and cursor:pointer.
• On mobile, some advocated auto-opening diagrams; others liked them closed but suggested a short “demo” tile to teach the interaction.
• There are bugs and browser quirks: pop-ins reportedly broken on Firefox, issues on Android and iOS, back navigation and scroll restoration behaving inconsistently.

Anchors, Scrolling, and Overengineering

• Many commenters felt the solution is overengineered and JS-heavy for a mild problem, especially when classic anchors and bottom padding or a large footer would largely fix it.
• Some strongly dislike any “scroll hijacking” (e.g., smooth-scroll libraries), arguing the site must not interfere with native scrolling at all.
• Alternative approaches proposed:
  • Simple: extra bottom margin or “giant footers” to ensure headings can reach the top.
  • Behavioral: Intersection Observer to mark active sections, highlighting all headings in view rather than a single one, or sticky/current headers.
  • Platform features: CSS scroll markers, text fragments, and details/summary elements.
• Several users reported that the final “beautiful” demo still mis-highlights sections or fails to bring the conclusion into view.

Accessibility, Semantics, and Shareability

• Strong criticism of using JS on non-interactive elements instead of real <a> anchors:
  • No keyboard navigation, no anchors without JS, and fragile custom elements that don’t render if JS fails.
  • URLs don’t expose #fragment anchors, so users can’t bookmark or deep-link sections.
• Some suggested combining real anchors (for URL and accessibility) with JS-only enhancements like temporary highlighting.

Meta Discussion: UX, Frontend, and Terminology

• Backend-oriented commenters expressed “horror” at frontend complexity; others replied that UI work is inherently messy because it deals with humans, not just data.
• Long subthread on UI/UX culture, user behavior, and “overdesign” versus necessary polish, with both respect and contempt for users and frontend practices on display.
• The section title “The final solution” triggered a debate: some saw it as insensitive or a potential dog-whistle given its Nazi association; others argued context and intent should matter, but most agreed it’s safer to avoid such phrases once flagged.

Overall impressions & goals

• Several users tried C3 for small tools and game-related work and found it a substantial ergonomic improvement over C while preserving the C ABI and familiar semantics.
• Pre‑1.0 rough edges exist, but people praise the design as pragmatic and “fun” rather than experimental or academic.

Comparison with Zig, Odin, Jai, Nim, etc.

• C3 is described as philosophically closer to Odin (focus on “joy of programming”, convenience, open extension) than to Zig.
• Zig is seen as emphasizing minimalism, explicitness, and composing small primitives instead of adding convenience functions, which some view as a “puzzle” style of programming.
• C3 and Odin trade some explicitness for ergonomic standard library helpers; Zig users may prefer constructing solutions from smaller pieces.
• C3 is available to download and try; this is contrasted with Jai’s closed beta model.
• Some note all these “C alternatives” are still pre‑1.0 and carry churn risk compared to C.

Types, vectors, and ergonomics

• C3 has built‑in vector types and swizzling (e.g. a.xxzx), which users like for 3D/graphics work; this is compared with Zig’s SIMD vectors (no swizzle) and Odin’s influence.
• Discussion of missing features: tagged unions are desired and apparently planned; no native fixed‑point yet, though it could be implemented via user types/methods and there’s an open proposal.

Macros, compile‑time, errors, and contracts

• C3 keeps macros but moves “conditional compilation” into parsed compile‑time constructs ($if, $switch, @if), not a C-style text preprocessor.
• Contracts (@require) are used for programmer errors; recoverable conditions use “faults” (faultdef and return SOME_FAULT?).
• Example: Base32 implementation uses contracts for impossible API uses and faults for invalid data; wrappers can reclassify contract checks into faults if desired.
• Future work aims to statically prove some contract violations at compile time.

FFI, C ABI, and single-header libraries

• C3 targets LLVM and follows the C ABI; interop with C libraries (including OpenGL, raylib, libtmx) is reported as straightforward.
• Single-header C libraries that require a defining macro (#define FOO_IMPL) can be integrated, but their compilation is delegated to a native C compiler, which limits cross‑compilation.

Memory model, RAII, and ownership

• C3 intentionally does not introduce RAII/destructors or a formal ownership system; it positions itself as a C alternative, not a C++/Rust competitor.
• Resource management is handled via:
  • Temp/stack-like allocators with explicit push/pop scopes.
  • Macro patterns with trailing blocks to scope resources (files, sockets, etc.).
• Some commenters argue this is “halfway” and advocate for full destructors; others prefer explicit contexts, claiming destructors can obscure control flow.

Syntax debates: fn, ::, const, switch

• fn is controversial: some dislike the break from C; proponents say it improves greppability, lambda syntax, and symmetry with macros. Removing it is considered unlikely but not impossible post‑1.0.
• :: is used for modules/paths, . for member access. Supporters like the visual disambiguation and avoidance of shadowing problems; critics find :: noisy and prefer a single ..
• C3 changes switch semantics to avoid implicit fall‑through, which is widely applauded.
• const is pared back; there is no general “read‑only pointer” like const int*—instead, parameter direction (in/out/inout) is used.

Debugging, sanitizers, and UB / provenance

• “Safe mode” with contracts can be kept in optimized builds (-O3 --safe=yes).
• LLVM’s address and thread sanitizers work; memory sanitizer support is in progress.
• Pointer provenance is acknowledged but not deeply specified; some UB notes may need revisiting. Users reference ongoing C/LLVM provenance debates as relevant for the future.

Concurrency and parallelism

• Cross‑platform threads and basic thread pools exist, but concurrency abstractions are still sparse.
• There is explicit disinterest in building async into the language; concurrency support is expected to evolve in the library and patterns.

Adoption, ecosystem, and churn

• Several commenters worry about adopting any non‑C alternative in companies (“island” problem) and about churn in young languages.
• The C3 author acknowledges this as a real issue and has written about the case against C alternatives; C3 aims for a frozen language spec at 1.0 with only stdlib/tooling changes afterward.

Community and language-politics meta-discussion

• Long side-threads debate:
  • Perceptions of Zig/Rust communities as “evangelical” vs. largely pragmatic.
  • Accusations and defenses around V language marketing and criticism by rival language leaders.
  • Whether GitHub stars, Wikipedia pages, or books are valid measures of “real” adoption.
• Some participants push for more cross-language curiosity and less adversarial framing; others emphasize that every language community inevitably critiques others.

Overall reception & UI

• Many commenters like the interface: fast, “slick,” reactive, good dark mode, and clear tables.
• AI-generated food icons are praised for quick visual recognition, though some want click-to-zoom to better match ingredients (e.g., specific lentil types).

Search, performance & bugs

• Multiple reports of issues: Safari losing input focus on each keystroke, first character being dropped, filters not returning results, errors on certain queries, client-side exceptions, CORS errors, and 521/“hug of death” outages.
• Author confirms several fixes and scaling issues; web search is positioned as more of a demo vs. the primary in-app experience.

Data sources, coverage & units

• Database includes alternate and non-English names, which users find helpful.
• Users ask for regional variants (e.g., UK vs US Coke) and better handling of generic queries (“can of coke,” “avocado”).
• Debate over including raw vs cooked items (e.g., bacon); some see raw data as essential for logging before cooking, others question relevance.
• Per-100g view exists in the web table; some want it surfaced more prominently, especially for European use.

LLM-generated micronutrients & accuracy debate

• Micronutrients, vitamins, amino acids and some descriptions are inferred using LLMs with grounding data and audit passes (including o1-pro).
• Strong criticism: several commenters say this is “not real data,” call it anti-scientific, and worry about serious users or medical dieters relying on unvalidated estimates.
• Supportive voices argue many existing app databases are already noisy; approximate, well-described estimates can be more useful than missing values.
• Specific issues were found (e.g., choline unit error in eggs, mismatch between website and downloadable line for a cereal), seen as evidence that more validation or clearer labeling is needed.
• There are calls for stronger, possibly license-enforced downstream disclaimers that the data is LLM-derived.

Comparison to other nutrition databases

• OpenFoodFacts (OFF) is repeatedly mentioned as a more “factual” alternative with an API, but limited mainly to packaged foods and what labels report.
• OFF cofounder notes ongoing work to add generic foods and approximate micronutrients from reputable databases and invites collaboration.
• Others reference NCC, Cronometer, Swiss and Japanese government datasets, and nutritionvalue.org as benchmarks or validation sources.
• Some suggest using LLMs only to map natural-language queries onto authoritative databases rather than generating new values.

APIs, licensing & openness

• Dataset is downloadable; some still want an API for freshness and possible monetization.
• License requires prominent attribution (similar to OpenFoodFacts/OpenStreetMap). Some find this restrictive for independent apps and question use of “Open” branding for a commercial product.
• Author argues attribution is necessary to justify the effort and that without it the alternative would likely be no open dataset at all.

Feature ideas & use cases

• Requests: portion scaling, recipe/URL import, better barcode and international support, translations (e.g., Hungarian names), hover tooltips explaining nutrients, and clearer ingredient interactions.
• Some users report the companion iOS app’s macro tracking, goal-setting, and graphs are unusually good and less naggy than incumbents, and would like an option to rely solely on OFF or other “verified” sources with AI as opt-in.
• Several commenters share that even imperfect tracking significantly improves diet awareness and habits, while others insist nutrition tools carry a higher ethical bar for accuracy.

Perceived Failure of Crypto’s Promises

• Many comments argue that crypto has largely failed to deliver its early promises: no transformative financial disruption, no mainstream “killer app,” and little visible benefit for journalists or dissidents.
• Instead, it’s framed as primarily a speculation vehicle and wealth-extraction tool for insiders targeting people who don’t understand it.
• Some see crypto as an embarrassment for the broader tech industry, comparable to NFTs and other fads.

Crime, North Korea, and “Playing by the Rules”

• The North Korean hacks are cited as evidence that crypto’s most successful real-world use case is crime: theft, scams, laundering, and sanctions evasion.
• A minority counters that, by crypto’s own “code is law” ethos, using protocol-compliant theft and mixing is simply playing the game as designed—not “cheating.”
• Others push back that moral and legal notions of theft exist outside protocol rules; breaking into systems or deceiving people is still fraud and theft, regardless of blockchain finality.

Regulation, KYC, and Exchanges

• Several note that exchanges now monitor addresses and often freeze clearly stolen funds, partially recreating traditional financial controls.
• There’s debate over KYC/AML: some say Western society benefits; others argue KYC harms privacy, burdens small businesses, and doesn’t clearly reduce crime.
• The Tornado Cash sanctions episode is cited as an example of regulators overreaching by “sanctioning code,” versus focusing on actual criminals.

Custody, Irreversibility, and Deflation

• The absence of FDIC-style protection and irreversibility of transactions are seen as major weaknesses, especially given common key loss and hacks.
• Comparison is made to losing a physical wallet: critics note people keep far more value in crypto wallets than in cash, making losses catastrophic.
• Lost coins and hacked funds are viewed as making Bitcoin effectively deflationary and unattractive as a currency.

Alternative Views and Possible Legitimate Uses

• Some participants report legitimate uses: crypto-backed loans, cheaper cross-border payments, and stablecoins as a convenient settlement layer.
• Others argue that smart contracts and instant settlement could reduce billing and reconciliation overhead—but skeptics say these problems are better addressed within regulated fiat systems.
• A long subthread frames the core issue as political, not technological: governance, courts, and regulation versus purely code-driven systems.

Universities as Businesses and Funding Leverage

• Many commenters argue universities have become risk‑averse corporations and real‑estate funds: preservation of brand, endowment, and grants now dominates over mission.
• Federal research money (especially NIH, NSF, DOE) is seen as a primary lever: institutions structurally dependent on hundreds of millions in grants are far more likely to “roll over.”
• Smaller liberal‑arts schools with little or no medical centers are less exposed and thus more willing to defy federal threats, though they still face some risk.
• One recurring suggestion: some colleges reject federal funds entirely to avoid political control, but others note this is only plausible for a small subset of institutions.

Free Speech, Activism, and DEI

• Strong disagreement over whether universities have long censored heterodox views or merely protected vulnerable groups from harassment.
• Critics cite DEI hiring statements, disinvited speakers, speech codes, and survey data on student self‑censorship as evidence of systematic suppression, mostly of right‑leaning views.
• Defenders argue earlier “speech restrictions” were attempts to counter longstanding systemic discrimination and create space for minorities; they see current crackdowns as far worse.
• Many distinguish between speech and conduct: blocking access, threats, arson, and harassment are repeatedly labeled as coercion or violence, not protected expression.

Public Resentment and “Culture War” Framing

• Several threads explore why large parts of the public cheer attacks on universities:
  • Elite schools’ political homogeneity and open alignment with progressive causes.
  • Tuition inflation, heavy debt, and the sense that universities gatekeep entry into the professional class while sitting on large endowments.
  • Anti‑intellectualism and decades of media attacks on “ivory tower” academics.
• Others see this as class warfare driven by populist right media; universities look left‑wing mainly because the broader Overton window has shifted right.

Cowardice, Hypocrisy, and Tenure

• Some argue universities are now reaping what they sowed: after years of selectively policing speech and yielding to student pressure, their free‑speech defenses ring hollow.
• Tenure is criticized as having failed its purpose: faculty are portrayed as cautious and careerist rather than using their security to defend principle.
• Others defend specific administrators who resisted post‑2020 illiberal demands and say those institutions are better positioned to credibly oppose current federal overreach.

Government Power, Rights, and Funding Conditions

• One camp views the current administration’s threats—cutting funds, targeting visas, public intimidation—as authoritarian, even “Nazi‑like,” and incompatible with constitutional protections.
• Another replies that conditioning federal money on compliance is longstanding practice (e.g., drinking age, Title IX) and not automatically a First Amendment violation.
• There’s an extended side debate about whether rights are inherent vs purely legal, and whether “rights” have any force when governments and courts decline to enforce them.

Research Funding and Alternatives

• Proposals to “just stop taking federal money” face pushback: modern basic research (labs, big instruments, graduate training) overwhelmingly runs through federally funded university systems.
• Commenters argue private or corporate research can’t realistically replace this without huge coordination and sharing problems, or a shift to national labs on a massive scale.
• Some still see dependence on federal grants as structurally dangerous and advocate diversifying funding sources, while others say the real fix is to make political retaliation illegal.

Safety, Antisemitism, and Line Between Speech and Harm

• Several focus on campus antisemitism and specific incidents (e.g., blocked access, “exclusion zones”) to argue administrators failed to protect Jewish students and are now being overruled by the state.
• Others counter that “student mobs” are being exaggerated to justify a much broader crackdown on dissent, including deportations and surveillance of lawful protest.
• There’s no consensus on the scale of antisemitic harassment or on how well universities responded; both minimization and alarmism are called out.

Impact on Students and Future of US Universities

• Commenters worry about chilling effects on international students (deportation risk, “black‑bagging” accusations) and on the US’s long‑term scientific and educational advantage.
• Some younger people are reportedly beginning to boycott high‑profile universities for perceived cowardice or complicity.
• Underneath the immediate Trump–university clash, many see a deeper, decades‑long drift: from liberal education and independent inquiry toward brand management, ideological policing, and political patronage.

Project concept & appeal

• InitWare is seen by several as a “middle ground” between classic inits and full systemd: a mostly systemd-compatible service manager that’s more modular, can run as PID 1 or under another init, and is portable to BSD.
• Some Debian, Alpine, and Nix/NixBSD users like the idea of swapping it in to gain systemd-style units and tooling without adopting the full systemd stack.
• Others praise the project’s explicit design scope and documentation (e.g., “Myths and Truths”).

Portability, cgroups, and Linuxisms

• Discussion challenges the idea that systemd is inseparable from Linux features: basic supervision of simple/oneshot services can work without cgroups, and BSD has alternative primitives (kqueue, login classes).
• Still, systemd’s robust tracking of complex forking patterns relies heavily on cgroups v2; that advantage doesn’t carry over cleanly to a portable fork.
• Some argue BSD never really “rejected” systemd; it simply wasn’t designed for BSD and depends on Linux-centric infrastructure like D-Bus and cgroups.

BSD attitudes and ecosystem fit

• Many BSD users in the thread actively don’t want a systemd derivative; third‑party init systems and GPL/LGPL code are culturally and legally unwelcome in core.
• Others care mainly about Linux-targeted apps that assume systemd; they see InitWare as a way to ease such ports while still keeping BSD distinct.
• There’s a strong “BSD is not Linux; if we wanted Linuxisms, we’d run Linux” sentiment.

Dropped components, scope, and security

• The long list of dropped components (DNS, crypto, boot tooling, etc.) is widely praised as prudent: better to defer to existing, well-audited tools than reimplement risky subsystems.
• Critics counter that systemd’s integrated cryptsetup/cryptenroll/unified kernels/systemd‑boot provide tested, end‑to‑end boot and disk‑security flows that are hard to replicate by hand.
• Broader debate breaks out around MAC vs DAC, SELinux complexity, and whether secure boot and “boot security” are valuable or overcomplicated compared to just full‑disk encryption.

Alternatives, licensing, and maintenance

• Alternatives like dinit and supervisord are mentioned as simpler, already-portable service managers.
• Fork being (L)GPL is considered a non-starter for some BSD folks, but others note that’s inevitable given its systemd origins.
• Several worry about the project’s low commit activity and high complexity for a small volunteer team; some argue one should reimplement ideas instead of forking PID 1 code.
• One commenter explicitly asks what concrete advantages InitWare offers over systemd or existing portable inits; the thread provides no clear consensus answer.

Steam Deck vs Switch (and Other Consoles)

• Many compare the Steam Deck favorably to the Switch/Switch 2 on openness and game pricing, even if Nintendo may win on battery, first‑party polish, kid‑friendly titles, and motion‑control experiences.
• Nintendo’s evergreen full-price games are contrasted with Steam’s heavy discounts; some see Nintendo’s pricing as preserving value, others as gouging.
• Several parents criticize Nintendo’s modern UX (store prompts, online hooks) as worse for young kids than older offline handhelds.

Valve, Openness, and “Software Freedom”

• Strong praise for SteamOS: Arch-based, desktop mode, Flatpaks, easy installation of other stores and even Windows. People note Valve’s long-term investment in Wine/Proton and Linux gaming.
• Others argue the headline overreaches: the Deck is “not hostile” to software freedom, but still DRM-heavy, full of proprietary blobs, and far from FOSS ideals.
• Some confusion about “software freedom” vs “choice”; commenters clarify it refers to licensing, transparency, and modifiability, not just being able to run many apps.

Monopoly, Anticompetitiveness, and the 30% Cut

• Heated debate over whether Steam is a monopoly: users have alternatives (Epic, GOG, publisher launchers), but devs say if you’re not on Steam, your game “might as well not exist.”
• Several point to most‑favored‑nation–style pricing parity and key policies as anticompetitive; lawsuits and judicial rulings allowing cases to proceed are cited.
• Others respond that competitors mostly “shot themselves in the foot,” and Valve wins by UX and trust, not OEM‑style strong‑arming.

Consumer Experience, DRM, and Gambling

• Steam is widely praised for UX, refunds (with caveats), family sharing/parental controls, Workshop, regional pricing, and not breaking games often. Many admit buying games on Steam they already own elsewhere just to avoid bad launchers.
• DRM is seen as relatively “benign” compared to others, but some insist any DRM is anti‑freedom and worry about long‑term access and lack of inheritance.
• Multiple commenters highlight Valve’s role in loot boxes / skin gambling as a major ethical black mark, especially regarding kids.

Steam Deck in Practice

• Users describe the Deck as transformative: handheld PC, dockable desktop, robotics controller, fallback workstation, and powerful emulation box.
• Critiques: “Verified” status sometimes overpromises; launchers and local multiplayer can be clunky; the device is bulky compared to Switch; some games need tinkering.

Wider Ecosystem and Future Risks

• Discussion of potential Xbox handhelds, other x86 portables, and dreams of “Steam Machine 2.0” or Framework partnerships.
• Many express anxiety about what happens after Gabe Newell—fear of IPO, shareholder pressure, and more aggressive monetization.

Overall reaction to Dijkstra’s essay

• Many readers find the piece strikingly clear, beautiful, and still relevant decades later.
• Some note his complaint about declining mastery of natural language feels timeless.
• There’s clarification that the text is from 1978, with a 2010 transcription.

Natural vs formal languages

• Strong agreement that forcing ideas into a formal language (math or code) improves thinking, exposes ambiguities, and reveals flawed requirements.
• Several note that natural language is especially bad at specifying rules and procedures; examples given: mathematics, programming languages, aviation weather codes, and legal drafting all evolve specialized, semi-formal notations.
• Others counter that real-world features begin in someone’s head and must first be expressed in natural language; translation to formal systems is unavoidable, so tools that help this step are attractive.

LLMs and “natural language programming”

• Critics fear overreliance on LLMs will erode competence and produce large, messy, hard-to-maintain codebases.
• Multiple comments liken “vibe coding” with LLMs to earlier “no-code” / flowchart / UML / BPML / AppleScript waves: appealing demos that fail to scale.
• Some argue LLMs are best seen as translators or assistants: turning specs into code, explaining code, navigating big codebases, generating docs and tests, or helping refactor—provided an experienced human keeps architectural control.
• There is a long, unresolved debate about whether a “sufficiently descriptive” natural-language spec could, with a “sufficiently powerful” model, fully determine a program; skeptics emphasize irreducible ambiguity and non-reproducibility, proponents say it’s theoretically possible but not here yet.

Thought, representation, and programming

• Extended subthread on whether ideas exist pre-language: some claim the act of verbalizing creates the idea; others point to non-verbal thinking, inner “shapes,” and graph-like mental models of code.
• Several describe programming as manipulating abstract structures rather than composing sentences, and imagine better structural GUIs or AR interfaces—but still grounded in formal semantics.

Types, errors, and formal methods

• Dijkstra’s praise of languages that turn “silly mistakes” into compiler errors is linked to static and strong typing.
• Discussion of Rust, Scala, etc. highlights a trade-off: rich type systems catch more errors but hinder rapid, exploratory work.
• Dijkstra’s advocacy of proving correctness (predicate transformer semantics, A Discipline of Programming) is mentioned as another largely ignored but relevant strand.

Domain and legal languages

• Several note that each business domain already has a quasi-formal jargon; Domain-Driven Design’s “ubiquitous language” is cited as formalizing that.
• Legal language and math notation are given as examples where natural language is sharpened into a more constrained, semi-formal code; suggestions appear for more symbolic legal systems to avoid ambiguity.

Historical patterns and expectations

• Commenters list recurring “simple” ideas that don’t scale (flowcharts, weak typing, constraint-based layouts, naive dependency management, many no‑code platforms), suggesting we should document their failure modes rather than repeatedly rediscover them.
• Others caution that some once-dismissed ideas (e.g., neural networks) eventually worked when constraints changed, so a “Hall of Definitely Bad Ideas” should instead catalogue hard problems and past pitfalls.

High-level synthesis

• A recurring theme: requirements vs implementation. Natural language is suited to stating goals and motivations; formal languages are needed for precise, reproducible behavior.
• Many see LLMs as potentially powerful tools to move between these layers, but not as replacements for the discipline of formal reasoning that Dijkstra defends.

Usability of Old ThinkPads Today

• Strong split: some say 15–20-year-old ThinkPads are “dog-slow” for modern web apps, video calls, Slack, and heavy multitasking; others daily‑drive T/X/W‑series from ~2009–2013 and report they’re fine for coding, browsing, office work, and light media.
• Performance is heavily tied to:
  • Swapping HDD → SSD
  • Maxing RAM
  • Running Linux or a lean Windows build
  • Aggressive ad‑/tracker blocking in the browser
• GPU is a common weak point (video, WebGL, some games), and 720p TN panels are widely disliked; some users do FHD/IPS or LVDS mod boards to fix this.

Modern Software Bloat vs Hardware Limits

• Several comments argue that poor performance says more about unoptimized, ad‑heavy, JS‑bloated web apps than about the old hardware.
• Others counter that real workloads (multiple browsers, Electron apps, video calls, AI tools) genuinely benefit from modern CPUs/GPUs and large RAM.

Repairability, Mods, and Parts Ecosystem

• ThinkPads are praised for:
  • Detailed maintenance manuals and FRU parts ecosystem
  • Socketed CPUs (in older models), replaceable Wi‑Fi, RAM, SSD/HDD, fans, keyboards, ports.
• Popular mods:
  • Coreboot / EC firmware patches, Wi‑Fi whitelist removal
  • CPU swaps (e.g., dual → quad core)
  • Keyboard swaps (T420/T520 keyboards into newer chassis)
  • USB‑C charging mods, ExpressCard/M.2 storage, eGPU use.
• Batteries are now the weak link; quality and longevity of third‑party packs are hit‑or‑miss.

Framework vs ThinkPad vs MacBook

• Framework:
  • Admired for ethos and modular design, but criticized as expensive, flexy, and still requiring costly mainboard swaps for big upgrades.
  • Second‑hand market and long‑term economics are debated; some see it as “gimmick priced like a premium laptop,” others as the only modern ThinkPad‑like option.
• MacBooks:
  • Praised for rigidity, screens, trackpads, and M‑series efficiency.
  • Criticized for soldered RAM/SSD, fragile screens, and lifecycle tied to Apple’s OS support; viewed by some as “folding smartphones.”
• Many commenters want a modern, rigid, ThinkPad‑style chassis (or “restomod”) with contemporary internals and true serviceability.

Keyboards, Pointing Devices, and Build Quality

• Old ThinkPad keyboards (7‑row, deep‑travel, TrackPoint with physical buttons) are a recurring obsession; many consider them unmatched.
• Newer Lenovo lines (soldered RAM, fewer ports, thinner shells, noisier cooling) are widely seen as a decline, though some recent T/X/P models still get positive notes.
• Durability stories (drops, spills, being stepped on, surviving a decade+ of travel) are common and contrasted with more fragile modern ultrabooks.

Fragility vs. Resilience of the U.S. System

• Several commenters argue the legal and political system is far less resilient than people assumed: a president with a compliant court and cabinet can radically reinterpret vague immigration and national-security statutes and upend lives of even legal residents.
• Others counter that the “system” is functioning as designed: visas and even green cards are discretionary, non-citizens have always been legally vulnerable, and what’s changing is mainly public awareness.
• There is debate over blame: some fault Democrats for failing to use hardball tools (court expansion, retirement pressure, primary challenges) while others insist Republicans and their long-term anti-government project are the core problem.
• A recurring theme is the collapse of “good faith” norms: institutions and laws depended on self-restraint that no longer exists; once bad-faith actors face no consequences, rule of law becomes paper-thin.

Immigration Law, Due Process, and Speech

• Lawyers are reportedly advising visa holders (H‑1B, TN, etc.) not to leave the U.S. and to travel only with “clean” devices; a Canadian firm and a U.S. law firm are cited as giving explicit travel-warnings to clients.
• Commenters describe U.S. immigration as long exploitative and anxiety-inducing, even pre-Trump, with high costs, arbitrary-feeling decisions, and risky “loopholes” that are in fact semi-official pathways.
• Strong disagreement over current deportations:
  • Critics say revocations, street detentions, and transfers to harsh foreign prisons without hearings violate 1st, 5th, 8th, and 13th Amendment principles and weaponize immigration law against protected speech (notably criticism of Israel).
  • Defenders stress that statutes like 8 USC 1182 and the Alien Enemies Act explicitly permit broad executive discretion, that many details are classified, and that non-citizens have no right to remain.
• Comparisons are made to Finland and Argentina, where deportation usually follows court review and minimal-force principles; U.S. practices are viewed by some as outside liberal-democratic norms.

Nativism, Radicalization, and Social Climate

• Multiple comments describe mainstreaming of “replacement” and antisemitic conspiracy theories among previously “normal” conservatives, driven by alt-right media and social platforms, leading to fear about where this trajectory ends.
• Some fear escalation from visa crackdowns to property restrictions or asset seizures for non-residents, while others note the U.S. already has partial analogues (land-ownership limits, civil asset forfeiture).
• There is concern that once due process is eroded for immigrants, it becomes easy to deny it to citizens by simply contesting their status.

Tech, Remote Work, and the Value of Immigrating

• Tech companies’ travel warnings to employees are framed as rational responses to legal risk, not altruism.
• Commenters note that remote-work “just work from abroad” is constrained by tax, employment, and licensure rules; U.S. law effectively pins many high-skill workers to specific jurisdictions.
• Some urge young immigrants to avoid or leave the U.S., arguing the risks and instability now outweigh the upside; others insist that, despite problems, U.S. compensation and everyday life remain significantly better than in most alternatives.

International Comparisons and Safety

• China is mentioned as now easier to enter and, anecdotally, feeling safer in day-to-day life—yet other commenters highlight China’s arbitrary detentions and hostage diplomacy as a warning that it is not actually safer in a political sense.
• Overall, there is a sense that many major countries are converging on more coercive, less rights-respecting migration regimes, but the U.S. shift feels particularly sharp to people who had believed in its myth of stability and rights.

Feasibility of Photo-Based Calorie Estimation

• Many argue the core claim (“90% accurate” calories/macros from a single photo) is effectively impossible: a camera can’t see portion size precisely, hidden ingredients, or fats/oils, sugar, fillings, or type/amount of cooking fat.
• Examples used: salad with/without lots of oil, cucumbers with/without olive oil, diet vs regular soda, butter on toast, bacon/cheese inside breaded meat, restaurant food loaded with hidden butter/sugar.
• Several posters say even nutrition labels and lab measurements have significant error; building on top of that with pure vision only worsens accuracy.
• A few suggest extra sensors (volume estimation, AR, hyperspectral cameras) might help, but still can’t resolve invisible ingredients.

Usefulness vs Harm

• One camp: rough estimates can still help most people; awareness and consistent logging matter more than precision, especially for beginners without strict macro goals.
• Counterpoint: for serious dieting, ±10–30% error can flip a deficit into a surplus; misleading low estimates may cause stalled progress and frustration.
• Some fear the app may be “actively harmful,” giving false confidence and hiding where calories really come from (oils, dressings, restaurant food).

Business, Marketing, and “AI Wrapper” Concerns

• Several see it primarily as an “AI wrapper” plus strong TikTok/influencer distribution, not a breakthrough in computer vision.
• Comparisons to earlier impossible-sounding “AI” startups and broader grifter culture: claims that marketing now routinely outruns technical reality.
• Disagreement over whether it’s a “great idea”: financially promising vs technically fraudulent and class‑action risk if claims are taken literally.
• One paying user praises the simple UI and barcode scanning but barely uses the photo feature and doesn’t plan to renew.

Founder and College Admissions Debate

• Large subthread around the founder’s public complaints about rejection from top universities.
• Critiques: essay read like a VC pitch (metrics, ARR, grindset talk), lacked self‑reflection, and signaled prestige‑hunting; some find the persona off‑putting.
• Others argue he’s clearly accomplished for his age and that elite admissions are broken, overly subjective, and hostile to tech‑optimistic profiles.
• Broader discussion of U.S. holistic admissions vs exam-based systems elsewhere, score inflation at elite applicant pools, and the role of soft factors and perceived character.

Meta and Cultural Reflections

• Some note HN is unusually unsympathetic to teenage founders here, attributing it to skepticism about the product’s truthfulness rather than age.
• Threads broaden into diet culture, public ignorance about nutrition, and a sense that many users just want something that “looks right,” even if it isn’t.

Business outcomes vs writing code

• Many comments agree with the article’s core idea: developers are hired to achieve business goals, not to write code per se.
• Analogies: NASCAR drivers are hired to win races, researchers to publish papers, surgeons to heal patients. Code is a tool, not the objective.
• However, several people push back that this can be overstated: you still hire a driver to drive, and you don’t get to unilaterally decide to “be the CEO instead of coding.”

Minimizing code and using existing tools

• Strong theme: “code is a liability.” Good engineers try to solve problems with as little new code as possible.
• Examples: use Remote Desktop instead of building remote control software; use WordPress or an off‑the‑shelf CMS instead of rolling your own, unless there’s a clear reason not to.
• Surgery metaphor: only “operate” (write code) when absolutely necessary, and do the minimum. Many praise deleting or compressing code as higher skill.

Roles, requirements, and communication

• Debate over whether engineers should also act as business analysts: some say that’s scope creep; others say translating messy requirements into correct software inherently demands domain thinking.
• Several note that developers are often isolated from customers and only handed pre‑digested tickets, which undermines the “problem solver” ideal.
• Mentoring advice emphasizes understanding the problem and trade‑offs, not just frameworks or LeetCode.

Engineering ethics and accountability

• Thread explores whether software should be regulated like other engineering disciplines, especially when code can kill or cause major financial harm.
• Some want liability and autonomy similar to licensed engineers; others argue software’s low stakes and rapid change make that unlikely except in safety‑critical domains.
• Long sub‑discussion compares unpredictability and change in civil/mechanical vs software engineering, with no consensus.

Incentives, management, and pay

• Officially, companies hire developers to make money; in practice, they often prioritize process adherence (RTO, hierarchy) over actual value creation.
• Complaints, especially from Europe/Netherlands, that programmers are paid and ranked below managers and “humanities” roles, and can only earn more by leaving coding for management.
• Observations that organizations promote the “well‑rounded” devs out of development, then wonder why remaining devs “don’t get it.”

LLMs, “vibe coding,” and volume

• Some see “vibe coding” and LLM‑driven development as a logical response when code quality isn’t valued; just ship slop the business can’t distinguish.
• One practitioner notes staff engineers running multiple AI‑driven branches in parallel, with CI breakage and incoherent conventions as the cost of higher volume.
• Others resist this shift, preferring slower, higher‑quality code they deeply understand.

What “obsolete” might mean

• Some interpret “obsolete in 5 years” trivially (GPT‑4 replaced by GPT‑5), others as architectural replacement (e.g., JEPA‑style models superseding pure language modeling).
• A different view: current approach becomes obsolete economically, as scaling is roughly linear in cost while expectations (and VC funding) assumed superlinear returns.

LeCun’s critique of autoregressive LLMs

• Discussion centers on his claim that token‑by‑token generation is “System 1” (fast, reactive) with no real “System 2” reasoning.
• Others note there are non‑autoregressive models that still don’t show qualitatively better reasoning, so “one token at a time” may not be the real bottleneck.
• JEPA/V‑JEPA is cited as his long‑term bet, though commenters note there’s little yet to show versus state‑of‑the‑art LLMs.

Math, logic, and modeling reasoning

• One camp argues no form of mathematics can fully model conceptual reasoning; math is just one tool of thought.
• Opponents insist reasoning is ultimately formalizable; alternative logics (e.g., paraconsistent logic) and probabilistic models could capture messy human preferences and inference.
• There’s back‑and‑forth over whether LLM behavior is “just probabilities” or something richer happening in latent representations.

Pattern matching as (or vs) intelligence

• Several argue that intelligence is largely sophisticated pattern‑matching: abstraction, compression, and recombination of patterns; logic is comparatively easy.
• Others push back: questions like dark matter, cancer cures, or world peace seem to demand more than pattern matching over existing data.
• Creativity is debated: is it just applying familiar patterns in new domains, or something fundamentally beyond interpolation? No consensus.

Real‑world value of LLMs

• One side: outside text generation and search, LLMs haven’t delivered major value; visible software quality and velocity don’t seem transformed.
• Counterpoint: text and search already underpin trillions in economic activity; coding assistance, prototyping, and problem exploration are concrete productivity gains for many.
• Some see LLM interaction as “just search,” others liken that objection to nitpicking whether airplanes truly “fly.”

LeCun’s track record and lab context

• A long subthread criticizes his moving goalposts: each time LLMs achieve something he previously claimed they couldn’t, he redefines what “matters” without revising core beliefs.
• Others defend updating views as normal and argue his core claim—LLMs alone won’t reach AGI—hasn’t been falsified.
• There’s meta‑skepticism toward all public predictions (both hype and dismissal) and calls to focus on actual research (e.g., JEPA) rather than personalities.

Squeezed Workplaces & Overmeasurement

• Many long‑tenured tech workers report far less slack than in the 90s–00s: every hour accounted for, endless backlogs, constant justification of work.
• Agile + Jira/metrics are seen as creating a parallel “model of the work” that must be maintained in addition to the work itself, consuming huge effort and locking in bad architectures/tech debt.
• Attempts to run people at near‑100% utilization are compared to overloading machines or CPUs: latency and quality blow up, burnout follows.

Management, Metrics & Organizational Scale

• Strong theme that measurement culture (Jira, dashboards, KPIs) drives “productivity theater,” Goodhart/McNamara effects, and overfitting to what’s countable.
• Unmeasured contributions (unblocking others, building robust systems, preventing incidents) are invisible in promotions/layoffs.
• Some defend Jira‑style systems as necessary for investors, customers, and regulators at scale; critics argue most numbers are guesses, so the whole structure is largely theater that “works” only in a narrow, scaled sense.

Slack, Burnout & Career Dynamics

• Calls for sustainable pace, explicit slack (e.g., 20% time, 2 hours/day for self‑directed work) as prerequisite for good work.
• Recognition that workers respond to impossible demands by gaming metrics, padding stories, or quietly doing less.
• Self‑promotion is increasingly required to survive; this promotes ladder‑climbers and fire‑starters over quiet, competent engineers.

Gig Economy, Low‑Wage & “Unskilled” Work

• Multiple anecdotes about TaskRabbit/Angi‑style jobs (furniture assembly, deliveries) being poorly done, with undertrained workers churning through jobs under time pressure.
• Gig work seen as structurally worse than traditional low‑wage jobs: no advancement path, no coworkers/network, algorithmic control, race to the bottom.
• Strong pushback on the label “unskilled”: driving, bagging, handyman work, etc., all demand real skill and experience, but are systematically devalued.

Quality Decline, Outsourcing & Enshittification

• Broad sense that service quality and documentation have declined even as tools improved; many tie this to outsourcing, XaaS/public cloud, private equity, and short‑term incentives.
• Outsourcing is framed as leaders externalizing responsibility: infrastructure, support, and even internal IT become consulting problems, not owned capabilities.

Consumer Role, Information & Policy

• “Pay more for better work” is appealing but hard to execute: pervasive obfuscation (reviews, branding, platforms) makes it difficult to identify genuinely better providers.
• Some argue individual “voting with dollars” is insufficient; they call for stronger labor laws, enforcement, and regulation of deceptive business models.
• Underlying divide: are bad outcomes mainly about bad systems and incentives, or also about individual work ethic and ethics? Most comments lean systemic but note individual responsibility still exists.

Scope of Tariffs & Immediate Reaction

• New regime: baseline 10% on all imports, with much higher country‑specific rates (e.g. ~54% on China when stacked with existing China tariffs; high rates on Vietnam, Thailand, EU, etc.).
• Tariffs apply broadly to all goods from targeted countries, not specific sectors. Some exemptions: chips, some minerals, certain Section 232 categories.
• Many commenters see this as a massive, regressive tax increase on US consumers and the largest protectionist move in modern US history.

Economic Impact & Inflation

• Broad expectation of higher prices on clothes, electronics, furniture, toys, industrial equipment; estimates in the thread put extra household cost in the thousands of dollars per year.
• Worry that businesses will add an extra margin on top of tariffs, using them as cover to raise prices.
• Several predict a US recession and global slowdown; others stress the main damage is long‑run uncertainty and misallocation of capital.

Manufacturing, Labor & Feasibility

• Strong skepticism that factories will “come back”:
  • US labor costs, housing, and regulations make low‑end manufacturing uncompetitive.
  • Factory projects have long payback periods; few expect firms to invest heavily into US plants on a 4‑year, unstable policy horizon.
  • US already has worker shortages in construction, logistics, and manufacturing; commenters doubt there is a large, willing industrial workforce at current wages.
• Some argue higher tariffs could eventually drive up blue‑collar wages, but others expect stagnant wages and falling living standards instead.

Rationale, “Reciprocity” & Calculation Method

• Administration markets these as “reciprocal” tariffs responding to foreign tariffs, VAT, and “non‑tariff barriers.”
• Multiple commenters reverse‑engineer the poster: “tariffs charged to the USA” column appears to be each country’s goods trade deficit with the US divided by its exports to the US, not actual tariff rates.
• VAT inclusion is widely criticized as wrong: VAT applies equally to domestic and imported goods and is more like sales tax than a border tariff.
• Debate whether there is a coherent strategy (re‑industrialization, dollar devaluation, restructuring foreign-held debt) versus ad‑hoc, politically driven “vibe‑governing.”

De Minimis & Small Parcels

• Removal of the de minimis exemption from China (and a floor of $25–$50 or 30% per shipment) is viewed as a huge change:
  • Direct‑from‑China platforms (Temu, AliExpress, etc.) likely to become far more expensive or restructure via US/EU warehouses.
  • Expectation of chaos for small buyers used to cheap parcels, and higher courier fees for customs handling.

Global & Political Fallout

• Expectation of retaliation focused on US exports and digital services (cloud, ads, tech platforms).
• Concern that this accelerates de‑dollarization, weakens US soft power, and pushes countries toward EU/Asian arrangements or deeper ties with China.
• Many see this as alienating traditional allies more than adversaries, and as politically timed: impose pain now, partially roll back or offset with tax cuts before midterms.

Abuse, moderation, and compliance costs

• Users immediately question how “upload your static site” avoids illegal content.
• Some argue content moderation is extremely hard and the true reason many cheap hosts aren’t really sustainable.
• Others say it’s manageable even for small orgs using modern ML classifiers, which are light enough to run on commodity VPS CPUs.
• Pico states they run ML models to detect illegal content and use internal admin tools, banning quickly, and publish clear abuse/content policies.
• Debate whether this is really different from any other $2–$6/mo shared hosting or cheap VPS, which already host plenty of potentially illegal content.

Pricing, sustainability, and target audience

• Many praise the $2/month price as “fun” and low-friction, making experimentation easy vs typical $10–$15 subscriptions.
• Others worry it’s unsustainably low; support costs in SaaS can dominate and usually push pricing much higher.
• Counterpoint: this audience (SSH-using devs) is likely low-touch support; simple infra can run cheaply, especially with careful architecture.
• Co-founders say: there’s a free starter tier, $2+ for extra features; goal is to compete with a $5/mo VPS, target individuals/small teams prototyping, not enterprises, and treat it as a side project they themselves want.

Infrastructure, bandwidth, and regions

• Discussion that bandwidth is inexpensive at non-hyperscale hosts (e.g. Hetzner) vs major clouds.
• Commenters infer some infra uses Oracle Free Tier (10TB/month fits); founders confirm multi-cloud and list regions (US/EU).
• Bandwidth review at 10TB cap raises “what happens then?”; no detailed process described beyond manual review.

SSH access, tunneling, and corporate firewalls

• Many tips for tunneling SSH over nonstandard ports (443, 993), HTTPS, or corporate proxies; some mention DNS tunneling.
• Note that modern NGFWs can detect SSH protocol regardless of port, limiting these tricks.
• Pico’s tunnel service can expose local services (including databases) over SSH with auth; internally uses custom daemon and Unix sockets.

Security, TOFU, and trust

• Host keys are published over HTTPS for out-of-band verification; some argue this goes beyond classic TOFU, others say it’s still weak in practice.
• Concerns: onboarding docs don’t strongly steer users to verify host keys, encouraging “yolo” SSH on untrusted networks.
• Broader critique that SSH is ill-suited as a mass-signup app platform due to MITM and phishing-style risks.

Features, positioning, and comparisons

• Users like the SSH-first workflows: static site deploys via rsync/scp/sftp, prose.sh for blogging, tuns.sh for tunneling, pastes for pastebin.
• Some want Netlify-like extras (e.g. form handling for static sites); maintainers say they’re considering it.
• prose.sh is explicitly inspired by Bear Blog’s minimalist, no-JS aesthetic; pgs.sh is framed as Netlify-like for static hosting.
• Comparisons made to sr.ht, SDF, and GitHub Pages + Cloudflare; some note Cloudflare Tunnels offer similar functionality for free.

Open source and self-hosting

• Several people want to self-host especially the pastebin; maintainers confirm everything is open source and link the repos.
• Under the hood, they’ve migrated from Wish/Bubbletea to Vaxis for TUIs; tunneling builds on the sish project.

UX and documentation issues

• Reports of TUI quirks (focus issues on buttons, token/key creation needing Tab, fish shell oddities); maintainers acknowledge and plan fixes.
• Confusion around rsync --delete support due to contradictory docs; clarified as supported and docs to be updated.
• Some users struggled to find pricing; navigation was adjusted (“pico+” renamed to “pricing”).

Code of conduct and content policy concerns

• One commenter objects to the “hate speech” and harassment clauses in the CoC as overly broad and potentially abusable, especially in current political climates.
• No detailed response in-thread on how those rules are interpreted or enforced beyond the general moderation stance.

Trust and data exposure via tunnels

• A user worries about compromise risk when exposing localhost services through tuns.
• Pico notes they technically can subscribe to any tunneled stream but state they only inspect for illegal activity; they caution that you should not fully trust any external service.

Overall Reaction & Trust

• Many are pleased to see Mozilla/Thunderbird attempt a real business model and see this as their most realistic plan in years.
• Others say Mozilla has “lost its way,” citing the recent Firefox ToS/privacy uproar and past statements on deplatforming as trust-breaking; some explicitly won’t touch a Mozilla-branded email service now.
• Several point out that this is run by MZLA (Thunderbird’s for‑profit subsidiary), but many commenters treat “Mozilla” as one entity and judge it accordingly.

Competition & Value Proposition

• Most see Thundermail as competing more with Fastmail/Proton/Migadu/mailbox.org than with Gmail/365 directly.
• Skepticism: email hosting is a crowded, mature market with strong incumbents and years of lead; Mozilla is “late” and needs something clearly better than existing privacy‑oriented services.
• Some ask why they should pick this over Proton/Fastmail, especially if there’s no strong end‑to‑end encryption story.

Data Location, Jurisdiction & Privacy

• Strong concern that a US non‑profit/for‑profit, regardless of server location, remains subject to US government access.
• Several Europeans explicitly want non‑US providers; some say this alone disqualifies Thundermail as a “privacy” option.
• Others are cautiously accepting of Mozilla’s “no AI training, no ads, no data sale” language but still wary.

Domains, Lock‑In & Longevity

• Big thread on owning your own domain: strong consensus among technically inclined users that provider‑independent domains are key to avoiding lock‑in and mitigating provider shutdown or bans.
• Multiple people say they’d only consider Thundermail if it supports custom domains; using a @thundermail.com address is seen as risky if the service dies in 5–10 years.
• Some counter that most normal users will never run their own domain; others argue providers could make this turnkey.

Thunderbird Client Quality & Features

• Many long‑time users report Thunderbird as stable and reliable; a few report historic mailbox corruption.
• Widely reported pain points: sluggishness with 100k+ messages, mediocre search (especially “smart” relevance ranking), lack of “focused inbox” like Gmail, and UI slowness on large setups.
• Others say it’s still one of the best cross‑platform desktop clients and significantly better than webmail for multi‑account workflows.

Business Model, Pricing & Timing

• Thundermail will be paid initially, with a free tier possibly later. Some see this as smart (serve paying early adopters, control onboarding); others think “charging vs free Gmail” means it can’t “take on” Google in a mass‑market sense.
• Several doubt Mozilla’s ability to sustain the service long term given past product shutdowns; others note even non‑profits must be financially viable.

Tech Stack & Protocols

• Use of the open‑source Stalwart stack and JMAP support draws real enthusiasm, especially from people frustrated with IMAP and slow/complex webmail.
• Some worry about Mozilla “pushing” features (calendar/contacts) onto the Stalwart maintainer; others welcome a full OSS alternative to Gmail/Outlook with integrated mail, contacts, and calendar.

Miscellaneous

• Landing page and branding (“Thundermail”, domain choices like tb.pro) are criticized as awkward or amateurish.
• Mobile and web experience, focused inbox, aliases/catch‑all handling, and clear details on hosting locations are flagged as critical unknowns for adoption.

Use of Signal for Sensitive/Classified Communications

• Many commenters see the core issue not as “using Signal” per se, but using an unofficial, auto-deleting app to plan military operations and discuss intelligence, bypassing normal classified channels and records laws.
• Some argue the motivation is clearly to evade discovery, FOIA, and future oversight, not to improve security. Others note FOIA technically doesn’t cover parts of the White House, but record-keeping laws still apply.
• There’s dispute over whether Signal is even approved on government devices; one side cites testimony claiming it’s CIA‑approved and preloaded, another points to NSA documentation and former officials saying it was never allowed for official communications, even unclassified.

Security, Backdoors, and Government Reliance

• Several see this as a strong endorsement of Signal’s security: if senior officials choose it to evade US surveillance, it’s likely hard to break.
• Others push back, citing BlackBerry as precedent: governments will backdoor or work around “secure” systems and later find other access vectors (device compromises, exploits).
• Debate over whether government dependence on Signal makes backdoors politically or operationally impossible; skeptics invoke NOBUS logic and intra‑governmental factionalism.

OPSEC Failures and the Journalist in the Chat

• The accidental inclusion of a prominent journalist in a war-planning chat is widely mocked as “Veep‑level” incompetence.
• Explanations debated: fat‑fingered UI, contact syncing quirks, prior sourcing relationship, or deliberate leak. Most commenters lean toward repeated sloppiness rather than conspiracy.
• The fact that no participant noticed or questioned the presence of an unexpected number is seen as damning for their security culture.

Transparency, Records, and ‘End of History’

• Auto‑deleting Signal chats are likened to using voice calls: ephemeral by default. Some say the real violation is failure to document decisions, not the tool.
• Others argue that for top officials, ephemeral apps systematically destroy the historical record and democratic transparency, “ending history” by design.

Neglected Subtext: Yemen and Power

• Multiple comments argue the fixation on apps and classification distracts from the larger moral issue: casual discussion and apparent normalization of bombing Yemeni homes to kill one target.
• There’s criticism of US media for being structurally non‑adversarial on foreign policy, and of the public for caring more about process violations than about civilian deaths.