Re: [services] [rt.blitzed.org #927] Re: Expiring channel founder takes channel(s) with them
"Andy Smith via RT" <[email protected]>
| Newsgroups | gmane.network.irc.blitzed.general |
|---|---|
| Message-ID | <[email protected]> |
On Sun, May 09, 2004 at 11:02:32AM +0100, Phil Clarke via RT wrote: > Andy Smith via RT wrote: > > a) Give the channel to the successor. If there isn't a successor > > set then give it to the user who is highest on the access list. > > In case of a tie in access levels, give it to the oldest nick. > > If there's no one on the access list, delete the channel. > > > > b) When the channel is a week or so away from being deleted, start > > to warn people on-join about that, so they know that they need to > > find their founder. Other than that, don't do anything - the > > channel can only be saved if someone finds the founder. > > > > c) As (b) above but then if it still ends up in deletion, do (a). > > c) + email to founder, but channel only given to someone else if > successor is defined. Presumably if they have set a successor then there is no need to actually warn the channel though, right? I mean, the warning would look a bit weird.. -ChanServ- The nickname of the founder of this channel will -ChanServ- expire in $foo days. If the founder doesn't identify -ChanServ- to their nick before then, this channel will be -ChanServ- transferred to the successor, $bar. See /msg ChanServ -ChanServ- HELP SET SUCCESSOR for more information. seems a bit lengthy, but anything less would confuse them more, or panic them if they thought their channel was going to be deleted. Better just to not tell them anything, only send an email to the founder? -- http://freebsdwiki.org/ - Encrypted mail welcome - keyid 0xBF15490B "In Vegas, I got into a long argument with the man at the roulette wheel over what I considered to be an odd number." -- Steven Wright