Because Slack killed their XMPP and IRC bridges, so the only way to connect to is via the official interface.
Not true. There’s several alternative clients.
I don't need ANY changes in my XMPP/IRC client to connect to a server.
But the reason why Slack discontinued XMPP/IRC is clear. They want people to use their shitty app/website.
>so the only way to connect to is via the official interface.
was clearly not about the UI but rather their HTTP way of accessing Slack. And right now there is no other way besides that.
Many folks I’ve talked to don’t realize there are alternative ways to connect to Slack still once the XMPP / IRC endpoints died. They think the only way is using the Slack developed apps. Thankfully, that’s becoming more and more not true each day.
Pedantic Point:
Re: > rather their HTTP way of accessing Slack
Slack uses Websockets. Websockets != to HTTP.
>Many folks I’ve talked to don’t realize there are alternative ways to connect to Slack still once the XMPP / IRC endpoints died. They think the only way is using the Slack developed apps. Thankfully, that’s becoming more and more not true each day.
Which are? Using a proprietary Websockets API is not "another" way if even the Slack app is using that (not sure). The main difference to XMPP/IRC is, that with the later ones not a single line of code needs to be written (not from me and not from IRC/XMPP developers). Just use the client you like, set server and credentials and you are done. That's why there are protocols.
>Slack uses Websockets. Websockets != to HTTP.
port 443 is close enough and http is needed to start anyway :P