1. 4

    The author mentions that Slack may be hacked in the future, exposing sensitive communication of your team, and proposes Mattermost and Rocket.Chat as alternatives.

    I’d like to point out that Mattermost and Rocket.Chat have the same problem — centralized servers that may be hacked (or may already have been).

    Keybase.io has recently announced [1] support for team communication. They’re still behind in team-features compared to Slack, but Keybase is end-to-end-encrypted, making a server hack a bit less scary.

    [1] https://keybase.io/blog/introducing-keybase-teams

    1. 3

      I’d like to point out that Mattermost and Rocket.Chat have the same problem — centralized servers that may be hacked (or may already have been).

      From the article:

      As we demonstrated above, companies need to find an alternative solution to Slack, one they can host themselves to reduce data leaks and industrial espionage and dependency on the Internet connection.

      The author specifically aims at the self-hosted variants of both. They can still be hacked, but it must be done one server at a time. They are kind of centralised, but not in the sense that Slack is.

      Yes, these are centralised, but there’s several reasons a company needs a centralised point of authority for their internal chat app - for example, compliance reasons.