Difference between revisions of "VHost"
Jump to navigation
Jump to search
(→Minutiae of the vHost system: made it clear that you cannot request a new vhost after getting one assigned) |
(changed wording on a couple things, added note to not use vhosts to impersonate under Usage rules) |
||
Line 15: | Line 15: | ||
Timing rules: | Timing rules: | ||
# wait 7 days | # wait 7 days before requesting a new vHost on the same nick | ||
# wait 1 day between vHost requests on grouped nicks | # wait 1 day between vHost requests on grouped nicks | ||
Usage rules: | Usage rules: | ||
# do not use vHosts to ban evade (doing so can lead to a network ban and a vHost ban) | # do not use vHosts to ban evade (doing so can lead to a network ban and a vHost ban) | ||
# do not use vHosts to impersonate other users or staff | |||
==Requesting a vHost== | ==Requesting a vHost== | ||
Line 35: | Line 36: | ||
*So if you keep on pounding the system without correcting your error, we see it. Over and over. | *So if you keep on pounding the system without correcting your error, we see it. Over and over. | ||
Once | Once a 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: | *When someone on the vHost team sees this message, we determine, based on the clues the vHost bot gives, such things as: | ||
**If the | **If the user has waited long enough before requesting a new vHost. | ||
**If the content and context of the vHost request passes | **If the content and context of the vHost request passes the rules. | ||
***This may include checking other language translations. | ***This may include checking other language translations. | ||
Line 48: | Line 49: | ||
Please do not experiment with different vHost requests, or put in a default example and expect to change it a few minutes later. | 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 cannot request a new vHost for a week. | *If it is accepted in one of those 13.8 second response times, you cannot request a new vHost on that nick for a week (As per timing rules above). |
Revision as of 15:17, 9 December 2013
A 'vHost' (virtual host) allows users to hide their hostmask (e.g., Rizon-BA37C5B3.rogers.com
) with something creative (e.g., i.am.awesome
). Colored vHosts can be won via a lottery: VIzon.
Rules
Format rules:
- must contain a dot (aka
.
) and can only contain alphanumeric characters, dots (.
) and dashes (-
);
some.vhost
somevhost
- must not contain a
@
blah@my.new.host
- must not be an IP or IP look-a-like
127.0.0.1
127.o.o.1
- must not resolve (basically, the vHost can't point to an actual site);
not.a.real.website
google.com
rizon.net
- 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;
join.my.channel
come.to.irc.blahblahblah.net
- must not refer to "kiddy"-like activity. (dosing, rooting, "carding," etc.)
Timing rules:
- wait 7 days before requesting a new vHost on the same nick
- wait 1 day between vHost requests on grouped nicks
Usage rules:
- do not use vHosts to ban evade (doing so can lead to a network ban and a vHost ban)
- do not use vHosts to impersonate other users or staff
Requesting a vHost
You must have a registered nickname in order to request a vHost.
- Type
/msg HostServ REQUEST vhost.goes.here
- Your request will be filtered by a bot
- Your request will then be manually approved by a human (please do not remind us of your request, we automatically get alerted already).
- Type
/msg HostServ ON
after you get a message saying the vHost was approved
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 a 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 user has waited long enough before requesting a new vHost.
- If the content and context of the vHost request passes the 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 cannot request a new vHost on that nick for a week (As per timing rules above).