Re: [Ledger] Proposal: Switching from Gitter to something else

Daniel Carroll <daniel.carroll@secureblockchains.com> Mon, 04 February 2019 05:23 UTC

Return-Path: <daniel.carroll@secureblockchains.com>
X-Original-To: ledger@ietfa.amsl.com
Delivered-To: ledger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4CFB130E09 for <ledger@ietfa.amsl.com>; Sun, 3 Feb 2019 21:23:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=secureblockchains.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w_yEE7eqkZlW for <ledger@ietfa.amsl.com>; Sun, 3 Feb 2019 21:23:36 -0800 (PST)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B2A21294FA for <ledger@ietf.org>; Sun, 3 Feb 2019 21:23:36 -0800 (PST)
Received: by mail-qt1-x82f.google.com with SMTP id u47so14184140qtj.6 for <ledger@ietf.org>; Sun, 03 Feb 2019 21:23:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureblockchains.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2ZsORy/t2baoQv35lLUDVl7icrTAdlPsVN7CmJzjSJw=; b=n5uQUGy+5e3lugOTxy7VUslt+Ka+kgTXTYQbJJjuYMeqNwv1hFnO+VTezHgcdSXKOD eRjVp+/lnHzYCq6QFpTLp11GaKepcqya4P5CvRGpbTC9UyfjoWDtQtt22HSdlgNPAxbl WYL3FzQseA1Kb5tI/rLnUum/g+Fcqr3ZJN9AXU9ksd3fNyOUwmWYGfMBit8I5a2xi4uE NTMoeECj+zhyfbld6cELymXmg5ZRIsWHI1SiTVpR/gnfTHOdezxc8GF8HYOIxLF1Nb2K Q6f6iHtOQ6KfOJqIG1+SbiqFBQmAsR+a28gEg6zPaYZ7t4Sg/Ih5KQwNRDI2ykkSKhVt FhKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2ZsORy/t2baoQv35lLUDVl7icrTAdlPsVN7CmJzjSJw=; b=nXQqnvPcrvNl2m7kuOgcqYg2orMj0oYj2lNMcvPwGjeH5egSB8N7wapIkfwSAAEZm4 I1R+X5GcI7L4aU9V5nHoAF9+VIf420OWfUPPoT2m9XqSO4MpXkBUDiYZcpe2oPCX1QiS u43oernVuOj8W8MRMMDPOJY+o4xyoCp1XiVZ4ejSQBjPAVMV/pL1MMtrozah7bAZRNrs 6o0Zh/89ITg9DUWUofu8MCOwPZd5r9aWmioKZCr+rRmfMDSNNMhd0PFvv4Zfrn1DiF9n McVcfqOWrBk3EDA3q9seZhVIR1ey0poJgTzud+RFAzk2yzXrvzKDyqBCSi/hDT+3dEWJ Y9JA==
X-Gm-Message-State: AHQUAua+oWsR5u8kD2e/cMWrOCpoqpVjrH992scU5lxJnG/js1wKbNtQ AW4WpzXnOX/G+P/tlL9P3159Zg==
X-Google-Smtp-Source: AHgI3IYfY+9oPUzjo4s3xwASB2lrrb4jSdA0SfmuqYphTCLBzh8yt1WiznlgFWK3eA8KGLBJxZkB5w==
X-Received: by 2002:ac8:7141:: with SMTP id h1mr422872qtp.78.1549257815370; Sun, 03 Feb 2019 21:23:35 -0800 (PST)
Received: from [192.168.1.207] (cpe-184-153-202-98.twcny.res.rr.com. [184.153.202.98]) by smtp.gmail.com with ESMTPSA id r1sm14244852qte.28.2019.02.03.21.23.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Feb 2019 21:23:34 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-606EA6E8-B202-48AF-B028-247120D97602"
Mime-Version: 1.0 (1.0)
From: Daniel Carroll <daniel.carroll@secureblockchains.com>
X-Mailer: iPhone Mail (16C101)
In-Reply-To: <6BDF9F10-AC5F-41C1-AEED-01DA8BA60C03@jabjabgroup.com>
Date: Mon, 04 Feb 2019 00:23:33 -0500
Cc: Yuriy Dybskiy <yuriy@dybskiy.com>, AKASH KHOSLA <akhosla@berkeley.edu>, hyperledger-quilt@lists.hyperledger.org, ledger@ietf.org, public-interledger@w3.org
Content-Transfer-Encoding: 7bit
Message-Id: <83B5D059-0BF6-4DE6-A4DD-266BA0FD6B1B@secureblockchains.com>
References: <5c564ea61729493b74000001@polymail.io> <CALqF4L6V8o0zZqyhpsHdyqA3DWS7kKYVNoyp1wUjagS_EazSqQ@mail.gmail.com> <6BDF9F10-AC5F-41C1-AEED-01DA8BA60C03@jabjabgroup.com>
To: Bhaves Shah <bhaves.shah@jabjabgroup.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ledger/sR9Sxp9C-FN5Pr3mq9pTisEo7FU>
X-Mailman-Approved-At: Mon, 04 Feb 2019 12:11:29 -0800
Subject: Re: [Ledger] Proposal: Switching from Gitter to something else
X-BeenThere: ledger@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." <ledger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ledger>, <mailto:ledger-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ledger/>
List-Post: <mailto:ledger@ietf.org>
List-Help: <mailto:ledger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ledger>, <mailto:ledger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2019 05:35:30 -0000

It would likely be good to have a couple of different platforms. 

I like Discord and Telegram for community chat and general sharing of information. But both are limited in how you can breakdown information into categories and maintain a logical history. 

I like Slack and Trello for grouping chunks of data within a team attempting productivity. 

Dan

> On Feb 3, 2019, at 9:47 PM, Bhaves Shah <bhaves.shah@jabjabgroup.com> wrote:
> 
> I assume when looking at the community at large we want a solution that is seccure in nature and also has the feature set to grow as the community grows, although cost could be an issue later..
> 
> You may want to check -  https://flock.com/
> 
> Cheers!
> Bhaves
> 
>> On 4 Feb 2019, at 10:36 AM, Yuriy Dybskiy <yuriy@dybskiy.com> wrote:
>> 
>> Akash, really great proposal!
>> I've been using Discord more and more lately so I'm definitely +1 on that one. 
>> Rocket.chat is built with Meteor and I used to be a huge fan of it so I'm +1 on that option as well :)
>> 
>> Discord might be the easiest to setup and more polished so slight preference there, but long term maybe Rocket.chat is a better option.
>> Curious what others think.
>> 
>>> On Sat, Feb 2, 2019 at 7:02 PM AKASH KHOSLA <akhosla@berkeley.edu> wrote:
>>> 
>>> Hi all,
>>> 
>>> I was wondering if there would be any interest in moving from Gitter to another platform. The main reason I bring this up is because Gitter could be out of the way for a lot of us and the application doesn't encourage dedicated usage. Email lists are a bit old school and signing up for the Interledger one is out of the way. I think the reason for such a cryptic interface for the w3c style/linux foundation emails list is sybil resistance and anti-spam since there are liberal write permissions to the lists. I think scaling the community requires something better than email and Gitter. Would be great to hear thoughts on this.
>>> 
>>> Couple problems with Gitter:
>>> Clunky interface
>>> Poor separation of conversations/rooms
>>> Bad search function
>>> Bad mobile app
>>> 
>>> Some alternatives I think users enjoy using, and are well known in dev communities:
>>> 
>>> Rocket.chat
>>> Pros:
>>> Open source chat (basically a friendly IRC replacement)
>>> Self hosting is free, cloud options available, easy to deploy with scripts
>>> Slack-like interface
>>> Good search functionality
>>> Threads are being implemented
>>> Usable mobile applications
>>> Actively maintained + marketplace integrations
>>> Can deploy at chat.interledger.org (would be happy to help).
>>> Easy sign in with GitHub, just like gitter.
>>> Cons:
>>> Not as well known as discord, slack or gitter from what I can tell, but I expect it to continue to grow in usage down the line and gain even more support than it already has.
>>> 
>>> Discord
>>> Pros:
>>> Commonly used
>>> Free to use unlike sack
>>> Fast and friendly
>>> Solid mobile apps
>>> Actively maintained
>>> No self hosting or maintenance
>>> Supports integrations
>>> Cons:
>>> May not be free forever
>>> Chat logs are owned by Discord
>>> More complex interface than Slack/Rocket (some colleagues and I describe it as heavier
>>> 
>>> This list may not be complete in terms of pros and cons so please chime in if you have a personal preference or have something to say about these platforms or others. I've spent some time with both alternatives, you can generally find demos on their corresponding websites to see what you like best.
>>> 
>>> 		
>>> Akash Khosla
>>> Fourth Year EECS
>>> akhosla@berkeley.edu
>> 
>> 
>> -- 
>> Best regards,
>> Yuriy @html5cat Dybskiy
>> 
>> e-mail: yuriy@dybskiy.com
>> phone: +1 (650) 434-2004
>> 
>> Dybskiy.com / Twitter / GitHub / Linkedin