- LiveKit call E2EE: CallE2EEManager exchanges encryption keys via Matrix
to-device events (m.rtc.encryption_keys) for interop with Element X
- Olm bootstrapped in index.html before Flutter init; main.dart logs result
- Encrypted messages shown with lock icon and informative fallback text
- Profile screen: key restore dialog + security setup (cross-signing/backup)
- Jitsi feature: welcome screen (public, no login), conference tab, full-screen
embed via JitsiMeetExternalAPI, JitsiLink parser for all common link formats
- Help tab: expandable cards for encryption, video calls, account management
- Web security model: no session persistence — device ID only across visits
- Media auth: MSC3916 authenticated endpoint for avatars (Synapse 1.120+)
- Router: welcome route as public landing page; jitsi route as public
- Manifest/index.html: M8Chat branding, dark theme colours
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Element X stays connected because it sees the state event clear while
we're still in the LiveKit room. Reversed the order: disconnect from
LiveKit first (remote party sees us leave), then clear the state event.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
When starting a call, the app now sends org.matrix.msc3401.call.member
state event to the Matrix room with LiveKit foci info. This is what
Element X listens for to show incoming call notifications.
On disconnect, the state event is cleared (empty memberships) so
Element X knows the call has ended.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- lk-jwt-service returns {jwt: '...', url: '...'} not {token: '...'}
Now reads both 'jwt' and 'token' fields for compatibility
- Server nginx: added proxy_hide_header to strip upstream CORS headers
preventing duplicate Access-Control-Allow-Origin (browser rejects)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Calls:
- JWT fetch now uses correct MSC4143 flow: get OpenID token from
Synapse, then POST to /_matrix/livekit/jwt/sfu/get (was using
GET with Bearer token to wrong path — returned 301→404)
- Error messages now visible for 3 seconds before popping screen
(was flashing away instantly — user couldn't see failure reason)
- Voice vs video calls differentiated via ?video=0/1 query param
- Debug logging added to JWT flow for troubleshooting
Messages:
- Chat timeline now shows newest at bottom (standard behaviour).
Was reversed twice: SDK returns newest-first, code reversed to
oldest-first, then ListView(reverse:true) put oldest at bottom.
Removed the extra .reversed — newest-first + reverse:true = correct.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
