11 ms·
>What's preventing someone maintaining a client fork where you can do this? We have the code to run a Signal-compatible networks and software that can support t
by Jiejeing 6y ago
>What's preventing someone maintaining a client fork where you can do this? We have the code to run a Signal-compatible networks and software that can support this, so why does nobody?
This is actively discouraged: https://github.com/libresignal/libresignal/issues/37#issuecomment-217211165 https://github.com/libresignal/libresignal/issues/37#issueco...
- growse 6y agoIf you read the link, what's discouraged is using the non official client to connect to the Signal service, or using the "Signal" name on something that isn't produced / run by OWS. There's nothing there about preventing anyone from running a signal-compatible service/network and shipping a fork of their own client to connect to it, which is my original point.
- zepto 6y agoIt’t not discouraged. In fact I’d say it’s actively encouraged to fork both the client and the server. What is not encouraged is just forking the client and using Signal’s servers. “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.“