Retirement of IRC Services and KDETalk.net (Jabber)

Ben Cooksley bcooksley at kde.org
Sat Jun 10 23:54:23 BST 2023


On Sun, Jun 11, 2023 at 3:52 AM Thiago Masato Costa Sueto <
herzenschein at gmail.com> wrote:

> Hello,
>
> I only want to comment on two things:
>
> > Depending on the level of community interest, we may opt to retain
> pursuivant however i'd like for it to be rebuilt as a Matrix native service
> rather than being a continuation of our existing irker based bot that
> occasionally has issues and falls off.
>
> FWIW I always found pursuivant really offputting for some of our groups.
> In some of them, like the documentation group, it's possible for the
> channel to be flooded with only bot messages for months. I can't really
> follow messages there, people who occasionally visit are put off by it and
> never see any replies either. It becomes a notification group, not a
> conversation group.
>
> If we're turning pursuivant into a Matrix service, I'd also like to ask
> for it to be used only on dedicated channels, not in rooms where users are
> expected to interact with other community members.
>

What messages are posted by pursuivant is fully tunable, and governed by
the configuration in sysadmin/irc-notifications

While the Jenkins components in there are no longer of use, the Bugzilla
announcements for new bugs, and commit announcements for commits to given
repositories both work and are fully tunable.


>
> > Telegram is huge popular in Brazil. Our KDE Brasil group has now 608
> members, and we have other KDE developers groups in Telegram related to
> Brazilian community.
>
> > Maybe if we have a deadline, we can make efforts to migrate the groups
> to Matrix. But, if we can not do that properly, we can take a look at
> other bots like telegram:t2bot.io [1]
>
> As mentioned we have 608 members. Of course, this also includes lurkers
> (inactive members).
>
> I made a recent count and apparently at least 67 are active members. In
> comparison, we have 12 Matrix members, all of them active, of which 5 are
> only on Matrix and prefer it over Telegram. One of our Brazilian KDE
> developers is only on IRC.
>
> Another thing to note is that I agree the current state of the bridge is
> NOT fine. The KDE Matrix Bridge bot gets kicked by the appservice bot too
> often, forcing me to re-add it, and it keeps sending join/leave
> notifications to the Telegram side, sometimes literally hundreds, flooding
> the channel. Our users have started to complain about it.
>

Note that "KDE Matrix Bridge" is different to the bridge i'm wanting to
discontinue here.
The bridge i'm looking to discontinue is the one known as "IrcsomeBot" (on
Libera/Matrix) which is quite different.


>
> We can pursue an effort to move fully to Matrix as Filipe said, maybe even
> stage some collaboration with a local homeserver (bolha.chat) for new
> accounts, or we can stay only on Telegram due to popular demand. We haven't
> decided yet.
>
> I'd personally be in favor of moving to Matrix.
>
> Regards,
> Thiago Sueto
>

Cheers,
Ben


>
> Em sáb., 10 de jun. de 2023 às 09:57, Filipe Saraiva <filipe at kde.org>
> escreveu:
>
>> Hello Ben,
>>
>> Em 21/05/2023 06:37, Ben Cooksley escreveu:
>> > Given that we are now fairly well migrated to Matrix, the need to
>> > maintain our Telegram bridging is much reduced, and i'd therefore like
>> > to retire that without replacement.
>> >
>>
>> Telegram is huge popular in Brazil. Our KDE Brasil group has now 608
>> members, and we have other KDE developers groups in Telegram related to
>> Brazilian community.
>>
>> Maybe if we have a deadline, we can make efforts to migrate the groups
>> to Matrix. But, if we can not do that properly, we can take a look at
>> other bots like telegram:t2bot.io [1]
>>
>> Best regards;
>>
>> [1] https://t2bot.io/telegram/
>>
>> --
>> Filipe Saraiva
>> http://filipesaraiva.info/
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20230611/0a35a888/attachment.htm>


More information about the kde-devel mailing list