James Hess wrote:
No amount of "some users have static IPs" justify SOp patterns like *!*sopusername@*.ipt.aol.com And yet, those sorts of patterns have been popular at times (in my estimation).
It's up to each channel founder to decide that for their channel.
Can you explain what it is about your use case, that prevents a NickServ access list from being used instead of a mask on the SOp list?
I was talking about SOP/AOP lists in general and not about SOP list in particular. An example would be an events channel run by 5 people from the same company with no regular nicknames. Rather than having them register 5 nicknames (they will never really use) just for the sake of holding op access (or a bot to automatically op them), they could just add *!*@A.B.C.* to the AOP list (or SOP list, if they want to permanently ban people too).
Listing the nickname in the ChanServ list provides better accountability, than a huge list of masks, 3 years ago, when nobody remembers which OP each mask belongs to.
In the past, services let people add un-registered nicks to AOP/SOP by *automatically* converting the entries to *!*ident@*.isp if they were online but not registered. This behaviour has been changed years ago and it is no longer happens automatically like it used to.
Furthermore, ChanServ SET IDENT is enabled by default so masks on AOP/SOP lists won't affect anything unless the founder specifically turns IDENT off.
Yes... I suppose they may give up with masks in frustration and try nickname.. or keep tinkering around with the settings until they figure out about this strange 'IDENT' setting, and how it's "stopping their ops from getting opped" (for some reason)
Then perhaps services should tell users they can't add masks to SOP/AOP lists while ident is enabled and why instead of letting them add it and "ignoring" it. -Kobi.