Goodbye, and Thanks for All the Bikesheds
A retiring FreeBSD veteran’s ACM essay arguing that “tech bro” absolutism on encryption helped provoke harsh new age-verification and surveillance laws draws sharp pushback. Commenters counter that governments and large platforms have long abused any technical “compromise,” so creating even minimal backdoors or identity-linked age checks inevitably erodes anonymity, chills political speech, and threatens FOSS. The thread also touches on whether parental controls could be a less invasive alternative, who really drives these laws (voters vs. lobbyists), and how sustainable LLM-based code review and AI tooling will be once today’s investment bubble cools.
Blame, compromise, and “tech bros”
- Many reject the article’s claim that “tech bros” and absolutist privacy stances caused governments to overreact.
- Repeated argument: there is no meaningful “minimal compatibility” with surveillance; any technical opening will be expanded and abused (Snowden, Stingrays cited).
- Others say ignoring political reality was naive: if you design tools that deliberately block investigations, states will respond, and insisting on all‑or‑nothing privacy helps produce harsher laws.
Age verification, anonymity, and backdoors
- Strong concern that age verification schemes are functionally identity verification and will end anonymous speech, enabling retaliation and authoritarian abuse.
- Some argue the real goal is broader control: linking identity to speech/actions, with “protect the children” as framing.
- Counterpoint: specific laws (e.g., California’s) can be relatively light-touch—device-level age flags, self‑attested birthdates, bans on facial recognition—and may actually pre‑empt worse ID‑scan-based regimes.
Parents vs. state and platform responsibility
- One camp: age gating should be handled by parents using OS/browser parental controls; state‑mandated verification is overbroad and privacy‑invasive.
- Opposing view: parental controls are fragmented, hard to use, and many parents are overstressed, single, or tech‑illiterate; relying solely on them is unrealistic.
- Some propose device‑level “child lock” signals, or kids’ phones without social media, as middle ground.
- Broader critique: platforms and big tech externalized harms (social media, NCII, exploitation), and are now lobbying to shape inevitable regulation in their favor.
Impact on FOSS and general‑purpose computing
- Fears that age‑gating plus attested software and locked‑down devices will marginalize or outlaw:
- Alternative app stores and unsigned software (e.g., FOSS on mobile).
- Anonymous code contributions and non‑ID‑verified development.
- Others think sensible scoping (only preinstalled consumer OSes, reversible unlock at adulthood) would leave traditional FOSS largely intact.
LLMs, security, and “bubble” claims
- Article’s suggestion that LLM‑assisted code review won’t be a long‑term disruptor is contested.
- Some agree new tools mostly front‑load discovery of certain bug classes, then plateau like past static analyzers.
- Others say LLMs are already changing workflows, continue to find bugs, and state or adversarial actors will keep pushing capabilities, so their impact is ongoing.
Reception of the article
- Multiple commenters describe it as incoherent, defeatist, politically loaded, or sexist (especially around “tech bros/tech sisters” framing).
- A minority defend it as politically realistic and worth rereading for its warnings about state adaptation and FOSS’s future.