In the early internet, only academics and researchers had access.
And every time a company has been hacked to hell because an employee opened some malware personal email, I have pounded the table for a separate internet for business and personal stuff, within an organization.
Overlap? Do you want kids buying stuff on Amazon (or other presumably non age-gated site?) Well, that's above my pay grade to solve.
So, there's an example of division within a site.
No "answer this question" such as "Who is Adlai Stevenson", providing that Claude and others get it wrong and you have to remember (IP-block Google).
Just musing.
This project has been kicking around in my head since I first heard about the webauthn PRF extension in early 2024. I've slowly chipped away at it since, and finally got things to a shareable state over the summer thanks to a very fun parental leave. Headed back to work tomorrow, so I figure there's no time like the present.
Since the blog post covers the why more than the how, here’s a technical tl;dr:
A client-held encryption key derived during passkey authentication encrypts all sensitive user data prior to persistence so that only the user is able to decrypt and reuse that data on their device. This allows short-lived, privacy-preserving age proofs to be issued to requesting applications (18+, no PII shared) without requiring users to re-upload their documents. The SSO user experience is built on top of the OAuth 2.0 Authorization Code Flow.
Demo video, high-level architecture, and FAQ can be found at https://loginwithone.com
Very open to feedback, and happy to answer any questions about the architecture, PRF/passkey encryption, or anything else!