A 'vHost' (virtual host) allows users to hide their hostmask (i.e.,
Rizon-BA37C5B3.rogers.com) with something creative (i.e.,
i.am.awesome). The nickname must be registered in order to request a vHost.
- must contain a dot (aka
.) and can only contain alphanumeric characters, dots (
.) and dashes (
- must not contain a
- must not be an IP or IP look-a-like;
- must not resolve (basically, the vHost can't point to an actual site);
- must not mimic government organizations (*.gov, *.gc.ca, FBI, etc.) or private organizations which have government affiliation (MPAA, RIAA, etc.);
- must not contain the words 'forum', 'ircop', 'admin', 'network', 'rizon', or any IRCop's nick;
- must not contain racist words (what is considered racist/derogatory is subject to discretion by vHost team members);
- must not refer to other networks/spamming;
- must not refer to "kiddy"-like activity. (dosing, rooting, "carding," etc.)
- vHosts are first filtered by a bot, which validates the vHosts against the rules. If your vHost keeps getting rejected and you think it is a mistake,
/join #servicesfor further assistance.
- vHosts must then be manually approved.
- Only one vHost every 7 days for the same nick; spamming the system with frequent requests will result in a ban from the vHost system.
- There is a waiting time of 1 day for newly grouped nicks.
- Ban evasion using vHosts will cause you to get: your vHost removed, network banned from Rizon for a set period of time, and vHost banned for an extended period.
Requesting a vHost
You must have a registered nickname in order to request a vHost. In order to register your nickname, please visit Register your nickname
To request a vHost, use the command
/msg HostServ REQUEST vhost.goes.here
Once your vHost is manually approved by a human, it can be turned on with
/msg HostServ ON
Minutiae of the vHost system
When you request a vHost, yes, a bot first checks it. But that request is also seen to the vHost team.
- So if you keep on pounding the system without correcting your error, we see it. Over and over.
Once your request is vHost bot approved, it is presented to the vHost team with a simple approve or reject choice.
- When someone on the vHost team sees this message, we determine, based on the clues the vHost bot gives, such things as:
- If the 7 day waiting period for new vHost requests has passed.
- If the content and context of the vHost request passes our rules.
- This may include checking other language translations.
And then finally, some human on the vHost team will accept or reject the request.
- This can take from between 13.8 seconds, and a few hours.
- Not everyone on the vHost team lives in your timezone.
- Sometimes a vHost team member may defer (put off) an answer pending consultation with other team members.
- Reminding staff to approve your vHost is nothing but frustrating. The vHost team did see your request in every condition where you got a valid response from the vHost request system. Please wait patiently.
Please do not experiment with different vHost requests, or put in a default example and expect to change it a few minutes later.
- If it is accepted in one of those 13.8 second response times, you are set with that vHost for a week.