From LizardWiki, FastLizard4's wiki and website
< LizardIRC
Revision as of 06:27, 9 June 2016 by Jasper Deng (Talk | contribs) (fix)

Jump to: navigation, search

These are the LizardIRC network rules and policies. All users are expected to abide by them. It's simple stuff.

General Rules

  1. Use common sense.
  2. Don't be an asshole.
  3. Don't abuse the network. No spam, flooding, spreading of malicious software, etc.
  4. No racism, sexism, discrimination based on religion, sexual orientation, favorite text editor, or the like.
  5. Use common sense and don't be an asshole.
  6. See 1, 2, and 5. We really mean it.
  7. No FSERVEs, warez, software piracy, illegal music distribution, and so forth.
  8. Do not ask if you can become network staff or have oper privileges (yes, this is a network rule). See here.
  9. All users are expected to abide by the laws of the United States of America as well as their own local laws. When a conflict exists, United States laws take precedence.
  10. All rules are subject to interpretation by the network staff.



Your use of LizardIRC constitutes acknowledgement of these rules and your agreement to them. Violation of these rules may result in your access to LizardIRC being terminated.

Additional Rule for #lizardirc

Additionally, to join a bot to #lizardirc, you must ask for permission from network staff first. Unauthorized bots will be kicked and/or banned.


A vHost, or cloak, is a piece of text that is shown in your /whois information to other users instead of your IP address, effectively hiding your IP.

You can - after registering your nickname - get a "standard" cloak by doing /msg HostServ TAKE lizardirc/user/$account

(For help registering your nickname, do /msg NickServ HELP REGISTER)

You can also request a custom vHost. Here are the guidelines on vHosts you can request:

  1. Standard vHosts are of the freenode-style, for example, project/username, project/position/username, project/otherproject.position.username, etc. "project" can be any website you affiliate with, for example Wikipedia, reddit, GitHub, even your own!
  2. Hostnames (e.g.,,, etc.) may be requested as vHosts as long as:
    1. The hostname is a valid and registered domain name with one or more valid A, AAAA, or CNAME records.
      • Note that "valid CNAME record" is defined as a CNAME record (or chain of CNAME records) that points to a domain name with one or more A or AAAA records.
    2. You own or control the hostname/domain in question.
    3. There is some extenuating circumstance that prevents you from simply connecting to LizardIRC from an IP address with a reverse DNS pointer to the hostname you want set as your vHost.
    • Network staff will contact you to verify your request in this case. Note also that, to prevent spoofing and to make it clear that you have a vHost, the domain name will have a "." added to the end (e.g., "").
  3. vHosts that are IP addresses are not allowed.
  4. vHosts in other formats, styles, or representations are not allowed.

Note that vHosts cannot contain non-ASCII characters, due to technical restrictions in InspIRCd.

For help requesting a vHost, do /msg HostServ HELP REQUEST. You will be notified with the results of your request by a MemoServ memo when you IDENTIFY to NickServ.

Cloaking Procedure

Note that the below applies to "standard" type cloaks (e.g., project/username, project/position/username, or project/otherproject.position.username). Hostname-type cloaks are handled differently - see item 2 in the above section.

  • Users may only request cloaks for themselves or registered bot accounts for bots they own. Cloak requests for oneself should ideally be made through HostServ using /msg HostServ REQUEST, but can also be made by asking staff directly or in the channel #help. Cloak requests for registered bot accounts can be made by asking staff directly or in the channel #help, or by using HelpServ (see /msg HelpServ HELP REQUEST).
  • Users may request that their cloak be changed at any time.
  • For popular/common websites/services/projects (for example, Wikipedia or GitHub), staff may set the cloak immediately or ask to verify your identity.
  • For smaller websites/services/projects, the owner or an authorized representative should register a GroupServ group in the project's name (e.g., !ourProject; see /msg GroupServ HELP). The group name (or a derivative thereof) will then be considered valid by network staff for use in a cloak.
    • Anyone with permission flags +F and +m in the group will be considered an "authorized group contact"
    • Though authorized group contacts still may not request cloaks on behalf of other users (aside from bots they own), when a user requests a group cloak, the authorized group contacts will be asked by network staff to confirm the request before it is granted. Change requests to a group cloak will also be verified with authorized group contacts, unless the new requested cloak isn't a group cloak or the requested change doesn't affect the group portion of the cloak (for example, for the cloak ourProject/position/otherproject.position.username, only the bolded portion is considered the group portion for the group !ourProject).
    • Finally, note that authorized group contacts may request that network staff add or remove a cloak to the group's offer list. These cloaks can be taken by any member of the group with the +v permission flag at any time, without the intervention of the group contacts or network staff. By default, a group's cloak offer list is empty.