The only "benefit" here seems to be user friendliness (HTTP is ancient and C++ is but both are still used)
On Wed, Jun 10, 2020, at 16:07, Nate Graham wrote: > +1 if even only for the new contributor friendliness angle. Many other > channels are bridged to Telegram; probably this one should be as well. > > Nate > > > > On 6/10/20 5:05 PM, Carson Black wrote: > > 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. > > >
