Re:Slack’s new WYSIWYG input box is terrible
by gsich on Thursday November 21, 2019 @09:06AM
(#21594090)
"connect" seems clear to me. But anyway, doesn't really make much of a difference.
>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
>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