Signal-Android VS Signal-Server

Haven't used Signal FOSS, but as it happens Molly bas just implemented OSM support, perhaps when it lands you might have better luck with it. Anyway, is there no issue tracker for that fork? I tried looking in their repo and found it disabled

Try using the Signal FOSS version from https://www.twinhelix.com/apps/signal-foss/

Yeah I followed that whole story. Since then some forks have been created that do not care what Signal Foundation thinks about using their servers. Molly and Signal-FOSS for example, both compatible to regular Signal. Those two forks will not keep SMS support, Molly never had it, and Signal-FOSS will most likely drop it because they think it's too much work to keep it while staying compatible and up to date. I hope there is going to be another fork specifically dedicated to keeping SMS support. We'll see.

You can get a completely open source version without the Google stuff here: https://www.twinhelix.com/apps/signal-foss/

Signal FOSS removes proprietary google blobs https://www.twinhelix.com/apps/signal-foss/

Signal - Molly , Foss-Signal

Maybe they had outdated info from when the server software was not updated for a long time. Or, it's regarding the dependencies on closed-source Google Mobile Services and Firebase libraries, though those can be removed... and have been in this fork.

> 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

https://github.com/signalapp/Signal-Server/blob/main/service/src/main/java/org/whispersystems/textsecuregcm/push/APNSender.java for APNs push notification payloads

git clone https://github.com/signalapp/Signal-Server.git

yes it is available here https://github.com/signalapp/Signal-Server/blob/main/service/pom.xml

You could also start your own signal server, but with blackjack, and hookers

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.

Further reading: https://drewdevault.com/2018/08/08/Signal.html

It’s actually the signal server that isn’t reproducible because of the abusive message filter that’s in a private repository. It’s clear as day here: https://github.com/signalapp/Signal-Server