Optional read-only information area for text channels

Problem

Project and topic channels often need both conversation and a stable source of information, such as updates from a GitHub webhook Currently, these updates must either be mixed into the chat, where they can get buried, or placed in a separate channel, which splits the context and clutters the channel list

Proposal

Allow text channels to optionally have a separate read-only information area, such as a tab or side panel Members could continue chatting normally while bots, webhooks, or permitted roles publish updates to the information area This could be an optional feature for text channels or a dedicated channel type

Notes

For example, a project channel could contain its regular discussion and a GitHub activity feed without requiring separate #project-chat and #github-feed channels The exact presentation is flexible The important part is keeping related information and conversation together without mixing both message streams.

#929 has a bunch of channel ideas, but I did not find an overlap

4 comments

RexSystem 1 vote 2mo ago originally by @Float-as on GitHub 3 replies

Maybe it could be implemented into threads (when they will get implemented). Basically channel threads could have webhooks. You could also set permission for a thread to only view message history? Kinda channel inside a channel.

RexSystem 1 vote 2mo ago originally by @Neonsy on GitHub OP

It very much depends on how threads are going to be implemented, since what you are describing sounds like a different idea, if compared to how they work on Discord

RexSystem 1 vote 2mo ago originally by @Float-as on GitHub

I'm thinking of a dedicated persistent thread for the functionality you are describing, because in theory sidebar works for desktop displays, but for mobile there would really be no space to display channel and the panel for updates, bots, etc

For mobile it would have to be like server members or something, where you have a dedicated button or whatever to open that view That would solve that problem with ease While it can be a part of threads, I think it would also benefit the normal channel type, cause you don't always want to have a thread for a single topic