Difference between revisions of "VHost"

From Rizon Wiki
Jump to navigation Jump to search
(→‎Understanding vHosts: Try to clarify the wording for the seven day rule)
(22 intermediate revisions by 10 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.
A 'vHost' (virtual host) allows users to hide their hostmask (e.g., <code>Rizon-BA37C5B3.rogers.com</code>) with something creative (e.g., <code>i.am.awesome</code>). Colored vHosts can be won via a lottery: [[Vizon|VIzon]].


==Rules==
==Rules==


All vHosts
Format rules:
# '''must''' contain a dot (aka <code>.</code> ) and can only contain alphanumeric characters, dots ( <code>.</code> ) and dashes ( <code>-</code> );
# '''must''' contain a dot (aka <code>.</code> ) and can only contain alphanumeric characters, dots ( <code>.</code> ) and dashes ( <code>-</code> ); <br> <code>{{xt|some.vhost}}</code> &nbsp; <code>{{!xt|somevhost}}</code>
#* Valid: {{xt|<code>some.vhost</code>}}
# '''must not''' contain a <code>@</code> <br> <code>{{!xt|blah@my.new.host}}</code>
#* Invalid: {{!xt|<code>somevhost</code>}}
# '''must not''' be an IP or IP look-a-like <br> <code>{{!xt|127.0.0.1}}</code> &nbsp; <code>{{!xt|127.o.o.1}}</code>
# '''must not''' contain a <code>@</code>
# '''must not''' resolve <sup>[[VHost#Resolving_hosts|[1]]]</sup> (basically, the vHost can't point to an actual site); <br> <code>{{xt|this.is.an.example}}</code> &nbsp; <code>{{!xt|google.com}}</code> &nbsp; <code>{{!xt|rizon.net}}</code>
#* Invalid: {{!xt|<code>blah@my.new.host</code>}}
# '''must not''' be an IP or IP look-a-like;
#* Invalid: {{!xt|<code>127.0.0.1</code>}} or {{!xt|<code>127.o.o.1</code>}}
# '''must not''' resolve (basically, the vHost can't point to an actual site);
#* Valid: {{xt|<code>not.a.real.website</code>}}
#* Invalid: {{!xt|<code>google.com</code>}} or {{!xt|<code>rizon.net</code>}}
# '''must not''' mimic government organizations (*.gov, *.gc.ca, FBI, etc.) or private organizations which have government affiliation (MPAA, RIAA, etc.);
# '''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 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''' 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 other networks/spamming; <br> <code>{{!xt|join.my.channel}}</code> &nbsp; <code>{{!xt|come.to.irc.blahblahblah.net}}</code>
#* Invalid: {{!xt|<code>join.my.channel</code>}} or {{!xt|<code>come.to.irc.blahblahblah.net</code>}}
# '''must not''' refer to "kiddy"-like activity. (dosing, rooting, "carding," etc.)
# '''must not''' refer to "kiddy"-like activity. (dosing, rooting, "carding," etc.)
# '''must not''' be more than 63 characters in length


==Understanding vHosts==
Timing rules:
# '''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 #services</code> for further assistance.
# wait 7 days before requesting a new vHost on the same nick
# '''vHosts must then be manually approved.'''
# wait 1 day before requesting a new vHost on a grouped nick
# You may only request a new 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.
Usage rules:
# 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.
# do not use vHosts to ban evade (doing so can lead to a network ban and a vHost ban)


==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]]
'''You must have a [[Register your nickname|registered nickname]] in order to request a vHost.'''


To request a vHost, use the command
# Type <code>/msg HostServ REQUEST <em>vhost.goes.here</em></code>
 
# Your request will be filtered by a bot
<code>/msg HostServ REQUEST <em>vhost.goes.here</em></code>
# Your request will then be manually approved by a human ('''please do not remind us of your request''', we automatically get alerted already).
 
# Type <code>/msg HostServ ON</code> after you get a message saying the vHost was approved
Once your vHost is manually approved by a human, it can be turned on with
 
<code>/msg HostServ ON</code>


==Minutiae of the vHost system==
==Minutiae of the vHost system==
Line 45: 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 your request is ''vHost bot approved'', it is presented to the vHost team with a simple ''approve or reject'' choice.
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 7 day waiting period for new vHost requests has passed.
**If the user has waited long enough before requesting a new vHost.
**If the content and context of the vHost request passes our rules.
**If the content and context of the vHost request pass the rules.
***This may include checking other language translations.
***This may include checking other language translations.


Line 57: Line 48:
*''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.''
*''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.
Although a new vhost can be requested instantly if the previous was rejected, 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.
*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).
 
==Resolving hosts==
To verify the ownership of your domain you can add a TXT record for your domain. Add a TXT record for your domain name with contents as follows:<br><br>
Allow anyone to use this domain as vhost:<br>
<code>rizon_vhost=*</code><br>
Only allow nick to request this domain as vhost:<br>
<code>rizon_vhost=nick</code><br>
Allow nick, nick2, and nick3 to request this domain as vhost:<br>
<code>rizon_vhost=nick,nick2,nick3</code>

Revision as of 23:18, 28 January 2017

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:

  1. must contain a dot (aka . ) and can only contain alphanumeric characters, dots ( . ) and dashes ( - );
    some.vhost   somevhost
  2. must not contain a @
    blah@my.new.host
  3. must not be an IP or IP look-a-like
    127.0.0.1   127.o.o.1
  4. must not resolve [1] (basically, the vHost can't point to an actual site);
    this.is.an.example   google.com   rizon.net
  5. must not mimic government organizations (*.gov, *.gc.ca, FBI, etc.) or private organizations which have government affiliation (MPAA, RIAA, etc.);
  6. must not contain the words 'forum', 'ircop', 'admin', 'network', 'rizon', or any IRCop's nick;
  7. must not contain racist words (what is considered racist/derogatory is subject to discretion by vHost team members);
  8. must not refer to other networks/spamming;
    join.my.channel   come.to.irc.blahblahblah.net
  9. must not refer to "kiddy"-like activity. (dosing, rooting, "carding," etc.)
  10. must not be more than 63 characters in length

Timing rules:

  1. wait 7 days before requesting a new vHost on the same nick
  2. wait 1 day before requesting a new vHost on a grouped nick

Usage rules:

  1. do not use vHosts to ban evade (doing so can lead to a network ban and a vHost ban)

Requesting a vHost

You must have a registered nickname in order to request a vHost.

  1. Type /msg HostServ REQUEST vhost.goes.here
  2. Your request will be filtered by a bot
  3. Your request will then be manually approved by a human (please do not remind us of your request, we automatically get alerted already).
  4. 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 pass 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.

Although a new vhost can be requested instantly if the previous was rejected, 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).

Resolving hosts

To verify the ownership of your domain you can add a TXT record for your domain. Add a TXT record for your domain name with contents as follows:

Allow anyone to use this domain as vhost:
rizon_vhost=*
Only allow nick to request this domain as vhost:
rizon_vhost=nick
Allow nick, nick2, and nick3 to request this domain as vhost:
rizon_vhost=nick,nick2,nick3