René Aaron on Nostr: 👀 ...
👀
nevent1qqsqwsev3yjctdz9erky4kcuaf4fjcppfr9r4wpm7k0fk6ndc0jpx6cppemhxue69uhkummn9ekx7mp0qgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75srqsqqqqqpudg
nevent1qqsqwsev3yjctdz9erky4kcuaf4fjcppfr9r4wpm7k0fk6ndc0jpx6cppemhxue69uhkummn9ekx7mp0qgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75srqsqqqqqpudg
quoting nevent1q…g4t2on the second flight I finished writing the implementation (and modifications to NIP-46) to make the following possible:
1. Alice goes to App A (e.g. Coracle) -- she clicks "create account" and gets a NIP-05 "alice@somesite.com". She uses Coracle as she normally would.
2. Alice goes to App B (e.g. Primal) -- she clicks "login" and types in "alice@somesite.com". A popup comes up and asks Alice if she wants to authorize this application to access her account. In an advanced setting She can scope down what the application can do (e.g. only create short notes but don't change the profile data)
At no point is there any mention of nsec, npub, keys, NIP-07, nsecbunker. Nothing. It just works.
cc Karnage (npub1r0r…q9ac) miljan (npub16c0…6nvr) Rabble (npub1wmr…g240)