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.

Reply to this note

Please Login to reply.

Discussion

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.