Signal-Server

You need to fix your shill propaganda. It's 4 months i.e. 120 days, not 4 weeks, before they delete your account https://github.com/signalapp/Signal-Server/blob/7f5097bd3317...

By default, the mobile app continually tries to connect to "updates2.signal.org" Perhaps manual, user-controlled updates is not part of the design If the source code is available^1 then surely someone has modified it to remove the phone number requirement, not to mention other improvements 1. https://github.com/signalapp/Signal-Server It seems like Signal may be another example of "read-only" open source, where there is no expectation anyone will actually try to _use_ the source code. Instead, there is an expectation that everyone will use binaries distributed by a third party and allow remote code installation and RCE of software on their computers _at the third party's discretion_. In other words, all users will cede control to a third party NB. This comment is not referring to the "Signal protocol". It pertains to _control_ over the

> Signal was made by people who then used it to push their get-rich-quick cryptocurrency scheme on users and who threw all their promises of being open-source and reproducible over board for it. I reviewed Signal's cryptography last year over a long weekend: https://soatok.blog/2025/02/18/reviewing-the-cryptography-us... There's a lot to be said for the utility of reverse engineering tools and skills, but I did not need them, because it was open source. Because Signal's client software still is open source. Whatever you think about MobileCoin, it doesn't actually intersect with the message encryption features at all. At all. The only part in Signal that's not entirely open source are the anti-spam features baked into the Signal Server software. And, frankly, the security of end-to-end encryption messaging apps has so little to do with wha

I thought you could compile from source and run Signal server instances, but there is no federation, so you would need a client that points to your server and you could only talk to other people using that client. https://github.com/signalapp/Signal-Server

Good news! https://github.com/signalapp/Signal-Server

Haven't tried it, but it seems so: https://github.com/signalapp/Signal-Server You probably have to rebuild the clients though to have it use a custom server.

FYI, the server is also open source. https://github.com/signalapp/Signal-Server

Huh, I was going to point out that the Signal server isn't Free Software either, since for a while it wasn't being published, but it seems they have gotten back into publishing it. https://github.com/signalapp/Signal-Server

Last commit two days ago: https://github.com/signalapp/Signal-Server Please don't spread FUD. If you're really this worried (about what? the client is still open too, or use Molly-FOSS if you're that paranoid), run your own server too.

I don't think so. Signal regularly stops committing code to the public repos (https://github.com/signalapp/Signal-Server) when they're working on some kind of big reveal (cryptocurrency integration and such), but the server code is out there for you to run yourself. Signal has the added benefit that it doesn't need to read what's in the messages you send. It needs some very basic routing information and the rest can be encrypted end to end. With AI stuff, the contents need to be decrypted in the cloud, so the end-to-end protections don't apply.

Signal apps and server are all on GitHub and frequently updated, for what it's worth: https://github.com/signalapp/Signal-Server https://github.com/signalapp/Signal-iOS.

> They could at least BSL the server code and allow others to verify the server code and host but not compete. This is exactly what they do (except they use AGPL): https://github.com/signalapp/Signal-Server

Both the app and the server is open source https://github.com/signalapp/Signal-Android https://github.com/signalapp/Signal-Server There are forks like Session which doesn't require a phone number to sign up https://github.com/oxen-io/session-android

The fact that it locks you into using their servers, does not distribute on F-Droid (only Google Play OR an APK with an insecure update mechanism), and has a completely closed-source "abusive message filter" module server side, that could functionally be used for censorship, storing messages for future decryption, or any other number of nefarious purposes - we have no idea since it's not open source (https://github.com/signalapp/Signal-Server/blob/main/.gitmod...). Additionally, you cannot distribute branded forks or Signal, and if you do fork it, your fork is not allowed to connect to Signal's "official" OWS (open whisper systems) servers - hostility to federation should be viewed with prejudice and suspicion at the very least, it suggests a vested interest in a single point of failure (or control), which goes against user interests. Fur