> [#929](https://feedback.fluxer.com/p/929) has a bunch of channel ideas, but I did not find an overlapRemoved: -### ChecksRemoved: -Removed: -- ☑ I searched existing discussions.Removed: -
Show
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
Edited by Rex
Changes
The important part is keeping related information and conversation together without mixing both message streams.Removed: -> [#321](https://feedback.fluxer.com/p/929) has a bunch of channel ideas, but I did not find an overlapAdded: +> [#929](https://feedback.fluxer.com/p/929) has a bunch of channel ideas, but I did not find an overlap### Checks
Show
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
Checks
☑ I searched existing discussions.
Original by ⦓⡷⠂NEONSY⠐⢾⦔
Show
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.
#321 has a bunch of channel ideas, but I did not find an overlap