Everything you need to get a bouncer, connect it, and get back in when you have forgotten something. If a question is not answered here, mail ninja@cocks.io.
Getting a bouncer
Accounts are open and reviewed by hand. Put your IRC nickname in the request, and the address you want your confirmations sent to. You get a bouncer name and a password by e-mail once it is set up.
Every registration e-mail contains a status link. If you did not get one, you can look the request up again with your address and the status secret from the mail.
There is no pricing page and no trial that expires. If the service is worth using, keep using it.
Connecting
irc.cocks.io on port 6697 — TLS only, there is no plain port.USER /quakenet: to that server. That single line is the whole connect command./msg NickServ IDENTIFY , or let the client do it for you.Prefer not to configure a client at all? chat.cocks.io is the same bouncer in a browser tab.
Commands worth knowing
After reconnecting, everything you missed is waiting. Most clients replay it automatically; if yours does not, /msg *bufferplay * replays it on request.
/msg *status help lists the status module commands, /znc help lists everything the bouncer itself can do, and /listqueries shows highlights waiting for you.
QuakeNet sees user@cocks.io with a real ident, not a tilde and not a datacenter address. There is nothing to configure; it is part of the service.
If something is wrong
You are probably not authenticated to QuakeNet yet. Authenticate with NickServ, then ask for the backlog again.
Check that you are on port 6697 with TLS enabled, and that the bouncer name and password are exactly as in the setup mail. Plain ports are closed on purpose.
Use the password reset form with the address the account was created under. The bouncer name is not needed for that — only the e-mail address.
Mail ninja@cocks.io with the bouncer name. Deletion is done by hand, and the buffers go with it.
The other cocks.io services