Slack will never replace email

Re:Slack will never replace email by brylie on Monday June 17, 2019 @03:45AM (#20200764)

Could someone convince the higher-ups to add back some form of federated protocol to Slack, so third party clients can access the conversations?

I really miss being able to communicate via a light-weight, open-source, multi-protocol IM client.

Honestly, Matrix/Riot are becoming more appealing with each release, and support federated clients.

[ Parent | on HN ]

Re:Slack will never replace email by Spivak on Monday June 17, 2019 @08:14AM (#20202109)

> open-source, multi-protocol IM client

If you're allowing your client to be multi-protocol then why is Slack's protocol unsuitable? You can use weechat with the Slack API right now and it works great.

The market for 3rd party applications using Slack is huge.

[ Parent | on HN ]

Re:Slack will never replace email by brylie on Saturday June 22, 2019 @04:23AM (#20248595)

I haven't found a multi-protocol IM that supports Slack without loading the Slack app entirely. E.g. Rambox just renders the Slack app.

https://rambox.pro/#home

I used to use Pidgin to connect to several communication networks via a common UI, even with the promise of having a single contact list:

https://pidgin.im/

I just realized that Pidgin may have a community-maintained Slack plugin!

https://developer.pidgin.im/wiki/ThirdPartyPlugins

We need a federated communication protocol, similar to email, where we can have real-time communication with people and groups on various networks and using differing software.

[ Parent | on HN ]