Vitor Pamplona on Nostr: There are always 4 ways to implement something in Nostr: 1. Bound to a relay 2. Bound ...
There are always 4 ways to implement something in Nostr:
1. Bound to a relay
2. Bound to a client
3. Bound to a key
4. Bound to an event
Communities, for instance, can be assembled at:
1. The relay level: pick a relay to join (NIP-29). The relay operator moderates the conversation and decides who can participate in. It centralizes in the relay itself. Forks are possible but hard to execute because it requires everyone to migrate their own settings. Whoever controls that relay can rug pull everybody.
2. The client level: pick a hashtag, label (NIP-32) and WoT algo to assemble the community's feed. The client moderates the conversation. It's fluid. No one controls the hashtag or the topic of the discussion. There are not master relays to get posts from. The conversation can be broken as separate users might use different relays and thus will see different things. Consistency is among users is not great. Rug pulls can only happen if the Client itself is affected.
3. The key level: pick a key to tag when talking about a topic that the key itself defines. The key controller defines the topic and thus, unlike hashtags, can change its picture/description over time including the choice of preferred relay to gather all comments. But the key cannot on itself moderate unless it also controls the preferred relay to delete posts. Rug pulls can happen by the key controller or if that key is stolen.
4. The event level: pick an event that describes the community (NIP-72, NIP-28). Moderation happens by admins marked in the event itself in any relay. Clients just obey the NIP to display approved posts. Moderation happens via Nostr events and are set for everyone participating in the discussion. Those moderators can rug pull the community.
Pick your poison.
1. Bound to a relay
2. Bound to a client
3. Bound to a key
4. Bound to an event
Communities, for instance, can be assembled at:
1. The relay level: pick a relay to join (NIP-29). The relay operator moderates the conversation and decides who can participate in. It centralizes in the relay itself. Forks are possible but hard to execute because it requires everyone to migrate their own settings. Whoever controls that relay can rug pull everybody.
2. The client level: pick a hashtag, label (NIP-32) and WoT algo to assemble the community's feed. The client moderates the conversation. It's fluid. No one controls the hashtag or the topic of the discussion. There are not master relays to get posts from. The conversation can be broken as separate users might use different relays and thus will see different things. Consistency is among users is not great. Rug pulls can only happen if the Client itself is affected.
3. The key level: pick a key to tag when talking about a topic that the key itself defines. The key controller defines the topic and thus, unlike hashtags, can change its picture/description over time including the choice of preferred relay to gather all comments. But the key cannot on itself moderate unless it also controls the preferred relay to delete posts. Rug pulls can happen by the key controller or if that key is stolen.
4. The event level: pick an event that describes the community (NIP-72, NIP-28). Moderation happens by admins marked in the event itself in any relay. Clients just obey the NIP to display approved posts. Moderation happens via Nostr events and are set for everyone participating in the discussion. Those moderators can rug pull the community.
Pick your poison.