Upheaval at freenode

Posted May 20, 2021 3:42 UTC (Thu) by rickmoen (subscriber, #6943)
Parent article: Upheaval at freenode

Occurrence just now noted without further comment, except that I've had ops (as "redrick") on Freenode's #svlug IRC channel for decades (and that my colleague Rob "lilo" Levin, faults notwithstanding, would have been embarrassed):

15:28 -!- Topic for #svlug: Welcome to #svlug, the Silicon Valley Linux User
Group's 24x7 meeting. Regular meeting 1st Wednesday.
http://www.svlug.org/
15:28 -!- Topic set by redrick [] [Thu Dec 8 19:10:41 2011]
15:28 [Users #svlug]
15:28 [@ChanServ] [ octorian] [ quaid] [ redrick] [ scubacuda]
15:28 -!- Irssi: #svlug: Total of 5 nicks [1 ops, 0 halfops, 0 voices, 4 normal]
15:28 -!- Home page for #svlug: http://www.svlug.org/
15:28 -!- Channel #svlug created Sat Nov 25 22:43:22 2006
15:28 -!- Irssi: Join to #svlug was synced in 8 secs
15:28 -!- mode/#svlug [+o redrick] by ChanServ
20:33 -!- redrick changed the topic of #svlug to: Welcome to #svlug, the
Silicon Valley Linux User Group's 24x7 meeting.
http://www.svlug.org/ IRC presence moved to irc.libera.chat .
20:33 -!- ChanServ changed the topic of #svlug to: Welcome to #svlug, the
Silicon Valley Linux User Group's 24x7 meeting. Regular meeting 1st
Wednesday. http://www.svlug.org/
20:33 -!- mode/#svlug [-o redrick] by ChanServ
20:33 -!- #svlug You're not a channel operator

Okay-then.

Upheaval at freenode

Posted May 20, 2021 4:33 UTC (Thu) by alison (subscriber, #63752) [Link]

> I've had ops (as "redrick") on Freenode's #svlug IRC channel for decades

Rick, svlug has had a channel for decades? Now you tell me!

Upheaval at freenode

Posted May 20, 2021 11:49 UTC (Thu) by grifferz (subscriber, #62128) [Link] (9 responses)

> 20:33 -!- redrick changed the topic of #svlug to: Welcome to #svlug, the Silicon Valley Linux User Group's 24x7 meeting. http://www.svlug.org/ IRC presence moved to irc.libera.chat .
> 20:33 -!- ChanServ changed the topic of #svlug to: Welcome to #svlug, the Silicon Valley Linux User Group's 24x7 meeting. Regular meeting 1st Wednesday. http://www.svlug.org/

Someone pointed out that #svlug has TOPICLOCK set on it, so isn't this just ChanServ setting the topic back to what it was locked to?

I too have been forced to remember more about IRC in the last two days than I am happy about.

Upheaval at freenode

Posted May 20, 2021 16:17 UTC (Thu) by rickmoen (subscriber, #6943) [Link] (8 responses)

grifferz, I notice that, but ChanServ immediately removing my nick's "o" flag after I attempted to set /topic (as shown) prevents me from taking further action. I'm not making accusations, but just note the odd coincidence of my account getting de-op'd the moment I tried to set /topic to mention a move to Libera.Chat. (Perhaps a weird anomaly, perhaps otherwise.)

My nick "redrick" has had and used +o on Freenode's #svlug channel for a very long time (reflected at the top of the transcript). Although I'm rusty at all this, I've re-queried ChanServ to confirm, and lack of an op flag in #svlug has persisted.

Upheaval at freenode

Posted May 21, 2021 1:35 UTC (Fri) by pabs (subscriber, #43278) [Link] (7 responses)

ChanServ says that you have access, so maybe do this:

/msg chanserv topic #svlug Moved to libera.chat

Upheaval at freenode

Posted May 21, 2021 4:57 UTC (Fri) by rickmoen (subscriber, #6943) [Link]

I would guess that a friendly admin fixed what ChanServe knew, as this happened today:

Day changed to 20 May 2021
08:07 -!- mode/#svlug [+o redrick] by ChanServ

My thanks to whoever (apparently) stepped in.

Upheaval at freenode

Posted May 23, 2021 21:39 UTC (Sun) by rickmoen (subscriber, #6943) [Link] (5 responses)

I'm afraid mischief on Freenode's channels continues. The last few days, I noticed that massive numbers of Devuan Project regulars were getting notices of the form

nn:nn -!- [nick] was kicked from [channel] by ChanServ [You are not authorized to be on this channel]

...for no apparent reason, usually followed by banning of the user's IP. (For context, nobody in Devuan Project has been involved even slightly in the dispute between Mr. Lee and the departed staff. ) For example, from yesterday:

05:42 -!- pepe75 was kicked from #devuan by ChanServ [You are not authorized to be on this channel]
05:53 -!- mode/#devuan [+o DocScrutinizer05] by ChanServ
05:54 <@DocScrutinizer05> moving channel to libera, please click
                          ircs://irc.libera.chat:6697/#devuan-dev  or see
                          https://libera.chat/ and
                          https://libera.chat/guides/registration
05:54 -!- mode/#devuan [-o DocScrutinizer05] by ChanServ
06:08 -!- mode/#devuan [+b *!*@p200300e617198700021fd0fffe8178d8.dip0.t-ipconnect.de] by ChanServ
06:08 -!- noxx was kicked from #devuan by ChanServ [You are not authorized to be on this channel]
06:08 -!- mode/#devuan [+b *!*@213.170.218.225] by ChanServ
06:08 -!- orcus-de was kicked from #devuan by ChanServ [You are not authorized to be on this channel]
06:15 -!- mode/#devuan [+b *!*@207.148.96.120] by ChanServ
06:15 -!- m4rley was kicked from #devuan by ChanServ [You are not authorized to be on this channel]
05:54 -!- mode/#devuan [-o DocScrutinizer05] by ChanServ
06:08 -!- mode/#devuan [+b *!*@p200300e617198700021fd0fffe8178d8.dip0.t-ipconnect.de] by ChanServ
06:08 -!- noxx was kicked from #devuan by ChanServ [You are not authorized to be on this channel]
06:08 -!- mode/#devuan [+b *!*@213.170.218.225] by ChanServ
06:08 -!- orcus-de was kicked from #devuan by ChanServ [You are not authorized to be on this channel]
06:15 -!- mode/#devuan [+b *!*@207.148.96.120] by ChanServ
06:15 -!- m4rley was kicked from #devuan by ChanServ [You are not authorized to be on this channel]
18:19 -!- mode/#devuan [+v infobot] by ChanServ
18:38 -!- mode/#devuan [+o Sigyn] by ChanServ
18:39 -!- mode/#devuan [+o Sigyn`] by ChanServ
18:49 -!- mode/#devuan [+o Sigyn] by ChanServ
19:43 -!- mode/#devuan [+o Sigyn] by ChanServ

This mass-exclusion reached me this afternoon:

13:06 -!- redrick was kicked from #devuan-offtopic by ChanServ [You are not authorized to be on this channel]
/join #devuan-offtopic
14:28 -!- Cannot join to channel #devuan-offtopic (You are banned)

Why? Unstated. At the time the dispute broke, a couple of days ago, I had mentioned on channel #devuan-offtopic a couple of mainstream news article URLs about it, without editorial comment — very nearly the only thing I've said there in a month or two. Am guessing that the new channel operators are reading IRC logs and kicking (and in some cases IP-banning) anyone who even mentioned the controversy in any way.

Upheaval at freenode

Posted May 24, 2021 0:37 UTC (Mon) by pabs (subscriber, #43278) [Link] (3 responses)

What you posted means the Devuan channel operators moved the channels to libera and then set the "restricted" mode on the channel, which prevents people from joining the channel and bans them when they do. It is a fairly confusing way of redirecting people to another network, but it is effective.

The Devuan website says that they have moved to Libera:

"Devuan-related channels are found on the Libera IRC network"

https://www.devuan.org/os/community

Upheaval at freenode

Posted May 24, 2021 1:31 UTC (Mon) by rickmoen (subscriber, #6943) [Link] (2 responses)

pabs, that's possible, thanks. I attended the Thursday Devuan planning meeting that agreed upon what to do about the dispute. FWIW, at that time there was no plan to set restricted mode on any existing channel -- to the best of my recollection.

Upheaval at freenode

Posted May 24, 2021 1:36 UTC (Mon) by pabs (subscriber, #43278) [Link] (1 responses)

That may have been my fault, I recommended restricted mode to DocScrutinizer05 for another channel after noting its use on another channel I was on.

I don't know if there is a less harsh but still effective way to indicate a channel has moved to another network.

Either way, it sounds like freenode policies are changing to allow them to revert any indicators that a channel has moved to another network.

Upheaval at freenode

Posted May 24, 2021 2:26 UTC (Mon) by rickmoen (subscriber, #6943) [Link]

That makes sense (and I just found the ChanServ docs explaining what SET RESTRICTED causes to happen in a channel, just as you posted that). Appreciate your help figuring it out.

Upheaval at freenode

Posted May 24, 2021 1:49 UTC (Mon) by pabs (subscriber, #43278) [Link]

FTR DocScrutinizer05 has switched #devuan-dev to moderated mode instead of restricted mode, the other channels might get the same treatment when an op is available.

Upheaval at freenode

Posted May 20, 2021 15:23 UTC (Thu) by amacater (subscriber, #790) [Link] (1 responses)

Having everyone except Debian ... someone made the point that Debian developers and some other Debian folks tended to hang out on OFTC while Debian _users_ tended to hang out on Freenode.

OFTC is still very much there so maybe those seeking Debian advice/assistance/company will re-coalesce there more readily.

[Disclaimer: Not speaking on behalf of the Debian Project: no particular connection with either IRC provision other than as satisfied user of OFTC for a while.]

Upheaval at freenode

Posted May 21, 2021 1:39 UTC (Fri) by pabs (subscriber, #43278) [Link]

Looks like the #debian channel is now on OFTC, freenode and libera, with the latter two having a reminder that irc.debian.org points at irc.oftc.net. There are a surprising amount of other Debian channels on freenode and libera, although most Debian channels are indeed on OFTC.