ringrtc
LibreSignal
ringrtc | LibreSignal | |
---|---|---|
7 | 49 | |
521 | 258 | |
-0.2% | 0.8% | |
9.1 | 0.0 | |
6 days ago | about 7 years ago | |
Rust | C | |
GNU Affero General Public License v3.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ringrtc
-
Strange signal debug log. Why does the product say panther? And why is signal contacting ringrtc? Does this look normal?
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
-
LiveKit – open-source, high performance WebRTC infrastructure
If you did not know, there is also https://github.com/signalapp/ringrtc by the Signal App team, which is written in Rust
-
Signal now supports group calls up to 40 people, using Rust
Huh, Signal's WebRTC implementation seems to be using Rust implementations of crypto primitives such as AES: example usage, Cargo.toml
-
WhatsApp and most alternatives share the same problem
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.
-
Does Signal still use the client-side fan-out method for group chats?
I know their voice/video chats are built on top of WebRTC, they call it RingRTC perhaps you can find the answers there
-
is anyone regretting moving to signal and moving back to whatsapp?
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.
LibreSignal
-
Show HN: Beeper Mini – iMessage Client for Android
>what does this mean?
Moxie (Signal's founder) has thrown fits in the past over the existence of third-party clients using their servers: https://github.com/libresignal/libresignal/issues/37#issueco...
-
Signal: The Pqxdh Key Agreement Protocol
0: https://github.com/libresignal/libresignal/issues/37
I push back when anyone recommends Signal because they are fundamentally not an open network.
-
Hosting Signal frontend on a local server (Like Signal desktop but through website)
OWS has historically been hostile to third party implementations outside of their clients. There are multiple unofficial options but the only one I've been looking at is the bridge with matrix, though setting up a matrix server just for this is likely overkill.
-
After High Court Ruling, Telegram Discloses Names/Numbers/IP of Users
I have to say that I find him fascinating too, but there are a few things that raise my suspicion, but of course do not convict him of anything:
The way he is attacking this alternative Signal client and rules out interoperability:
https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
Signal was a word before he decided to turn it into a brand.
The signal server source code repo was not updated for a year. Communication intransparent.
https://www.androidpolice.com/2021/04/06/it-looks-like-signa...
I am not even against crypto integration, but I found the choice of MobileCoin odd. Instead of integrating an existing privacy coin or working with the community, he decided to integrate MOB and to be one of their "advisors":
https://techcrunch.com/2018/04/24/mobilecoin-moxie-marlinspi...
https://www.coingecko.com/en/coins/mobilecoin
-
Snap Store administrators removed signal-desktop from Ubuntu Snap
Is that so surprising? Signal had always a hostile attitude to alternative clients. They have this weird disconnect of the new CEO saying they want to be available to as many people as possible and be a fully commited FOSS app, and then have no version on F-Droid (while Telegram has!) and actively fight alternative clients (see https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)
Because of this hostility Signal is not a trustworthy organization at all.
-
Signal discontinuing SMS support.
LibreSignal existed before Moxie was like “no, don’t”: https://github.com/LibreSignal/LibreSignal
- Combattez la censure Iranienne en hébergeant un proxy Signal
-
Nokia 1680 phone gets new PCB, runs mainline Linux
They have shut down third party clients, and resve the roght to continue that.
https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
-
Office 365 implementing AI to detect employees colluding, leaving and more
1) You need to audit that code, which.. everyone will have to do.
2) https://signal.org/blog/reproducible-android/
> the Signal Android codebase includes some native shared libraries that we employ for voice calls (WebRTC, etc). At the time this native code was added, there was no Gradle NDK support yet, so the shared libraries aren’t compiled with the project build.
a good answer in my opinion, but it means what you run from the play store is not reproducible and thus can never really be confirmed to be what the sources actually include. There are also binary blobs needed for interacting with Google Play.
3) Signal is openly hostile to third party client implementations: https://github.com/LibreSignal/LibreSignal/issues/37
-
Axolotl: First cross-plattform Signal client
Moxie Marlinspike on May 5th 2016:
> I'm not OK with LibreSignal using our servers, and I'm not OK with LibreSignal using the name "Signal." You're free to use our source code for whatever you would like under the terms of the license, but you're not entitled to use our name or the service that we run.
> If you think running servers is difficult and expensive (you're right), ask yourself why you feel entitled for us to run them for your product.
Moxie Marlinspike left Signal this January[2] 2022.
Whose to say whether there will be any change, but it's been interesting seeing Signal as a somewhat defended property. Although various third party clients/tools/libraries do exist already.
The claim that running servers is expensive would have been more interesting, imo, had there been any viable way to run your own. But for a long while Signal server source code wasn't being updated at all.
[1] https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
[2] https://signal.org/blog/new-year-new-ceo/
What are some alternatives?
Signal-Server - Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS
mollyim-android - Enhanced and security-focused fork of Signal.
TextSecure - A private messenger for Android.
livekit - End-to-end stack for WebRTC. SFU media server and SDKs.
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
libwebrtc - LibWebRTC tooling, rust bindings and more
calyxos-fdroid-repo
OvenMediaEngine - OvenMediaEngine (OME) is a Sub-Second Latency Live Streaming Server with Large-Scale and High-Definition. #WebRTC #LLHLS
Signal-Android - Patches to Signal for Android removing dependencies on closed-source Google Mobile Services and Firebase libraries. In branches whose names include "-FOSS". Uses new "foss" or "gms" flavor dimension: build with "./gradlew assemblePlayFossProdRelease".
webrtc - A pure Rust implementation of WebRTC
Signal-iOS - A private messenger for iOS.