Replying to Avatar Vitor Pamplona

No, we can't. Either the sender of events MUST connect to 20 relays so that all 20 have the same info and receivers then don't need to connect to all 20 OR The sender just sends to ONE relay and receivers must connect to all 20 to get all events.

There is no "smart" way around this.

That's why keeping the list small is EXTREMELY important.
Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago 💬 1

then you might need to make some suggestions in the nips repo about nip-65 that there be a cap on this for these reasons

clients can then refuse to set more than this number, or crop them, and other clients will have to follow suit to help their users

Reply to this note

Please Login to reply.

Discussion

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i have 4, i think that's reasonable... two i pay for, 1 i host and one i manage from a hosting provider... i'd say probably the spec should stipulate "no more than 5" there's really no benefit from allowing more than 5 for in/outboxes

3 is probably enough for most cases but 5 is complete, you can't argue you need more redundancy than that