3 ms·
Why doesn't anybody fork the Signal clients? There are so many bad design decision in the clients (for instance no message backup on iOS or no way to save all m
by oezi 4y ago
Why doesn't anybody fork the Signal clients? There are so many bad design decision in the clients (for instance no message backup on iOS or no way to save all media to storage automatically) that I don't understand why people accept the Signal Foundation's stewardship of the client code.
- Aissen 4y agoThere are forked clients, but usually you can't use Signal's server infrastructure, so you need to roll your own, and now it brings another set of problems.
- xcdzvyn 4y agoYou're not allowed to: https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217211165 https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
- NoGravitas 4y agoBecause while both the server and the client are Open Source, the server doesn't federate. If you want to be able to communicate with anyone, you have to use the official server instance. And the official server instance doesn't allow unofficial clients (though some clients seem to get away with it for a while).
- _emacsomancer_ 4y agoMolly[1], a fork of Signal, seems to work fine. I've used it for a long time and never had any issues with it (and it connects to Signal fine). But for security reasons one of their changes was dropping SMS, so switching to it won't do you any good there. [1]: https://github.com/mollyim/mollyim-android https://github.com/mollyim/mollyim-android