ZEKORO / changes zekoro.one What changed, newest first. The how-it-works is in structure.txt, answers to the last security review are in qna.txt. ──────────────────────────────────────────────────────────────────────── 2026-11-14 / polish round ──────────────────────────────────────── EDIT AND DELETE MESSAGES Hover (or tap) one of your own messages for Copy, Edit and Delete. An edit is a new sealed message that names the one it replaces, inside the encryption, so the server can't swap one message's text into another or replay an old version over a newer one. Edited messages say "edited". Delete removes the message for everyone, in DMs and in server channels. Moderators with Manage messages can still delete other people's channel messages. STATUSES Online, Idle, Do not disturb and Invisible, under Settings, My profile. Idle also switches on by itself after 5 quiet minutes and never overwrites the status you picked. Invisible looks exactly like offline to everyone else. IMAGE VIEWER Click a photo in a chat to open it: zoom (wheel, buttons, double-click, pinch), drag, rotate, copy, download, open in a new tab, next and previous, and keyboard shortcuts. BACKGROUNDS Settings, Appearance: your own gradient (up to three colours and an angle) or your own image, with a dim slider. They stay on this device and are never uploaded or synced. Choosing a new image replaces and deletes the old one. SETTINGS AND SERVERS, REWORKED Settings has a category sidebar (a list on phones). On wide screens a server shows its members in a panel on the right, with a button to hide it. SMALLER THINGS Faster first paint, better contrast, pinch-zoom allowed, no stray 401 on the login screen, and db.zekoro.one fixed after a certificate mix-up. ──────────────────────────────────────── 2026-09-26 / third review round ──────────────────────────────────────────────────────────────────────── SERVER ONLY ANSWERS CLOUDFLARE zekoro.one and db.zekoro.one refuse connections that don't come through Cloudflare, so nobody can skip its protection by going to the server's address directly. CALL RELAY LOCKED DOWN It can't be pointed at private, local or reserved addresses, can't reach other services on the server, doesn't relay TCP, and keeps no logs. OLD-FORMAT MESSAGES Marked "unverified". Once a chat has had a protected message on your device, any unprotected message after it is refused. YOUR DATA Settings > Your data: download everything we store about you, or delete your account yourself. PRIVACY PAGE Who runs Zekoro and how to reach them (privacy@zekoro.one), why data is processed, your rights, where it's hosted, who processes it, and how long everything is kept. DOCS Synced passkeys added to sharp edges, desktop apps explained, iPhone app marked as no longer updated. ──────────────────────────────────────────────────────────────────────── 2026-09-26 / passkeys ──────────────────────────────────────────────────────────────────────── PASSKEYS Sign in with a passkey instead of your password, from Settings > Security. Where the device supports it, the passkey also unlocks your messages, so there's no password at all. Each passkey shows the device it was created on, where it was last used, which passkey manager holds it, and whether it can unlock messages. Rename or remove them anytime. "Sign in with a passkey" on the login screen, "Unlock with a passkey" on the unlock screen. FACE ID REMOVED The iPhone-only Face ID unlock is gone. Passkeys replace it everywhere. ──────────────────────────────────────────────────────────────────────── 2026-09-26 / second review round ──────────────────────────────────────────────────────────────────────── DATABASE VIEWER MOVED TO db.zekoro.one Its own origin now, so a bug there can't reach the app's stored keys. zekoro.one/db redirects there. It has its own sign-in and sign-out. SERVERS STOP ENCRYPTING TO CHANGED KEYS Like DMs: if someone's key changed since your device first saw it, your channel messages skip them until you accept the new key. MESSAGES CARRY THEIR OWN CONTEXT Every message is sealed with where it belongs, a random id and the send time. Messages moved to another chat or replayed are caught and hidden; a send time that doesn't match gets a warning. HIDE MY IP ADDRESS IN CALLS New setting. Calls and voice channels go through our relay only, so the other side never sees your IP and Google's STUN server isn't contacted. FIXED: THE CALL RELAY NEVER WORKED The relay's address pointed at Cloudflare, which can't carry relay traffic, so calls only connected when a direct path existed. It now has its own direct address (turn.zekoro.one). Also fixed: network details that arrived while a call was still ringing were being thrown away. FIXED: JOINING A SERVER FROM AN INVITE LINK The address bar was left on an old path that 404'd if you reloaded. NEW PAGES zekoro.one/privacy: what's stored, what's visible, who else touches it. features.txt: everything you can do, and what admins can do. Links to both from the sign-in screen and Settings. ──────────────────────────────────────────────────────────────────────── 2026-09-26 / servers round: permissions, settings, voice, /db ──────────────────────────────────────────────────────────────────────── PERMISSIONS Servers have real Discord-style permissions now instead of "the owner does everything". Ten permissions, set on @everyone and on roles, with per-channel overrides (allow / inherit / deny). Every server action checks them. You can only hand out or act on permissions you have yourself, so mods can't promote themselves or kick admins. Private channels are private for real: their messages are only encrypted to people who can see them. Existing servers: @everyone can view, send, join voice and create invites, same defaults as a new Discord server. SERVER SETTINGS Full-screen settings like Discord's, from the gear next to the server name (or the server icon): Overview name, emoji, colour, icon upload/remove, quick stats Roles @everyone + roles, colour, name, every permission as a switch Channels create text/voice channels and categories, rename, move up/down, delete, per-channel permission overrides Members search, change roles, kick Invites custom link, generated links with expiry and max uses, copy / revoke You only see the tabs you have permission for. The old inline forms in the sidebar are gone. Deleting a server now asks you to type its name. Also: invite button next to the gear (makes a 7-day link and copies it), "+" on categories and a gear on channels for quick edits, and you can delete your own messages in a channel (or anyone's with Manage messages). Channels you can't post in show a read-only composer. VOICE CHANNELS Click a voice channel to join. Peer to peer mesh, up to 8 people, sealed setup like 1:1 calls. Everyone in the server sees who's in each channel, with a green ring on whoever is talking and a marker on anyone muted. Bottom-left bar has mute, deafen and disconnect, and stays while you move around the app. New servers come with a "General" voice channel. Drops back in automatically if your connection blips. /db zekoro.one/db: read-only database viewer for admin accounts. Locked sign-in page for everyone else. Overview (users, messages, sessions, recovery code and email adoption, auth-key migration, db size, 30-day signup and message charts) and every table with search, sort, paging and a row detail panel. Secrets are redacted and emails masked (except for the owner); see structure.txt for exactly what's hidden. ──────────────────────────────────────────────────────────────────────── 2026-09-26 / security review round ──────────────────────────────────────────────────────────────────────── Prompted by an outside review. Everything below is live. PASSWORD NO LONGER SENT TO THE SERVER Before: login, signup, password change and reset all sent the raw password, and the server checked it with scrypt. The same password unwraps your private key, so in principle the server could have used it to open your key blob. The old version of structure.txt said the server "never receives your password"; that was wrong for login. Sorry. Now: the browser sends a separate auth key, PBKDF2(password, authSalt, 600k). It is not the key-wrapping key and cannot open the blob. New /prelogin step fetches the auth salt. Old accounts migrate automatically on their next login or unlock (new endpoint /keys/upgrade). KEY WRAPPING 210k -> 600k PBKDF2 ROUNDS New and changed passwords wrap the private key with 600,000 rounds of PBKDF2-SHA-256 (OWASP guidance). Existing 210k blobs are re-wrapped at 600k the next time the password is typed. The iteration count is now stored per account (kdf_iter). Login takes a bit longer on slow phones; that is the point. SAFETY NUMBERS 60-digit number per pair of people, same on both screens, compare it out of band. Open it from the lock badge in a chat or "Verify safety number" on someone's profile. You can mark a contact verified; the badge turns green. Settings now shows your own key fingerprint. KEY CHANGE WARNINGS Your device pins the first key it sees for each person. If it changes: - red banner in the DM, badge says "Key changed" - direct messages and calls are paused until you accept the new key (your draft stays in the box) - in servers, a warning marker next to that member and a one-time notice This is what catches a server swapping keys, or someone taking over an account through a password reset. CALL SETUP IS SEALED The SDP offer and answer (which carry the DTLS fingerprints that protect call audio and video) used to pass through the server in plaintext, which would have let the server sit in the middle of a call. They are now sealed with nacl.box to the other person's pinned key. Unsealed or tampered call setups are refused. DOCS structure.txt rewritten: auth key, 600k, recovery code wrapping, key verification, calls, how group removal works, and a new SHARP EDGES section (no forward secrecy, Cloudflare terminates TLS, the server serves the code that does the encryption, pins are per device, metadata). New: changes.txt (this file) and qna.txt. NOT CHANGED (on purpose, for now) No forward secrecy yet. That needs a ratchet (Signal's double ratchet or similar) and a rework of how history syncs across devices. Documented as a sharp edge instead of pretended away. Recovery codes still wrap at 210k rounds. They are 80 random bits, so the round count is not what protects them. ──────────────────────────────────────────────────────────────────────── Earlier ──────────────────────────────────────────────────────────────────────── Voice and video calls (WebRTC + TURN relay), native iOS call screen, profile popouts, grouped member lists, servers with categories and roles, recovery codes, email-optional signup with code verification, password resets through RSTPSW, moderation tools.