FoxByte on Nostr: How do we force code owners to change their code? How do we force relays ...
How do we force code owners to change their code? How do we force relays configuration to send notifications on deletes. I think this is a nonstarter because it presupposes any ability to control others (namely relay operators). Even if it got added to the protocol spec, nobody HAS to implement it. I just dont see how this is possible... If we could FORCE relay operators to send notifications on deletes, then what else could we FORCE them to do? Slippery slope IMO.
#Nostr is the bazaar model. Anything goes, and there is very little control. I think really what needs to happen here is that if you want to have the ability to control what gets deleted and why, then you setup your own relay. If you want to notify people on deletes, do it, and advertise it so people use your relay over other relays.
#Nostr is the bazaar model. Anything goes, and there is very little control. I think really what needs to happen here is that if you want to have the ability to control what gets deleted and why, then you setup your own relay. If you want to notify people on deletes, do it, and advertise it so people use your relay over other relays.