Re:Tell HN: Slack decides to close down IRC and XMPP gateways
by dangom on Wednesday March 07, 2018 @05:57PM
(#16540768)
I guess this is about to break because of the current announcement?
[ Parent
| on HN ]
Re:Tell HN: Slack decides to close down IRC and XMPP gateways
by anglebracket on Wednesday March 07, 2018 @06:05PM
(#16540825)
I don't believe so. emacs-slack uses their official OAuth2 + Websocket integration https://github.com/yuya373/emacs-slack#how-to-get-token-the-...
Re:Tell HN: Slack decides to close down IRC and XMPP gateways
by eadmund on Wednesday March 07, 2018 @07:58PM
(#16541380)
This is, incidentally, an argument about how a well-designed system like emacs can make writing a truly-native app easy: so easy that some random guy was able to take the API and write a client for a text editor (granted, the greatest & best text editor the world has ever known …).
If it's so hard to write native macOS, Windows, gtk+ or Qt apps — maybe that's a fault of those development environments. Granted, 'display sequences of text, optionally with some images' is kinda in emacs's wheelhouse.
Re:Tell HN: Slack decides to close down IRC and XMPP gateways
by pseudalopex on Thursday March 08, 2018 @02:09AM
(#16542862)
It isn't hard to write native apps, but if you already have a web app, wrapping it in Electron is a lot cheaper.
Re:Tell HN: Slack decides to close down IRC and XMPP gateways
by RaycatRakittra on Wednesday March 07, 2018 @06:36PM
(#16541000)
Correct. emacs-slack uses WebSockets and Slack's Real-Time Messaging API.