Re: Retirement of IRC Services and KDETalk.net (Jabber)
On Sun, May 21, 2023 at 3:12 PM Ben Cooksley wrote: > > On Sun, May 21, 2023 at 10:42 PM Christian (Fuchs) wrote: >> Bouncer wise: 30 connections isn't exactly none, especially if that contains >> active people. These would be forced to migrate to a service (and register at >> such) which is not under KDEs control and, as far as I am aware, has a >> mandatory registration. As far as memory serves some communities, e.g. I >> think krita, still had active devs / maintainers on IRC. > > > Yes, there is a cost-benefit analysis to all services we run however - and if > there is a minimal number of people benefiting from it, sometimes it is time > to retire a service. > > Note that the 30 I quoted was a count of TCP connections - so included > inbound and outbound links. > The number of connected clients is much, much smaller - so it is possible > there are some IRC connections still active for people that are no longer > around, or who have moved to Matrix and not deactivated the BNC. I would argue that the low usage is in part due to lack of awareness. It has a one-line mention on the "Internet Relay Chat" community wiki page (which wasn't added until 2019) that doesn't even explain the benefits of using it. IRC in combination with the BNC is much more suited to intermittent usage than Matrix is, which currently obligates the user to "be active" every 30 days, or risk (permanently!) losing access to the entirety of the history of all of their joined channels (even the parts for which they were present). The BNC happily buffers the text until your client is able to reconnect. As an example, this allowed me to read discussions that happened while I endured an extended power outage, even when Matrix had decided that I was idle for "too long". So instead of shuttering the service, I recommend that more attention be drawn to it.
Fwd: Survey for prioritization of requirements for an IM/chat solution for KDE
On Mon, Sep 4, 2017 at 8:48 PM, Eike Hein wrote:
> On September 5, 2017 8:15:47 AM GMT+09:00, Thomas Pfeiffer
> wrote:
>>Here are the results of the survey:
>>https://sessellift.wordpress.com/2017/09/05/results-of-the-requirements-survey-for-a-kde-wide-chat-solution/
>>Now it's time for us to find a solution that fits the profile!
>>Cheers,
>>Thomas
>
> Hi,
>
> I propose we:
>
> * Turn the must-have list into a wiki table and create columns for each chat
> solution
I've created the table and done a first pass of filling in the IRC
information: https://community.kde.org/IM_Survey_Results
I had a bit of trouble with Calligra Sheets, and so the first pass of
short descriptions is all there is for now.
> * In each cell, use
> ** ... a red background to indicate a feature is not available, and neither
> planned nor likely to happen
> ** ... a yellow background if a feature is either not yet widely available or
> still in the planning stages, with text (in the cell? footnote?) having to
> provide details including timeline of expect ed availability
> ** ... a green background if a feature is supported
Your wish is my command. It uses the same templates as WIkipedia:
{{No}, {{Maybe}}, {{Yes}}. There's also an {{H}} template (as on
Wikipedia) that provides a tooltip for longer explanations. If you
would like to know more about how to use them, you can check out their
documentation.
> I can take a stab at the Matrix and maybe IRC v3 columns (especially as the
> Konversation UI rewrite and planned Matrix support imho turns some
> additionals cells yellow, but even without Konvi-NG I think it's compelling
> personally).
>
>
> Cheers,
> Eike
> --
> Plasma, apps developer
> KDE e.V. vice president, treasurer
> Seoul, South Korea
~Eli
Re: The status of freenode (the IRC network used by KDE)
At the moment the "old" network appears to be broken into about 4 pieces. chat.freenode.net and irc.freenode.net point to the "new" network. The "new" network servers have a very low limit for connections per IP address (I don't know the number), and only 20 channels per user. I don't recommend connecting to the "new" network from a shared service such as bnc.kde.org. classic.freenode.net points to the most functional piece of the "old" network. If you wish to remain connected to the "old" network, replacing chat or irc.freenode.net with classic.freenode.net may work for the time being. I don't know for how long, nor how reliable. ~Eli On Mon, Jun 14, 2021 at 10:43 PM Nicolás Alvarez wrote: > > Freenode has now set up new servers without migrating the > nickserv/chanserv databases, and will likely turn off the old servers > later. You could say freenode has shut down and there is now a new > network under its name. We don't have any registered channels in the > "new network", or even channel topics set. > > Are we going to move to libera.chat already? > > It has been more than three weeks since Andrew Lee took over. I'm > *done* waiting for Matrix to reconfigure the bridge. Leaving it > unbridged entirely is preferred to the current situation. You can't > say that would split the chat community because it's already split > anyway (there's more users in libera.chat KDE channels every day, as > of yesterday irccloud users couldn't use freenode anymore, #kde hasn't > been properly bridged for a long time, etc). > > Just tell me when and I'll switch IrcsomeBot/sKreamer/pursuivant bots > to libera.chat, and update documentation (I already prepared commits > for 30+ repos for this). I can also bring IrcsomeBot into Matrix rooms > temporarily until the proper Matrix appservice is set up. But I will > not accept any more delays caused by Matrix/EMS. Let's get out of > freenode. > > -- > Nicolás
