W3C home > Mailing lists > Public > public-interledger@w3.org > August 2016

Re: IRC and Gitter

From: Marta Piekarska <marta@blockstream.io>
Date: Tue, 30 Aug 2016 06:13:10 -0700
Cc: Marta <marta@blockstream.com>, Adrian Hope-Bailie <adrian@hopebailie.com>, Daniel Bateman <7daniel77@gmail.com>, Interledger Community Group <public-interledger@w3.org>
Message-Id: <DB9EC6BF-6F21-4546-B08C-90FB772392C4@blockstream.com>
To: M AV <av_m@hotmail.com>
Also for slack - it has huge security issues:)
—
Security Architect @ Blockstream

mp@blockstream.com

+491703311307 (Germany)
+14159608938 (U.S.)
Signal, Wickr (martap)

> On Aug 29, 2016, at 10:34 AM, M AV <av_m@hotmail.com> wrote:
> 
> Cool – thx!
> 
> From: Adrian Hope-Bailie [mailto:adrian@hopebailie.com]
> Sent: Monday, August 29, 2016 1:34 PM
> To: M AV <av_m@hotmail.com>
> Cc: Daniel Bateman <7daniel77@gmail.com>; Interledger Community Group <public-interledger@w3.org>
> Subject: Re: IRC and Gitter
> 
> I polled the group about using Slack a while back and the general consensus was that they didn't want to use it and would prefer open tech like IRC.
> 
> If you log into Gitter you'll be able to link it to a Slack channel if that's what you'd like to do.
> 
> On 29 August 2016 at 18:27, M AV <av_m@hotmail.com> wrote:
> Any reason not considering Slack?
> 
> From: Adrian Hope-Bailie [mailto:adrian@hopebailie.com]
> Sent: Monday, August 29, 2016 5:57 AM
> To: Daniel Bateman <7daniel77@gmail.com>
> Cc: Interledger Community Group <public-interledger@w3.org>
> Subject: Re: IRC and Gitter
> 
> Update: Since the W3C IRC has no NickServ we can't use sameroom.io which requires this :(
> 
> On 29 August 2016 at 11:46, Adrian Hope-Bailie <adrian@hopebailie.com> wrote:
> re: 'possibly host' : We can host it ourselves (I will see if Ripple can sponsor this) or we can use a hosted service like sameroom.io.
> 
> re cost:
> - Sameroom.io = $49/month (5 channels),
> - hosted = is cost of hosting and people to manage/setup
> 
> On 26 August 2016 at 16:22, Daniel Bateman <7daniel77@gmail.com> wrote:
> For option 2, what is the cost of managing another service? And why is it 'possibly host?'
> 
> Daniel
> 
> On Aug 26, 2016 10:04 AM, "Adrian Hope-Bailie" <adrian@hopebailie.com> wrote:
> Hi all,
> 
> I have done some investigating and have two options for us with regard to using Gitter but still offering IRC for those that prefer that channel.
> 
> Option 1: Switch to Gitter hosted IRC server
> 
> If you visit http://irc.gitter.im you'll see instructions for connecting to a secure IRC server using a unique, per-user server key.
> 
> Once you connect you'll be logged into an IRC channel for each Gitter room and use the same Nick as your github username.
> 
> Anything posted in either system is mirrored in the other.
> 
> Pros:
> - Secure IRC
> - Tight integration with Gitter
> 
> Cons:
> - Need to switch to a new IRC server
> - Lose the W3C IRC bots
> 
> Option 2: Setup a bridge between Gitter and W3C IRC
> 
> There are bots that can monitor both systems and mirror messages between them. We can use https://sameroom.io or host a bot ourselves.
> 
> Pros:
> - Keep same IRC server and channel
> 
> Cons:
> - Need to manage (and possibly host) yet another service
> 
> Anyone have any thoughts on these options?
> 
> Adrian


Received on Tuesday, 30 August 2016 13:13:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 30 August 2016 13:13:44 UTC