This document details the rules and operational policies of the Squick IRC network (henceforth referred to simply as Squick). By connecting, you agree that you have read this page, understand the policies, and submit to these rules for the duration of your session.
The rules and policies were last modified on May 6th, 2016, to convert them to a dynamic template on the backend, and apply a few more minor wording edits. No rule-altering semantic differences between this version and the last should be present, but for transparency's sake, notice is given. Prior versions of this page are archived here.
You must be over 18 years of age or legally considered an adult in your country of residence to use the network. Squick's content is not specifically adult-oriented, but nor is it moderated. Network discussions may contain content unsuitable for minors, and so minors are forbidden from connecting.
Open proxies and public gateways/bouncers may not be used to connect to Squick. The administrators have mechanisms in place to automatically disconnect users on these systems, and manually clean up any that slip through.
Do not try to circumvent network bans, also known as "k-lines" and "g-lines". Administrators don't ban anyone without a good reason (if you feel they have made an error, contact Squick). If you evade a network ban, the duration of the ban will be increased exponentially for each evasion. Repeated violations of this rule will result in Squick contacting your ISP's abuse department, and if warranted, the authorities.
Exploitation of bugs (whether client or server) to disrupt the network or access data you do not have permission to will not be tolerated. If you find a serious bug pertaining to Squick's server software or security policies, please be responsible with your disclosure, and notify an administrator in private as soon as possible.
Attempting to crack a user or channel's password is grounds for a permanent ban, and abusing an unintentionally leaked password will be punished with a long-duration or permanent ban, depending on the severity and nature of the abuse.
If you allow a password to leak, you are expected to change it immediately. IRC is realtime and public, and there's no way to make observers unsee a slipped password.
For community users
Do not evade channel bans or attempt to otherwise gain access to a channel you are not allowed in. Intentional breaches of this rule will result in a network-level ban, which is likely to be permanent.
To avoid being banned from a channel, be civil and follow its rules; visit your channel's homepage or request its rules from one of its staff members to figure out what's taboo. Squick administrators DID NOT create your channel's rules, and cannot help you if you are banned for violating them.
For community owners
Channels may be freely registered without administrative review or explicit permission.
Squick does not moderate channel content or topics, nor will its administrators arbitrate channel-level issues unless they threaten network stability or security. Keeping a channel's users in line is the job of your channel staff. Choose your operators well.
If a channel is attracting harmful users to the network, or otherwise encouraging the abuse of network resources, it may be forcibly dissolved, and its staff banned from Squick.
Bots may be freely brought online without administrative review or explicit permission, so long as a user's bot operation privilege has not been revoked.
Bots may not be malicious in nature. Malicious in this case refers to programs designed to spy on others, harvest login credentials, disconnect other clients with a flood of data, or otherwise abuse network resources and harass users. Violating this rule unintentionally (through a badly-written loop resulting in flooding, for example) will result in a warning. Violating it intentionally will result in revocation of bot operation privileges. Repeat offenders in either situation will be banned from the network at the staff's discretion.
All bots must set mode +B on themselves after connecting. This flags them as a bot for our administration lists and users that
The official implementation of Squick's server software is incapable of intercepting or logging channel text and private messages. It also does not log session lengths or origins, or any other data that might identify a user's activity patterns. While it is possible to modify the software to allow this, it would be trivially detected; any administrator doing so, and their server, would be permanently expelled from the network. Squick promises to notify all network users in the case of such an incident, in as timely a manner as possible.
The above statement is modified somewhat if you register with NickServ. The following information about you is retained and updated until you deregister ("drop"): your last IP address, your host access list, your email address, a hash of your password (which we cannot decrypt into the original), the channels you own or have power on, your grouped nicknames, your vhosts, your memo inbox (which is NOT encrypted!), and all user options. This information will never be sold or freely given to a private third party for any reason, but a court order from the country of a server's residence may require us to turn it over to law enforcement. If possible, we will notify all affected users of government requests for their data.
User discipline is handled on a per-channel basis, by that channel's staff. The administrators are responsible only for maintaining the network and dealing with active attacks on network infrastructure. Squick does not and cannot manually screen every incoming user on a network level.
Squick's users create the network's content, not the administrators or the servers. Individual users take any responsibility for any illegal or immoral transmissions they create. You agree to hold Squick harmless for any improper or offensive content you find on the network. Squick only provides an automatic conduit for transmissions; it does not initiate or design them, and has no control over their targets. No copies of the transmissions themselves, modified or otherwise, are retained after delivery to their intended recipient, except in the case of undeleted MemoServ memos (out of technical necessity).