Communities, but they don't work well because the moderators has to approve every post, rather than every npub.
Discussion
And communities aren't real boards unless you have a board UI. Like, there are 3 different communities with the same topics, sometimes, and they can't find each other.
If there are 3 communities called "relays", they should be listed together in the UI, so that an npub can decide which ones he wants to follow. And they should be able to merge and fork or change ownership.
Wiki's can help solve this too.
On the page about "Relays" I want to see:
- wiki entries
- hashtags linked to this subject
- forums (group chats) that discuss this
- kind-1's about Relays
- articles about Relays
- ...
In short, displaying wiki entries is only the start
Yeah, I just had the same thought, since the Wiki has a composite page for each topic, that could serve as a jumping-off point.
Nostr allows for complex workflows because you can have a gazillion views and constellations of the same data set.
Yup!
I especially need these kind of pages for onboarding.
As in, I don't want to let users read my boring text about what relays are or make some sub-standard video about it.
I want to link to a Relay wiki that let's users discover what they are in whatever way they want.
For some that might be watching Instagram-like stories about it, for others it might be joining a forum full of golang geeks.
Yup indeed 🤦.
Group chats are the way.
Just have to clearly separate the "chat" from the "forum" side of things.
Chat is where you say GM.
Forum is where you start serious conversation threads.