Thank you for the hint on mobile extension behavior. Will move the Sign in with extension button to advanced section in case where extension isn't yet 'authorized'.

> Nip 46 is supposed to fix issues with mobile app login … but nsec bunker holds private keys in custody … so “Nostr login” was created as a “local storage” implementation. 

Nostr login is not a "local storage" implementation. This sentence makes no sense to me. And even if you meant nsec.app instead of nostr login, it follows nip46 spec and doesn't invent anything proprietary wrt nip05 addresses etc.

> Nostr login requires what “looks like” a Nip05 address, but IS NOT.

It is nip05 address, you can have many of them, your nsecbunker/nsec.app issues one for you, as per nip46 spec.

> There’s not even a name to call this email looking address you’re “supposed” to enter … but it’s only available at one of two domains.

We call it username. And it's available on all modern nip46 services, except for locally-hosted ones like Gossip app.

> ALSO not explained is the fact that it’s “non custodial” (users have no idea) AND once you create one you have to remember it IN ADDITION to the Nip05 address AND Zap address that are ALL essential parts of Nostr.

You're probably speaking about nsec.app's 'non custodial' nature? It's not directly related to nostr-login library, but yes - I don't like it that you have to remember yet another username/nip05 address to login. I have some ideas here, thank you for reminding me.

> This is a MESS.

It is, this whole Nostr thing is a giant mess. It's our job to both create it and to manage it. Thank you for participating.