Discord API Errors • Hacker News Board

Re: Discord API Errors

#21

Post by tourist2d » Sun, Nov 17, 2024, 9:57 AM UTC

KronisLV wrote: post #18

Spivak wrote: post #7

Earlier quoted context omitted.

It's a completely free, both in message volume and queue size, highly available hosted 1-1 and 1-n topic based message queue with automatic sharding, excellent performance, and high-quality prebuilt libraries. It has built-in notification support to all platforms and a basic UI toolkit that is easy to use. The fact that it's also a chat thing is honestly secondary to the foundational tech.

> It's a completely free, both in message volume and queue size, highly available hosted 1-1 and 1-n topic based message queue with automatic sharding, excellent performance, and high-quality prebuilt libraries. It has built-in notification support to all platforms and a basic UI toolkit that is easy to use. "Thanks, I'll base my next enterprise project on Discord as the message queue of choice." Hah, what an amusing…

[dead]

Re: Discord API Errors

#22

Post by stavros » Sun, Nov 17, 2024, 11:10 AM UTC

dijksterhuis wrote: post #13

paulddraper wrote: post #11

Earlier quoted context omitted.

Are you serious?

not the parent, but yeah. they’ve basically described the system of discord there. 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 messa…

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!

Re: Discord API Errors

#23

Post by KronisLV » Sun, Nov 17, 2024, 11:44 AM UTC

KronisLV wrote: post #18

Spivak wrote: post #7

Earlier quoted context omitted.

It's a completely free, both in message volume and queue size, highly available hosted 1-1 and 1-n topic based message queue with automatic sharding, excellent performance, and high-quality prebuilt libraries. It has built-in notification support to all platforms and a basic UI toolkit that is easy to use. The fact that it's also a chat thing is honestly secondary to the foundational tech.

> It's a completely free, both in message volume and queue size, highly available hosted 1-1 and 1-n topic based message queue with automatic sharding, excellent performance, and high-quality prebuilt libraries. It has built-in notification support to all platforms and a basic UI toolkit that is easy to use. "Thanks, I'll base my next enterprise project on Discord as the message queue of choice." Hah, what an amusing…

Clarification, due to the other person's (now flagged) comment: https://news.ycombinator.com/item?id=42163157

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.

Re: Discord API Errors

#24

Post by LelouBil » Sun, Nov 17, 2024, 12:03 PM UTC

stavros wrote: post #22

dijksterhuis wrote: post #13

Earlier quoted context omitted.

not the parent, but yeah. they’ve basically described the system of discord there. 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 messa…

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

#25

Post by retrodaredevil » Sun, Nov 17, 2024, 9:43 PM UTC

voidfunc wrote: post #4

retrodaredevil wrote: post #3

Meanwhile I cannot turn my living room LED lights on or off because I control them through discord. I guess that's what I get for relying on a messaging service to control my lights.

Whyyyyyy?

I have individually addressable LEDs, so I created a domain specific language (DSL) to control the LEDs, meaning controlling the pattern of the LEDs is best done by sending a message to it.

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.

Re: Discord API Errors

#26

Post by reissbaker » Sun, Nov 17, 2024, 10:33 PM UTC

throwaway71271 wrote: post #19

golergka wrote: post #15

Earlier quoted context omitted.

That's a serious part of Midjourney business strategy. Hard to imagine how much money did they save on the frontend.

or how much money they lost on missed business

You don't have opportunity cost of missed business, if the alternative is that you don't exist. If it allows you to launch faster, you aren't losing business by not having every feature; you're gaining business that you would've lost by not launching sooner. You can always build the extra features later.

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.

Re: Discord API Errors

#27

Post by paulddraper » Mon, Nov 18, 2024, 2:17 PM UTC

dijksterhuis wrote: post #13

paulddraper wrote: post #11

Earlier quoted context omitted.

Are you serious?

not the parent, but yeah. they’ve basically described the system of discord there. 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 messa…

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

#28

Post by dijksterhuis » Mon, Nov 18, 2024, 2:50 PM UTC

paulddraper wrote: post #27

dijksterhuis wrote: post #13

Earlier quoted context omitted.

not the parent, but yeah. they’ve basically described the system of discord there. 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 messa…

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.

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.

Re: Discord API Errors

#29

Post by fschuett » Wed, Nov 27, 2024, 6:23 PM UTC

Spivak wrote: post #7

voidfunc wrote: post #4

Earlier quoted context omitted.

Whyyyyyy?

It's a completely free, both in message volume and queue size, highly available hosted 1-1 and 1-n topic based message queue with automatic sharding, excellent performance, and high-quality prebuilt libraries. It has built-in notification support to all platforms and a basic UI toolkit that is easy to use. The fact that it's also a chat thing is honestly secondary to the foundational tech.

I use Discord for notifications when someone starts a "Chat with customer support" chat on my site. I tried various "chat button" solutions, but I ended up writing the chat system myself because no solution was really tailored to my task (esp. custom file type uploads and Google Ads integration, so I know which ad started a chat). I need to react 24/7 to new customers, so I needed a tool to ping me with notifications on my phone. The chat messages are still saved in the company database, but I send a link with the Chat ID to Discord, so that someone can instantly login to the admin panel and reply to the customer.

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).