Let's try to send a few hundred messages per second over it, a task any queue should be able to perform easily, and see how well it performs!
I mean, huge bots are doing just that.
Your own non-approved bot might get rate-limited hard though.
Re:Discord API Errors
by paulddraper on Monday November 18, 2024 @09:17AM
(#42172463)
This is just such a terrible idea. You really don't need to defend it.
You'll get rate limited in two seconds, for no upside.
Re:Discord API Errors
by dijksterhuis on Monday November 18, 2024 @09:50AM
(#42172770)
if i walk in and out of a room 100 times in a day, that is an average of 0.001157 messages per second required to turn lights on/off.
i highly doubt i’ll be rate limited for that.
were not talking an enterprise use case here. not every problem is faceboook scale.
also, discord is free to use and has very thorough documentation, on top of all the things previously mentioned. so there’s definitely upsides to it.
chat stuff is just one possible use case for the system.
like, when i read the root comment i was a bit like “huhhh?” but reading Spivak’s comment it now makes total sense.
also to add —
* discord gives you easy topic queue debugging. just login yourself and read the queue entries.
* something like 2000 character text content per message
* RBAC for topic queue access
* can probably turn it into a pub/sub topic queue system if you start adding webhooks and bots.