VHost: Difference between revisions

From Xertion Wiki
Jump to navigation Jump to search
← Older edit
→‎Rules: Revoked '@' rule
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!
 
(One intermediate revision by the same user not shown)
Line 15: Line 15:
#* 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, you will need to prove domain ownership to us;
#* 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;
Line 38: Line 38:


==Things to know about the vHost system==
==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.
# '''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.
# 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.
# 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.
# 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.
# 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.
# 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!'''
# 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.
# 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.


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"