Using tinyclient

One window for every network you sign in to. What each network can do is on Networks & terms.

The window

You start tinyclient. It starts chatd when nothing is already listening on the local socket. chatd holds the connections and the cache. The window only draws what chatd reports.

tinyclient --text prints account status and the inbox as lines of text, then exits. An interactive terminal is not built. The socket protocol is the API for one.

Keyboard shortcuts

Menus, tooltips and Settings › Keyboard Shortcuts show the keys for your system, and so does the table below when this page can tell which one you are on. On Linux, Super stays with the desktop. The same chord is Command on macOS and Ctrl on Linux and Windows. Option becomes Alt. Control+Command becomes Ctrl+Alt, so full screen is Control+Command+F on macOS and Ctrl+Alt+F elsewhere. Shift stays Shift.

MenuCommandmacOS
tinyclientSettings…Command+,
tinyclientHide tinyclientCommand+H
tinyclientHide OthersOption+Command+H
tinyclientQuitCommand+Q
FileNew MessageCommand+N
FileAttach File…Command+U
FileClose WindowCommand+W
EditUndo / RedoCommand+Z / Shift+Command+Z
EditCut, Copy, Paste, Select AllCommand+X, C, V, A
EditFind › Search in Conversation / Search EverywhereCommand+F / Shift+Command+F
ViewInbox / PeopleCommand+1 / Command+2
ViewQuick SwitcherCommand+K
ViewHide Sidebar / Close Right PaneCommand+\ / Command+.
ViewBigger, smaller, actual sizeCommand++, Command+−, Command+0
ViewEnter Full ScreenControl+Command+F
ConversationBack / Forward / Up a LevelCommand+[ / Command+] / Command+Up
ConversationNext / PreviousOption+Down / Option+Up
ConversationNext unread / Previous unreadOption+Shift+Down / Option+Shift+Up
ConversationMark as ReadShift+Esc
ConversationShow Details / Start Call / Open in AppOption+Command+I / Shift+Command+C / Option+Command+O
WindowMinimizeCommand+M
HelpKeyboard ShortcutsCommand+/
CallsMute, deafen, leaveShift+Command+M, D, H
CallsAccept, decline, go to the callShift+Command+A, R, J

Text fields use the platform’s own editing keys. On Linux and Windows that is Ctrl+C, V, X, A and Z, Ctrl+Left and Ctrl+Right to move by word, and Home and End inside the line. The optional send shortcut is Command+Return on macOS and Ctrl+Enter elsewhere.

Notifications

chatd decides what notifies, so notifications arrive with the window closed. By default a direct message or a mention notifies, one notification per conversation with its newest lines, taken away once you read it, here or on another device. Your own messages, history and the conversation open in front of you never notify. Conversations you muted never notify, and Do Not Disturb set in Slack or Discord is followed here. Calls ring with Accept and Decline.

Calls and voice

Calls run on Discord, in DMs and voice channels, and on a Tiny server you add. A Discord call can carry a camera, and Go Live sends the screen. A Tiny room can show one picture: a screen share, or one other person’s camera. The camera and screen share send on Windows, macOS and Linux. Settings › Voice and Audio & video apply to both.

Updates

While the window is open it asks GitHub, about once an hour and again shortly after launch, whether a newer release exists. The request is User-Agent: tinyclient/<version> and nothing else: no account, no machine id.

A newer release is shown until you dismiss it. Check for Updates… asks again. With automatic install on, and only for an installed copy (not a build under target/ or a copy in the Nix store), the archive is downloaded, checked against that release’s SHA256SUMS, and on macOS checked with codesign before it is kept. It replaces this copy when you quit. The menu then says Restart to Update. A failure is remembered for a day and said only in About.

When the newest release has the same version number as this copy, tinyclient asks GitHub whether this build’s commit is older than the release, and offers the release if it is. About shows the version and the commit. On Windows, the update waits for tinyclient’s programs to stop, rolls back if a step fails, and opens the app again either way. A copy you cannot write to offers the download instead.

Linux: leave chatd running

By default, quitting the window stops the daemon it started. Logs go to chatd.log.

The .deb, .rpm and Nix packages can install tinyclient-chatd.service. The unit is disabled. With it disabled, nothing about startup changes.

To let systemd manage the daemon, quit tinyclient first so its daemon releases the socket. From a terminal in your graphical session:

systemctl --user daemon-reload
systemctl --user import-environment WAYLAND_DISPLAY DISPLAY XDG_CURRENT_DESKTOP
systemctl --user enable --now tinyclient-chatd.service
journalctl --user -u tinyclient-chatd.service -f

To go back to automatic startup, quit the window and run systemctl --user disable --now tinyclient-chatd.service.

For sign-in diagnostics, import TINYCLIENT_LOGIN_DEBUG=1 into the user manager, restart the service, and watch the journal. Unset it when you are done. The messages name whether the helper is waiting on a login page. They do not include credentials.

A scratch directory (TINYCLIENT_DIR) and an explicit TINYCLIENT_CHATD always start the daemon directly. For a source build or a .tar.gz install, copy packaging/linux/tinyclient-chatd.service to ~/.config/systemd/user/, set ExecStart to the absolute path of that chatd, and reload the user manager. Keep the four programs together. AppImage builds stay on automatic startup.

Edit this page on GitHub