Join and use a server
For a member: get in with an invite, sign in, and know what the server can see.
You need tinyclient and an invite from someone on the server. A Tiny server is run by its owner, not by the tinyclient project.
Join with an invite
An invite is a link that starts https://tinyclient.io/invite#, or a code that starts tc1. Both hold the server’s address, so there is nothing else to type.
- Open the link. The page opens tinyclient. The part after the
#is never sent to tinyclient.io. Or, in tinyclient, choose Join a server on the Tiny rail and paste the link or the code. - Check the address. tinyclient shows which server you are about to join and asks before it goes on. Continue only if you trust that server.
- Sign in in your browser. tinyclient opens the server’s sign-in page in your own browser and waits. It moves on by itself when you are done. If the page did not open, choose Open the page again.
tinyclient waits five minutes for the browser. After that, start again from the invite; nothing was spent.
If you already have an account on a server, choose I already have an account and type its address instead.
A plain http address works, for a server on your own machine or network. Anyone on the way can then read the session and everything sent. tinyclient says so under such an address.
Sign in
tinyclient never sees a password. What the browser shows depends on what the server’s owner chose:
- The server’s own passkey page. New here: type the name others will see and choose Create my account. Your device makes a passkey, which may ask for your fingerprint, face or PIN. Coming back: choose Sign in with a passkey.
- A sign-in provider the owner set up, Pocket ID by default, where you also sign in with a passkey. With Pocket ID, an invite can make your account there: choose I’m new here.
- Some servers offer both.
Keep your recovery codes
When you make an account with a passkey, the page shows 10 recovery codes once. Save them somewhere other than the device that holds the passkey. A code lets you make a new passkey when you have lost yours, and is used up when you do: choose Lost your passkeys? on the sign-in page.
Lose every passkey and every code, and the account is gone. The server holds no email address or phone number to prove who you are. The owner can invite you again as a new person; your old messages stay with the old account.
Server Settings › Sign-in lists your passkeys. Add a passkey makes a link that opens in your browser; open it on another device to give that device a passkey of its own. New recovery codes replaces the set. Both ask you to have signed in within the last ten minutes.
What you see
A server has its own place on the rail, laid out as a Discord server is: text channels and voice rooms in categories on the left, people by role on the right.
- Text channels and direct messages: text, replies, files, reactions, edit and delete. A file is held until the server’s scan passes it.
- Voice rooms: click one to join. Mute, deafen, see who is speaking, and leave.
- A direct call: call another member from your conversation with them.
What you may do in each room and channel depends on the roles the server gave you.
Calls
A room carries everyone’s audio and, when the room allows video, one picture: a screen share while someone is sharing, otherwise one other person’s camera. The camera and screen share send on Windows, macOS and Linux.
Echo cancellation, noise suppression and automatic gain are on unless you turn them off. Using tinyclient covers the microphone, push to talk and devices.
A call says how it is encrypted. End-to-end encrypted: only the people in the call can hear it. Encrypted to the server: the server could hear it. Open the call’s security panel for the call code and the safety numbers, and compare them with the others over a channel you trust. How to read them.
While you are in a call, your computer talks directly to the server’s media port, so the server sees your address.
Encrypted conversations
Direct conversations are created end-to-end encrypted when the server offers it. A channel is encrypted only if it was made or upgraded that way. tinyclient labels each conversation, and says so when the server can read one.
- A new device cannot read earlier encrypted messages by itself. Link it from a device you already use, at Server Settings › Encryption, to carry your history over.
- There is no key backup. If you lose every device, the old encrypted messages cannot be read again, even after you sign back in.
End-to-end encryption has the rest.
What the server can see
The person who runs a server can read every conversation that is not end-to-end encrypted, and its files. Even for encrypted ones they see who talks to whom and when. Other members see your name, your picture, your roles and, unless the owner chose otherwise, when you were last online. Server privacy and security lists all of it.
Sign out
- Signing out in tinyclient ends that session on the server, then removes the server’s messages and media from your computer.
- Sign out everywhere, in Settings › Accounts, ends your sessions on that server on every computer.
- A session ends by itself after 30 days unless the operator set otherwise. tinyclient then asks you to sign in again.
You can add more than one server. Every server’s session is kept in your system’s credential store, in one item they share.