Announcements

13 posts

Cuff-Link Network Update

Hello, We have finished updating the network to InspIRCd 3. InspIRCd 2 is end of life beginning June 2020 after a decade. InspIRCd 3 uses IRCv3 protocols (updated IRC for modern times), which provides better security and more advanced features as clients catch up. If you are experiencing strange issues such as nicklists not updating when people join or mode changes happen, wonky text formatting issues, or connection issues, try updating your client before joining […]

Discontinuing Mibbit Use on Cuff-Link

We have only made one decision in the past regarding outright disallowing a client to be used on Cuff-Link, but the time has come to disallow a second. On November 15, 2019, it will not be possible to connect to Cuff-Link via Mibbit. While we have several reasons for this, the main two are: Mibbit cannot keep their TLS/SSL certificate in place consistently, which poses a security problem. Traffic between Cuff-Link and Mibbit is insecure, […]

Changes to Auth Servers

More changes were implemented. You can now use: Server: irc.cuff-link.mePort: 7797Enable SASL and connect with a registered nickname. Important: If you have received the message that “regular connections are not permitted from your host, be sure to wait at least 60 minutes before trying to reconnect with the updated settings shown above.

Private Message Restriction

Due to several security-related factors, some including spam bots and abusive users, we have made the decision to only allow private messages by registered users. To register, use the following command: A confirmation code will be emailed to you. You will then copy the confirmation line from the email and paste it into IRC. Make sure you have no spaces before the / and no spaces after the code — a space before or after […]

Cuff-Link is Going TLS-Only

Consent. Privacy. Security. These are the three things that help us ensure safety and minimal risk for everyone who uses Cuff-Link. We cannot properly do this while allowing people to connect to the network with insecure [unencrypted] connections. After several months of mulling it over, the decision has been made to go TLS-only [aka SSL-only] by February 1, 2018. This gives us 3 months to assist people with updating their clients to the correct ports […]