VHost: Difference between revisions

From Xertion Wiki
Jump to navigation Jump to search
← Older edit
mNo edit summary
m Changed the Valid example for non-resolving hostnames from 'not.a.real.website' to 'this.website.is.not.real', as 'real.website' is an actual domain name that points to a website. Thanks to zaphod for pointing this out!
 
(20 intermediate revisions by 5 users not shown)
Line 1: Line 1:
A 'vHost' (virtual host) allows users to hide their hostmask (i.e., <code>Rizon-BA37C5B3.rogers.com</code>) with something creative (i.e., <code>i.am.awesome</code>). The nickname must be [[Nick Registration|registered]] in order to request a vHost.
{{Main|HostServ}}
 
A "'''vHost'''" ('''virtual host''') is a vanity hostname that users may use instead of their default cloaked hostname. The nickname must first be [[NickServ:Register|registered]] in order to request a vHost.


==Rules==
==Rules==
Line 7: Line 9:
#* Valid: {{valid|<code>some.vhost</code>}}
#* Valid: {{valid|<code>some.vhost</code>}}
#* Invalid: {{invalid|<code>somevhost</code>}}
#* Invalid: {{invalid|<code>somevhost</code>}}
# '''must not''' contain a <code>@</code>
# '''must not''' contain an @ anywhere
#* Invalid: {{invalid|<code>blah@my.new.host</code>}}
#* Valid: {{valid|<code>some.vhost</code>}}
#* Invalid: {{invalid|<code>some@fake.vhost</code>}}
# '''must not''' be an IP or IP look-a-like;
# '''must not''' be an IP or IP look-a-like;
#* Invalid: {{invalid|<code>127.0.0.1</code>}} or {{invalid|<code>127.o.o.1</code>}}
#* Invalid: {{invalid|<code>127.0.0.1</code>}} or {{invalid|<code>127.o.o.1</code>}}
# '''must not''' resolve (basically, the vHost can't point to an actual site);
# '''must not''' resolve (basically, the vHost can't point to an actual site);
#* Valid: {{valid|<code>not.a.real.website</code>}}
#* Valid: {{valid|<code>this.website.is.not.real</code>}}
#* Invalid: {{invalid|<code>google.com</code>}} or {{invalid|<code>xertion.org</code>}}
#* Invalid: {{invalid|<code>google.com</code>}} or {{invalid|<code>xertion.org</code>}}
#* Exception to this rule is '''''if''''' you own the domain. Please join #help and speak with an operator;
#* Exception to this rule is '''''if''''' you own the domain. Please join #help and speak with an operator, you will need to prove domain ownership to us;
# '''must not''' mimic government organizations such as FBI, CIA, ATF, Interpol, etc. This also refers to MPAA or RIAA;
# '''must not''' contain any control codes (bold, color, underline, etc). Colored vHosts are only given out at staff discretion;
# '''must not''' be any instutional/co-operation lookalike (i.e, search.google.com or someguy.gov);
# '''must not''' contain the words 'ircop', 'admin', 'network', 'xertion', or any IRC Operator's nick;
# '''must not''' contain the words 'ircop', 'admin', 'network', 'xertion', or any IRC Operator's nick;
# '''must not''' contain racist words (what is considered racist/derogatory by operator discretion);
# '''must not''' contain racist words (as to what is considered racist/derogatory, is at staff discretion);
# '''must not''' refer to other networks/spamming;
# '''must not''' refer to other networks/spamming;
#* Invalid: {{invalid|<code>join.my.channel</code>}} or {{invalid|<code>come.to.irc.blahblahblah.net</code>}}
#* Invalid: {{invalid|<code>join.my.channel</code>}} or {{invalid|<code>come.to.irc.blahblahblah.net</code>}}
# '''must not''' refer to "kiddy"-like activity. (dosing, rooting, "carding," etc.)
# '''must not''' refer to fraudulent activity. (DoSing, rooting, "carding," etc.)


==Understanding vHosts==
==Project Cloaks==
# '''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, <code>/join #help</code> for further assistance.
Project cloaks are vHosts assigned to your group, such as {{valid|<code>wikia/acwiki/username</code>}}. These types of vHosts cannot be requested using the HostServ system. Project cloaks are assigned by an IRC operator directly. Join #help to have these assigned to you.
# '''vHosts must then be manually approved.'''
# Ban evasion using vHosts will cause you to get: your vHost removed, network banned from Xertion for a set period of time, and vHost banned for an extended period.


==Requesting a vHost==
==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]]
Your nickname must first be [[NickServ:Register|registered]] in order to request a vHost.
 
To request a vHost, use the command
 
<code>/msg HostServ REQUEST <em>vhost.goes.here</em></code>
 
Once your vHost is approved, it can be turned on with
 
<code>/msg HostServ ON</code>
 
==Understanding of the vHost system==


When you request a vHost, yes, a bot first checks it. But that request is also sent to the vHost team.  
To request a vHost: <code>/msg HostServ REQUEST <em>your.vhost.here</em></code> - replacing "your.vhost.here" with the custom virtual host you want.
*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.
Once approved, your vHost is automatically set and activated. If it is not, you can turn it on manually: <code>/msg HostServ ON</code>


And then finally, some human on the vHost team will accept or reject the request.
==Things to know about the vHost system==
*This can take anywhere from 6 seconds, and a few hours.
# '''ALL''' vHosts are checked by a bot to ensure compliance with our vHost rules. They are then passed to staff for further verification and to await activation.
**Not everyone on the vHost team lives in your timezone.
# Using a vHost to evade channel bans will likely result in a network ban from Xertion + your vHost being removed and/or banned from requesting vHosts for a set time.
**Sometimes a vHost team member may defer (put off) an answer pending consultation with other team members.
# Please do not repeat your vHost request over and over. When you request a vHost, all staff are automatically notified. Repeatedly hammering the system with requests, be it because you are too impatient or think we forgot or otherwise, will result in automatic rejection of your request and/or a temporary suspension from the vHost system, or possibly more severe consequences.
*''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.''
# If your request passes the bot's checks, manual staff verification will usually occur within a few minutes to several hours, depending which staffers are available. We ask that you not constantly remind us of your request - this only serves to further frustrate us which might very well lead it to be rejected. Remember, ALL staffers see the request, '''you will HAVE to be patient!'''
# Last but not least, please don't experiment with different vHost requests in a short period of time, and please don't use the default examples. Pick a vHost and stick with it, if you must change it, please wait at least a week or two before requesting a new one.


Please do not experiment with different vHost requests, or put in a default example and expect to change it a few minutes later.
[[Category:Rules]]
[[Category:Commands]]
[[Category:General]]
[[Category:Services]]

Latest revision as of 02:37, 5 November 2019

Main article: HostServ

A "vHost" (virtual host) is a vanity hostname that users may use instead of their default cloaked hostname. The nickname must first be registered in order to request a vHost.

Rules

All vHosts

  1. must contain a dot (aka . ) and can only contain alphanumeric characters, dots ( . ) and dashes ( - );
    • Valid: some.vhost
    • Invalid: somevhost
  2. must not contain an @ anywhere
    • Valid: some.vhost
    • Invalid: some@fake.vhost
  3. must not be an IP or IP look-a-like;
    • Invalid: 127.0.0.1 or 127.o.o.1
  4. must not resolve (basically, the vHost can't point to an actual site);
    • Valid: this.website.is.not.real
    • Invalid: google.com or xertion.org
    • Exception to this rule is if you own the domain. Please join #help and speak with an operator, you will need to prove domain ownership to us;
  5. must not contain any control codes (bold, color, underline, etc). Colored vHosts are only given out at staff discretion;
  6. must not be any instutional/co-operation lookalike (i.e, search.google.com or someguy.gov);
  7. must not contain the words 'ircop', 'admin', 'network', 'xertion', or any IRC Operator's nick;
  8. must not contain racist words (as to what is considered racist/derogatory, is at staff discretion);
  9. must not refer to other networks/spamming;
    • Invalid: join.my.channel or come.to.irc.blahblahblah.net
  10. must not refer to fraudulent activity. (DoSing, rooting, "carding," etc.)

Project Cloaks

Project cloaks are vHosts assigned to your group, such as wikia/acwiki/username. These types of vHosts cannot be requested using the HostServ system. Project cloaks are assigned by an IRC operator directly. Join #help to have these assigned to you.

Requesting a vHost

Your nickname must first be registered in order to request a vHost.

To request a vHost: /msg HostServ REQUEST your.vhost.here - replacing "your.vhost.here" with the custom virtual host you want.

Once approved, your vHost is automatically set and activated. If it is not, you can turn it on manually: /msg HostServ ON

Things to know about the vHost system

  1. ALL vHosts are checked by a bot to ensure compliance with our vHost rules. They are then passed to staff for further verification and to await activation.
  2. Using a vHost to evade channel bans will likely result in a network ban from Xertion + your vHost being removed and/or banned from requesting vHosts for a set time.
  3. Please do not repeat your vHost request over and over. When you request a vHost, all staff are automatically notified. Repeatedly hammering the system with requests, be it because you are too impatient or think we forgot or otherwise, will result in automatic rejection of your request and/or a temporary suspension from the vHost system, or possibly more severe consequences.
  4. If your request passes the bot's checks, manual staff verification will usually occur within a few minutes to several hours, depending which staffers are available. We ask that you not constantly remind us of your request - this only serves to further frustrate us which might very well lead it to be rejected. Remember, ALL staffers see the request, you will HAVE to be patient!
  5. Last but not least, please don't experiment with different vHost requests in a short period of time, and please don't use the default examples. Pick a vHost and stick with it, if you must change it, please wait at least a week or two before requesting a new one.
Retrieved from "https://wiki.xertion.org/index.php?title=VHost&oldid=2249"