Added this - the last param to connect and create_account is the list of requested permissions, i.e. sign_event:1,sign_event:3 implemented at nsec.app and nostr-login, check in action on nostr.band. Any feedback? Should we be adding this to nip46?

Reply to this note

Please Login to reply.

Discussion

Yep, we already use a similar thing for Amber, nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5

I think Amber and nsecbunker do something like this already. I agree, it would be nice to formalise it in the spec.

Yeah, this sounds reasonable to me

Isn’t it too complicated for normies to understand technical/dev terms without a clickable explanatory statement?!

We're discussing the protocol level, the UI on screenshot is just the first implementation of it, we will make it more meaningful and simple later.

Excuse me for interfering in your technical discussion and allow me to annoy you with another question; Nostr provides some addresses such as NIP-05 (account verification address) or Alby’s addresses etc., wouldn’t it be useful to allow users to have email accounts using the obtained addresses?! (So that the email and the generated password can be connected somehow to any Nostr client without the nsec and used for third-party login?!

Sorry, I didn't mean to discourage you from providing feedback.

Some nip05 services also provide email service using the same name, but not sure if that's relevant here.

The nip05 and password can be used to sign in to (soon to be) any nostr client using nsec.app or other nip46 implementations. Try signing up on nsec.app (or import your relay keys there) and then you can use your name@nsec.app to sign in to nostr clients like Nostrudel, Snort, Habla etc.