[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Bridging #kde-devel on Freenode to Telegram
From:       Nicolás_Alvarez <nicolas.alvarez () gmail ! com>
Date:       2020-06-15 0:29:36
Message-ID: CANPC-tt-zYTnQoB+hpg7D-mFobPqR-YtqBDgP1rj4qHxM14wFw () mail ! gmail ! com
[Download RAW message or body]

El mié., 10 de jun. de 2020 a la(s) 20:16, Nicolás Alvarez
(nicolas.alvarez@gmail.com) escribió:
>
> El mié., 10 de jun. de 2020 a la(s) 20:06, Carson Black
> (uhhadd@gmail.com) escribió:
> >
> > Currently, #kde-devel is not set up with an IRC bridge to Telegram,
> > meaning users cannot access it from Telegram.
> >
> > Plugging it into our current bridge infrastructure would have the
> > following benefits:
> > - Telegram-only users (yes, those exist because neither IRC nor Matrix
> > are suitable for their needs and wants) don't have a room to discuss
> > KDE development stuff, and end up clogging other rooms with tangential
> > topics
> > - This lowers the barrier to entry for new contributors regarding
> > conversation both in terms of internet connections (IRC and Matrix
> > aren't very good regarding tolerance to bad internet for different
> > reasons) and in terms of user experience (IRC is ancient, Matrix is
> > often overwhelmed and laggy).
> > - Improving the coverage of the IRC bridge infrastructure allowing
> > contributors to freely choose what service they'd like to converse
> > with KDE with.
> >
> > If nobody has any objections to bridging #kde-devel to IRC, the bridge
> > bot will be set up to bridge https://t.me/kdedevel to #kde-devel.
>
> (Carson knows this but background for everyone else:)
>
> #kde-devel currently has an IRC ban on *@*/bot/*, which prevents any
> (properly identified) bots from joining, including our Telegram
> bridge. This block has been there since at least 2017 (probably *much*
> earlier, but that's the earliest I find in my IRC logs). I assume that
> ban is there for a reason, and I didn't want to remove it without some
> semblance of community agreement.
>
> Maybe someone remembers why bots are banned in #kde-devel?

Well, if there are no objections, I will remove the bot ban in
#kde-devel and set up the bridge tomorrow.

-- 
Nicolás
[prev in list] [next in list] [prev in thread] [next in thread]