Shut down Slack

[wiz]

This is a Bisq Network proposal. Please familiarize yourself with the submission and review process.

It seems like almost everybody has migrated from Slack to Keybase - 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?

[thehapax]

I concur. The only thing worth keeping around the Slack would be its archival history, if needed, imho

[m52go]

Looks like Keybase has picked up sufficient momentum, so I think it's finally time to do this. The phased approach is good. I'll start readying PRs to achieve 1, so they can be merged when this proposal is approved, pending any objections.

[FKrauss]

I concur. The only thing worth keeping around the Slack would be its archival history, if needed, imho

But that is also ethereal. Every new message posted deletes an old message, because we use the free version of it. So in reality we have a rolling archive with no control over the speed of it (private messages also count against that). We should just move out and give the proper notices wherever needed.

[FKrauss]

I guess the only downside of keybase is that we can't do this:

But I think we can live without custom emojis

[m52go]

PRs are ready for review.

bisq-network/bisq-website#302
bisq-network/bisq-docs#182

@FKrauss are you aware of the /giphy command on Keybase? All we need to do is add some Bisq GIFs to giphy.com and that's a solved problem ;)

[beingindot]

Is it possible to know online/offline status of a user in keybase? that's one imp thing im missing.

[FKrauss]

Sort of... if you go to their profile the green dot will tell you that, but my experience with it is that it tells you if the person has KB running in any of their devices (inactivity doesn't mark you as offline)

…

On Wed, 4 Dec 2019 at 08:06, beingindot ***@***.***> wrote: Is it possible to know online/offline status of a user in keybase? that's one imp thing im missing. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#144?email_source=notifications&email_token=ABEY5SYEHP3JEK5LNHOK7W3QW5JJHA5CNFSM4JQJAK52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF3653I#issuecomment-561508077>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEY5S5PT4GPSDYBZATNTP3QW5JJHANCNFSM4JQJAK5Q> .

-- *Fábio Krauss Stabel* +45 93 93 21 31 PGP keys <https://keys.mailvelope.com/pks/lookup?op=get&search=0xE5058064B3E7342F>

[beingindot]

tried searching that green dot. not able to find.
keybase/keybase-issues#3080

[FKrauss]

click on someone's profile, where you get the button to follow them [image: image.png]

…

On Wed, 4 Dec 2019 at 11:45, beingindot ***@***.***> wrote: tried searching that green dot. not able to find. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#144?email_source=notifications&email_token=ABEY5S45EOVOVRUODJKTKN3QW6C53A5CNFSM4JQJAK52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF4SBBQ#issuecomment-561586310>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEY5S7ZMYU3JHDNIMI2MVLQW6C53ANCNFSM4JQJAK5Q> .

-- *Fábio Krauss Stabel* +45 93 93 21 31 PGP keys <https://keys.mailvelope.com/pks/lookup?op=get&search=0xE5058064B3E7342F>

[beingindot]

yeah. thanks. It was not explicit for me. though as you mentioned inactive not marked.

[FKrauss]

the thing is that that dot is green almost 24/7 if you leave the computer open with Keybase. Unlike with slack where, if you're inactive (in slack) for some time, it marks you as inactive and not online

…

On Wed, 4 Dec 2019 at 12:08, beingindot ***@***.***> wrote: yeah. thanks. It was not explicit for me. though as you mentioned inactive not marked. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#144?email_source=notifications&email_token=ABEY5SYZTWJYFBOF2YPOZUDQW6FTPA5CNFSM4JQJAK52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF4UWWY#issuecomment-561597275>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEY5S65ER5OTHFAAOBTXGLQW6FTPANCNFSM4JQJAK5Q> .

-- *Fábio Krauss Stabel* +45 93 93 21 31 PGP keys <https://keys.mailvelope.com/pks/lookup?op=get&search=0xE5058064B3E7342F>

[mpolavieja]

Close as it got approved

[wiz]

@mpolavieja why you close this issue? approved does not mean close the issue, that's what the tag is for. we still have to finish the tasks inside the proposal before it can be completed 😅

[mpolavieja]

In theory the proposal should be closed once the discussion about executing or not the proposal is over and a decission about the proposal has been taken (accepted, rejected, ignored, invalid, etc) or the proposal stalls.

These are the rules about closing proposals (although I am being much more flexible than what is described here):

Step 3. Evaluate
After the two-week review period is over, a maintainer will evaluate reactions to and discussions about the proposal and will close the issue with a comment explaining that it is approved or rejected based on whether a rough consensus was achieved.

Approved proposals will be labeled with was:approved. Rejected proposals will be labeled with was:rejected.

If rough consensus has not been achieved, e.g. because discussion is still ongoing, dissenting concerns have not been addressed, or the proposal has turned out to be contentious, the maintainer will indicate that they cannot close the proposal, and that it is up to the submitter to take next steps to move the proposal forward. If the proposal does not move forward after another two weeks, the maintainer will close and label it was:stalled.

If there have been no or very few reactions to a proposal after the two-week period, the maintainer will close it and label it as was:ignored.

However, if you still think I should reopen the issue, I´ll do.