Clearly, as a team-communication tool, this is problematic to universally mute a colleague (e.g. what if they actually need to use the tool for a work-critical task)
Perhaps this can be
1) channel specific: "This person has smart things to say about Project Blue, or the For Sale, but I don't need to know their opinions in ~coffee"
2) limited only to channels with more than n number of members. That way, smaller project channels will enable unfettered communication, but users can curate their content in large interest-based channels.
3) auto-collapse instead of 'hide' the content and not have that content trigger an "unread" channel or message notification. That way, the content can be expanded and viewed if another message's content requires context.
Clearly, as a team-communication tool, this is problematic to universally mute a colleague (e.g. what if they actually need to use the tool for a work-critical task)
Perhaps this can be
1) channel specific: "This person has smart things to say about Project Blue, or the For Sale, but I don't need to know their opinions in ~coffee"
2) limited only to channels with more than n number of members. That way, smaller project channels will enable unfettered communication, but users can curate their content in large interest-based channels.
3) auto-collapse instead of 'hide' the content and not have that content trigger an "unread" channel or message notification. That way, the content can be expanded and viewed if another message's content requires context.
Thanks for the consideration.
(I guess email could be a backup, huh?)