Updates to user hostmasking per our last round of discussions #174
Added new config.h option: USER_HOSTMASKING_FALLBACK_TO_IP. This is used to hostmask using the user's IP address if we are unable to hostmask using their hostname. This usually happens if they're using a domain name without a lot of labels: somehost.com or company.co.uk or similar.
Do not attempt to mask the Staff_Address for opers.
Do not allow opers who are already hostmasked to set +H as this results in weird /whois results.
Send out WATCH notifications if the hostname changes due to a mode H change. I am open to feedback whether this makes sense or not, but I thought of it as I was testing so I figured I'd add it.
Added new config.h option: NO_UMODE_H_FLOOD. Do not allow the user to change user mode H too often, to prevent WATCH flooding.
Do not allow user mode H to be changed if the user is in any channels. This is to prevent potential client-side weirdness from happening if a user's host changes while they're already in one or more channels.
I setup the error messages to use a simple NOTICE because it seems like that's what we've been doing lately. Are we abandoning the whole concept of numerics? Or should I convert these errors to numerics instead?
Updates to user hostmasking per our last round of discussions #174
USER_HOSTMASKING_FALLBACK_TO_IP. This is used to hostmask using the user's IP address if we are unable to hostmask using their hostname. This usually happens if they're using a domain name without a lot of labels: somehost.com or company.co.uk or similar.NO_UMODE_H_FLOOD. Do not allow the user to change user mode H too often, to prevent WATCH flooding.I setup the error messages to use a simple NOTICE because it seems like that's what we've been doing lately. Are we abandoning the whole concept of numerics? Or should I convert these errors to numerics instead?