Replying to Avatar elsat

I created test keys.

I understand your motivation, and know that this will preclude most people from using the app. Its akin to asking a gmail user to add pop3 and smtp servers, before they can send and receive emails.

Ideally you solution “autopilot” / outbox where the app is smart enough to figure out everything automagically. Specifying relays could be reserved for an unhappy path.

One of the things I am hearing from nostr users that have endured the pain and enjoy being here is that they dont have the patience to figure out specific purpose relay (e.g. for DMs).

Consider defaulting DMs relay for new users to one/a few DM relays like 0xchat relay, and importing DM relays for existing nsecs.

If existing nsecs dont have a relay DM, add whatever you think is best. Just dont wipe the relay list created in other apps.
Avatar
Patrick 5mo ago

Thank you again for this feedback! You're spot on that this is a hurdle for user adoption outside power nostr users.

I just pushed a new change that will remove the forced relay settings. We still check your npub for relay lists but if you don't have one it no longer forces you to settings to configure one. It will now just use a default list of relays inside the app (nostrcal, nostr.band, nostr1) and leave it up to the user to find their way to settings to configure their own 10050 lists in the future. We won't issue a 10050 unless the user wants one so we don't overwrite anything.

I also remembered that it didn't have proper NIP-59 support around RSVPs and took the time to get that sorted out. Now private RSVPs should check for the p tag's 10050 to broadcast to it instead of using their own 10050 lists.

Reply to this note

Please Login to reply.

Discussion

No replies yet.