[bisq-network/proposals] Shut down Slack (#144)

wiz notifications at github.com
Thu Nov 21 22:28:24 UTC 2019


> _This is a Bisq Network proposal. Please familiarize yourself with the [submission and review process](https://docs.bisq.network/proposals.html)._

It seems like almost everybody has migrated to Slack - in the interests of security for Bisq's public channels and privacy for DMs between Bisq users chatting, I propose that we phase out Slack entirely as follows:

1) November 30, 2019 - remove links to Bisq's Slack workspace from all public Bisq websites, docs, etc.
2) December 31, 2019 - disable new user registration on Bisq's Slack workspace with a message pointing them to Keybase
3) January 30, 2020 - lock down the workspace so nobody else chat there, with a message pointing to Keybase

This way if anything happens to Keybase, or we want to migrate back, we can always re-enable the Slack workspace, but we will force users to use E2E encrypted/signed/verified chat on Keybase within ~2 months.

Is there any reason why people still want to use Slack for some things and we shouldn't shut it down?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/144
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191121/24f1b15b/attachment.html>


More information about the bisq-github mailing list