Carsen,
The biggest issue with these sorts of chat utilities (except for Skype) is that they do not work for a vast majority of those in corporate or networked environments.
The answer to this (which I found after researching) is simply that the 'websockets' type of protocol that these chat systems use, are not supported by ANY proxy system (such as squid) that is used in most professional networked environments. This is why the reach to those who actually are interested and willing to join (like myself) cannot do so.
Skype does not work this way, and Microsoft know this. It can be forced through a http proxy like squid, and until squid (the most widely used proxy in the world) supports such protocols, then discord and slack and many others that use this protocol WILL be out of reach to those that cannot access it.
Just a FYI moment here, as I see SO many companies pushing this type of communications for the 'home user' but not the ever important corporate/professional networked user also.
#crysx
If the Discord desktop app doesn't work, then you can access the Discord browser app (discordapp.com) and that should work, at least for the text chat; because the app runs inside the browser and the browser tunnels all websocket requests through the proxy server.
As far as I know, the Discord desktop app doesn't support proxy usage, so if your squid proxy is not set up to be transparent then Discord won't know to connect through the proxy. I believe this is under development at Discord.
If it doesn't work at all in browser, it's probably because it's been disallowed by the proxy policy, in which case you'd need to get it checked and allowed by IT.
Websockets get tunneled through yes.
Which is why it still doesn't work mate. They are not disabled by default either, it's just that these protocols are not supported by the mainstream proxies like squid. Not yet anyway.
Still looking for a workaround, without disabling the proxy altogether.