Skip to content

Lightning 0.6.0

Choose a tag to compare

@Mizerd Mizerd released this 12 Aug 07:22
· 3044 commits to main since this release

Lightning 0.6.0 — threads, E2EE recovery, and smooth scrolling.

Timeline scrolling. The discrete-wheel path now runs a continuous-velocity motion engine in C++ (exponential approach with a bounded settle speed) instead of restarting a fixed 140 ms animation per notch — the confirmed cause of chunky movement inside long wrapped messages. Very fast keeps its distance; touchpad pixel scrolling, reversal, bounds, pagination, Jump to latest, reply navigation, and per-room anchors are unchanged. Home/End are instant programmatic jumps.

Matrix threads (SDK-backed). Thread timelines are matrix-sdk-ui TimelineFocus::Thread timelines flowing through the same generation-isolated diff pipeline as rooms. The thread panel pins the root above the reply list with loading/failed/empty states; thread roots in the room timeline show a clickable summary (server-aggregated reply count, latest reply, conservative receipt-based unread dot). Composing sends real m.thread relations through the SDK (rich replies within threads via the thread timeline's send_reply; encrypted rooms use the normal SDK encryption path; local echoes, failure and Retry ride the SDK send queue). A per-room Threads view lists threads via the SDK ThreadListService; follow/unfollow uses MSC4306 server-side thread subscriptions where the homeserver supports them; reading a thread sends a deduplicated THREADED receipt, never a room-wide one. The thread panel has its own isolated wheel-motion engine.

E2EE recovery and security. A read-only Security status card mirrors sanitized SDK state (device/identity trust, cross-signing keys, backup, recovery, secret storage). The client enables the SDK's AfterDecryptionFailure backup download strategy, so missing room keys are fetched from key backup per unable-to-decrypt event once backup access exists; the SDK's redecryptor applies arriving keys in place without restarts or room switches. Unable-to-decrypt placeholders show a safe reason category, a manual bounded Retry decryption, and a Security settings jump. A read-only Sessions card lists the account's devices with honest trust labels; SAS verification (both directions, explicit confirmation) is unchanged. Recovery accepts a recovery key or passphrase (masked, wiped after dispatch, never logged). Cryptography remains entirely inside the Matrix Rust SDK — no custom crypto, no store resets, no secrets crossing into QML.

Notifications and mentions. Native freedesktop notifications with three privacy modes (default: sender only; undecryptable events always show a generic placeholder), local per-room All/Mentions only/Mute modes (explicitly this-device-only), active-room suppression, invite and verification-request notifications, and click-through navigation to the room/event/thread. Mention highlighting uses the event's m.mentions metadata, never substring matching.

Honest limitations: thread-composer attachments, remote session sign-out (UIA), new cross-signing/backup setup, server push rules, QR verification, and notification sounds are not implemented in this release. Live interoperability of threads and E2EE recovery against another client was not re-verified as part of this automated release pass.

Matrix SDK versions are unchanged: matrix-sdk 0.18.0, matrix-sdk-ui 0.18.0.


Mirrored from the canonical release: https://gitlab.smetonis.net/Mizerd/lightning/-/releases/v0.6.0 — installation packages are hosted on GitLab:
(source-only release)