Wow! Yeah that’s a good one! #[2]​ can we validate that the npub file value starts with npub word, so if you put nsec we detect it and show an error?

Reply to this note

Please Login to reply.

Discussion

the Password might get an nsec dropped in it

Yes, good edge case, will add the warning UI. Thanks a lot for the fresh eyes. 💜🧡

What about something like this? They can dismiss it.

public key(npub)

private key(nsec)

is bothering me still

maybe “Your npub (private key)”

“Password for nostr.build” might be enough

#[4]​what’s the best design to not screw this up?

The way I have it now;

- Registration asks for a user public key and will only take something starting with npub1

- Registration tells the user NOT to enter their private key and to enter a NEW password

- Login I don’t tell people that because I assume they paid attention at registration and used correct credentials