Current problem
A UX problem currently exists where messages from webhooks in an announcement channel are not auto-published to followed channels. For these messages to publish, someone has to manually publish the message.
This is an issue as of
Fluxer 2026.1107.20335.Proposed change
There are two proposed changes that I'm providing, the first being the most ideal and the second being the least ideal:
- Have webhook messages be auto-published. If someone is managing many announcement channels across multiple communities, it becomes incredibly difficult to remember to publish these messages, especially if webhook messages are being sent by another party and not the creator of the announcement channels.
- Make it incredibly obvious to the users who have permissions to publish these messages that they haven't been published yet. This is an improvement over the current UX, but manually publishing many webhook messages can still be a chore.
Platform
macOS, Windows, Linux, Web, Self-hosting
4 comments
Comment by Fullest
- Hover the message
- Click the megaphone icon in the hover to publish
This is probably because the publish prompt only shows for messages you send into the announcement channel (other users don't get the publish prompt for messages sent by another user either btw), but perhaps webhook messages should show the prompt to anyone who has the ability to publish messages in an announcement channel. What do you think?Screenshot_20261107_124337.png
447×378 | 45 kB Link to Screenshot_20261107_124337.png
Comment by Falco
Comment by Fullest
Comment by Falco