Files
lockbitchat 4000bde857
CodeQL Analysis / Analyze CodeQL (push) Canceled after 0s
Deploy Application / deploy (push) Canceled after 0s
Mirror to Codeberg / mirror (push) Canceled after 0s
Mirror to PrivacyGuides / mirror (push) Canceled after 0s
v6.8.1: the downloads point at desktop 1.0.3
Desktop 1.0.3 fixes video on a call placed after a group call — the two shared
one peer connection, the second call opened a second video section, and the two
H264 profiles collided, so the call carried sound and no picture. It also ships
the STUN and TURN list this client uses, which is what lets a browser and a
desktop agree on a path instead of one of them offering no relay at all.

The version lives in two places on this side (the landing page and the download
grid), and the consistency test also reads the README badge, the changelog and
the cryptography document, so all of them move together.

Riding along: the group status dot now takes its colour from the theme in the
call and group views, which is what the desktop's copy of groupsStore.js was
compared against.

Claude-Session: https://claude.ai/code/session_019RCW2Fm7dkAaU2zeHDksei
2026-09-11 22:58:20 -04:00
..

Documentation

Technical documentation for SecureBit.chat. Start with the project README if you are looking for an overview or a quick start.

Document What it covers
ARCHITECTURE.md How a session is established, verified and torn down, and where each guarantee comes from
CRYPTOGRAPHY.md Key schedule, the Double Ratchet, SAS verification, memory handling
DESCRIPTOR-SBQ2.md The invitation format: wire layout, why it is small, the in-band key exchange, decoder rules
CONFIGURATION.md Deployment, ICE and TURN setup, privacy modes, file transfer policy
CALLS.md Voice and video: codec choices, adaptation, and why each value was picked
API.md Internal interfaces of the WebRTC manager and file transfer system
CONTRIBUTING.md Development workflow and what needs extra review
USE-POLICY.md Terms of use, intended use, and the limits of what the software can protect

Security policy and vulnerability reporting live in SECURITY.md at the repository root, where GitHub expects to find them.

Keeping this accurate

These documents describe the current release and are expected to change with it. Every value quoted here (limits, timeouts, algorithm parameters) is taken from the source rather than restated from memory, so if you change one in code, change it here in the same commit. CONTRIBUTING.md lists which documents are affected by which areas of the code.