Platform scalability is and will always be terrible for the social media end user experience. Most of the issues I see is the lack of real time interaction like we had with IRC. A user shouldn’t be able to jump into a conversation on their lunch break 6 hours later because they see a post they don’t agree with. Users should be forced to respond in real time or lose access to the conversation.
Discussion
Should have a choice between static and dynamic engagement, but perhaps when the algorithms are completely removed, more of the dynamic is allowed to foster.
The nostr protocol should integrate something that allow Discord-like "channels" - maybe call them doors - tied to public keys. It would be a great integration for dynamic chat rooms and a great harkening back to mIRC. Let the naming convention for channels be whatever is typed between double hashtags, i.e. ##first door## for instance. The user/public key can carry these "doors" or "channels" with them, allow other public keys in, moderate them, remove them, etc.
I’m totally going to agree with you later this week sometime…
This is an interesting thought. I have been thinking a lot about how to use nostr like IRC. We need a nostrChat client...
1. client allows user to invtive npubs starting a chat
2. the user that starts the chat hosts it peer to peer: no relay needed, anyone can be invited
3. everyone that joins the chat is direct connected to the starting user's session (database)
4. database can be cleared after the chat ends, or the session can be passed off to any other user in the chat for them to host it.
Not sure if the protocol supports all that, but it should not be too much to add a nip. My idea of doing this peer to peer keeps from adding cost to the relays. Best way to code this would be an api that could be added to any client.