[bisq-network/bisq] Seeding signed accounts (#3576)

FKrauss notifications at github.com
Sun Dec 1 11:26:18 UTC 2019


I think that's a good idea. But we need to check how archiving works there.
We wouldn't want to have a huge list of archived channels showing up
whenever people want to manage their notifications. In slack it's pretty
straight forward, but keybase seems to be a bit behind in things like that.

Let me check that and I'll be back in a min



On Sun, 1 Dec 2019, 02:53 eigentsmis, <notifications at github.com> wrote:

> Maybe we can setup specific Keybase channels for certain bisq issues on
> github? So that we can discuss easier, with less friction?
> #3576_SeedingSignedAccounts (or something of this nature, to reference the
> specific open github issue)
>
>> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/bisq-network/bisq/issues/3576?email_source=notifications&email_token=ABEY5S7VGRT2F5INCOQ5AU3QWMKH3A5CNFSM4JKHDKY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQYILA#issuecomment-560038956>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABEY5S3G66J6YU4HG5EJP2TQWMKH3ANCNFSM4JKHDKYQ>
> .
>


-- 
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/bisq/issues/3576#issuecomment-560095213
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191201/190c4c9f/attachment.html>


More information about the bisq-github mailing list