On 7/19/13, Holbrook Bunting <holbrook@dal.net> wrote:
To keep from them changing their host like you suggest would be to place a limit on how often they can change their hostname for said nickname. Once a week? Once a month? [snip] I would say it's important that the Mask displayed not be false. The hostname should be an agreeable hostname according to internet standards; and it should not be possible to display a "fraudulent" mask such as OTHERISP.COM or DomainNotRegisteredToTheIRCUser.com.
The hostname should end with "masked.dal.net" or something else, that clearly demonstrates its a masked name, that could never be registered by anyone else; even under the new ICANN Generic TLDs program. Mandatory inclusion of a HEXCODE as I suggested above, also has great benefits, and I would strongly suggest that. If host masking is implemented; users should not be allowed to create "confusion"; by pretending "this is my real hostname", convincingly, when in fact, it is some kind of fiction. If custom domains are allowed, then the user should be required to demonstrate they can receive mail sent to postmaster@domain.example, or Administrative contact of the domain listed in WHOIS OR that there is a forward A record for that domain to an IP address that user has exclusive control over. -- -JH