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.

Reply to this note

Please Login to reply.

Discussion

Great points! I had debated going the route of auto assigning 10050 if none was found but was afraid a user may use a relay I didn't query and end up overwriting their desired ones. I just noticed that I'm suggesting general relays over DM relays too at the moment so will get that fixed so it at least gives a solid default list and will consider best ways to ensure defaults better.

nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl what do yall recommend for DMs relay approach for a calendar app, used by general nostr enjoyers?

auth.nostr1.com is good

How does nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgdwaehxw309ahx7uewd3hkcqpqtm99pgz2lth724jeld6gzz6zv48zy6xp4n9xu5uqrwvx9km54qaq743a4w handle managing 10050 lists if it doesn't find one on a user? Are you auto assigning relays if they don't have any?

If there is no 10050 list, the message will be sent to the recipient's inbox relay. If there is no inbox relay either, the message will fail to send.

I'm thinking I'll update to check for 10050, if none set then use a default list of 10050 relays automatically until the users issues their own 10050 set. Right now we're set to force you into settings to define the 10050 set if you don't have one.

auth.nostr1.com is only choice for now. I've a domain nip17.com, I will setup a dm relay for it, but I didn't have time yet.

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.

This post has sat in my mind for a week now and it's because nostr:nprofile1qqspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03qppamhxue69uhkumewwd68ytnrwgqs6amnwvaz7tmwdaejumr0dsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7m7dh6a is right. NostrCal will need a reliable free option for public and private events to showcase how nostr can be better. I'm going to buy a new SSD today and use some hardware I picked up from nostr:nprofile1qqsplqcdmp63xzcnf7ln7faxnmkdscf6fxt53fcmtgn35uvlawhpfmgpzpmhxue69uhkummnw3ezuamfdejszrthwden5te0dehhxtnvdakqz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wspyfxrn last year to deploy a new version of relay.nostrcal.com that won't have a charge for using it. I'd certainly recommend looking at some paid plans from someone like nostr.land if you want long term private event storage but this will at least ensure users have a better first touch when exploring the app for the first time.

nostr:nevent1qqsf3jwkpzuqyt59h4ypmhd20ukrh0s57m3jyq7pcxjstyje4mrtn0spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqh2wxu9f38d8gfgsl33smuhc6cl26mh7vpzu6592nutlchrmthcspsgqqqqqqs3krppd