IRCv3 support
Vela follows the Modern IRC Client Protocol and the IRCv3 specifications. When it connects, it negotiates capabilities with CAP LS 302 and asks for everything below that the server offers. Features that depend on a capability simply don't appear when the server lacks it.
Capabilities
| Capability | What Vela does with it |
|---|---|
sasl | Logs in while connecting, with PLAIN (account and password) or EXTERNAL (TLS client certificate). |
sts | Upgrades a plain-text connection to TLS on the port the server names, and saves the change. |
cap-notify | Follows capabilities the server adds or removes while you're connected. |
server-time | Shows when a message was actually sent, which matters for history and bouncers. |
message-tags | Carries reactions, replies and typing indicators (see client tags below). |
echo-message | Shows your messages as the server received them. |
batch | Groups history and bouncer responses. |
labeled-response | Matches replies to the requests that caused them. |
chathistory (and draft/chathistory) | Fetches messages you missed when you connect, and older history as you scroll up. |
away-notify | Dims people in the member list when they go away. |
account-notify, account-tag, extended-join | Keeps track of which account each person is logged in to. |
multi-prefix | Knows every rank someone holds (for example both @ and +). |
userhost-in-names | Knows everyone's host from the start, for hover details and /ban. |
chghost, setname | Updates hosts and real names without a fake quit and rejoin. |
invite-notify | Shows invitations to channels you're in. |
standard-replies | Shows FAIL, WARN and NOTE replies; failures appear in the conversation you're looking at. |
draft/message-redaction | Lets you delete your own messages, and shows deleted messages as Message deleted. |
Client tags
These ride on message-tags. Vela respects the server's CLIENTTAGDENY, so a feature the server blocks is hidden.
| Tag | Used for |
|---|---|
+draft/react, +draft/unreact | Reactions |
+draft/reply | Replies |
+typing | Typing indicators (sending them can be turned off) |
Bouncer extensions
| Capability | What Vela does with it |
|---|---|
soju.im/bouncer-networks, soju.im/bouncer-networks-notify | Lists the networks on your soju bouncer, adds each one to the sidebar, and keeps the list in sync. |
znc.in/playback | Asks ZNC only for messages Vela hasn't stored yet. |
znc.in/self-message | Shows messages you sent from your other clients. |
znc.in/server-time-iso, znc.in/batch | ZNC's older names for server-time and batch. |
See Connecting through a bouncer.
Also supported
- TLS with certificate validation, an opt-in Allow invalid certificates for self-signed bouncers, and client certificates (CertFP).
ISUPPORT: the network name, channel types, member prefixes, case mapping (soNick[a]andnick{a}are the same person), history limits andCLIENTTAGDENY.- CTCP:
ACTION(/me), and automatic replies toVERSION,PING,TIMEandCLIENTINFO. - mIRC formatting: bold, italic, underline, strikethrough, monospace, colors 0–98, hex colors and reverse.
- Reconnection with backoff, after a dropped connection, a network change, or your Mac waking up.
Requested, not used yet
Vela already asks for draft/read-marker, but doesn't yet sync your read position between clients. That's on the roadmap, along with draft/multiline, draft/metadata-2 avatars, message editing once the spec settles, and image uploads through soju's FILEHOST.