Re:How Discord Handles Two and Half Million Concurrent Voice...
by marksomnian on Monday September 10, 2018 @03:46PM
(#17954567)
> open up their protocol
Both the Rest API (that official clients use internally too), as well as the real-time WebSocket protocol are described here:
Re:How Discord Handles Two and Half Million Concurrent Voice...
by Ycros on Monday September 10, 2018 @08:25PM
(#17956231)
Unfortunately you can't use these APIs to create third party clients because that violates their ToS, they are meant only for writing bots. If they catch you using these APIs with your full account credentials they'll ban your account.
Re:How Discord Handles Two and Half Million Concurrent Voice...
by tenryuu on Monday September 10, 2018 @10:27PM
(#17956763)
They can't catch you using these apis since these are the same apis the first party client runs off of
Re:How Discord Handles Two and Half Million Concurrent Voice...
by Fnoord on Tuesday September 11, 2018 @01:34AM
(#17957404)
Of course they can catch you if your client isn't 100% the same as the original there are going to be differences which "forensic" tools are going to prove.
Re:How Discord Handles Two and Half Million Concurrent Voice...
by tenryuu on Tuesday September 11, 2018 @08:29PM
(#17964638)
Forensic net requests?
You can MITM the entire traffic. Mimicking it's nature isn't the hardest task in the world if all the data is handed on a silver platter, and it's even easier when their client code is uncompiled JavaScript. There are always people data mining the client.
If you're thinking they're going to check the actual software. Like ass I'm going to let someone into my house to check if I'm breaking their terms of service
Re:How Discord Handles Two and Half Million Concurrent Voice...
by scrollaway on Monday September 10, 2018 @02:23PM
(#17953833)
I agree on opening the protocol but if what you want is a gateway, it's already open enough for that.
I haven't made many calls but the sound was always crisp.