Information about NewNet services upgrade of 2015-08

The following conversation in ****** #**** indicates that the network services were updated, causing some registered channels to be dropped because their access lists contained incompatible entries:

	<P***> what happened? Why some channels were unregistered?
	<@R********> ccess lists a lil differnt
	<@R********> err
	<@R********> services update handles access lists a lil differntn
	<@R********> so some chans r expiring
	<@R********> need to rereg and updated userlist
	<P***> uh... Sorry, but I don't understand
	<@R********> its a side effect of new services update founders not identifying and users not being reconized on access list as far as i can tell
	<P***> ah, okay, thanks. Should I reregister channels, or just wait until it will be repaired?
	<@R********> rereg and look nat6 new access list options
	<@R********> at
	<P***> k, thanks

To re-register your channel, everybody will must leave the channel, then the owner must join the channel, obtaining mode +o, before registering it with ChanServ (see /msg ChanServ HELP REGISTER).

P.S. If ChanServ is squatting in a channel after you re-register it, and you want him to leave, the ChanServ PART command will no longer work, and you'll have to instead use the following two commands, replacing #channel with the name of your channel:

	/msg ChanServ SET PERSIST #channel OFF
	/msg BotServ UNASSIGN #channel