MovingChannels

Differences between revisions 1 and 2
Revision 1 as of 2010-01-17 09:15:09
Size: 2166
Editor: a88-112-92-111
Comment:
Revision 2 as of 2011-05-23 02:31:47
Size: 2389
Editor: cpc2-smal7-0-0-cust80
Comment: Update and add extra info
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
/MSG ChanServ op #oldchannel
/MSG ChanServ op #newchannel
Line 10: Line 12:
/MSG ChanServ SET #Oldchannel GUARD ON
/MSG ChanServ SET #Oldchannel MLOCK +tnmif #Newchannel
/MSG ChanServ SET #Oldchannel TOPICLOCK ON
/MSG ChanServ SET #Oldchannel PRIVATE ON
/MSG ChanServ SET #oldchannel GUARD ON
/MSG ChanServ SET #oldchannel MLOCK +tnmif #newchannel
/MSG ChanServ SET #oldchannel TOPICLOCK ON
/MSG ChanServ SET #oldchannel PRIVATE ON
Line 25: Line 27:
to let Chan``S``erv always sit in the channel. to let Chan``Serv always sit in the channel.
Line 33: Line 35:
/MSG ChanServ FLAGS #oldchannel LIST /MSG ChanServ ACCESS #oldchannel LIST
Line 38: Line 40:
/MSG ChanServ FLAGS #newchannel <Nickname/Mask> <Flags> /MSG ChanServ FLAGS #newchannel <Account/Mask> <Flags>
Line 40: Line 42:
where ''<Identifier>'' and ''<Flags>'' are the ones shown in the list. where ''<Account/Mask>'' and ''<Flags>'' are the ones shown in the list.
Line 45: Line 47:
}}}

It is also recommended that the [[IRC/IrcCouncil|IRC Council]] are added to the access list:
{{{
/MSG ChanServ FLAGS #newchannel UbuntuIRCCouncil +votiA

When an IRC channel's name must be changed, there are procedures that can ease the transition and automatically redirect users to the new channel.

These instructions assume that #oldchannel needs to be closed, and moved to #newchannel.

If you have any questions, please join the channel #ubuntu-irc for further assistance.

To achieve this, the channel contact, or another operator with a sufficiently high access level, can use the following commands:

/MSG ChanServ op #oldchannel
/MSG ChanServ op #newchannel
/TOPIC #oldchannel We have moved to #newchannel, please type /join #newchannel to get to us
/MSG ChanServ SET #oldchannel GUARD ON
/MSG ChanServ SET #oldchannel MLOCK +tnmif #newchannel
/MSG ChanServ SET #oldchannel TOPICLOCK ON
/MSG ChanServ SET #oldchannel PRIVATE ON

This should be done after registering #newchannel, which can be achieved in the following way:

/JOIN #newchannel
/MSG ChanServ REGISTER #newchannel

and optionally

/MSG ChanServ SET #newchannel GUARD ON

to let ChanServ always sit in the channel.

Please keep the Channel name policies in mind when creating new Ubuntu channels.

Then, the access list (the list of operators) must be re-created on #newchannel.

The access list of #oldchannel can be viewed with

/MSG ChanServ ACCESS #oldchannel LIST

Operators can then be added to #newchannel with

/MSG ChanServ FLAGS #newchannel <Account/Mask> <Flags>

where <Account/Mask> and <Flags> are the ones shown in the list.

It is highly recommended that freenode staff is added to the access list:

/MSG ChanServ FLAGS #newchannel *!*@freenode/staff/* +votiA

It is also recommended that the IRC Council are added to the access list:

/MSG ChanServ FLAGS #newchannel UbuntuIRCCouncil +votiA

Bots

If any bots were present in #oldchannel, you should contact the bot owners to notify them of the channel name change.

As a temporary stop-gap measure, however, you can try to kick the bots using the command

/KICK #oldchannel <BotNickName>

after the previous steps have been completely. It is then possible, though not guaranteed, that the bot will join the new channel.

Remember that you should still contact the bot owner in any case!


CategoryIRC

IRC/MovingChannels (last edited 2021-06-22 11:36:57 by guiverc)