5 ms·

I don't believe so. emacs-slack uses their official OAuth2 + Websocket integration https://github.com/yuya373/emacs-slack#how-to-get-token-the-harder-yet-offici

I don't believe so. emacs-slack uses their official OAuth2 + Websocket integration https://github.com/yuya373/emacs-slack#how-to-get-token-the-harder-yet-officially-sanctioned-way https://github.com/yuya373/emacs-slack#how-to-get-token-the-...

RaycatRakittra 9y ago
Correct. emacs-slack uses WebSockets and Slack's Real-Time Messaging API.
eadmund 9y ago
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.
- pseudalopex 9y ago
  It isn't hard to write native apps, but if you already have a web app, wrapping it in Electron is a lot cheaper.