- From: Daniel Bateman <7daniel77@gmail.com>
- Date: Fri, 26 Aug 2016 15:22:37 +0100
- To: Adrian Hope-Bailie <adrian@hopebailie.com>
- Cc: Interledger Community Group <public-interledger@w3.org>
Received on Friday, 26 August 2016 14:23:08 UTC
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 Friday, 26 August 2016 14:23:08 UTC