*A reason to allow toggling, is a user may be listed in some access lists using their old hostmask, and in other access lists using the masked version of their host. For example, they may be an operator of multiple channels, and be on the access list of multiple bots, some of which have been updated, some of which have not. It could be inconvenient for them to be unable to exercise access to both bots. If they could not switch between masked and unmasked, they might be forced to log multiple clients on IRC. Or reconnect each time, which causes inconvenience due to (1) the amount of channel chatter annoying other IRC users, and (2) needing to rejoin channels and re-authenticate with services every time. On Sat, Oct 31, 2009 at 10:26 AM, Vin King <vin.king@gmail.com> wrote:
To add to this, after looking into how much stuff I personally have that absolutely relies on hostmasks not silently changing, it turns out my script relies entirely on mIRC Internal Address List. Everything my script does assumes that hostmasks will not change during a session. I'm probably not the only mIRC user on the network, and I'm probably not the only user who uses it's IAL features extensively.
mIRC updates its internal address list at various times when presented with new information, it does not only update its internal address list at the start or end of a sesssion. mIRC also provides (or provided) commands that allow you the user to manipulate the IAL or even disable the IAL and rely on the client requesting userhost info each time. -- -J