Discord API Errors
discordstatus.com
discordstatus.com
Honestly the DSL really isn't that great. I've been meaning to redesign it using something like ANTLR rather than the mess that I made a few years ago.
I do eventually want to have a local-first way to send messages to the program, but creating that isn't worth my time at the moment.
only according to the more modern definition of “hacking”
the earlier version of the term referred to people who write novel, interesting or clever software for the love of the craft.
i think using discord as a free message queue (see spivak’s comment in the thread) is pretty damn clever actually.
i kinda want to build something with it now.
The fact that it's also a chat thing is honestly secondary to the foundational tech.
Using Discord, all I had to do was to create a new, empty company server, copy the webhook URL and then POST to the URL and boom I get a ping notification with the Chat ID on my phone (or I can @ a colleague to distribute the customer support for different timezones).
It's not a very "orthodox" solution, but it certainly sucks less than the alternatives (plus it's free).
"Thanks, I'll base my next enterprise project on Discord as the message queue of choice."
Hah, what an amusing way to look at things, thanks for that.
None of this is meant to ridicule anyone. If using Discord for home automation works, great, have fun at it, feels like a cool way to have a hacker mindset (not to discount the arguments that suggest that there are also other alternatives).
I still think that describing a popular chat platform as a highly available message queue is funny though, because that's a very unconventional way of looking at things.
Midjourney avoided having to make a frontend at first, meaning they launched faster. Once they got product/market fit, they built a web frontend, which is now better than the Discord interface. Seems like a pretty smart strategy, that worked well, for a completely bootstrapped company that never raised VC.
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.
Your own non-approved bot might get rate-limited hard though.
You'll get rate limited in two seconds, for no upside.
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.
Frustrating!