Video summary

California Just Exempted Linux From Age Verification

Main summary

Key takeaways

News and Commentary

Summary of the video (California age-verification law: “Good, Bad, and Ugly”)

Main report / news point

The video discusses California bill AB 1856, which the creator says is headed toward implementation around 2027. The creator argues that the bill functions as a form of age-gating at device/app setup: operating systems must collect an age indication (birth date, age, or both) from the user at account creation—but without ID verification.

Specifically, as described in the video, the bill does not require:

  • IDs/passports/selfies
  • Credit card checks
  • Database lookups

The creator claims the bill passed overwhelmingly (Senate 39–0, Assembly 69–0) and was unsigned by Newsom at the time of recording.

“Good” (what the creator views as improvements)

The creator highlights three main “good” points:

  1. Linux/open-source operating systems are exempt (based on how the creator reads the bill).
  2. The bill nearly expanded to cover the web (sites/browsers) but did not—which the creator frames as a larger win than the Linux exemption.
  3. The approach is described as less invasive than identity verification, because it relies on self-reported age brackets rather than authentication.

“Bad” (exemption loophole and likely uneven impact)

The creator argues the exemption may be narrow and misaligned with how the ecosystem works:

  • They believe the exemption may apply to “operating system provider” definitions, not app/developer definitions.
  • As a result, they suggest many open-source apps and tools could still be required to request age signals, including examples mentioned:
    • Brave Browser
    • ProtonVPN
    • ProtonPass
    • Onion Browser
  • This raises concerns about how an independent app developer could comply without wanting to collect user data.

The creator also suggests the policy could work like a “gateway”: once an app legally receives the age bracket, additional child-safety-related obligations could follow.

They emphasize that the creator is not a lawyer, but still sees potential for liability and pressure on developers, even if the law doesn’t require strict ID checks.

“Ugly” (broader implications beyond the tech)

While some privacy advocates propose solving these issues with technology (e.g., zero-knowledge proofs), the creator argues the problem isn’t purely technical:

  • The system still effectively splits the internet into restricted vs. unrestricted access.
  • Even without formal verification, access depends on the claimed age, creating a parallel information environment.
  • They use a library analogy: broad restrictions lead to constant questions like what qualifies as “not fit for children,” how to handle edge cases (e.g., an older-than-expected youth needing adult materials), and whether adults can bypass restrictions on a child’s behalf—ultimately constraining freedom of information structurally.

Creator’s thesis / conclusion

  • The creator frames the bill as the best possible version, since it avoids IDs, biometrics, and birthdays treated as verified facts.
  • However, they still oppose the overall idea of age-gating, because it inherently segments access and changes how information is distributed.

Action steps recommended in the video

  1. Check your device settings now — the creator notes age controls already exist on iOS in some regions, including Apple account/app age settings.
  2. Start with practical privacy tool changes rather than switching OS immediately (e.g., browser, VPN, password manager). Prioritize tools that handle data sensitively—or ideally don’t request it.
  3. Engage politically/industrially: contact companies and politicians. The creator claims earlier versions were worse (no open-source exemption and broader web coverage) and that advocacy helped narrow the final outcome.
  4. Subscribe/join for updates, including:
    • newsletter
    • private signal group
    • RSS feed (all referenced as links/resources)

Sponsor segment (privacy/security money angle)

A sponsor promotes Cake Wallet, described as an open-source non-custodial wallet (not tied to a single coin), emphasizing privacy and reducing reliance on identity-based banking checks.

The creator cites an example in which Cake Wallet’s creator (“Vic”) had a Chase account frozen after a flagged transaction.

Presenters / contributors

  • Techlore video creator / presenter (unnamed in the subtitles)
  • Cake Wallet sponsor (Vic) — referenced as CakeWallet’s creator

Original video