Monday April 09 2018 • posted by james

Image avatars

Today we’re releasing image avatars, a new feature we’ve been testing in our labs section. They come in 2 flavours, public and private, and look like this:

You’ll need to make sure the “User icons” setting is switched on in Layout & Design to see avatars. There’s also a separate setting to disable image avatars completely.

You can click on an avatar or nickname to see a larger version of it in the context menu. Avatars will also appear at the top of private messages.

Public avatars

A public avatar will work on most IRC networks, using an image tied to your user ID, a bit like a gravatar.

Upload a public avatar from your account settings and it’ll be visible to other IRCCloud users on any server based on your ident/hostmask.

Private avatars

Private avatars are only available on private team servers for now, and you can use a different image for each team.

Choose a team avatar by clicking the user icon next to your nickname in the input box.

Behind the scenes

Private avatars work using an updated version of IRCv3 metadata, a deprecated protocol extension that we’re helping to revisit and restore. Technically, any IRC server or client could support metadata avatars today, they just aren’t widely implemented yet.

We use the metadata framework to set your avatar to an unguessable URL, that won’t be published outside of the team.

If you’re running your own bot on a team server, you can give it an avatar by uploading an image and configuring it to send the following command on connect:


Public avatars work differently. They rely on a URL that maps an image to your user ID (the bit in your ident/hostmask that looks like sid3 or uid7). We use this to detect other IRCCloud users and check whether they have a public avatar by loading that URL, e.g.

We don’t expect other IRC clients to support public avatars, since they only work for IRCCloud users, but they could if they wanted to. It’s intended as a stop-gap until IRCv3 metadata is more widely adopted, and a way for people to try out and get used to avatars on IRC.

As usual, let us know what you think on Twitter, email or IRC.

Monday August 07 2017 • posted by james

Reply threads

As part of our ongoing IRC modernisation work, we’re introducing threaded conversations for team servers today.

Screenshot of reply threads

Reply threads: collapsed, expanded, and opened in a side pane.

Behind the scenes, this feature uses an IRCv3 message tag, meaning any IRC server could support it in future, but we’re not aware of any in widespread use so far.

By default, reply threads will display in an expanded state, where all messages are visible in the main chat area in their original sequence. On the first message of a thread, a single speech bubble icon appears on the left, while all subsequent replies get double bubbles.

An expanded reply thread

You can click on any of these bubble icons to open up the thread in its own side pane. This lets you follow and reply to a thread independently of any other messages sent to a channel.

You can also collapse threads, leaving only the original message showing in the main chat area, with the reply count and participants summarised underneath. You can click on this summary line to open the thread in a pane as before.

A collapsed reply thread

Collapsing threads lets you choose which conversations you want to give your full attention, while filtering out those you’re less interested in. Depending on how your teams and channels use threads, you may want to collapse all threads by default, so we’ve added a per-channel setting you can toggle from the options menu.

Per channel setting to collapse all reply threads

Threads can also be expanded and collapsed individually, by using the plus and minus icons that appear on the right when you hover over a threaded message. This is also where you’ll find the reply icon (curling arrow), which lets you start a new thread.

Message actions for adding replies and reactions to messages, and collapsing and expanding a thread

Another feature seen here is the reaction icon (smiley face), which lets you choose an emoji to attach to a message. It’s a nice way to give quick feedback on a message. We released emoji reactions on team servers at the end of last year, but never blogged about them. They’re another feature built with message tags.

Emoji reactions

We looked at a lot of different message threading approaches in other chat services while designing IRC replies, and we’ve tried to create useful, familiar interactions, while avoiding common implementation weaknesses. But we recognise this is new territory for IRC, so we’ll be paying close attention to feedback as people experiment and come up with new ways to use threads.

As always, you can tweet, email or find us on IRC to share your thoughts.

We also hope to see more servers supporting these features in future; we think they have a lot of potential to make IRC more manageable for communities and teams alike.

Friday February 24 2017 • posted by russ

February 2017 Security Notice

Today Cloudflare, one of our infrastructure providers, revealed that they were subject to a security vulnerability which may have resulted in some private IRCCloud data, including passwords and chat history, being leaked between September 2016 and February 2017.

No payment details were affected.

We understand the chances of any information being compromised are very low, but we take these issues very seriously indeed. We are immediately requiring all users to re-authenticate when they next load IRCCloud. We’re sorry for the inconvenience this will cause.

We recommend that all IRCCloud users change their account passwords, and we are reviewing our security in light of this issue.

Friday February 10 2017 • posted by james

IRC Strict Transport Security

TL;DR: IRCCloud now supports the IRCv3 Strict Transport Security draft.

We’ve always worked hard to ensure secure access to our service. For instance, we’ve enforced HTTPS in our web and mobile apps from day one. We were also early adopters of an HTTP Strict Transport Security (HSTS) policy that adds even stronger safeguards to secure connections, and our policy is now preloaded in all major browsers.

Employing strict security policies for access to our service is important because it protects users who might otherwise be using an untrusted internet connection. But until now, onward connections to IRC networks haven’t enjoyed the same degree of protection.

As mentioned in a previous post, we’re an active participant in the IRCv3 working group. Recently this has involved developing a Strict Transport Security (STS) mechanism for IRC. A first draft specification has now been published, and we’ve just enabled support in IRCCloud.

This means we’ll verify that IRC servers support STS, and always use secure connections with servers that do. Also, if an STS-enabled server fails certificate validation, we’ll refuse to connect and show errors like these:

This is an important change. An invalid certificate can indicate that a secure connection has been compromised and is no longer secure. Previously, if you chose the “Secure port” option when joining a new network, we made sure to connect using TLS/SSL, but we wouldn’t inform you if any certificate errors are encountered. For servers without STS, we aren’t changing this behaviour straight away.

This decision was made because a significant number of IRC networks are set up to use free, self-signed certificates that can’t be validated. These networks are largely volunteer-run with no budget, but our users still expect to be able to connect to them. If we showed an error message on each of these connections, users would quicky learn to ignore security warnings.

However, that situation is gradually changing. With an increased interest in securing our communication channels, and the emergence of free certificate authorities such as Let’s Encrypt, we’re starting to see more IRC networks switch to validated certificates.

In light of this shift, and along with mandatory certificate validation for servers that use STS, we’ll be looking into ways to better surface certificate errors in future.

In the mean time, the IRCv3 STS specification is still being finalised, and you can keep track of its progress on GitHub.

Monday January 25 2016 • posted by james


IRCv3 is a working group of client/server software authors and network operators from the community, set up to advance the IRC protocol.

IRCCloud has been an active participant in the group since early on, and we’ve implemented the protocol enhancements where they’ve made sense.

Today, we gave a big upgrade to our support and we now handle most of the IRCv3.2 specification. You can check our compatibility progress in the client support tables.

We’re excited to be part of the future of IRC, and support for these enhancements represents our commitment to IRC as the best-suited chat protocol for open communities.

Here’s a brief summary of the features we support and what they mean for users:


CAP is the mechanism used to negotiate all other features. IRCv3 specifications are backwards compatible, and enhancements are only enabled if both server and client support them.

SASL is an authentication protocol, which improves the way e.g. NickServ login is performed, allowing connections to be established more quickly.

multi-prefix allows clients to keep track of more than one level of channel mode, so a user that has both op and voice will appear correctly when de-opped.

account-notify lets a client know when users in channels they share become authenticated or deauthenticated with their account (with NickServ for example). A user’s logged in account can be seen by clicking on their nickname.

away-notify lets a client know when users go away or come back, so that the member list can be greyed out accordingly without having to continually poll the server for this status.

extended-join lets a client know the real name and account name of a user when they join a channel. This information is shown when you click on a user’s nickname.


account-tag attaches a user’s account to every message they send, which can be helpful when private messaging someone who doesn’t share any channel with you.

batch allows servers to batch certain messages. This isn’t used for anything yet, but as batch types become available on IRC networks we’ll be able to enable it more easily.

cap-notify lets a client know when a server adds or removes support for a new capability. This is used by bouncer software like ZNC to vary the available features when you detach or reattach to a server.

chghost sends a host change message to a client when they cloak or decloak, instead of faking a quit and rejoin.

invite-notify sends a specific command to channel members with appropriate permissions when someone is invited to the channel.

server-time allows a client to show the actual time a message was received by a server, useful when playing back history from an external bouncer. This is available in newer versions of ZNC (1.2+).

userhost-in-names provides full userhost details for members when joining a channel. This makes it easier to apply bans or ignores by clicking on a user’s nick name, without having to /whois them first.

Vendor specific is a CAP used by ZNC that makes sure all connected sessions receive a copy of any private messages sent by any other session.

Server compatibility

Not all of these enhancements are supported by all IRC networks yet. For instance, many of you connecting to Freenode won’t immediately be able to take advantage of away-notify from 3.1 or any of the 3.2 CAPs. But support for these will improve in time.

Take a look at the server compatibility tables, for an idea of how well these features are supported by various IRCd software.

In future, we’re planning to use IRCv3 to enable more enhancements on our team servers, things like user avatars, rich bot payloads and more, and hopefully these will make their way out to the larger public networks to improve the IRC experience for everyone.

Send us an email on or join us in #feedback if you’d like to discuss any of these features in more detail.