Please remember to read the network rules before connecting for the first time.
LizardIRC is an IRC network originally founded by FastLizard4 in July of 2010, the name "LizardIRC" of course based on his online pseudonym. Now it has grown to a stable, full-serviced, friendly network of everything, from gaming to politics, heated debate to idle conversation, and programming to (gentle) operating system wars. Overseen by friendly staff, we aim to provide an excellent IRC experience with minimal hassle. LizardIRC Network Staff, sometimes colloquially referred to as "opers", are friendly and are people just like you. We won't bite, and we're more than happy to talk to you! Give LizardIRC a try, and we're sure you'll love the network so much you'll make it your home. Welcome!
- #lizardirc - The lobby for the network, if you will. The network's main channel. IRC relays for LizardNet Minecraft servers s2 and s2.5.
- #help - Network help and support channel. Have a question about LizardIRC? Need help creating a channel? Problem user you think should be banned from the network? Ask in here! (Network staff are present in this channel, and have operator status within.)
- #Metroid - The official unofficial Metroid chatroom! Please remember to read the #Metroid channel rules and info before joining.
- #devops - LizardNet Development and Operations. Official LizardNet support channel and home of the Gerrit Code Review and LizardNet Continuous Integration bots.
- #SpaceWeather - Discussion about space weather and related phenomena (auroras, solar flares, etc.). Also contains a bot that relays current conditions and alerts from the NOAA Space Weather Prediction Center.
Web/cloud IRC clients
The following web/cloud IRC clients are compatible with and recommended for use with LizardIRC:
But please feel free to use one not listed above!
LizardIRC uses the Atheme services package, and has a "you own your nickname policy" - i.e., we use NickServ, not AuthServ/UserServ. Here is a partial list of services supported by LizardIRC:
- NickServ - Nickname registration, user authentication, and nickname services
- ChanServ - Channel registration and administration services
- MemoServ - Asynchronous ("offline") messaging service for registered users
- HostServ - vHost ("cloak") management
- ALIS - Channel listing and searching
- ChanFix - EFNet-style ChanFix, for users who don't wish to deal with services and/or who don't want to bother registering a channel with ChanServ.
- And others....
LizardIRC is now accepting applications for linking servers. The linking policy, including requirements and procedure, can be found here.
Network Staff (oper)
Part of the mission of this network is to make network staff less of something to be feared, but more of simply trusted users that have more capabilities than most. To this end, new network staff are selected internally by consensus of the current active network staff, with candidates being well-known, trusted, long-time users of the network. When a consensus is reached, the chosen candidate will be approached with an offer.
Do not ask if you can become network staff or have oper privileges. As all selections are made internally when staff are needed, we do not accept applications, and asking is a waste of your time and ours. Furthermore, asking is a good way to get yourself permanently barred from even being considered for the position. If you are actually interested in becoming network staff, be an active, helpful, well-known, trustable user on the network for a year or more, and if you meet the qualifications and there is a need, you will be approached with an offer. Again, because this cannot be emphasized enough: DO NOT ask us if you can become network staff or have oper privileges. DO NOT.
Be advised that asking to become network staff is against the network rules. This means that you can be banned from the network (at staff discretion) if you ask, though we probably won't ban you the first time you ask - only if you become annoying about it.
While we don't support usermode
+x, you can get a basic cloak by registering with NickServ, then running the command
/quote hs TAKE lizardirc/user/$account. If you want a different cloak, read the network rules for instructions on requesting a custom cloak, as well as the cloak format guidelines.
LizardIRC makes use of the DNSBL (domain name system blacklist) module in InspIRCd. When you connect to LizardIRC, your hostname and/or IP address are checked against the blacklist provided by dronebl.org, which maintains an RBLDNS (real-time blacklist for DNS) database of spammers, known botnets, etc. If you are listed in the dronebl DNSBL, you will be automatically Z:lined (i.e., globally banned) from connecting to the server for a period of time. If you are banned because you are listed on the DNSBL, you have two courses of action:
- Use the link that is automatically provided when you were Z:lined to request removal from the blacklist, and/or:
- Email the LizardIRC admins at (click here to expose email address), who can set a E:line (i.e., ban exemption) for you.
If you were banned by the DNSBL system because you use Tor or run a Tor exit node, please connect to LizardIRC using our Tor hidden service. See here for more info.
Open Proxy Scanner
LizardIRC makes use of the BOPM open proxy scanner and all connecting users are scanned for open proxies. If you are found to be running one, you will automatically be banned from connecting. The scans originate from 220.127.116.11 and are not an attack on your computer, though they may appear to be so to an improperly configured antivirus scanner or in your logs. Your usage of LizardIRC constitutes your acknowledgement of this policy and your consent to be scanned and banned if you are running open proxies. If you do not wish to be scanned for open proxies, your usage of LizardIRC is unauthorized and you may not connect to the network. If there is some extenuating reason why you must use an open proxy, please send an email to the LizardIRC admins at (click here to expose email address).
LizardIRC supports the use of spamfilters in the form of Perl-compatible regexes. Depending on the type of spam being blocked by the regex, the action taken by the spamfilter may be to merely prevent the message from being sent, killing the offending client, or G:lining the offending client. The spam filter may apply to any combination of messages or notices to users or channels, part messages, and/or quit messages.
If you are hit by a spamfilter and your message is blocked or you are killed, you can request help from an oper in #lizardirc. If you trip a spamfilter and are G:lined, you must wait some time for the G:line to expire (which varies from filter to filter), or send an email to the LizardIRC admins at (click here to expose email address).
|Graphs provided by Netsplit.de|