Hacker News: b1naryth1ef

New comment by b1naryth1ef in "How Discord Handles Two and Half Million Concurrent Voice Users Using WebRTC"

b1naryth1ef — Mon, 10 Sep 2018 19:38:30 +0000

We've put a lot of work into our clients and our backend to make sure the impact of being on 1 vs 100 guilds is negligible. It helps that most of the folks building Discord are power users in a bunch of servers (so we feel the pain of poorly optimized paths early). Generally if you don't look at a server often it shouldn't effect the performance of the app / bandwidth usage. I think we have some more blog posts in the works regarding some of these topics so look forward to those!

New comment by b1naryth1ef in "The Discord Store Beta"

b1naryth1ef — Thu, 09 Aug 2018 17:25:27 +0000

We won't have support initially but as a Linux user internally I'm definitely hoping to push for it, and I see no reason why it wouldn't get built!

New comment by b1naryth1ef in "How Discord Resizes 150M Images Every Day with Go and C++"

b1naryth1ef — Tue, 14 Nov 2017 17:43:21 +0000

Ah sorry I misunderstood you. We keep the original image around and provide different sizes for different platforms/resolutions/dpis/etc.

New comment by b1naryth1ef in "How Discord Resizes 150M Images Every Day with Go and C++"

b1naryth1ef — Tue, 14 Nov 2017 17:38:54 +0000

As mentioned in the post, one of our core product features is preventing your IP from being shared. Given that requirement, images shared in chat have to be proxied through our infrastructure. When doing this we save a lot of money and improve client performance by reducing image sizes.

New comment by b1naryth1ef in "How Discord Resizes 150M Images Every Day with Go and C++"

b1naryth1ef — Tue, 14 Nov 2017 17:34:46 +0000

vips (Go binding) is included in the benchmarks mentioned in the post, but at the time of running them (~10 months ago) vips pulled 51482954 ns/op on a 1024x1024 test image, where as pillow-simd managed 3324135.3035 ns/op.

How Discord Resizes 150M Images Every Day with Go and C++

b1naryth1ef — Tue, 14 Nov 2017 17:03:41 +0000

Article URL: https://blog.discordapp.com/how-discord-resizes-150-million-images-every-day-with-go-and-c-c9e98731c65d

Comments URL: https://news.ycombinator.com/item?id=15696855

Points: 303

# Comments: 145

New comment by b1naryth1ef in "Discord Postmortem from Friday"

b1naryth1ef — Tue, 17 Oct 2017 04:59:22 +0000

GCP has a virtual networking stack to support a bunch of crazy (and awesome) features Google has built. Unfortunately the complexity here seems to hurt power-users like us. In this case it appears that for some unknown reason the node failed to program its network stack when coming up, meaning it was completely unavailable (even the metadata service used internally by google failed).

New comment by b1naryth1ef in "Discord Postmortem from Friday"

b1naryth1ef — Tue, 17 Oct 2017 04:54:05 +0000

Yup this, our privacy policy plainly states that we're not in the business of making money from your data. We have various provisions which limit how and when we can share your data.

New comment by b1naryth1ef in "Discord Postmortem from Friday"

b1naryth1ef — Tue, 17 Oct 2017 00:28:35 +0000

Thanks, we try our best with these. Past experience has shown they can be very valuable, and help everyone at the company get context on the system and how we handle failures.

Reliability testing is definitely something we're interested in as we spin up more SRE/reliability focused individuals, but also has probably the least amount of cost-benefit for us (compared to engineering effort on improving the things we know need work). Some of the failure in the system we experienced is related to issues we know about, but haven't prioritized (read; had time for) yet.

For the library, we believe the bug is related to hackney and the fact it uses the high priority setting for its pool process. For some reason (this is the part we're not entirely sure on, and still spending some time investigating) this high priority process got stuck and consumed all of the scheduler time (presumably related to the earlier API degradation), breaking the distribution port and the application in a weird way. Oddly enough the systems we run on are SMP, so in theory one rogue process should not be able to have this effect.

New comment by b1naryth1ef in "Discord Postmortem from Friday"

b1naryth1ef — Mon, 16 Oct 2017 21:13:17 +0000

Ahhhh, thats actually something we're aware of. Currently direct calls run on an entirely separate set of metals vs. everything else (this was mostly to help us test/measure video & screenshare rollout). Unfortunately some providers seem to be having issues with DDoS filtering over-triggering when they see video traffic, which negatively impacts the whole server. Something we're hopefully fixing in the short term!

New comment by b1naryth1ef in "Discord Postmortem from Friday"

b1naryth1ef — Mon, 16 Oct 2017 21:01:41 +0000

Very possible you saw a slight interruption around 11:30PST for around 10 minutes until we found and decommissioned the host that experienced this problem. We generally don't update status until we can verify impact/source, we see tons of limited outages from ISPs misbehaving.

New comment by b1naryth1ef in "Discord Postmortem from Friday"

b1naryth1ef — Mon, 16 Oct 2017 20:48:28 +0000

Can you give more explicit examples of the bad audio quality you experience? I'd be happy to forward this onto our native team to look into if there are some concrete things they can look at. Generally 99% of the audio issues we see people experience are due to ISP/peering/DDoS/etc issues, most of which are handled automatically by our servers within a few minutes.

Discord Postmortem from Friday

b1naryth1ef — Mon, 16 Oct 2017 19:53:05 +0000

Article URL: https://status.discordapp.com/incidents/qk9cdgnqnhcn

Comments URL: https://news.ycombinator.com/item?id=15486145

Points: 96

# Comments: 42

How Discord Scaled Elixir to 5M Concurrent Users

b1naryth1ef — Tue, 11 Jul 2017 21:01:53 +0000

Article URL: https://blog.discordapp.com/scaling-elixir-f9b8e1e7c29b

Comments URL: https://news.ycombinator.com/item?id=14748028

Points: 802

# Comments: 251

Making a Game in Rust

b1naryth1ef — Tue, 09 May 2017 16:51:51 +0000

Article URL: https://michaelfairley.com/blog/i-made-a-game-in-rust/

Comments URL: https://news.ycombinator.com/item?id=14301646

Points: 418

# Comments: 121

New comment by b1naryth1ef in "Backdoor in the firmware of Antminer Bitcoin mining hardware"

b1naryth1ef — Wed, 26 Apr 2017 22:45:36 +0000

Bad and hard to grok code can be created in any language. Even more-so in languages that have more syntax complexity than C.

New comment by b1naryth1ef in "Tell HN: Discord is violating open source licenses"

b1naryth1ef — Tue, 25 Apr 2017 16:48:27 +0000

(Discord Dev here)

Hey Alex, this definitely sounds like a miss on our part, so apologies.

As you know, we're fans of uws and not including the original license was a screw-up in our automation. We're working on fixing it and immediately releasing it with the proper license. I've also asked support to follow up with you directly in case there are further issues.

For the contact, either opening an issue on one of our repos or emailing our legal team (abuse@discordapp.com) would have been guaranteed to get you an accurate response. Unfortunately the verbiage you used in the email is very similar to that used in other support tickets we get for our API, and our team (as they did in your case) forwards users on to our API chat which can provide more in-depth/advanced support.

New comment by b1naryth1ef in "Electron is flash for the desktop (2016)"

b1naryth1ef — Tue, 11 Apr 2017 23:10:45 +0000

Discord desktop is electron. Only our iOS app is react native. We spend quite a lot of time and effort optimizing performance however, something thats required given the number of large servers with many thousands of concurrent users.

New comment by b1naryth1ef in "Discord is down"

b1naryth1ef — Tue, 21 Mar 2017 23:46:21 +0000

fwiw, here is our postmortem from the incident: https://status.discordapp.com/incidents/dj3l6lw926kl

New comment by b1naryth1ef in "Cloudflare Reverse Proxies Are Dumping Uninitialized Memory"

b1naryth1ef — Fri, 24 Feb 2017 18:54:41 +0000

No worries, thanks for the response anyway!