The structural siloing pressure you're describing happens in every channel-based organizational chat (though admittedly, some got it worse than others). I'm working on a chat app that uses a different model to combat this. Instead of channels, every message has at-least-one tag that describes it. It's similar to specifying recipients in email, only that you don't need to know the actual people. The message is publicly readable by default, and routed to the inbox of anyone who follows any of its tags.
Hoping to make the repo public soon.