Nostr Web Client

It would not be hard to adapt keys to relays in a transport-agnostic way. Just add a new event kind 3xxxx which means "I am a relay" with tags declaring relay address under different transport (wss, onion, etc).

> The reason that devs keep wanting to put logic directly into the relay is that nostr has no official spec for moderation of a relay and the nostr world is very opposed to talking about moderation or making it easy, so it is a green field.

This misses the point for me. Relays largely already have everything they need to do moderation (nip 56, auth, and deleting stuff), which means the best form of moderation is going to be implicit on the protocol level, explicit on the human level.

But I agree that the needs of a community for policy enforcement neatly match those of any kind of relay.

cloud fodder 11mo ago

nip56 was created to get damus into the app store. not a lot of thought was put into that.

what is missing is fine grain control. clients decided to send reports to all relays (flawed). imo to really manage a relay you are purposefully telling it what to do, and from the convenience of one key that you are reading the relay from. if you want to delete offtopic or etc from your relay, you do not care about other relays nor do you want to broadcast your actions globally for all time.

Reply to this note

Please Login to reply.

Discussion

hodlbod 11mo ago

For end users and moderators, I think nip 56 is perfect, since reporting should be declarative rather than imperative. For administrators who actually want to unambiguously delete stuff, NIP 86 is probably the right way.