Oddbean new post about | logout
▲ ▼
brugeman | 9 months ago (raw) | root | parent | reply | flag +1 
 This project has nothing to do with opensats.

Re your other points I agree that we should provide much more customization. Which design elements you would like to exclude? Header?
▲ ▼
brugeman | 9 months ago (raw) | root | parent | reply | flag 
 We could provide just functions that accept username and handle the rest, then you could implement your own forms as you wish. These isn't much login in them aside from checking nip05
▲ ▼
ManiMe | 9 months ago (raw) | root | parent | reply | flag 
 Thanks. 
I’m still a bit foggy on the how various nip46 implementations work. (I imaging a lot of nostr users and nostr devs still are…tbh… given the recent “awareness” that original nsecbunker has access to read nsecs) Given this, I’m trying to wrap my head around the code your developed with `noauth`, `noauthd`, and `nostr-login`…

In the end, what’s important to me as a client dev is:

- what are minimum tools I need to implement “local storage” nip46 signin and signup form for my users?

- how do i host a “local storage” nsec bunker at my client domain? (if my new signups are gonna get a nip05 name out of it… I’d rather it be from my onboarding client domain… with integrated key management tools right there … cause first client “should be able to be” the only client a new user needs.)
▲ ▼
brugeman | 9 months ago (raw) | root | parent | reply | flag +1 
 To implement nip46 sign in simplest thing is nostr-login or nostr-ignition. Couple lines of code and your app can be signed into.

If you want to give new users your own nip05 you don't have to run the full nsec.app service - I can fire onAuth event on sign up and you can run users through your own onboarding and give them your own nip05. 

If you do want to host your own version of nsec.app I will have some instructions in readme soon.
▲ ▼
ManiMe | 9 months ago (raw) | root | parent | reply | flag +1 
 These are awesome tools!
My only concern with running either (nostr-login or nostr-ignition) is the lack of customizability. Thanks for offering. Because nostr-login supports “local naec storage”, I’ll use this. 

Yes please. I’d like to:
- add a “form only” component for nip46 signup (or signin) without the modal, modal header, or modal footer content. 
- run users through my own onboarding, and give them my own nip05 without needing to host nsec.app myself. (Without breaking “oauth” style nip05 signin flow for my new users in other clients?)
▲ ▼
ManiMe | 9 months ago (raw) | root | parent | reply | flag 
 P.S. I will prolly want to host nsec.app at my own domain in the future… or provide some affordance for new users to manage their keys from within the onboarding experience.
▲ ▼
brugeman | 9 months ago (raw) | root | parent | reply | flag +1 
 Nostr ignition seems to be functionally the same, both are a way to access keys using nip46. It's more customizable atm from what I read in their docs, although I am not sure how ready it is.

Thanks for your feedback I will get back to you when we have more customization options and onAuth event fired for you to run your own onboarding.