Really cool ⚡
What do you mean by "Only PUBLIC login available for outside domains." ? Thanks
We’re building an onboarding client to support friends inviting friends to nostr.
Beta release is almost ready to launch.
Follow nostr:npub1advc8wuyjh7e230xrpafhy2zd3f40kuy5yfat09zj27rcxzfg4ys997ukp for announcements and to be included in the awards program. Top Nostr advocates will be zapped every month!
Discussion
lol. Right now … password login isn’t even enabled. Working on this now.
But TBH, not happy with current nip 46 implementations. So, until I hand roll my own … only accounts @ nostrmeet.me will be able to login with nip05 and password.
Nip05 addresses will be given to all new accounts created (and will be available to advocates as well) This “oath style” login will only be available because new accounts created will have their nsec encrypted locally (with the password) and stored in “the cloud”. Login to the client again from anywhere to retrieve the nsec for use in other clients.
It’s still a WIP
Heres why we’re not gonna use nsec.app for onboarding …
> The smoothest mobile-first signup experience is when you just generate nsec in your client and eventually when user is ready start explaining to them how to get their nsec 'reused' in other apps.
nostr:note1svppcyasj4g9z3mz937zf456fs2n4qtzknd8mw030jqt0k4karusjmnkz3
So … the entire “invite experience” is usable by advocates with only npub or nip05 “public” login. Private login (will be) used for customizing and tracking invites. DM client will be integrated, so could also be used for that.
New “invited” accounts will be logged in privately with an nostrmeet.me nip05 from go. They will have access to DM chat with advocate, wot follow suggestions, client / relay discovery, and other onboarding tools.