|
|
|
|
|
|
by jitl
674 days ago
|
|
|
I agree with the problem description but I don’t understand how RelayBeam is addressing the problem. If I use RelayBeam, how will that solve my overflowing inbox problem or information scattered across Slack threads/channels? It seems RelayBeam also has an inbox (it has N inboxes instead of one), and it encourages private messages between closed groups, which completely silos information making it worse than slack where at least most channels are open and you can go read the history when linked to gain context. |
|
|
Using ports (as inbox) users can segregate the messages as per the context, this should simplify the information management, because users can search for information in the relevant port.
Users can compose new threads for different topics of discussion, hence these threads will only be relevant with respect to their topics.
As and when the new messages keep coming, there will be some threads where the discussion is no longer active, and users don't need to keep track of such thread discussions. This should solve the problem of overflowing inboxes.
Do you have any suggestions on how this can be further improved? I'd be happy to discuss.