Run /msg NickServ LISTCHANS
to see what permissions you have in what channels.
For each channel you have +s
, +R
and either +o
or +O
or +t
permissions in, run:
/msg ChanServ OP #channel
/msg ChanServ SET #channel TOPICLOCK OFF
/msg ChanServ TOPIC #channel We have moved to irc.libera.chat
/topic We have moved to irc.libera.chat
/msg ChanServ SET #channel TOPICLOCK ON
/msg ChanServ SET #channel KEEPTOPIC ON
/msg ChanServ SET #channel GUARD ON
/msg ChanServ SET #channel ENTRYMSG We have moved to irc.libera.chat
/msg ChanServ SET #channel MLOCK +fist ##moved_to_libera
/msg ChanServ CLEAR #channel BANS I
/msg ChanServ CLEAR #channel USERS We have moved to irc.libera.chat
/part #channel
These will kick everyone out of the #channel
(ChanServ is unkickable), and will make any attempts to join the channel result in joining ##moved_to_libera
instead. Note that this clears channel's invite list to achieve that.
It will also hide the channel from /list
, in a perhaps futile attempt to slow down the new Freenode staff from dropping the channel.
You might want to edit the message to indicate the new channel name, if it differs on Libera. Note that the message is used in four places, so don't forget to edit them all!
If you are extra paranoid, you could setup your own duplicate of ##moved_to_libera
, e.g. #channel-libera
, and use that instead.
Explanation of the required channel permissions: you need +s
to use the SET
commands, +R
to use the CLEAR
commands and any of +o
/+O
/+t
to change the channel topic one way or another.
If you only have +o
or +O
permissions in a channel, you could achieve close to the above by running:
/msg ChanServ OP #channel
/topic We have moved to irc.libera.chat
/mode #channel +fist ##moved_to_libera
then checking the invite list with /mode #channel +I
and removing everyone from it one by one with /mode #channel -I nick
,
then kicking everyone from the channel one byone with /kick nick We have moved to irc.libera.chat
.
It is possible for the /topic
command to fail if the channel has TOPICLOCK
flag set and you don't have +t
permission.
Note that the channel modes will be lost if the channel becomes empty, so without being able to use MLOCK
to make the modes persistent, it's the best to stay in the channel to keep them alive. If the channel has GUARD
listed in /msg ChanServ info #channel
then ChanServ should remain in the channel, which should prevent the channel from dropping the modes.
@Minoru added the
ENTRYMSG
.