A short guide for people using DarkChan (not running the server — that's docs/OPERATIONS.md).
DarkChan is an end-to-end encrypted messenger for a small trusted group. Someone you know runs the server; you connect a client to it. You need three things:
For now, build the client from source (see the README). Native apps for Linux, Windows, and Android — and a browser-based web portal — are the supported clients; packaged installers are on the way. If you can only use a browser, the operator can enable the web portal (see the reduced-security note in the README first — the browser is the weakest client).
Building the app yourself (Linux, Windows, Android, or the browser portal) is covered in INSTALL.md.
On first launch you'll enter:
chat.example.org:7420), as given to you by the operator —
the field starts empty, because DarkChan has no default server: someone
has to run one and give you its address,., _ or -. The app
suggests one from your display name as you type it
("elodie.martin"); keep it or type your own. If it is already taken, the
app fills in the next one ("elodie.martin2") — tap Create account again.
Capitals do not make a different account — "Nocteus", "NOCTEUS" and
"nocteus" all sign in to the account nocteus. (Left the
display name empty? Then the username, as you typed it, is your display
name.)Let your password manager choose it. On Android with Google Password Manager, tap the Password field while creating an account: the keyboard offers Suggest strong password. Accept it, and Google fills both password fields and saves the password for you (type your username first, or Google asks for it). In the browser portal, Chrome and other browsers offer the same in the password field once "Create account" has shown "Confirm password". Or tap Suggest password on the card for seven made-up words — easier to write down, filled in both fields.
Pasting (the address someone sent you, for example): on a phone, press and hold the field for about half a second, then lift — the clipboard is pasted into it. On a computer, Ctrl+V.
Password managers. On Android 8 and later, the app
works with the password manager set as the phone's autofill service
(Google Password Manager, Bitwarden, 1Password, KeePassDX…; Settings →
Passwords & accounts, or search the system settings for "autofill").
After your first successful sign-in it offers to save
the login; next time, tap the Username or Password field and pick the
saved entry (with Google's service and a keyboard such as SwiftKey or
Gboard, the entries appear as chips above the keyboard). The saved
username reads you@chat.example.org:7420, because one entry
restores the server address too. An entry named
recovery · you@… is your recovery key
(§6), not a password: the sign-in screen never uses it as one. Picking
it there fills your username and keeps the key; enter your password, and
your history is restored once you are signed in. In the browser portal,
your browser offers to save the password after you register or sign in.
On the desktop, or on Android 7, "Remember password" is what remains —
it keeps the password on this device only, and is less safe than a
password manager.
Sign in automatically. Tick it on the sign-in card, and next time the app starts it signs you in on its own with the details it remembers. The box needs the remembered password, so ticking it ticks the two "Remember" boxes too. Log out pauses it: after a Log out the app waits on the sign-in card until you sign in by hand once, and then it signs in automatically again. In the browser portal the same box appears in browsers that can hand a saved password back to the page silently (Chrome, Edge and the other Chromium browsers; not Firefox or Safari). It uses the password your browser saved, never one stored by the portal, and it needs "Trust this browser". Sign out pauses it there too. On a phone, the sign-in card and a conversation open without the keyboard. Tap a field or the message box when you want to type.
Tap Create an account to switch the card to a new account, fill it in, then Create account. Your account is created in a pending state: you can't sign in until an admin approves it. This is normal — ask whoever runs the server to approve you, then sign in.
Stuck on "Connecting…"? After 15 seconds without an answer the card says why ("no answer from the server…", "the server refused the connection…") and tries again. After three tries that never reached the server it stops and returns to the sign-in card with "Can't reach the server: …" — check the address and port, then sign in again. "No answer" almost always means a wrong address or port, a server that is down, something other than a DarkChan server at that address, or a network (a workplace or public Wi-Fi, sometimes a mobile carrier) that blocks the port — try another network, or ask the operator. Once you have been signed in, a dropped connection is retried for as long as the app is open: that is the server restarting or your network changing, and it comes back by itself. If the server is refusing sign-ins for a while (it limits how often one address may sign in), the app says "The server is limiting sign-ins. Trying again in N s…" and waits about a minute before the next try, instead of signing you out.
Coming back after a long time away. A device that was off for days, or a fresh install, fetches everything it missed in one go when it signs in. That can take a moment on a busy account; the messages fill in while the connection stays up.
No network (airplane mode). On Android the app notices when the phone has no network at all, stops trying, and shows "No network — waiting for one…" (under New chat on the main screen, above the messages in a conversation); it reconnects as soon as a network comes back. Those minutes do not count toward the three tries above. While the server is merely unreachable the same places say "Reconnecting…".
DarkChan asks for as little as it can, and asks at the moment it needs it rather than at launch:
It does not ask for your camera, contacts, location or files. Attaching a photo or video goes through Android's own picker or camera app, which hands DarkChan only the one file you chose.
DarkChan encrypts everything end-to-end, but on its own that does not stop a malicious server operator from handing you a fake key for a contact and reading your messages. The defence is to compare safety numbers.
Open a chat, go to the contact's safety number screen, and you'll see a long number (and the app will tell you whether the contact is verified). Compare those digits with your contact in person, or over another channel you trust (a phone call, a different app). If they match, choose Mark verified. If they don't match — stop, and check with your contact; someone may be tampering.
Unverified contacts are labelled "Not verified — this contact could be impersonated." Take that seriously; verify the people who matter. Group conversations have a whole-group safety number that works the same way.
If the app warns that the server's identity key has changed, do not just continue. That warning means the server is presenting a different identity than the one your app remembers (it pinned it the first time you connected). It is either a legitimate server change the operator can confirm, or an attack — ask the operator before proceeding.
Once you're in: private 1:1 chats and group chats, public channels you can browse and join, image / file / voice attachments (with an image gallery and download), emoji, stickers and reactions, reply / edit / delete, message search, profile pictures, presence and read receipts (each with a privacy toggle), and link previews. Everything is encrypted; the server stores only ciphertext.
The main screen. Along the top: the magnifier opens Search, the gear Settings, and the door-and-arrow logs you out. Below it, type a name and press New chat for a 1:1 chat; the + beside it opens New group…, Browse channels… and — for account admins — Approvals…. Admins see a red count on the + when accounts are waiting for approval; it refreshes about once a minute while the main screen is open.
Leaving the app on Android. The phone's Back button on the main screen (or the sign-in screen) puts DarkChan in the background like any other app: you stay signed in and messages keep arriving as notifications. To sign out, use the door-and-arrow button. Swiping DarkChan away from the recent-apps list also keeps notifications coming: it restarts in the background within a few seconds (reliably when DarkChan is exempt from battery optimisation, see section 8).
Links, pictures and videos. Tapping a link opens it in your browser. Pictures show in the conversation by themselves: a small preview the sender made, or — for a picture sent from the web portal or an older app, up to 8 MiB — the picture itself, downloaded and decrypted on your device. Bigger ones show View. A video shows its first frame (when the sender's app could make one) with a play button: tapping it downloads the video and opens it in your phone's video player. Videos do not play inside DarkChan itself.
Voice messages. Tap a voice message to play it. While it plays, the play button turns into a square, the part of the waveform already heard stays bright while the rest dims, and the time reads played / length ("0:03 / 0:07"). Tap it again to stop. The web portal shows the same.
Joining a channel. Browse channels… lists the server's public channels by their listing name: the name its admins gave it when it was created as public, or later in its Members screen. The listing name is the one thing about a channel the server can read. Everything said in the channel stays encrypted. A channel without one shows as "Channel" and a short code. Join sends a request. When one waits, the channel's admins and moderators see "1 join request to review" on its row; they approve or refuse it in the channel's Members screen, and you are in.
On Android, the camera button in the message box offers Photo or Video: it opens your camera, and what you shoot is saved privately to DarkChan — not to your phone's gallery — then sent as a normal encrypted attachment.
Emoji categories. Under the emoji search box, a row of buttons narrows the list: All, then smileys, people and hands, hearts and symbols, animals and nature, food, and activities and things (each shown by a typical emoji; a category the emoji sets do not have is left out). Typing in the search box looks through every category at once. The panel shows four rows at a time (fewer only on a screen too short for them); the bar down its right edge shows where you are in the list — drag it, or press anywhere on it, to jump there. The panel stays open after you pick an emoji, so you can add several; the ones you just used join the recent row at the start of All the next time you open it (adding them while it is open would shift the whole grid under your finger). Closing the panel with the emoji button again brings the phone's keyboard back only if it was showing when you opened the panel; tap the message box to bring it up.
Stickers. The emoji button opens a panel with two
tabs, Emoji and Stickers. Stickers are
bigger pictures, and clicking one sends it straight away — a
sticker is a whole message, not something you add to what you are
typing, so there is nothing to press afterwards. They are supplied by
whoever runs your server: if that person has not made a sticker pack,
the tab says "No sticker pack on this server", which is not a fault on
your end. The tab is not offered when you are picking a reaction to
someone else's message, because a reaction is always an emoji. If
someone sends you a sticker your copy of the pack does not have yet, you
see its short name as plain text (like :party_cat:) until
the pack catches up.
Writing a message. Enter sends; Shift+Enter starts a new line. With a keyboard, ↑ / ↓ move the cursor one line up or down (keeping its column; from the first line ↑ goes to the very start, from the last ↓ to the very end), and Home / End jump to the start / end of the whole message. Hold Shift with any of those keys to select, or drag across the text with the mouse (Shift+click extends a selection). Ctrl+A selects everything; Ctrl+C / Ctrl+X copy / cut the selection (or the whole message when nothing is selected); typing, pasting, Backspace or Delete replace what is selected.
Copying and message actions. On a phone, press and hold a message for about half a second: a bar opens above it, while your finger is still down, with Copy, Reply, React, 👍, and — where you are allowed — Edit (your own text messages) and Delete. Tap outside the bar, scroll, or press Back to close it. 👍 is a one-tap reaction: tap it again to take it back. On a computer, right-click a message to copy it (right-clicking a link inside a message still copies just the link), and the small buttons beside each message do the rest. In the web client, the ⧉ button beside a message copies it.
Writing to someone privately from a group or channel. On someone else's message in a group or channel, Message (in the phone's press-and-hold bar), the @ button beside the message on a computer, or the speech-bubble button in the web client opens your direct conversation with that person, or starts one if you have none. To start one from the main screen, type their username and press New chat: that always opens your direct conversation with them, never a group or channel the two of you happen to share. In the web portal, New DM does the same: it opens the conversation you already have with that person instead of making another.
What gets copied: a message's text (for a reply, the reply itself, not the quoted message above it), or an attachment's file name. Stickers and voice messages have nothing to copy, so Copy is not offered for them.
Formatting a message. Messages understand a small, safe part of Markdown, the same on the phone, the computer and the web portal:
| Type | Shows as |
|---|---|
**bold**, *italic*,
`code` |
bold, italic, code |
~~struck~~ |
|
# Title, ## Subtitle,
### … |
a heading, slightly larger (a # needs a
space after it) |
https://… pasted as is, or
[text](https://…) |
a link |
- item, 1. item, > quote,
``` fenced code |
a list, a quote, a code block |
a fence of four or more backticks (````) |
a code block that can contain a ``` line; it ends at a
line of at least as many backticks |
~~~ fenced code (three or more tildes) |
a code block, like ```; it ends only at a line of at
least as many tildes, so it can contain a ``` line (and a
backtick fence can contain ~~~). ~~struck~~ at
the start of a line is still struck: a fence needs three tildes |
\* |
a literal * — a backslash keeps any symbol as
typed |
| a table (rows of cells separated by pipes) | a table, everywhere — sized to its content; a table wider than the message scrolls sideways (drag it, or its scrollbar, which stays at the bottom of the screen while the table is taller than it) |
#general with no space is not a heading: it is a
channel reference. When it names a group or channel you
are in, it shows as a link — tap it to open that conversation; a name
you are not in stays plain text. @name is highlighted, and
@you stands out more.
One-line previews. Where a message is shown on a
single line — the last message under a conversation in the list, the
quoted message at the top of a reply, the "Replying to …" bar above the
composer, and search results — the formatting is kept but squeezed onto
that line: bold, italic, code, struck text and link colours
stay, emoji show as pictures, headings are bold, quotes are dimmed, list
bullets and heading # are dropped, a table's cells are
joined with |, and line breaks become spaces. A long
message ends with … where the line runs out; the formatting
symbols themselves are never what gets cut off. Links in a preview are
coloured but not clickable — open the message to follow one.
Notifications (Android and the web portal) cannot show formatting at
all, so they show the plain text: the same words without the
**, # or -.
Pictures are never loaded from a link (that would tell the linked
site who reads your messages), and only
http/https links are clickable. A link
whose text is not its address —
[My bank](https://somewhere.else) — tells you where it
really goes before opening: in the app the first tap shows "Link goes to
somewhere.else — tap again to open"; in the browser, hover to see the
address. A pasted address opens straight away.
Copying part of a message. On a phone, press and hold a word in a message: it is selected, with a handle at each end and a small bar — Copy, All (the whole message) and ⋯ (the message actions above). Drag a handle to take more or less. On a computer, drag across the text with the mouse, double-click a word or triple-click the message, then use the bar or Ctrl+C. Holding a message beside its text (its padding, its time) still opens the actions bar instead. A tap elsewhere, Escape/Back or leaving the chat clears the selection.
A selection stays inside one message. What is copied is the text as
you see it: Markdown symbols such as ** are left out, and
an emoji copies as its :name:, which shows as the emoji
again when pasted into DarkChan. On a computer, pressing on a message's
text now selects rather than scrolls — scroll with the wheel, or drag
beside the text.
Swipe to reply. Drag a message to the right: it follows your finger and a ↩︎ appears beside it, turning blue once you have dragged far enough. Let go there and you are replying to that message; let go sooner and it slides back with nothing done. A swipe that starts mostly up-or-down scrolls instead, and one that starts sideways never scrolls — so a slightly crooked swipe still does what you meant. With a mouse, hold the button and drag the same way.
Holding a message never pastes into the message box — to paste, hold the box itself (see "Pasting" above).
Themes. Settings → Theme steps through the themes in alphabetical order: Dark, High contrast (white on black with a yellow accent), Light, Lightroom (charcoal greys with a blue accent, after Adobe Lightroom — the default), Nord (cool blue-greys), OLED black (a true-black background, kinder to OLED phone screens) and Sepia (warm paper, brown ink). The change applies at once and is remembered on this device. Every theme keeps text readable against what it sits on (at least the WCAG AA 4.5:1 ratio). An install that had never chosen a theme (it was on Dark, the old default) opens in Lightroom; pick Dark again to keep it. The web portal has the same themes, in the same order and with the same default, under Settings → Theme → Change, plus System (light/dark): its original look, which follows your computer's light or dark setting. The choice is remembered by that browser, so even the sign-in page uses it.
Emoji style. Settings → Emoji style
switches between DarkChan (the server's own pictures,
the default) and Noto (Google's emoji, about 330 of
them, shipped with the app). It only changes how emoji look on YOUR
screen: the other person sees them in their own chosen style. An emoji
only one style has is always shown from that style, so nothing turns
into :text: because of the setting.
Quick reaction. The one-tap reaction button (👍 at first) can be any of 👍, heart, laugh, wow, fire, party or check: Settings → Quick reaction steps through them, on the phone, the computer and in the web portal's Settings. Each choice exists in both emoji styles. The setting is per device; the people you react to see the emoji itself.
Presence. People you share a conversation with see when you're connected, and a rough "last seen" once you're not. If you'd rather not broadcast that, turn Settings → Share when I'm online off: the server then publishes nothing about you — no online marker, no last-seen — and the change takes effect straight away, not at your next login. You still see other people's presence; the switch governs what you send out, not what you receive.
Disappearing messages. In a 1:1 chat the Vanish button in the header sets how long messages are kept — off, 7 days, 30 days, 90 days or a year. Either of you can set it, and it applies to the whole conversation. When a message reaches that age it is deleted from the server and from your own device, so it stops appearing in your history. Groups and channels have the same setting on their info screen, where an admin or moderator sets it.
Two honest limits. It cannot reach the other person's device: if they are running an older version, or have saved a copy elsewhere, that copy is theirs and out of your control — this is a tidy-up, not a guarantee against someone who wants to keep what you sent them. And a screenshot was never yours to delete. Also note the server operator may set a global default that trims the server's own storage; that one does not delete your local copies.
Search. The search screen looks through the messages, attachment names and conversations your device is holding, updating as you type. Nothing about what you type leaves the phone or PC.
It also searches older messages your device tidied away. To keep memory sane your device only keeps the most recent messages of a conversation loaded, but the ones it sets aside stay searchable — locally, instantly, and without asking the server for anything. You should rarely notice the difference.
There is still history even that cannot reach: messages set aside before this version, messages tidied away on a DIFFERENT device of yours, or very old ones pushed out to keep the set-aside store bounded. For those, use Search older messages… underneath the results. That fetches your older messages back from the server, still encrypted, and searches them here on your device. It shows what it is doing and you can Stop it at any moment, and it tells you when it ran out of time or hit its limit rather than pretending it searched everything.
Two honest limits. Disappearing messages and deleting a message remove it from the set-aside store too — if it was meant to be gone, search will not quietly bring it back. And direct messages are different: they are protected so that even your own device cannot re-read old ones once they have been tidied away, so "Search older messages…" cannot cover a 1:1 chat. It says so on screen rather than silently finding nothing.
Three things to expect from it. It is slower than the instant search, because it is genuinely pulling history over the network. What it finds is shown, not kept — that is deliberate, since re-saving it would undo the very trimming that made your device tidy. And it cannot search 1:1 direct messages: those are protected so that even you cannot re-read the encrypted copy on the server once your device has moved on, which is the same property that stops anyone else reading it later. Group and channel history searches fine. History the operator has already deleted under a retention policy is gone for everyone and no search will bring it back.
Pictures, voice and emoji in the web portal. The browser shows emoji as pictures (the server's set, or Noto — ⚙ Settings → Emoji style), shows an image attachment in the conversation (small ones by themselves, larger ones after View; Download still saves the file), and plays a voice message with ▶. Click a picture to see it full size: it opens over the whole window, shrunk only if it is bigger than the window. If it was shrunk, click it again to see it at 100 % and scroll around it; click again to fit it back. Esc, a click beside the picture, the ✕ button or the browser's (or the phone's) Back button closes it. Everything is decrypted and checked in the browser before it is shown or played, as in the app. Videos and other files are still download-only there.
Message actions, emoji and voice in the web portal. Every message in a conversation you can write to — direct messages, groups and channels alike — has React (pick an emoji), a quick 👍 (or the quick reaction you chose in Settings), Reply, and on your own text Edit; Delete for everyone is on your own messages, and in a group or channel you administer or moderate, on everyone's. On a phone or tablet, swipe a message to the right to reply. The composer's emoji button opens the same picker (search by name: "cat", "heart", …, or narrow it with the category buttons under the search box, as in the app), which stays open so you can add several — close it with ✕ or Esc — and the microphone records a voice message: tap it, speak, tap ■ to send (Esc cancels; at most 5 minutes). The browser asks for the microphone the first time; if you refuse, it says so and nothing is recorded. The message box takes several lines: Enter sends, Shift+Enter starts a new line (for lists, code blocks and tables), and the box grows as you type. A conversation opens at its newest message and follows new ones as they arrive. Scroll up to read older ones and it stays where you are; a round ↓ button then appears in the bottom-right corner of the conversation and takes you back to the newest message. It disappears once you are there. Delete in a conversation's header removes it from this browser's list only, nothing on the server or your other devices. It comes back as soon as anyone writes in it, you included from another device; a public channel can also be reopened at once from Browse channels… (Open).
Names in the web portal. The server never knows anyone's display name (it only sees encrypted messages), so names travel inside conversations: the portal sends your display name and status, encrypted, into each conversation you open or write in (once per sign-in), and remembers every name it has seen in this browser. Someone who has never written anywhere you can read still shows as a short code until they do.
One name on all your devices. Your display name and status are the same everywhere: change them in the app's Settings or in the portal's Settings → Save profile, and your other devices take the newest one the next time they receive a message from you in any conversation (each change is sent into your conversations). The web portal no longer replaces the name you chose in the app with your username. If no device has ever chosen a name, your username is used.
In the app, Save profile takes you back to your conversations, which then say "Profile saved." Set avatar… (Settings) and Set group photo… (a group's member screen, admins only) report on the button itself: "Uploading…", then "updated", or why it failed. Any picture your device can open works (PNG, JPEG, WebP, GIF); it is shrunk to 256 px first, so a full-size camera photo is fine.
Search in the web portal. The portal has the same Search button beside Channels, over the same three things: message text, attachment names and conversations. It has no "search older messages" button and does not need one — the browser re-downloads the whole history the server still keeps every few seconds, so it is already searching all of it, direct messages included. What the operator's retention policy has already deleted is gone for everyone, and no search on any client will bring it back.
Notification privacy (Android). By default a notification tells you a message arrived and who from, but not what it says — a lock screen is readable by anyone holding the phone. Settings → Notification preview turns the text on if you would rather see it.
Reply and Mark as read from a notification (Android). A message notification has two buttons. Reply opens a text field in the notification itself: what you type is sent as an ordinary end-to-end encrypted message and appears under the conversation's messages in that notification. Replying also marks the conversation as read on all your devices, as answering in the app does. If you are offline, or the app has to sign in again first, the reply waits and goes out once it is connected; if the phone restarts before that, it is lost, so check the chat when it matters. A reply to a contact whose safety number changed after you verified it is not sent, and the notification says so: open the chat and check the new number first. Mark as read clears the notification and the conversation's unread count on all your devices, as opening the chat does, and sends a read receipt when Send read receipts is on (a reply does the same). Neither button appears on the lock screen: unlock the phone to answer. With previews turned on, notifications show as a conversation (who said what), which also puts DarkChan in Android's Conversations section of the notification shade.
Android Auto. DarkChan can read your messages in the car and, if you allow it, let you answer by voice. It has no screen of its own there: the car shows DarkChan's message notifications, with Read aloud and, with voice replies on, Reply. To turn it on, in Settings → Notifications:
You can tick these in any order and ahead of time, even before your first drive or with the message text still hidden. A row that cannot work yet is drawn dimmed, and while the text is hidden the first one reads Android Auto (needs message text): it starts working as soon as you show the text.
What the car reads: a text message or a reply as written; a picture as "Photo", a video as "Video", another file as "File: " and its name; a voice note as "Voice message, 12 seconds" (it is not played or transcribed); a sticker by its name ("Sticker: thumbs up"); a link by its card's title. In a 1:1 conversation whose safety number you have not verified, each message starts with "Unverified contact:", and if the number changed since you verified it, with "Safety number changed." — the car cannot show the shield the chat header draws, so it says it. (The same words appear in the phone's notification while Android Auto is on.) Groups and channels have no per-member verification, so they get neither.
These choices belong to the account you are signed in with: another account on the same phone starts with them off. Conversations you have muted, or set to Notifications off, stay silent in the car too.
What it costs in privacy — read this before turning it on. DarkChan's messages are end-to-end encrypted up to your phone. In the car, Google takes over: Android Auto sends your notifications to Google for features such as reading them aloud (its own settings say so), Google's Assistant reads them to you, and a voice reply is dictated through Google's speech recognition. DarkChan itself still talks to no Google server; Android Auto and the Assistant, which you installed and set up, do. If that is not acceptable for a conversation, mute it, or leave Android Auto off.
Good to know:
Who is muted. A group or channel admin or moderator
can mute a member: their messages are refused by the
server, so nothing they send arrives. The member list on the group's
info screen marks anyone muted — alice (mod) (muted) — and
in the web portal's Manage… panel the same row reads
· muted with the button offering Unmute.
This is worth knowing because until 2026-09-11 a mute was invisible: it
was enforced silently, so a muted member discovered it only by being
ignored, and the moderator who set it had nothing showing it was still
in force. Mute stops someone sending; it does not stop
them reading, and it is not the same as muting a conversation's
notifications for yourself.
Be clear-eyed about this — it's the honest core of the design (docs/THREAT_MODEL.md):
Your account's identity key is stored on the server encrypted under your password — the server cannot open it — and each of your devices keeps its own copy, also under your password. That is what lets a new phone sign in with just your username and password, and what lets you change your password (Settings → Change password) without your contacts noticing anything.
If you forget the password, the operator cannot recover your account or read your messages for you — that's the whole point, and there is no "reset password" on the server side. You would start over with a new account, and messages encrypted to your old keys stay unreadable. Keep your password safe, ideally in a password manager (§2).
Forgot the password, but have your recovery key (§"Backups and your recovery key" below)? On the sign-in card, fill in the server and username, tap Forgot password?, enter the recovery key and a new password twice. You keep everything: the same account, contacts and groups, no warning for anyone, and your history comes back from your backup. Your other devices then ask for the new password, and once for the old one (or link themselves again).
Lost both the password and the recovery key? Your
identity is gone — nobody, the operator included, can open what it
protected. The operator can still give you your account
back: they run reset-user and give you a reset
code. Tap Forgot password?, type the code
where the recovery key goes, and choose a new password. You keep your
username, but with new keys: your old devices are signed out, your
contacts see that your safety number changed, every group and channel
has to re-admit you (an admin or moderator approves
"account reset" in its approvals list), and your old direct-message
history stays unreadable.
Have an email address on your account (Settings → Email…, if the server sends email): type the address (on Android 8 and later, tapping the field also offers the addresses your phone's autofill service knows) and your password, then the six-digit code it receives. Then you can type the address instead of your username on the sign-in card, and — if one day you lose both your password and your recovery key — tap Forgot password? → Email me a reset code. The code works 24 hours later, and meanwhile every device you are signed in on says a reset was requested, with a button to cancel it: if someone got into your mailbox, you have a day to stop them. Typed in the same screen with a new password, the code gives your account back exactly like a reset code from the operator (new keys, groups re-admit you). Changing or removing the address asks for your password and tells the old address. The server's operator can see your address.
In the web portal, "Trust this browser" on the sign-in card decides what the browser keeps. Ticked (your own computer): your conversations stay in the browser, encrypted so they open only after you sign in. Unticked (the default, for a shared computer): they live only in the open tab and are gone when it closes; only your password-protected device key stays, so the next sign-in is the same device. The portal's "Forgot password?" takes a reset code or an emailed code; a recovery key resets your password in the app. "Create account" first asks for the password a second time (Confirm password); "Suggest a password" fills in seven made-up words in both fields.
A contact's safety number changed. The chat header says "identity CHANGED — check" when someone you had verified now has new keys — after a reset like the one above, or because someone is impersonating them. Nothing you write goes out until you open the safety number (tap the header) and mark them verified again, or unverified; ask them, outside the app, first.
After you change your password, your other devices still hold their keys under the old one. Sign in on them with the new password: the app then shows "Password changed" and asks, once, for your previous password, which keeps that device exactly as it was. If you no longer remember it, choose Link this device again: the device keeps its message history and replaces itself in your account (it shows up as a new device in Settings → Devices, and the old entry is removed), and its direct-message sessions are set up again automatically.
When you create your account, the app makes a recovery
key — 56 characters in 14 groups of four — and shows it once:
save it in your password manager (Android: Save in password
manager, stored as recovery · you@server:port; if
no save prompt appears, the manager already holds that key; desktop:
Copy, then paste it into yours), or write it down. To
confirm, the app asks you to type its last group.
Choose Later and it asks again at your next sign-in.
Nobody can give you this key back — not the operator either.
With it, each of your devices backs up your conversations and group keys to the server once a day (and on Android when the app goes to the background, if the last backup is more than 6 hours old), encrypted with the recovery key: the server stores them and cannot read them. It sees how big they are and when they were made.
Settings → Backups & recovery key shows when this device last backed up and lets you:
On a new phone, sign in with your username and password as usual. If none of your other devices is online to hand the key over, the app opens this screen: type the recovery key (letters in any case; spaces and dashes don't matter, and a typo is caught before anything is downloaded), and your history is restored, direct messages included if they were backed up — which matters, because direct messages are otherwise never copied to a device added later (§7). If another device of yours is online when you sign in, it gives the new one the key by itself.
What a backup does not hold: pictures and files (they come back for as long as the server keeps them), and anything newer than the last backup that no other device of yours still has.
Settings → Delete my account… (the same in the web portal's ⚙ Settings). The screen says what goes, asks for your password again, and the red button does it. Once the server confirms:
There is no undo and no grace period. Your username becomes free; if you (or anyone) registers it again, that is a new account with new keys, and your former contacts are warned that the key changed.
If you are the server's only admin it refuses — make
someone else admin first, or nobody could approve new accounts again.
Lost your password or your phone? Ask the operator: they can delete the
account for you (darkchan-admin delete-user, OPERATIONS.md
§3).
You can use one account on several devices (say your phone and your laptop). Sign in on the new device with the same username and password — it sets itself up automatically, and your existing device shares your chat history with it. Messages you send show up on all your devices.
This works between any of the clients: an account you create in the web portal opens on the desktop or Android with the same password, and an account created on the desktop opens in a browser — the browser simply adds itself as another device the first time you sign in there.
Two things to know:
darkchan-admin device-restore). New devices are also
limited to a few a minute from one network.The app is not tied to a particular server: sign out and enter a different address, and it connects there instead. Each server keeps its own account, message history and emoji pack on your device, so nothing bleeds between them — even if you use the same username on both. Once you've used two or more, a Recent servers list appears above the Server field so you can pick instead of retyping. You can still type any address you like.
Signing in to a second server means creating (or already having) an account there: accounts do not transfer between servers, and neither do contacts, groups or history.
Android aggressively stops background apps, so to get message notifications while DarkChan is closed, install the small ntfy app once — it holds a single battery-friendly connection to your community's own push server and wakes DarkChan when something arrives. No Google services are involved, and the wake-up carries no message content (your messages are only ever decrypted on your phone).
io.heckel.ntfy.https://chat.example.org:7460).push on.
push none means ntfy is not installed; reg…
means ntfy answered but your DarkChan server has not been told yet — if
that persists, the phone is having trouble reaching your DarkChan
server.With screenshots: docs/NTFY_SETUP.md walks through the same three steps with pictures of each screen, and covers what to check when something does not work. 5. If notifications still lag: tap the Battery row in DarkChan's settings, pick DarkChan in the list Android shows and choose "Don't optimize", and do the same for ntfy — some phones (Xiaomi, Huawei, Oppo…) additionally need an "autostart" toggle in their own settings; see https://dontkillmyapp.com for your vendor.
DarkChan → Settings shows a live status line —
Background: … (shortened to Bg: … on a narrow
screen). It is there so the app can admit when the phone has stopped it
from working, rather than silently going quiet:
| It says | Meaning | What to do |
|---|---|---|
push on |
ntfy is connected and your server knows where to reach you | nothing — this is the working state |
push reg… |
ntfy gave us an endpoint but your DarkChan server has not recorded it | normal for a moment after signing in; if it stays, the phone is not reaching your DarkChan server — check ntfy's Default server too |
push none |
no distributor installed | install ntfy (step 1 above) — delivery still works, just less reliably |
notif OFF |
you declined the notification permission | Android Settings → Apps → DarkChan → Notifications |
vault off |
the app cannot restore its session after a reboot | sign in again; if it persists, report it |
Battery: optimized |
Android may suspend the app | tap that row and allow background use |
Nothing about your messages travels in a wake-up: it is an empty "you have new data" ping. Your phone then connects, syncs and decrypts locally, and the notification you see was written by your own device — which is also why the sender's name shows up even though the push server never knew it.
Without ntfy, DarkChan still delivers: it keeps its own connection while backgrounded when the system allows it, and always catches up the moment you open the app.
The left bar groups your world like Discord servers: Home (the "@" icon) holds your direct messages and private groups; each instance below it holds that community's channels, grouped into categories. Hover an icon for its name (on Android, hold it — a tap just opens it, and lifting your finger after the name has shown does not); click to enter; right-click to mute it on a computer (its unread badge disappears until you unmute). Unread counts appear on the icons — red once someone mentions you.
Joining: someone shares an invite — a
darkchan://…/join/… link, its QR code, or just the code.
Click + in the bar, paste it, Join. Default channels
of the instance request access automatically; an admin approves you
(access to a channel is always cryptographic — an approval re-seals the
key to your devices). Leaving is on the instance view; open instances
(the whole server community) cannot be left.
Instance admins get Manage…: category lists, member roles, kick/ban, and invite revocation. Note that instance names, categories, memberships and avatars are visible to the server operator — your messages never are.
In the web portal the same bar sits on the left:
Home, your instances, and + to join from a pasted link
or code (an invite handed out as
https://<server>/#join/<code> opens that card
for you after you sign in). An instance lists its joined channels by
category, with Browse channels… to find more and
Instance info… for its description, a one-time invite
link to share, and Leave. In Browse channels… a channel
you have not joined shows as "Channel" and a short code: its name is
end-to-end encrypted, so only its members can read it, and you see it
once you are let in. A channel you are already in shows its name, with
Open. If you administer the instance, that same screen
edits the category list and lists the members — role, kick, ban, unban —
and the outstanding invites, with Revoke; a channel's category and its
default-channel flag are on the channel's own Manage
screen.
Unread counts appear on the bar and on conversation rows (red once someone @-mentions you) and in the browser tab title; right-click an instance icon to mute it. The portal has no background connection — it notices new messages when its regular refresh runs, so leave the tab open to be told about them. Desktop notifications are off until you turn them on in Settings (the gear next to Refresh); they are built from messages this browser decrypted itself and show only who and where unless you also turn on the message preview.