nip29 is not private or encrypted in any way, its just a way to do community groups without tons of noise.. if you run the relay, then it's more hidden because you can gate reading with auth.. #nerdstuff
Login to reply
Replies (9)
(so, similar to IRC but with nostr ident) an IRC server also can see everything..
So the relay runner can see all, ya?
my jumble fork at
supports these rooms also i think

Smesh
A user-friendly Nostr client for exploring relay feeds
on mobile this app has some serious bugs. mostly the reply in thread view can quickly fall off the bottom of the page and doesn't allow scroll. i'm fixing that now and also making the post open the feed page where it inlines the compose at the top of the feed for OPs. the not-jumping-to-feed for compose is just annoying but the reply modal is impossible to use effectively. i hate react.
yes, the relay holds a key and is a superuser. nothing is encrypted, and that relay key also manages the groups on the relay (like a bot)
Yeah, that's why I'm not a fan.
@npub1t7el...tg0z @npub1l8tl...5t9v Nostrord usa nip29
Primeiro parágrafo:
This NIP defines a standard for groups that are only writable by a closed set of users. They can be public for reading by external users or not.

GitHub
nips/29.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
Em metadados:
private indicates that only members can read group messages. Omitting this tag indicates that anyone can read group messages.
restricted indicates that only members can write messages to the group. Omitting this tag indicates that anyone can send messages to the group.
hidden indicates that relays should hide group metadata from non-members. Omitting this tag indicates that anyone can request group metadata events.
closed indicates that join requests are ignored. Omitting this tag indicates that users can expect join requests to be honored.