James Hess wrote:
So, since there's no way to perform a transactional sequence of all-or-nothing services commands, there's a chance that a previous temp founder could be erroneously kicked and banned by services, due to a net split.
In between issuing the "SET FOUNDER" command and the "SOP ADD" command, which services never receives due to the netsplit.
Sure, but it's a chance we're willing to take.
Out of curiosity... does this mean if you use "SET FOUNDER" on a channel, you must be removed from all AOP and SOP lists first for SET FOUNDER to succeed... or that ChanServ will automatically remove the new founder from all AOP and SOP lists while performing this operation?
No, it's working exactly like before although I guess it might make sense to remove them from any access list during a successful ChanServ SET FOUNDER. -Kobi.