Difference between revisions of "Cloaks/vHosts"
From freenode wiki
m Tags: Reverted Visual edit: Switched |
m (Protected "Cloaks/vHosts" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading]) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
In the past users were able to request a cloak for a particular group they were affiliated with or an unaffiliated cloak. When we changed IRCD we decided to | In the past users were able to request a cloak for a particular group they were affiliated with or an unaffiliated cloak. When we changed IRCD we decided to make cloaks mandatory for all users connecting to freenode, even if they decide not to register their nicknames. Protecting a user's IP was important and a good way of keeping users' information confidential from other users. Keep in mind staff can still see a users IP no matter what.<br/> | ||
=='''HostServ'''== | =='''HostServ'''== | ||
| Line 7: | Line 6: | ||
==='''VHost Rules'''=== | ==='''VHost Rules'''=== | ||
* must | * must contain a dot (aka . ) and can only contain alphanumeric characters, dots ( . ) and dashes ( – );<br/> | ||
my.vhost.here my-vhost<br/> | my.vhost.here my-vhost<br/> | ||
* must contain a @<br/> | * must not contain a @<br/> | ||
b@man<br/> | b@man<br/> | ||
* must be an IP or IP look-a-like<br/> | * must not be an IP or IP look-a-like<br/> | ||
127.0.0.1 127.o.o.1<br/> | 127.0.0.1 127.o.o.1<br/> | ||
* must not resolve (basically, the vHost can’t point to an actual site);<br/> | * must not resolve (basically, the vHost can’t point to an actual site);<br/> | ||
| Line 26: | Line 25: | ||
'''Please do not remind us of your request'''<br/> | '''Please do not remind us of your request'''<br/> | ||
'''Please do not request more than | '''Please do not request more than one vHost in a week’s time. So make sure you pick something that is suitable.'''<br/> | ||
Latest revision as of 18:46, 31 May 2022
In the past users were able to request a cloak for a particular group they were affiliated with or an unaffiliated cloak. When we changed IRCD we decided to make cloaks mandatory for all users connecting to freenode, even if they decide not to register their nicknames. Protecting a user's IP was important and a good way of keeping users' information confidential from other users. Keep in mind staff can still see a users IP no matter what.
HostServ
If a user would like a unique cloak or vhost they can reach out to a staff member in #help or in #freenode to make that request.
VHost Rules
- must contain a dot (aka . ) and can only contain alphanumeric characters, dots ( . ) and dashes ( – );
my.vhost.here my-vhost
- must not contain a @
b@man
- must not be an IP or IP look-a-like
127.0.0.1 127.o.o.1
- must not resolve (basically, the vHost can’t point to an actual site);
this.is.an.example google.com
- must not be a partial host or IP;
example: hub.google.com
- 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 ‘ircop’, ‘admin’, ‘network’, or any IRCop’s nick;
- must not contain racist words (what is considered racist/derogatory is subject to discretion by staff members);
- must not refer to other networks/spamming;
join.my.channel come.to.irc.blahblahblah.net
- must not refer to “kiddy”-like activity. (dosing, rooting, “carding,” etc.)
Please do not remind us of your request
Please do not request more than one vHost in a week’s time. So make sure you pick something that is suitable.
