really needs a minimal pairing of a relay-selective kind-1 client and a simple way for write permissions to be set up that doesn't bleed over into other clients (so, a special admin permissions based list), and yes, a relay that also understands this scheme
#realy and #jumble could be a good combo for this
gonna of course be thinking about it more, try and figure out a plan
nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h is building a nice terminal based nip-17 chat client, perhaps we can come up with a plan
This sounds like the communities I'm building for.
For proper NIPs publishing and discussions, you at least need:
:wiki: Wikis for the actual NIPs (that can be targeted at the concerning communities)
:thread: Forum-like posts/threads
:chat: Chat
Having all other content types + zaps as a byproduct is great.
Wikis of the NIPs should then probably also be indexed in a 30040 event (type: documentation) to be rendered and organised properly.
yep, that's the general overview of what #gitcitadel is for
from the beginning it has been about opening up the discussion, i think you would have to be completely retarded to think that the current nips repo and cadre of nip guardians are doing this the right way
for a start, most of them are literally not server developers, so letting them dictate protocol seems like a really silly idea to me
