ringrtc VS OvenMediaEngine

On the two points you raised: - Panther is the codename given by Google for the Pixel 7 device. - RingRTC is a middleware library providing Signal Messenger applications with video and voice calling services built on top of WebRTC: https://github.com/signalapp/ringrtc

If you did not know, there is also https://github.com/signalapp/ringrtc by the Signal App team, which is written in Rust

Huh, Signal's WebRTC implementation seems to be using Rust implementations of crypto primitives such as AES: example usage, Cargo.toml

Signal is still an improvement over other non-federated messengers in that it's open-source, so you actually can try to improve the situation, although it's notoriously difficult. As an example of more platform support: https://github.com/signalapp/ringrtc/pull/12

signal-cli is an example of a 3rd party client which is tolerated for now: https://github.com/AsamK/signal-cli

The main problem right now is that they don't have enough developers to take care of everything, but it's not specific to centralized services (no developer == no code). If you care about it, you can develop your own client using their library (à la signal-cli).

Regarding your last paragraph: I could probably list 20 features I'd like to see in Signal. That doesn't mean I want somebody implementing them with no guarantee about how securely they are implemented. One of the main goals of Signal is to provide guarantees against dragnet surveillance, and that constraint takes precedence.

I know their voice/video chats are built on top of WebRTC, they call it RingRTC perhaps you can find the answers there

Outside of the Android app, they had a bunch of "new developers" join, and they ported the call signalling framework to Rust: https://github.com/signalapp/ringrtc . This Rust library is now used by the other apps.

We're thrilled to announce the release of OvenMediaEngine 0.15.16!

We are pleased to announce that OvenMediaEngine has been updated to version 0.15.15. This update follows the recent 0.15.14 release, which introduced the SRT Push Publisher and support for OCSP stapling. With the 0.15.15 update, we have fixed a few crash issues. Thank you for your continued support, and we look forward to providing you with more reliable and enhanced streaming solutions.

OvenMediaEngine has been updated to 0.15.13, which includes 0.15.12 with support for HEVC in SRT Provider and LLHLS Publisher. In 0.15.13, we have enhanced compatibility and usability to make the streaming server more stable. For more information, see the release notes for versions 0.15.12 and 0.15.13.

The following content is taken from OvenMediaEngine Discussions #1242.

OvenMediaEngine has been updated to version 0.15.10, please see the release notes for details.

Info: OBS Studio 29.0.2, OME 0.15.7

Since OvenMediaEngine's update to version 0.15.4 uncovered several policy and feature conflicts, which have since been resolved in the latest version, 0.15.7. For more details, please look at the release notes for versions 0.15.5, 0.15.6, and 0.15.7.

With the 0.15.3 update, OvenMediaEngine supports multiple audio track inputs via SRT and stream creation/deletion APIs. Please see the release notes or below for details.

Also, we are preparing to show you OvenMediaEngine, a sub-second latency streaming solution using LLHLS and WebRTC, and give you a chance to experience the OvenMediaEngine Enterprise Demo.

The first update of OvenMediaEngine for 2023 has been released. This is version 0.15.0 and has improved stream quality for WebRTC providers. Please check out the release notes or below for details.