radical proposal: move IRC to Rocket.Chat

[Christian Loosli]

Hi, 

Yup, I am aware, I already did spread that freenode internally a couple of 
weeks ago (when I saw the first post on planet KDE), thanks. 

Our current issue is more the mix of authentication systems and to use 
something like SAML or the likes to integrate them, which, as far as I am 
aware, is not a point resolved in brooklyn  (minor sidenote: that name is 
already taken by the apache foundation). 

I'm sure we'd get in touch with them once we are in a stage where we tackle 
the problems brooklyn tackles, unfortunately as an already existing network we 
have a couple of additional things to tackle first. 

Thanks for the info, kind regards, 

Christian 

Am Mittwoch, 9. August 2017, 09:49:27 CEST schrieb Cristian Baldi:
> We have a GSoC student working on a RocketChat<~>Telegram<~>Irc bridge
> which as of now has support for files, images, video messages and so on.
> Take a look here
> http://rivadavide.blogspot.com/2017/08/brooklyn-02-released-ready-for.html
> .  We are using it at WikiToLearn and it is working fine.
> 
> On Wed, Aug 9, 2017, 11:28 Christian Loosli <kde at fuchsnet.ch> wrote:
> > Post Scriptum, as I discussed this and learned that what I hinted at in
> > the -
> > cafe channel yesterday is public information:
> > 
> > We (freenode) are looking into support (not moving to, mind) for rocket.
> > Some details can be found here:  https://www.facebook.com/eximious/posts/
> > 
> > 10155436766365761?comment_id=10155438680590761&comment_tracking=%7B%22tn%2
> > 2%3A %22R3%22%7D
> > <https://www.facebook.com/eximious/posts/10155436766365761?comment_id=1015
> > 5438680590761&comment_tracking=%7B%22tn%22%3A%22R3%22%7D>
> > 
> > (sorry for facebook link, quote for those who rather not:
> > "We (freenode) have had quite a few conversations with projects that
> > struggle
> > with Slack -- they use it but are finding it difficult, partly because it
> > is
> > proprietary and doesn't align too well with their values and partly
> > because it
> > is resulting in a great deal of community fragmentation. We're currently
> > looking at implementing rocket.chat support to allow projects such as
> > those to
> > map their own rocket.chat instances to their channel namespace on freenode
> > in
> > a bid to reduce the community fragmentation they experience. Totally
> > hoping
> > that it will solve those issues for them!")
> > 
> > which might be a solution that pleases both people who want to use Rocket
> > and
> > people who want to not abandon other more or less well used protocols.
> > 
> > Bonus points: due to the Matrix and Telegram bridge we already have, if we
> > manage to properly integrate Rocket, one can probably use either of the
> > four
> > and be happy. Obviously with some loss of features, as e.g. protocol a
> > might
> > not support something of protocol b. How well this will be implemented
> > depends
> > on the bridge, e.g. files or stickers could be integrated via links iff
> > someone
> > codes that.
> > 
> > Unfortunately IRC would still not get support for animated stickers and
> > custom
> > pile of poop emojis, sorry to crush hopes there.
> > 
> > Sorry for not mentioning this earlier, I wasn't sure at this very early
> > stage
> > whether it is public or not.
> > 
> > Regards,
> > 
> > Christian