VHost: Difference between revisions

From Xertion Wiki
Jump to navigation Jump to search
← Older editNewer edit →
CuleX (talk | contribs)
emailconfirmed
40 edits
→‎Rules: Broaden gov't affliation rule
Rewrote page, cleaned it up a bit, specified that a single @ can be included in a vHost request to change the ident as well.
Line 1: Line 1:
{{Main|HostServ}}
{{Main|HostServ}}


A "'''vHost'''" ('''virtual host''') allows users to hide their hostmask (i.e., <code>xertion-6mau9k.fl.comcast.net</code>) with something creative (i.e., <code>i.am.the.doctor</code>). The nickname must be [[NickServ:Register|registered]] in order to request a vHost.
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 9: 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>
# '''MAY''' contain ONE <code>@</code> - this is called a vIdent (virtual Ident) and is also supported.
#* Invalid: {{invalid|<code>blah@my.new.host</code>}}
#* Valid: {{valid|<code>blah@my.new.host</code>}}
#* Invalid: {{invalid|<code>blah@my.new@host.name</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>}}
Line 16: Line 17:
#* Valid: {{valid|<code>not.a.real.website</code>}}
#* Valid: {{valid|<code>not.a.real.website</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''' contain colour codes. Colored vHosts are given at operator discretion;
# '''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''' 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>}}
Line 26: Line 27:


==Project Cloaks==
==Project Cloaks==
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 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.
 
Project cloaks must be given by an IRC operator directly. Join #help to have these assigned to you.
==Understanding vHosts==
# '''vHosts are regulated 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.
# '''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 [[NickServ:Register|Registering 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>
 
Your vHost is activated automatically upon approval.
 
If it is not, you can turn it on using: <code>/msg HostServ ON</code>
 
==Understanding of the vHost system==


When you request a vHost, it is sent to the staff for activation.
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 sending your request without correcting your error, we see it. Over and over.


*This can take anywhere from 6 seconds, and a few hours.
Once approved, your vHost is automatically set and activated. If it is not, you can turn it on manually: <code>/msg HostServ ON</code>
*Not everyone on the staff lives in your timezone.
*Sometimes a staff member may defer an answer pending consultation with other operators.
*''Reminding'' staff to approve your vHost is nothing but frustrating. The staff saw 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.
==Things to know about the vHost system==
# '''ALL''' vHosts are manually approved by staff at their earliest discretion after they verify it meets the above guidelines.
# 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.
# When a new vHost is requested, the staff receives a message from services automatically. Each time a request is made, we see it. Repeating your request will NOT speed it up any. In fact, it might just cause us to reject it. So please don't repeatedly send requests over and over.
# Staff approval of a vHost request can take anywhere from a few seconds to perhaps a few hours, depending on time of day, what staff are available to approve requests, and if we need to consult eachother about a given vHost.
# Constantly reminding us of your vHost request will not get it approved any faster. It only serves to further frustrate us. Rest assured we saw your request, and we will get to it as soon as we are able to. '''PLEASE 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.


[[Category:Rules]]
[[Category:Rules]]

Revision as of 06:58, 14 January 2016

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. MAY contain ONE @ - this is called a vIdent (virtual Ident) and is also supported.
    • Valid: blah@my.new.host
    • Invalid: blah@my.new@host.name
  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: not.a.real.website
    • 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 manually approved by staff at their earliest discretion after they verify it meets the above guidelines.
  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. When a new vHost is requested, the staff receives a message from services automatically. Each time a request is made, we see it. Repeating your request will NOT speed it up any. In fact, it might just cause us to reject it. So please don't repeatedly send requests over and over.
  4. Staff approval of a vHost request can take anywhere from a few seconds to perhaps a few hours, depending on time of day, what staff are available to approve requests, and if we need to consult eachother about a given vHost.
  5. Constantly reminding us of your vHost request will not get it approved any faster. It only serves to further frustrate us. Rest assured we saw your request, and we will get to it as soon as we are able to. PLEASE be patient!
  6. 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=1993"