Make rate limit more relaxed and/or configurable

[ShadowJonathan]

Share your bug report, feature request, or comment.

Right now, the rate-limiter is way too strict for some chat usage, and can get very annoying/in-the-way.

Its not configurable, as it is hard-coded here.

It might be better to be configurable per streamer, and/or expanded into other features, such as slow-mode, together with telegraphing when a limit is over to the client, disabling sending for that time, to not make it annoying to send multiple messages. (Also possibly saving the message that got sent and got caught by rate-limits, so that its not "eaten")

It might also be worth looking into multiple-messages-per-multiple-seconds, for example, sending 3 messages within 3 seconds should be alright, it allows them to be sent in quick succession (such as follow-ups like "lol" or quick edits via asterisk), while anything more would get caught.

[gabek]

Once in a while somebody will say it's too strict, and once in a while somebody will say it's too relaxed. But both are pretty rare, so I think it's a middle ground.

If people generally agree the current value isn't correct, then we should talk about the value should be. I have no opinion on how strict or relaxed this value is. I picked something that seems to work for most people, and it does seem to.

In general, I'm being more sensitive about just adding more knobs and switches to the admin. So many things are already configurable in the admin, and I'm not interested in adding a new setting for each specific thing people want to configure.

Each decision somebody has to think about makes Owncast seem far more complex and difficult to understand than it is. So if we added a customization where somebody had to understand, and then decide how sensitive rate limiting is, that creates cognitive overhead, when in reality, almost nobody ever needs to change it from the default. The 80/20 rule applies.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this was a feature request that others have shown no interest in then it's likely to not get implemented due to lack of interest. If others also want to see this feature then now is the time to say something! Thank you for your contributions.

[ShadowJonathan]

not stale