What client?
FROST bunker requires a little update: all bunker uris before had the user pubkey on them, so instead of calling get_public_key clients were just taking the pubkey from the uri; FROST bunker can't support that, it uses a different key for each user, not the actual user's key, so clients have to call the get_public_key method.
Yeah thanks, I know about that upgrade - just didn't get to that issue due to old ndk misbehavior. Now implementing it in nostr-login, thanks for the push.
Btw frost bunker can't do nip04/nip44 encryption/decryption, right?
Exactly, it is an inherent limitation.
Imho we put too much into that identity stuff. It makes onboarding unnecessarily difficult.
What do you mean?
What's the meaning of that characters?
Nice answer 😁 Anyway, if there should be accountable adaption, nostr needs different Auth. Nobody wants to share their secret with one or many service. I.e. a delegation signing key per service, created while onboarding, secured by passkey etc. Every other approach imho is distortion...
Bunkers have exactly this goal, they are revocable tokens used to sign events.
Thanks nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk, and sorry that I was to lazy to read the complete thread. Than bunkers are great 😁
