Age Assurance Is an Identity Infrastructure Problem
Why age assurance should be treated as an identity, privacy and infrastructure problem, not merely a child-safety compliance step.
Read time is estimated dynamically rather than using a flat words-per-minute figure. I start with a base speed by writing type then adjust for how airy or dense the piece is.
Notes use a base speed of 230 WPM, article uses 210 WPM and research or PoC work uses 190 WPM. The estimate then adds +5 WPM per major heading, capped at +20 and +3 WPM per substantial text break, capped at +12.
It subtracts 8 WPM for each genuine fenced code block, 6 WPM for each markdown table and 5 WPM for each embedded image. The adjusted speed never drops below 140 WPM and the final read time is the word count divided by that adjusted speed, rounded up to the next minute. Inline code styling on its own does not count as a code-block penalty.
RSS is a standard feed format that lets you follow this writing in a feed reader without checking the site manually.
The feed lives at /rss.xml and includes published writing entries only, using the latest revision of each piece rather than every historical version.
If you use Feedbin, NetNewsWire, Reeder, FreshRSS or another reader, add https://steadytao.com/rss.xml to subscribe.
6 results
Why age assurance should be treated as an identity, privacy and infrastructure problem, not merely a child-safety compliance step.
Why modern DNS now carries connection policy, privacy bootstrap material and edge configuration, with practical consequences for operators and tooling.
A protocol-level walkthrough of what can happen between name resolution and the first HTTP request on a modern HTTPS connection and why DNS now participates in bootstrapping transport, protocol and privacy decisions.
A high-level write-up on CVE-2026-33825, public disclosure and why Defender local privilege escalation deserved the urgent attention it was given.
Why inventory, discovery and readiness come before algorithm replacement.
A Caddy case study on why RFC compliance alone does not settle implementation strategy.
Try removing one or more filters or adjust the search query.