b1naryth1ef

5 ms·

1.
by b1naryth1ef 8y ago
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
2.
by b1naryth1ef 8y ago
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!
3.
by b1naryth1ef 9y ago
Ah sorry I misunderstood you. We keep the original image around and provide different sizes for different platforms/resolutions/dpis/etc.
4.
by b1naryth1ef 9y ago
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 impr
5.
by b1naryth1ef 9y ago
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.
6.
How Discord Resizes 150M Images Every Day with Go and C++(blog.discordapp.com)
303 points by b1naryth1ef 9y ago|145 comments
7.
by b1naryth1ef 9y ago
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 faile
8.
by b1naryth1ef 9y ago
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.
9.
by b1naryth1ef 9y ago
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 intereste
10.
by b1naryth1ef 9y ago
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 pro
11.
by b1naryth1ef 9y ago
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
12.
by b1naryth1ef 9y ago
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 pe
13.
Discord Postmortem from Friday(status.discordapp.com)
96 points by b1naryth1ef 9y ago|42 comments
14.
How Discord Scaled Elixir to 5M Concurrent Users(blog.discordapp.com)
802 points by b1naryth1ef 9y ago|251 comments
15.
Making a Game in Rust(michaelfairley.com)
418 points by b1naryth1ef 9y ago|121 comments
16.
by b1naryth1ef 9y ago
Bad and hard to grok code can be created in any language. Even more-so in languages that have more syntax complexity than C.
17.
by b1naryth1ef 9y ago
(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 imme
18.
by b1naryth1ef 9y ago
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.
19.
by b1naryth1ef 10y ago
fwiw, here is our postmortem from the incident: https://status.discordapp.com/incidents/dj3l6lw926kl
20.
by b1naryth1ef 10y ago
No worries, thanks for the response anyway!
21.
by b1naryth1ef 10y ago
Coming from a company that regularly goes down to DDoS attacks :thinking:
22.
by b1naryth1ef 10y ago
Mind emailing me some details? az@discordapp
23.
by b1naryth1ef 10y ago
The point of our service is that chat is persistent. You can scroll back through time and read all the messages you sent. Users are free to delete whatever they sent whenever if they wish, but for almost everyone persistent chat history is
24.
by b1naryth1ef 10y ago
Our realtime messaging is done over Websockets using either JSON (for web/non-native) or ETF ( http://erlang.org/doc/apps/erts/erl_ext_dist.html ). Almost all user-based actions are sent over our HTTP API
25.
by b1naryth1ef 10y ago
- E2E/OTR encryption is something some of us are interested in, but due to the nature of our platform probably isn't going to happen anytime soon (we'd want to do it right, which requires time and effort). - Some libraries su
26.
by b1naryth1ef 10y ago
We've adamantly stated many a time that we will never sell users data, or put ads in the app.
27.
by b1naryth1ef 10y ago
What features in particular? The most common one we hear is search, which is actually implemented and undergoing internal testing before a public preview soon.
28.
by b1naryth1ef 10y ago
Yup. We (discordapp) had to manually spin up our own stuff to route around the issue. Not great communication from Google on this one, status page update took ~20 minutes.
29.
by b1naryth1ef 10y ago
Drop me a line (andrei @ discordapp.com) and I'll at least take a look.
30.
by b1naryth1ef 10y ago
(Discord Dev here) Awesome to hear Discords a good fit for workplace environments too, we've heard a couple success stories around remote teams swapping. Search is a huge priority for us, but its also something we wanna spend time gett

More ›