[Feature Request] External Chat Filter

[jprjr]

Share your bug report, feature request, or comment.

Hi there! I wanted to throw out the idea of an external chat filter.

The general idea is a chat message could be sent to a remote server for processing, and the processing service dictates how to handle the message. It could be something like - user submits a message on the chat websocket, Owncast makes an HTTP POST with similar details to a CHAT event, the service could return:

• HTTP 204 - Owncast uses the message as-is, everything proceeds normally.
• HTTP 200 - Owncast reads the response body for JSON, and uses that as the event.
• HTTP 4xx - Owncast rejects message (maybe with text returned by service?)

The Owncast chat UI could show a rejection as an error message.

The use-cases are for things like, maybe there's some new movie/game out and you don't want people spoiling things so you reject certain phrases, or silly April-Fool's day type things like converting messages to all-caps.

As far as what to do when the external service is down, probably just display an error message? I'd imagine if somebody's taken the time to set up a service they'd rather it block everything when it's broken, as opposed to blocking nothing.

[gabek]

It's an interesting idea, but I can't see very many people taking advantage of it. Additionally, it seems like something that would fit better with the "plugin" approach as opposed to a webhook, something that has been on the table but isn't possible with the current architecture.