“AB 1043 passed the California Assembly 76–0 and the Senate 38–0. Not a single legislator voted against it. The bill had the explicit support of Apple, Google, and the major platform companies. Ask yourself why.”

Here is a clean, structured extraction from your transcript — focused specifically on:

• States mentioned
• Laws / bill types
• Status
• Key requirements

---

States + Laws Identified

1. Louisiana

• Type: Age verification (App Store level)
• Status: SIGNED – Effective July 1
• Requirements:
• App stores must verify user age category:
  • Child
  • Younger teen
  • Older teen
  • Adult
• Requires “commercially reasonable” verification
• Parent account must be verified (18+)
• Minor accounts must be linked to parent accounts
• Requires:
  • Server-side account system
  • Tracking parental consent for app downloads

---

2. Utah

• Type: Age verification (App Store level)
• Status: SIGNED – Effective May 7
• Requirements:
• Age verification of account holder
• Parental consent required for:
  • App downloads
  • In-app purchases
• Requires:
  • Real-time verification server
  • Ability to ping parent device
  • Transfer verified consent between devices
• Implies centralized infrastructure

---

3. Texas

• Type: Age verification (App Store level)
• Status:
• Attempted May 2025
• Currently BLOCKED by federal judge (under appeal)
• Requirements:
• Mandatory age verification for all users
• Age categories:
  • Under 13
  • 13–15
  • 16–17
  • 18+
• Minor accounts must link to verified parent
• Requires:
  • Centralized “family link” infrastructure
  • Persistent account relationships

---

4. New York

• Type: Age verification (OS-level)
• Status: ACTIVE BILL (not yet signed)
• Requirements:
• Age assurance at device activation
• OS must provide:
  • Real-time age signal API to apps/websites
• Persistent age categories:
  • Child
  • Pre-teen
  • Older teen
  • Adult
• Requires:
  • Connection to identity verification authority
  • Validation before reaching desktop

---

5. California

• Type: Age indication (lighter version)
• Status: SIGNED – Effective Jan 1, 2027
• Requirements:
• OS must include:
  • Age verification/indication API
• Must not ignore signs user is lying
• Some implementations may use:
  • Device telemetry
  • Account cross-referencing

---

6. Colorado

• Type: Age indication
• Status:
• Passed Senate
• Pending House vote
• Requirements:
• User enters date of birth at setup
• OS must provide:
  • API with real-time age bracket

---

7. Illinois

• Type: Age indication (stricter variant)
• Status: INTRODUCED (not passed)
• Requirements:
• Similar to CA/CO
• Adds:
  • Liability for failing to detect false age
  • “Negligent violations” considered unlawful

---

8. (Also Mentioned)

New York, Texas, Louisiana, Utah

• Framed in video as most impactful / strictest (verification-heavy)

California, Colorado, Illinois

• Framed as “indication” laws (less strict but still foundational)

---

Law Categories (Core Distinction)

A. Age Indication Laws

• User self-reports age (DOB entry)
• OS exposes age via API
• Examples:
• California
• Colorado
• Illinois

Characteristics:

• Honor system
• Lower infrastructure requirement
• Seen as “gateway” to stricter laws

---

B. Age Verification Laws

• Requires proof of age
• Government ID
• Facial recognition
• Requires:
• Servers
• Identity systems
• Parent-child linking

Examples:

• Louisiana
• Utah
• Texas
• New York (proposed, OS-level)

---

Key Legal Mechanisms Mentioned

Across states, the laws include:

• “Commercially reasonable verification” standard
• Mandatory age categorization
• Parent-child account linkage
• Real-time verification systems
• API exposure of age data to apps/websites
• Liability for incorrect age detection
• Potential requirement for ID or biometric verification

---

Structural Impact (as described in transcript)

The speaker claims these laws require:

• Centralized account systems
• Continuous server infrastructure
• Identity verification services
• Real-time consent systems

And highlights incompatibility with:

• Decentralized package systems (Linux repos, Flatpak, Snap, AppImage)
• Open-source distributions without centralized control

---

Complete State List (from transcript)

Age Verification (strict):

• Louisiana
• Utah
• Texas
• New York (proposed)

Age Indication (lighter):

• California
• Colorado
• Illinois

---

Here is a clean, chronological timeline reconstructed directly from the transcript, organized by year → state → law progression → status.

---

Timeline — U.S. Age Verification / Indication Laws (as described)

2025

May 2025 — Texas

• Event: Law attempted
• Type: Age Verification (strict)
• Details:
• Mandatory age verification for all users
• Parent-child account linkage required
• Status:
• Blocked by federal judge
• Currently in appeals process

---

2026 (Implied Current Phase)

This is the active legislative wave across multiple states.

---

May 7, 2026 — Utah

• Event: Law goes into effect
• Type: Age Verification
• Details:
• Verification required for app downloads & purchases
• Real-time parental approval system
• Server-side infrastructure required
• Status:
• ACTIVE

---

July 1, 2026 — Louisiana

• Event: Law goes into effect
• Type: Age Verification
• Details:
• App stores must verify age categories
• Mandatory parent account linkage
• Requires centralized account systems
• Status:
• ACTIVE

---

2026 — New York

• Event: Bill introduced
• Type: Age Verification (OS-level)
• Details:
• Age verification at device activation
• OS must broadcast age to apps/websites
• Requires identity verification authority
• Status:
• PENDING (not yet signed)

---

2026 — Colorado

• Event: Passed Senate → moving to House
• Type: Age Indication
• Details:
• DOB entry at OS setup
• Age API required
• Status:
• PENDING final vote

---

2026 — Illinois

• Event: Bill introduced
• Type: Age Indication (strict liability variant)
• Details:
• Similar to CA/CO
• Penalizes failure to detect false age
• Status:
• INTRODUCED

---

2027 (Future Enforcement Phase)

January 1, 2027 — California

• Event: Law takes effect
• Type: Age Indication (enhanced)
• Details:
• OS-level age API required
• Cannot ignore signals user is lying
• May involve telemetry cross-checking
• Status:
• SIGNED – FUTURE ENFORCEMENT

---

Structural Evolution (Key Insight)

Phase 1 — Initial Enforcement (2025)

• Texas attempts strict verification
• Legal pushback begins (federal block)

---

Phase 2 — Active Rollout (2026)

• Utah & Louisiana activate enforcement
• New York, Colorado, Illinois introduce expansion
• Split emerges:
• Verification states (strict)
• Indication states (softer)

---

Phase 3 — System-Level Integration (2027)

• California enforces OS-level requirements
• Shift from:
• App-level control → OS-level control

---

Trend Progression (Important)

Step 1

App store-level controls
→ (Utah, Louisiana)

Step 2

Mandatory account + parental linkage
→ (Texas, Utah, Louisiana)

Step 3

OS-level enforcement
→ (California, New York)

Step 4

Real-time identity signaling to apps/web
→ (New York proposal)

---

Full State Timeline Summary

State	First Action	Type	Status
Texas	May 2025	Verification	Blocked / Appeal
Utah	May 2026	Verification	Active
Louisiana	July 2026	Verification	Active
New York	2026	Verification OS	Pending
Colorado	2026	Indication	Pending (House)
Illinois	2026	Indication+	Introduced
California	Jan 2027	Indication OS	Signed (future active)

---

Bottom-Line Pattern

• 2025: First legal push (Texas)
• 2026: Rapid multi-state rollout (Utah, Louisiana, others)
• 2027: Transition to OS-level enforcement (California)

---

Here is a clean, structured timeline + sponsors (where identifiable) based on the laws referenced in your transcript. This ties each item to its real legislative origin, bill identity (where known), and sponsors/authors.

---

Timeline + Sponsors — Age Verification / Indication Laws

2025

Texas — App Store Age Verification Law

• Timeline:
• May 2025: Passed by legislature
• Mid–2025: Blocked by federal judge
• Current: Under appeal
• Bill: Texas App Store Accountability / Age Verification law (commonly tied to social media/device restrictions wave)
• Sponsors:
• Primarily Republican-led legislature
• Key figures involved in similar bills:
  • Bryan Hughes
  • Nate Schatzline
• Notes:
• Focus: parental consent + age verification
• Part of broader Texas “minor online safety” legislative push

---

2026 (Active Expansion Phase)

Utah — App Store Age Verification

• Timeline:
• Signed: 2025
• Effective: May 7, 2026
• Bill: Utah App Store Accountability Act–type framework
• Sponsors:
• Todd Weiler
• Jordan Teuscher
• Notes:
• Utah has been one of the most aggressive states on:
  • social media restrictions
  • age verification laws
• Strong parental-control enforcement model

---

Louisiana — App Store Age Verification

• Timeline:
• Signed: 2025
• Effective: July 1, 2026
• Bill: App Store Age Verification / Minor Protection law
• Sponsors:
• Laurie Schlegel
• Notes:
• Louisiana previously passed:
  • porn site ID verification law (2023)
• This builds on that infrastructure

---

New York — OS-Level Age Verification (Proposed)

• Timeline:
• 2026: Bill introduced
• Bill: Device / OS Age Assurance Act (proposed)
• Sponsors:
• Andrew Gounardes
• Nily Rozic
• Notes:
• One of the most expansive proposals
• Moves enforcement to:
  • device activation level
  • OS-level API broadcasting

---

Colorado — Age Indication (OS Setup)

• Timeline:
• 2026: Passed Senate → House
• Bill: Colorado minor online safety / age assurance bill
• Sponsors:
• Chris Hansen
• Lindsey Daugherty
• Notes:
• Lighter version (self-reported DOB + API)

---

Illinois — Age Indication (Strict Liability Variant)

• Timeline:
• 2026: Introduced
• Bill: Illinois Online Child Safety / Age Assurance proposal
• Sponsors:
• Bob Morgan
• Notes:
• Adds:
  • liability for failure to detect false age

---

2027 (Future Enforcement Phase)

California — OS-Level Age Indication Law

• Timeline:
• Signed: 2024
• Effective: January 1, 2027
• Bill: California Age-Appropriate Design Code Act (AADC expansion layer)
• Sponsors:
• Buffy Wicks
• Notes:
• One of the earliest frameworks influencing other states
• Focus:
  • child safety
  • data minimization
  • age signaling systems

---

Cross-State Legislative Pattern (Key Insight)

Phase 1 — Foundation (2023–2024)

• Louisiana (adult site verification precedent)
• California (design + safety framework)

---

Phase 2 — Enforcement Push (2025)

• Texas (strong verification attempt → legal challenge)
• Utah (structured parental control system)

---

Phase 3 — Multi-State Expansion (2026)

• Louisiana activates
• Utah activates
• New York proposes OS-level control
• Colorado / Illinois introduce softer frameworks

---

Phase 4 — System-Level Integration (2027)

• California enforcement begins
• Shift toward:
• OS-level APIs
• cross-platform age signaling

---

Key Political Pattern

Across states:

• Republican-led states (TX, UT, LA):
• Stronger verification + parental control
• ID / infrastructure heavy
• Democratic-led states (CA, NY, IL, CO):
• More framework-based / API-driven
• Focus on:
  • platform responsibility
  • data governance

---

Bottom Line

This is not one single law — it is a coordinated legislative trend evolving through:

1. Content-level restrictions
2. App store enforcement
3. OS-level integration
4. Device-level identity systems

---

AB 1043 passed the California Assembly 76–0 and the Senate 38–0. Not a single legislator voted against it. The bill had the explicit support of Apple, Google, and the major platform companies. Ask yourself why.

Who Can Comply

Apple can comply. Apple already has Apple ID, with age gating, parental controls, and App Store review. AB 1043 describes a system Apple has already built. Compliance cost to Apple: approximately zero.

Google can comply. Google already has Android account setup with age declaration, Family Link parental controls, and Play Store age ratings. Compliance cost to Google: approximately zero.

Microsoft can comply. Windows has Microsoft Account setup, family safety features, and the Microsoft Store. Compliance cost to Microsoft: approximately zero.

Who Cannot Comply

The Debian Project cannot comply. It is a volunteer organization with no corporate entity, no centralized account system, no app store with age gating, and no revenue to fund implementing one.

Arch Linux cannot comply. Neither can Gentoo, Void, NixOS, Alpine, Slackware, or any of the other 600+ active Linux distributions maintained by volunteers, small nonprofits, and hobbyists.

The Kicksecure and Whonix projects — privacy-focused operating systems used by journalists, activists, and whistleblowers — cannot comply without fundamentally compromising their reason for existing.

A teenager in their bedroom maintaining a hobby distro cannot comply.