It's not a licensing restriction, it's a terms of use for their network service. It's also not enforced. Their clients are open source, signal-cli uses a fork of the Android app's client library.
I cannot speak for moxie or Signal. I can speak for my own experiences, as the maintainer of a fork of signal-cli, and I have never seen any evidence that Signal's servers block signal-cli or my fork. I don't know about signal-cli but my fork clearly identifies itself in the user agent (and another field called the "signal agent") to the server. If they wanted to block me they could.
Because open source is only used as a publicity tool by Signal. That's why their server code was abruptly closed sourced without announcement for a year (purportedly to add a scam cryptocurrency that Moxie has a conflict of interest in).
It's hard to trust a project with a divisive, evasive and concealing leader.
Macha|4 years ago
https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
When did this stance change? Is there a current statement from moxie to that effect?
finnn|4 years ago
I cannot speak for moxie or Signal. I can speak for my own experiences, as the maintainer of a fork of signal-cli, and I have never seen any evidence that Signal's servers block signal-cli or my fork. I don't know about signal-cli but my fork clearly identifies itself in the user agent (and another field called the "signal agent") to the server. If they wanted to block me they could.
edit: signal-cli also sets a user agent clearly identifies itself: https://github.com/AsamK/signal-cli/blob/05abb3f9f6294677d2d...
gnull|4 years ago
swiley|4 years ago
dheera|4 years ago
0xy|4 years ago
It's hard to trust a project with a divisive, evasive and concealing leader.
unknown|4 years ago
[deleted]