VHost - Revision history

Bronya: 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!

2019-11-05T02:37:37Z

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!

← Older revision		Revision as of 02:37, 5 November 2019
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;

Bronya: /* Things to know about the vHost system */ Revised vHost rules, cleaned it up a little bit, we also use a bot to run some of our checks now.

2017-04-21T09:01:55Z

Things to know about the vHost system: Revised vHost rules, cleaned it up a little bit, we also use a bot to run some of our checks now.

← Older revision		Revision as of 09:01, 21 April 2017
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.

Bronya: /* Rules */ Revoked '@' rule

2016-05-07T03:13:47Z

Rules: Revoked '@' rule

← Older revision		Revision as of 03:13, 7 May 2016
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>}}
	# '''~~MAY~~''' contain ~~ONE <code>~~@~~</code> - this is called a vIdent (virtual Ident) and is also supported.~~		# '''must not''' contain an @ anywhere
	#* Valid: {{valid\|<code>~~blah@my.new~~.~~host~~</code>}}		#* Valid: {{valid\|<code>some.vhost</code>}}
	#* Invalid: {{invalid\|<code>~~blah@my.new~~@~~host~~.~~name~~</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>}}

Bronya: Rewrote page, cleaned it up a bit, specified that a single @ can be included in a vHost request to change the ident as well.

2016-01-14T06:58:26Z

Rewrote page, cleaned it up a bit, specified that a single @ can be included in a vHost request to change the ident as well.

← Older revision		Revision as of 06:58, 14 January 2016
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]]

CuleX: /* Rules */ Broaden gov't affliation rule

2013-08-13T11:13:29Z

Rules: Broaden gov't affliation rule

← Older revision		Revision as of 11:13, 13 August 2013
Line 18:		Line 18:
	#* 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;
	# '''must not''' contain colour codes. Colored vHosts are given at operator discretion;		# '''must not''' contain colour codes. Colored vHosts are given at operator discretion;
	# '''must not''' ~~mimic government organizations such as FBI, CIA, ATF, Interpol, MPAA~~, or ~~RIAA, etc~~.;		# '''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 (what is considered racist/derogatory by operator 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 fraudulent activity. (~~dosing~~, rooting, "carding," etc.)		# '''must not''' refer to fraudulent activity. (DoSing, rooting, "carding," etc.)

	==Project Cloaks==		==Project Cloaks==

Kaishiro at 20:28, 20 October 2012

2012-10-20T20:28:59Z

← Older revision		Revision as of 20:28, 20 October 2012
Line 1:		Line 1:
			{{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''') 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.

Line 55:		Line 57:

	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.

	~~See also: [[HostServ]]~~

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

Kaishiro: Added Services Category

2012-10-16T17:03:00Z

Added Services Category

← Older revision		Revision as of 17:03, 16 October 2012
Line 61:		Line 61:
	[[Category:Commands]]		[[Category:Commands]]
	[[Category:General]]		[[Category:General]]
			[[Category:Services]]

Kaishiro at 17:02, 16 October 2012

2012-10-16T17:02:10Z

← Older revision		Revision as of 17:02, 16 October 2012
Line 55:		Line 55:

	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.

			See also: [[HostServ]]

	[[Category:Rules]]		[[Category:Rules]]
	[[Category:Commands]]		[[Category:Commands]]
	[[Category:General]]		[[Category:General]]

Kaishiro at 23:54, 15 October 2012

2012-10-15T23:54:51Z

← Older revision		Revision as of 23:54, 15 October 2012
Line 24:		Line 24:

	==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 must be given 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.

Kaishiro at 23:50, 15 October 2012

2012-10-15T23:50:16Z

← Older revision		Revision as of 23:50, 15 October 2012
Line 34:		Line 34:
	==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 registered nickname in order to request a vHost.''' In order to register your nickname, please visit [[NickServ:Register\|Registering your nickname]]

	To request a vHost, use the command		To request a vHost, use the command

← Older revision		Revision as of 03:13, 7 May 2016
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>}}
	# '''~~MAY~~''' contain ~~ONE <code>~~@~~</code> - this is called a vIdent (virtual Ident) and is also supported.~~		# '''must not''' contain an @ anywhere
	#* Valid: {{valid\|<code>~~blah@my.new~~.~~host~~</code>}}		#* Valid: {{valid\|<code>some.vhost</code>}}
	#* Invalid: {{invalid\|<code>~~blah@my.new~~@~~host~~.~~name~~</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>}}