https://bugs.kde.org/show_bug.cgi?id=527918
Bug ID: 527918
Summary: Call support (MatrixRTC)
Classification: Applications
Product: NeoChat
Version First unspecified
Reported In:
Platform: postmarketOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
As of now NeoChat cannot place or answer calls, and calls from Element X /
Element Call are hidden from the timeline completely i.e. a missed call is
invisible.
Are there any plans/road map for adding call support: 1:1 and group calls
including E2EE.
I found earlier efforts but they were all stopped without a proper reason
- !194 Draft: Calls
- !366 Draft: Add voip call functionality
- !2018 Draft: Video call support
- !2334 Draft: Implement call ringing
I would be up for contributing, but its quite a bit of new code so one would
need to split it something like:
0. Notify about incoming calls even without call support: recognise the ring
event (rtc.notification), show "X is calling you" (category call.incoming,
ringtone) until it expires or is declined, then "Missed call from X".
1. Show call events in the timeline (rtc.notification, rtc.decline, call.member
joined/left)
2. libQuotient: receive to-device events, send encrypted custom to-device
events (needed for call encryption keys)
3. Call membership model (Element's current call.member format, delayed leave
via MSC4140)
4. Focus discovery and LiveKit token (rtc_foci / rtc/transports, OpenID ->
lk-jwt-service)
5. Optional (at build time) LiveKit media backend, without LiveKit SDK call
features are hidden
6. Call UI and ringing, behind a flag?
Im really interested in your optinions about this.
--
You are receiving this mail because:
You are watching all bug changes.
