socketchat --version to see the version you have, and Updating shows how to get the newest one.
Version numbers follow Semantic Versioning: the first number changes when something stops working the old way, the second for new features, the third for fixes.
This release makes a file someone sends easy to save, and keeps the path of a file on your computer out of the chat.
New
- A file line says how to save it: when someone sends a file, the room shows “Ada sent report.pdf (1.2 MB). Type /save report.pdf to save it to Downloads.”, with the command in the accent color. When the room holds more than one file with that name, the command names this one, as
/save report.pdf:2, and a name with spaces comes in quotes. Lines from earlier versions stay as they were. - Click a file line to save it: one click on a line that says someone sent a file saves that file to Downloads. A second click says where it went. Dragging over the line still selects and copies it, and
/mouse offturns clicks off. /savealone saves the newest file someone else sent in the open room.- Tab completes the file after
/save:/saveand Tab, or Up and Down, go through the room’s files, newest first. A name two files share comes up asreport.pdf:1andreport.pdf:2.
Changed
- A saved file leaves a line in the room: “Saved report.pdf to ~/Downloads/report.pdf.” Only you see it. Before, the bottom line said where the file went until the next key.
/helpshows/save [file] [folder], says it saves to Downloads unless you name a folder, and says Tab completes the name.
Security
- A path to a file on your computer never goes out as a message: when Enter would send nothing but the path of a file on this computer, Socketchat attaches the file instead and says so on the bottom line, as in “The path stays on this computer. File 1 is report.pdf, 1.2 MB. Enter sends it.” A message that mentions a path among other words still sends as text, and commands run as before.
Fixed
- Drop a file in a terminal that types it: some terminals, such as Nyx, write a dropped file’s path into the window as typed keys instead of as a paste. Socketchat now reads keys that arrive all at once as a paste, so the drop shows as
[File 1]straight away and Enter sends the file. Typing and held keys work as before.
This release makes dropping a file on the window work on Windows.
Fixed
- Drop a file on Windows: a file dropped on the Socketchat window in Windows Terminal, the classic console or VS Code now shows as
[Photo 1],[Video 1]or[File 1], as it does on macOS and Linux. Before, its path pasted as text, because Socketchat read the backslashes in a Windows path as escapes. Paths with spaces, which these terminals wrap in double quotes, andfile:///C:/links work too.
This release lets you invite someone you already share a room with by name, with
/invite <name>, and they join with /join <room>. Commands are easier to find: / and Enter opens a help box you pick from, Up and Down step through the commands that start with what you typed, and Tab fills in names after /invite and invited rooms after /join. Dragging the mouse over messages copies them, and a file dropped on the window waits in the message box for Enter. Each room says once that it is end-to-end encrypted, the People title counts the people you verified, and Socketchat warns you when someone joins under a verified person’s name with a different key. /status and socketchat status show the server, the connection, the open room and the app in one place. Apps and servers on 0.4.0 to 0.5.2 still work with 0.6.0; “Upgrading” at the end lists what changes for them.New
- Invite someone you share a room with:
/invite <name>, and they type/join <room>, as in IRC. In a room,/invite Boinvites someone you already share another room with;/invite Bo "Climbing Saturdays"invites them to a room that is not open. Their app writes a line into the room they have open, as IRC shows an invite in the open window, such as “Ada invites you to Climbing Saturdays. Type /join Climbing Saturdays to join.”, and shows it on the status line. An invite that comes while their chat screen is closed waits in the room you share and moves to the room the chat screen opens on, so it shows once. It names the room’s server when they have never used it, says when they have not verified you, and adds the start of your key, asAda#1a2b, when someone else there has your name./join Climbing Saturdaysjoins, and/joinalone joins when one invite waits. When more than one fits, nothing is joined and the app lists them by number, in the order they came, with “(verified)” after each inviter you verified: “More than one invite waits for Climbing Saturdays: 1. from Ada (verified), 2. from Cy (on chat.example.org). Type /join 1 or /join 2.” A number always means that invite, even next to a room called “2”./invite Ada Smithmeans Ada into the room Smith; when someone called Ada Smith also shares a room with you, the app asks for quotes. Nothing opens on its own and no single key joins a room. There is nothing to decline: an invite nobody takes ends after 24 hours, and your room then shows “Bo didn’t join Climbing Saturdays.” A join shows “Bo accepted your invite and joined.” The room you invited them to keeps a line, “Invite sent to Bo.”, that only you see, so you know the invite went. Room settings apply as for any invite: in an admins-only room a member hears “In this room only admins can invite people.” A name that two people share is refused with a tag for each and “(verified)” after each one you verified: “More than one person called Bo shares a room with you: Bo#1a2b (verified) in Book club and Bo#9f3c in Hikes. Type /invite Bo#1a2b or /invite Bo#9f3c.” From a terminal,socketchat invite --group <room> <name>invites by name, andsocketchat syncprints the line when someone invites you. - The command in an invite line stands out: in “Ada invites you to Climbing Saturdays. Type /join Climbing Saturdays to join.”, the command
/join Climbing Saturdaysshows upright and bold in the theme’s accent color, and the rest of the line reads as a notice, so a room name with spaces is easy to read and type. Copying the line still copies plain text. - Tab completes names after
/invite:/inviteand Tab, or/invite Band Tab, puts in the name of someone who shares a room with you, and each further Tab moves to the next, going round; Shift-Tab goes back. People who are not in the open room come first. Two people with the same name come up asBo#1a2bandBo#9f3c, so the command names one person, and a name with a space comes up in quotes. Someone whose name has not reached your app yet does not come up, since/invitecannot name them either. - Tab completes the room after
/join:/joinand Tab puts in the room of an invite that waits for you, newest first, and further Tabs go through the others;/join Cland Tab takes only the rooms that start with “Cl”. With no invite waiting, the bottom line says “No invite waits for you.” - Up and Down after
/switch,/inviteand/join: with/switch,/inviteor/joinin the message box, and any letters after it, Down puts in the next room or name that Tab would and Up the one before, going round, and Enter after/switchopens the room shown. Shift-Tab after/switchnow goes back through the rooms too. An empty box, a lone/, a message and an earlier line that Up brought back still step through earlier lines./helplists these keys. - Pick a command from the help box:
/help, or/and Enter, lists every command in alphabetical order with the first one highlighted. Up and Down move the highlight and go round from the last command to the first, the mouse wheel moves it too, and PgUp and PgDn scroll a page. Enter runs the highlighted command, or puts it in the message box with a space after it when it needs more, such as/join. A click on a command highlights it, and a second click uses it. Esc closes the box. - Up and Down after
/: type/and a letter, and Up and Down put each command that starts with those letters in the message box in turn, in alphabetical order, going round. Tab and Shift-Tab go through the same list, now in alphabetical order too, and typing ends the run. With a lone/, an empty box or a message, Up and Down bring back earlier lines as before. - Enter on the start of a command: when only one command starts with what you typed, Enter runs it, so
/qquits, or puts it in the box to type the rest, so/jogives/join. - A line that says a room is end-to-end encrypted: each room you make or join shows one line in the notice color: “End-to-end encrypted. Only the people in the People list can read this room. The server passes messages along but cannot read them. /details says what it can see.” A direct chat says “Only the two of you can read this chat.” instead. While a join waits for its inviter, the line says “Waiting for Ada to confirm your invite, so nobody here is verified yet.”; after a failed invite check the red warning stays and the line leaves out who can read the room. Rooms made before this release show the line once, after their newest message, the first time they open.
- Encryption in
/details: a new section says the room uses end-to-end encryption with MLS (RFC 9420), whether its messages and files have post-quantum key exchange, read from the room’s own suite, what the server cannot see and what it sees. - Verified count in the People title: “People 2 of 3 ✓” counts the verified marks the list shows, yours included. A narrow window shortens it to “People 2/3 ✓” or “2/3 ✓”.
/status: one box with the open room’s server and port, whether Socketchat is connected and since when, the protocol in use, the certificate fingerprint your app trusts for that server, and the server’s rule on inviting into rooms; your name, your half of each safety number and how many of your rooms are on that server; the room’s kind, members and how many are verified, admins, your role, settings, whether it has a topic, and its encryption with the suite’s name and number; and the app’s version, update check with the newest release it last found, theme and mouse setting. A last line points to/detailsfor what the server can see. The box scrolls, and drag copies from it like the other boxes. From a terminal,socketchat statusprints the same lines, and--group <name>adds a room. Servers do not tell apps their Socketchat version, so the box shows the protocol instead.- Select and copy with the mouse: drag over messages to select them, and Socketchat copies the text when you let go, while clicks and the scroll wheel keep working. The status line says “Copied.”, or that Socketchat asked your terminal to copy when no clipboard program could. A message the screen wrapped copies as one line, a message of several lines copies its lines without the indent the screen puts under the first, and dragging past the top or bottom of the messages scrolls them a row at a time. Text in the
/help,/details,/about,/invitesand/serversboxes copies the same way. Esc, typing, a new click or new messages clear the selection. Holding Shift as you drag (Option or Fn on a Mac) still selects the terminal’s way, and/mouse offstill gives the mouse back to your terminal. - Drop a file to send it: drag a photo, video or other file onto the window, and the message box shows
[Photo 1],[Video 1]or[File 1]while the bottom line names it, as in “Photo 1 is beach.jpg, 2.1 MB. Enter sends it.” Enter sends each file as/senddoes, then the words you typed as a message, and Backspace removes a placeholder with its file. A folder, a file Socketchat cannot read, a file moved since the drop or one over the server’s limit is named on the bottom line with the reason, and the draft waits.
Changed
- Ctrl-C twice to quit: one Ctrl-C no longer closes Socketchat, so a Ctrl-C meant to copy does no harm. The bottom line says “Press Ctrl-C again to quit.”, and a second Ctrl-C within 2 seconds quits, in a box too. Any other key, or 2 seconds passing, starts over. With text selected, Ctrl-C copies it, as letting go of the drag does.
/quitstill quits at once. - Invite box: the text under an invite link now says the person can paste it into an open chat with
/join, and that/invitewith a name invites someone you already share a room with./helpsays the same. /aboutnow says what the server still sees: timing, message sizes, IP addresses and how many people are in each room.
Fixed
- Tab completes
/help:/hand Tab now give/help, and/helplists itself. Before, Tab said “No command starts with /h”, because/helpwas missing from the list Tab reads. - Messages in the order the server stored them: a server on 0.6.0 sends each message and room change to everyone before it answers any request that came after it, so messages reach everyone in the order the server stored them. Two admins who finish closing a room at the same moment now agree on who closed it, and someone removed from a room hears of the removal before the server refuses their next request.
Security
- Invites by name stay between two people: the invite travels through a room you both share. Its other members see that an invite went by and whether it was taken, never which room it is for, its server, its invite token or the joiner’s keys, which travel sealed with HPKE (RFC 9180) under keys made for that invite alone.
- Consent and once-only: the person’s app makes the keys that let anyone add them only when they type
/join. Each app takes each step only from the member it expects, so no other member can pose as the inviter or join for the person invited. An invite works once and ends after 24 hours, or when either person leaves the room it travels through, and the inviter’s app cancels its link. - No verified mark from an invite by name: a newcomer shows as verified only to members who had verified them before. The newcomer’s own app counts the room verified only when the Welcome comes from the inviter’s key the invite named and they had verified the inviter; otherwise their name stays out of the room, as for an unchecked link.
- Too many invites: an app keeps at most 3 open asks from one member of a room, drops one whose offer does not follow within minutes, holds at most 20 invites at once, and ignores the same person’s invites for an hour after one runs out. An inviter whose offer would come too late says so and can invite again at once.
- Someone new under a verified name: Socketchat remembers the names of the people you verified, with their identity keys, after they or you leave a room. While someone shows under one of those names with a different identity key, the People title reads “People ! check” and their row carries a
!, and when their name arrives the room says “Bo joined with a different key from the Bo you verified. Treat them as someone new until you compare safety numbers: /verify Bo”. Verifying them, or their leaving, clears the mark. Names match ignoring spacing, invisible characters and the case of ASCII letters, as/verifymatches them. Weekly key refreshes keep the same identity key and stay silent. Profiles from earlier releases learn these names from the member lists they already hold.
Upgrading
- Apps on 0.5.2 and older ignore the four new kinds of encrypted message, numbers 14 to 17, and work in the room as before.
/invite <name>refuses someone whose app says it runs 0.5.2 or older: “Bo’s app is too old for this kind of invite. Send them a link with /invite.” - Profiles from 0.5.2 and older upgrade in place the first time 0.6.0 opens them: Socketchat adds tables for invites by name, the encryption line and the names you verified, and keeps every room, message and key as it was.
- Servers need no update. An invite by name uses the requests a link uses, and its link counts toward
max_accounts_from_room_linkslike any room link, though nobody makes an account with it. On a server from before 0.5.0, an unused link from an invite that ended expires on its own instead of being cancelled.
This release lets a room’s admins choose who can invite, turn on slow mode and set a topic, gives each server a pace for posting, brings back earlier lines with Up and Down, puts a QR code a phone can open in the invite box, and says when a newer release is out. Apps now pad every message, so the server sees its size rounded up to 256-byte blocks. Apps and servers on 0.4.0 to 0.5.1 still work with 0.5.2; “Upgrading” at the end lists what changes for them.
New
- Who can invite, per room: a room’s admins choose whether anyone in the room or only admins can bring people in, with
/settings invite adminsand/settings invite anyone. Rooms start with anyone, as before. In an admins-only room the server refuses a member’s invite link and a member’s add, every app refuses such an add too, and links members made before the change stop working; someone waiting on one hears that it stopped working./settingsand/detailsshow the setting, the room shows a line such as “Ada let only admins invite people to this room.”, and a member who tries to change it hears “Only admins can change this room’s settings.” - Room topic:
/topic <text>sets one line for the open room, and everyone in it sees it under the room’s name, as/topicworks in IRC (Internet Relay Chat)./topicshows it with who set it and when,/topic --clearremoves it, and/detailsshows all of it. Each change shows in the room as a line such as “Topic: Piranesi, chapters 1 to 5 (set by Ada, verified, 2026-10-25)”, and someone who joins sees the same line. Only admins set the topic, as IRC’s+tmode does, until an admin runs/settings topic anyone;/settings topic adminsgoes back, and a member who tries without the right hears “Only admins can set this room’s topic.” A topic is at most 300 characters. From a terminal,socketchat topic --group <name>prints a room’s topic,socketchat topic --group <name> <text>sets it, and--clearremoves it. The topic travels encrypted, so the server never sees it; it sees only the setting for who may set it. - Slow mode: a room’s admins make each member who isn’t an admin wait between messages with
/settings slow <seconds>, up to 6 hours, and turn it off with/settings slow off. Admins are not held. The server enforces it, and the room shows a line such as “Ada turned on slow mode: one message every 30 seconds for each member who isn’t an admin.” - A pace for posting: a server limits how fast each member posts in each room: a burst of 30 messages, then one every 5 seconds, with a byte allowance that only large messages meet. Admins get ten times that. A message over the limit waits in the app, which says “This room limits fast posting; sending in 4 seconds.” and sends it, after any others waiting in that room, once the server allows. The app encrypts nothing for a room while the room holds it back. Messages the app sends on its own, such as your name after someone joins, wait the same way without a word. A waiting message goes only to the people who were in the room when you typed it: if someone joins or leaves first, the app says “Not sent, because the people in this room changed while it waited. Send it again if you still want to.” and puts the text back in the message box. Quitting while a message waits asks first. The server never removes or bans anyone for posting fast. A member can always ask to leave, once each time the room changes, and removing someone is never held up.
socketchat sendwaits until its message goes. Operators change the pace insocketchat-server.toml; How fast members can post explains the defaults. - Earlier lines: in the message box, Up brings back the last message you sent or command you ran in the open room, and each further Up goes one line further back. Down goes forward again and, past the newest line, gives back what you were typing. Each room keeps its own lines, the newest 100, and a line repeated in a row is kept once. Socketchat keeps them in memory only and never writes them to disk, and
/leave,/clearand/forgetdrop a room’s lines at once./helplists Up and Down, and the help line says what they do while an earlier line shows. - Update notice: once a day Socketchat asks GitHub whether a newer release is out. When one is, the chat screen’s bottom line and the output of commands such as
socketchat syncsay “Socketchat 0.5.3 is out. Run socketchat update.”, or “Run brew upgrade socketchat.” for a copy Homebrew installed. The request carries nothing about you or your chats, and a check that fails says nothing./updates offturns the check off and your profile keeps the choice;SOCKETCHAT_NO_UPDATE_CHECK=1turns it off for one run. While it is off, Socketchat makes no request at all./aboutsays whether the check is on and when GitHub last answered. socketchat update: prints the command that installs the newest release, for the way your copy was installed:brew upgrade socketchatfor Homebrew, the install command again for the installer (thecurlcommand on macOS and Linux, the PowerShell command on Windows), or all of them when it cannot tell. It installs nothing itself. On macOS and Linux the install command checks a SHA-256 checksum that comes from the same release, and on Windows it checks none; to check a release’s build attestation, rungh attestation verify <file> --owner sachio222 --cert-identity-regex '^https://github\.com/sachio222/socketchat(_v4)?/\.github/workflows/release\.yml@refs/tags/v'on the file.- Homebrew:
brew install sachio222/tap/socketchatinstalls Socketchat, and each release now updates the formula in the tap by itself, sobrew upgrade socketchatfinds the new version.
Changed
- QR codes for phones: the QR code in the invite box now holds
https://socketchat.org/join#socketchat://..., so a phone camera opens a web page that explains how to join, instead of a link it has no app for. The text under the box is still thesocketchat://link to paste into a terminal. For a long link the code uses lower error correction when that makes it fit, and the box shows the whole code or a note to make the window larger. - Invite message: the first step now says to install Socketchat on your computer.
- Joining with a web link:
socketchat joinand/joinalso takehttps://socketchat.org/join/#socketchat://..., the address a browser shows after the join page’s redirect. Any other web address is refused with “That is not a Socketchat invite link: the only web address that carries an invite is https://socketchat.org/join.” Socketchat reads these links and never opens them, so the invite after#goes nowhere. - New repository name: the code now lives at https://github.com/sachio222/socketchat. Links to the old name still redirect.
- Two server settings in place of one:
members_can_inviteinsocketchat-server.tomlsplits in two.members_make_accountscovers bringing new people onto the server: server invites from members, and accounts for people who join through a member’s room link.members_can_invite_to_roomscovers bringing people into rooms: when it isfalse, every room on the server is admins-only for invite links and adds, whatever its own setting says,/detailssays “Who can invite: admins only, because this server lets only admins invite people”, and an admin who runs/settings invite anyonehears “This server lets only admins invite people into its rooms, so this room stays admins-only.” Both default totrue, where each room decides. Apps ask a server on protocol 3 for this rule. - Protocol 3: apps and servers on 0.5.2 speak protocol 3, which adds one answer for a post that came too fast and one request for the server’s rule on inviting into rooms. An app takes protocol 3 to mean that the server also enforces each room’s settings.
Fixed
- Server errors on Windows: a server that refuses the connection now reads “connection refused” on Windows too, the same as on macOS and Linux, and the message no longer ends in two full stops.
Security
- Message padding: Socketchat pads every encrypted message with zeros to a whole number of 256-byte blocks, so the server sees each message’s size rounded up instead of its length. Every text of up to about 170 characters of English now has one size, and a longer message grows a block at a time. A one-word message grows from about 150 to 318 bytes. There is no setting to turn padding off, because someone who did would stand out in a shared room by their exact lengths. Padding hides length only: the server still sees when each message is sent, and how big each file is. Rooms made or joined before this release start padding the next time the app opens.
- Room topics stay plain text: every app takes a topic only from someone in the room who may set it at that point, an admin or any member while the room allows it, and ignores one from anyone else or from a member removed before it arrived. Each topic carries the setter’s signature, so the admin’s app that passes it on to a newcomer cannot change its words or name someone else as its setter. Before showing a topic, apps remove control characters and escape codes, direction controls, invisible characters and Hangul fillers, and fold line breaks into spaces, so a topic cannot move the cursor, recolor the screen, set the terminal’s title or disguise a file name. A topic always shows after
Topic:in its own color, never in the colors of the app’s notices, warnings or verified mark, and a link in it shows as its full address. A topic counts toward the room’s posting pace like any message, and leaving,/clear,/forgetand a room’s ending delete it from the computer. - Message senders: apps take each message as its sender’s only when the key that signed it, in the epoch it was written, belongs to the member in that place in the room now, and ignore it otherwise.
- Constant-time helpers: Socketchat now uses ctutils 0.4.4, whose comparisons and masks, which the encryption code relies on, run in the same time whatever the values (RUSTSEC-2026-0385).
Upgrading
- Room settings and apps on 0.5.1 or older: such apps work as before in rooms on the default settings. A room’s admins can change a setting only once everyone in the room runs 0.5.2 or later and has opened it once since updating, which refreshes that app’s keys in each room; until then the admin’s app names who it waits for. While a room has settings, an app on 0.5.1 or older cannot join it, and its owner hears “this room needs Socketchat 0.5.2 or later; update Socketchat, then ask for a new invite link”.
- Room settings and servers on 0.5.1 or older: such a server cannot keep room settings, so an app on 0.5.2 refuses to set them there: “This server runs an older version of Socketchat, so it can’t keep this setting. Ask the person who runs it to update.” Setting a room back to the defaults still works.
/settingsand/detailssay “This server runs an older version of Socketchat, so it can’t enforce who can invite or slow mode.” - The pace limit and apps on 0.5.1 or older: a 0.5.2 server holds them to the same pace. Over it they show “this room limits fast posting; try again in 4 seconds” as an error, and the message stays in the message box to send again. What those apps send on their own may show the same words as a warning, and goes on a later sync.
- Servers that set
members_can_invite = falsekeep everything it stopped: the server reads it asmembers_make_accounts = falseandmembers_can_invite_to_rooms = false, so members still cannot bring new accounts onto it or people into its rooms, whatever a room’s setting says. The old key never loosens a new key set beside it, and a config the server saves writes the two new keys. - Apps on 0.4.0 to 0.5.1 read padded messages. They send their own messages unpadded until they update, so in a room with such an app the server still sees the exact length of that person’s messages.
- Room topics and apps on 0.5.1 or older: the topic is a new kind of encrypted message, added after every kind those apps know, and the message format changes in no other way. Apps on 0.5.1 or older ignore it, show no topic, and keep working in the room as before. Letting anyone set the topic is a room setting, so it waits until everyone in the room runs 0.5.2, as the other settings do.
- Servers need no update for padding or for room topics, which happen in the app. Room settings, letting anyone set the topic among them, and the pace limit need a 0.5.2 server.
This release adds a list of the servers you use, mouse support, Tab completion for commands and a new color theme. It also fixes security problems that a review of Socketchat’s code found. Apps and servers on 0.4.0 and 0.5.0 still work with 0.5.1; “Upgrading” at the end lists what changes for them.
New
- Servers: the chat screen shows the open room’s server next to its name, and
/detailsnames it./serverslists every server your profile knows, numbered, with how many of your rooms are there and whether it is connected, could not be reached and why, or not tried yet./forget <number>asks first, then deletes that server from your computer with its rooms, their messages and keys, rooms there that ended with messages you have not read, the joins waiting there, the invite links you made there, its certificate and your account key. The server is not told, so others still see you in its rooms until an admin removes you. From a terminal,socketchat serversandsocketchat servers --forget <number>do the same, and--yesskips the question. - Mouse: click a room in the Chats list to open it, click a panel to move to it, and scroll the messages,
/help,/invitesand/detailswith the wheel. Boxes have buttons along their bottom edge, such as Yes and No when Socketchat asks a question. While the mouse is on, hold Shift as you drag to select text (Option or Fn on a Mac)./mouse offgives the mouse back to your terminal, and Socketchat keeps the choice in your profile. - Tab completes commands: in the message box, Tab completes a command that starts with
/, and Tab or Shift-Tab steps through the matches when there are several. Matching commands show on the help line,/themeTab cycles the color names, and a grey suggestion after the cursor shows what Tab would add; Right arrow accepts it. Tab still moves between panels for anything else. - Colors: the chat screen has a new default look called phosphor, green on a near-black screen.
/theme classicbrings back the old colors, which use your terminal’s own background, and/theme phosphorswitches back. Socketchat saves the choice on your computer, andSOCKETCHAT_THEME=classicoverrides it for one run. Phosphor uses exact colors whenCOLORTERMistruecoloror24bit, and 256-color approximations otherwise. - Invite message:
/invitecopies an invite message as the invite box opens, and C copies it again. The message says to install Socketchat from https://socketchat.org and then runsocketchat join "socketchat://...", ready to paste into a terminal; the quotes keep the link whole in every shell. A line under the link says “Copying…” while the clipboard program runs, then whether the copy worked, and the screen keeps taking keys meanwhile. Socketchat copies with the computer’s clipboard program (pbcopy, wl-copy, xclip, xsel or clip.exe) and asks the terminal to copy when there is none. The box still shows the bare link and its QR code.socketchat joinand/joinaccept web links of the formhttps://socketchat.org/join#socketchat://...as well as thesocketchat://link, andsocketchat invitestill prints only thesocketchat://link. - Getting started: the installer ends with the commands that start a server, join one and open the chat screen.
socketchaton a computer with no profile prints the same steps and exits without an error. - Version and about: the chat screen shows
socketchatand its version at the right end of the bottom line, and drops it when the window is too narrow to keep the help text whole./aboutshows the version, what Socketchat is, the project link and the license. - Checking a download: every file in a release now has a GitHub build attestation, a signed record of the commit and the release workflow that built it.
gh attestation verify <file> --owner sachio222 --cert-identity-regex '^https://github\.com/sachio222/socketchat(_v4)?/\.github/workflows/release\.yml@refs/tags/v'checks one, as the README shows. - IPv6 in invite links: an IPv6 address may be written in brackets, as in
socketchat://[2001:db8::7]:7444/j/....
Changed
- New rooms go where you expect:
/newmakes the room on the open room’s server, or on the newest server you joined when no room is open, and says which.socketchat newuses the newest server, and--server <number>picks another from thesocketchat serverslist. - Errors name the server: a server Socketchat cannot reach is named, as in “Could not reach chat.example.com: connection refused.”, with a pointer to
/serversorsocketchat servers. A dropped connection names its server too. - Message box: the empty message box reads “What’s on your mind? #Book club”, naming the open room after a #.
- Name: the product is written Socketchat in the app and the docs; the command stays
socketchat. - Busy servers: a server checks a room change while it goes on answering everyone else’s requests.
Fixed
- New rooms after a server stops: new rooms used to go on the first server you joined, so once that server stopped,
/newfailed even after you joined another. - Long messages: the chat screen wraps only the messages that can reach the window, so a room full of very long messages no longer slows every key press.
- Late joins: a join completed after the invite’s 24 hours waits for the inviter to confirm it, instead of showing the invite as expired.
- Sideways photos: a JPEG keeps its orientation, so a photo taken sideways shows the right way up.
- The chat screen on errors:
/save ""no longer closes the chat screen, and the terminal goes back to normal when the chat screen stops on any error, on a crash, or when the system asks it to stop on macOS and Linux (SIGTERM, or SIGHUP when the terminal window closes). A crash message prints after the terminal is back to normal instead of over the chat screen, and a crash while reading the keyboard ends Socketchat with an error instead of looking like a normal quit. - Setting up again: if making a profile stopped part way, the next
socketchat joinmoves what it left aside, renaming the files to end in.unfinished-and a time, says so, and makes a new profile. Socketchat never deletes a salt file. A salt file without its database stopsjoinwith a message that names it, and a profile whose salt file is missing says so instead of saying there is no profile.
Security
These changes come from a review of Socketchat’s code. Some of them run on the server and some in the app, so update both. SECURITY.md describes what each part protects.- Room changes: apps refuse a room change from anyone outside the room and show a warning when one arrives. They also check admin rights themselves and refuse, with a warning, a change only an admin may make, such as removing someone or changing the admins, when someone else sent it. When the last admin leaves, each app checks the new admin against its own record of who joined when. The member list shows everyone in the room, and someone the app has no name for shows as “someone” with a short form of their key.
- Joining with an invite: the person who invited you shows as verified once their app confirms the invite from inside the room, which it does by itself the next time it connects; until then Socketchat says “Waiting for <name> to confirm this invite.” Your own name, identity key and app version stay out of the room until that confirmation, and until then you cannot make invite links or start direct messages from that room. If the inviter cannot confirm it, your name stays hidden until you compare safety numbers with someone there and mark them verified. An invite link verifies only the person who joined with it.
- Removing someone: removing someone from a room, or their leaving it, cancels the invite links they made there and drops any join still waiting on those links. Socketchat apps no longer let anyone in through a link whose maker left the room, and someone who already used such a link hears from their app that it stopped working and needs a new one. A removed member’s key cannot join the room again.
- Connections before sign-in: a server closes a connection that has not signed in within 60 seconds of connecting, whatever it sends. Until then it takes frames of at most 8,192 bytes from it, and all such connections together hold at most 8 MB of partly sent frames;
max_frame_before_sign_inandmax_buffered_before_sign_in_mbinsocketchat-server.tomlchange the two sizes. - New accounts through room links: the room links one account makes register at most 100 new accounts every two days;
max_accounts_from_room_linkschanges the number. A link past that, or one made by someone with no account on the server, still brings the person into the room, but they need a server invite before they can start rooms or direct messages. - Storage limits: a server keeps at most 200 MB of messages and 4,000 MB of files per room, 4,000 MB of files per member of a room, 100 people waiting to join a room, and 8,000 MB in all, of which files may use nine tenths; a new setting in
socketchat-server.tomlchanges each one. Past a limit it refuses the message or the file with a reason, such as “this server is full”, which apps show as an error. Someone redeeming a link into a room that cannot take them hears why from their own app, and the link stays unused. If an add is refused later, the inviter’s app says so, once per link each time it runs. A full room still takes requests to leave and changes that only take people out, and removing someone deletes the files only they were waiting for. An upload that does not finish is deleted after 6 hours, or sooner when the same member starts a fourth while three are unfinished. - Server data directory: on macOS and Linux a server keeps its data directory for its own account (0700 for folders, 0600 for files, the certificate and its key included), narrows a directory an earlier release made when it starts, and says so in one line on standard error. Deleting a room or a member’s data also clears SQLite’s write-ahead log, and a Welcome nobody fetched before its person was removed goes with the removal.
- Photos: Socketchat cleans a photo by writing a new copy with only what is needed to draw it, so location and device data also leave thumbnails, the second images some phones add, and anything stored after the picture. GIF images are cleaned too, keeping their frames, timing and loop count, and PNG and WebP photos lose their color profiles, as JPEG photos already did. HEIC, TIFF, camera raw, JPEG XL, JPEG 2000 and Photoshop files, and photos over 100 MiB, ask before sending, as videos do.
- Saving files: when more than one file in a chat has the same name,
/savelists them and saves the one you pick by number, as in/save beach.jpg:2, and the status line names the person whose file you saved. On macOS and Linux, a download goes into a new file only your account can read, and the hidden part file a stopped download leaves behind is deleted the next time you save that file, once nothing has touched it for an hour. Saved names never start with a dot or name a Windows device such asCON. - Questions on the chat screen: the boxes that ask about a new server certificate, a safety number match, or sending a video or a photo that cannot be cleaned take y only as the first key pressed, as the yes-or-no questions already did. Any other key answers no, and keys typed or clicks made before a box showed never answer it. The video or photo goes to the room that was open when Socketchat asked. A room you join while words wait in the message box or a box is open does not open by itself: the status line names it, and the room you were in stays on screen.
- Pasting: on macOS and Linux, a paste goes into the message box as text, with its line breaks shown as ↵, and nothing is sent or run until you press Enter. Text with a line break never runs as a command, and a command runs only when it starts the message box and has single spaces between its words. A command too long for the box shows its start and its end. The message box takes at most 16 KB, as much as one message carries, and says so when it cuts a paste or fills up. This needs a terminal that marks pastes (bracketed paste), which most do.
- Spaces in names: Socketchat writes every name, room name and file name with one plain space between words, so a name sent with two spaces in a row, a tab or a full-width space can still be typed after
/kick,/verify,/dm,/admin,/rename,/switchand/save. A name already kept with other spacing matches too. socketchat logandsocketchat sync: the second and later lines of a message print indented by four spaces, so a line that starts at the left edge always begins a message and names the person who wrote it. Names and room names in this output are cleaned of control characters, as message text already was.- Server addresses in invite links: Socketchat refuses an invite link whose server address is not a host name or an IP address, before it stores anything, and
socketchat server initrefuses such a--host. Server addresses in Socketchat’s warnings and errors are cleaned of control characters. - Profile folder: on macOS and Linux, Socketchat keeps your profile folder for your own account (0700 for the folder, 0600 for its files). When it opens a folder made by an earlier release, it narrows the folder and its files and says in one line what it changed. On a drive that cannot change these settings, such as a FAT or exFAT drive, it warns and opens the profile anyway. It will not open a profile folder that another user account owns, and says why. A profile folder reached through a link is checked where the link points.
- Empty passphrase: Socketchat no longer makes a profile with an empty passphrase. A
SOCKETCHAT_PASSPHRASEthat is set but empty stopssocketchat joinwith a message before it makes anything, and one that is not valid text is refused everywhere. - Passphrase hashing: new profiles turn the passphrase into a key with Argon2id at 64 MiB of memory, 3 passes and 4 lanes, up from 19 MiB and 2 passes, so each guess at the passphrase of a copied profile takes about five times the computing and over three times the memory. A Raspberry Pi Zero 2 W should still open a profile in under about 2 seconds.
- Prebuilt programs: the
socketchatprogram in a release leaves out code that only the tests use, and the release workflow checks for it before publishing. Release builds use a pinned Rust version, 1.98.1, and the exact library versions inCargo.lock.
Upgrading
- Update the server and the apps. Apps and servers on 0.4.0 and 0.5.0 keep working with 0.5.1, whose protocol is unchanged, and some of the protections above need both sides on 0.5.1.
- Server addresses that are not ASCII: 0.5.1 apps refuse an invite link whose server address is not ASCII, so a link that 0.5.0 accepted with a name in another script no longer works. Write such a name in its
xn--form inpublic_host. A 0.5.1 server warns about this when it starts, and still starts. Members who joined through such a link keep that address on their computer, so their 0.5.1 apps make no invite links there and say why. After changingpublic_host, send each of them a new server invite so they can start new rooms there; rooms they joined through the old address still cannot make links. - Profiles from earlier releases keep their Argon2id settings, 19 MiB and 2 passes, and open as before. Apps on 0.4.0 and 0.5.0 also open profiles that 0.5.1 makes.
- A profile made with an empty passphrase by an earlier release still opens with an empty one, and Socketchat warns each time that it has no passphrase.
- Pastes on Windows still arrive as typed keys, one line at a time, so each line is sent or run as you would type it.
- Invite links whose maker left: a link stops working once the member who made it leaves the room or is removed. Ask someone still in the room for a new one.
- Requests before sign-in: a request over 8,192 bytes sent before signing in, which an app sends only when the server no longer knows any of its keys, now drops the connection instead of getting a refusal.
- Server disk space:
max_stored_mbis a fixed 8,000 MB by default. On a larger disk, raise it insocketchat-server.toml, or apps hear “this server is full” at 8 GB. - Forgetting a server: a room that ended for you before this update, with messages you have not read, stays after you forget its server until you read it or 30 days pass.
- Saved files: on macOS and Linux a saved file is readable only by your account. To share one from a shared or web-served folder, change its permissions after saving.
This release lets you move between rooms, rename them and close them, deletes a room’s history from your computer once you are done with it, and lists the invite links you made that still work. Apps and servers on 0.4.0 still work with 0.5.0.
- Moving between rooms:
/switchopens another room, and Tab completes its name. Unread counts stay right after you close and reopen the app, andsocketchat logmarks the messages it prints as read. When more are unread than it prints, it prints the oldest unread ones first. Anything you had before this update counts as read. - Renaming a room: admins rename a room for everyone with
/title, and the room shows who renamed it. - Closing a room:
/closeasks to close a room for everyone, and the room closes once its admins agree: every admin when the room has up to three, more than half of them when it has more. A room with one admin closes at once./keepsays no, and a request to close stays open for seven days. - Room details and muting:
/detailsshows a room’s admins, how many people are in it and when it was made. A server on 0.4.0 cannot say when, so that line is left out./mutehides a room’s new-message count on your own computer, nobody else sees that you muted it, and/unmuteshows the count again. - Leaving, removal and closing: when you leave a room, socketchat deletes the room’s keys from your computer at once. When you are removed or the room closes, it deletes them as soon as your app learns of it, which for an app that was not running is its next sync with the server. When you leave, the room’s messages go at the same time, and
/leavefirst shows any new messages and asks you to type/leaveagain. A room you were removed from or that closed stays on screen, saying so, and its read messages go when you open another room or quit. Unread messages stay until you read them and still show who wrote them. Once 30 days have passed since the room ended for you, socketchat deletes them anyway the next time it opens, you open another room or it quits. - Deleting data on your computer:
/cleardeletes a room’s messages and its files list from your computer while you stay in it. socketchat turns on SQLite’ssecure_delete, so deleted rows are overwritten inside your encrypted profile. A join request made with 0.5.0 no longer leaves spare keys on your computer once you join. Opening 0.5.0 deletes the history of rooms you left with 0.4.0. - Invite links you made:
/inviteslists the ones that still work, and/cancel <number>stops one. From a terminal,socketchat inviteslists them, andsocketchat invites --cancel <number>stops one and names the link it cancelled. - Servers delete rooms nobody is in: a 0.5.0 server deletes everything it holds for a room at once when a 0.5.0 app leaves it as the room’s only member, as happens at the end of a close. Its hourly sweep also deletes rooms that have no members.
- Working with 0.4.0: apps and servers now use protocol 2, and still use protocol 1 with apps and servers on 0.4.0. A 0.5.0 server serves apps on 0.4.0, so you can update the server first. A 0.5.0 app works with a server on 0.4.0. A feature that needs a newer server says so and leaves the rest of the app alone.
- Messages from add-ons and other programs: rooms now carry them, end-to-end encrypted like text. One that carries a summary line shows it in the chat, and apps on 0.4.0 skip them. Each app also tells its rooms which version it runs.
- Contributors:
sh scripts/crate-age-check.shkeeps libraries released less than 30 days ago out ofCargo.lock, so this release builds against older versions of some of them.
The first release of socketchat v4: a rewrite in Rust of the earlier Python versions, with standard group encryption and a server you run yourself.
- Group chats encrypted end to end with MLS (RFC 9420, through OpenMLS 0.9.1), on the hybrid post-quantum suite ML-KEM-768 with X25519 by default. The suite comes from an IETF draft that is not final; SECURITY.md explains what that means.
- Invite links with no usernames or directory. A link works once, expires after the time the server sets (24 hours unless changed), and lets the new person check who invited them.
- Verification: safety numbers to compare in person, with a QR code.
- A server that cannot read: it checks signed group changes and admin rights, stores only encrypted data, and keeps no record that ties one person’s groups together.
- Files, photos and videos, encrypted in chunks with a fresh key per file. Photos lose their location and device data before sending; videos ask first, because they keep theirs.
- A terminal chat screen that works at 80 by 24 and over SSH, with commands for invites, direct chats, files, verification and admins.
- Encrypted local storage keyed by your passphrase, locked so only one copy of socketchat opens a profile at a time.
- A server built to face the open internet: every connection has a memory budget, idle and silent connections are closed, large backlogs come back in pages, and a server that is full says so. Three rounds of security review went into this release.
- One-line installers for macOS, Linux and Windows. The Linux programs run on Intel and AMD machines and on 64-bit ARM, which includes a Raspberry Pi 4 or Zero 2 W.