I'm thinking, what was the point in Nostr if things can get blocked , taken down by relay hosts. For which most people use the same few big ones. Its better than twitter but only on par with mastadon (which is also more reliable )
Discussion
Nostr provides censorship resistance through replication. You use multiple relays. If stuff is taken off one of those relays you are not censored, you just have 1 fewer replication points. At that point you go add another relay to your relay list.
I am not suggesting censorship, nor am I promoting it. I have no intention of sending anybody such a message. But I develop the chorus relay, and some operators will censor stuff, and I wanted to add code to make sure that when this does happen at least the person being censored finds out about it.
I am just wondering what is the best way to handle a large stack of DM messages to a friend list that should not be made public. do we giftwrap all of them or pick a select relay that is app specific for this stack of DMs?
the "right way" to do things on nostr feels like its moving and changing constantly so I am just asking
I'm not familiar enough with the DM chat NIPs to answer this with any confidence. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn and nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 all know more than me about multi-party DM.
I don't know if I follow? Can't you just send each as a separate event?
You could but if a big stack of DMs goes to a large relay they can rate limit or block, as it can look like spam.
cc: npub1ymt2j3n8tesrlr0yhaheem6yyqmmwrr7actslurw6annls6vnrcslapxnz
Just pick 2+ relays for your kind 10050 relay list and you should be good. Local backups are a good extra measure, either on a local relay or using a jsonl file.