@sp1rit @friend The ToS is an issue between Signal and the *user* of such a fork.
I don't know if services are legally permitted to dictate *how* users of the service can connect to it. In any case, there is precisely zero from stopping a software developer from publishing a non-Signal-branded fork of Signal that connects to Signal servers.
Signal would have to take that issue up with the users that are using that nonbranded fork to connect. I don't think they would.
@sp1rit @friend i'm not a lawyer but i'm not sure that there is any legal distinction between an authorized user of the Signal online service using the Signal-branded GPL client and a non-Signal-branded fork client.
technically, if the fork doesn't diverge much, it wouldn't even be possible for Signal to know you're using a fork.
@sp1rit @friend I just read the Signal service ToS and nowhere does it say you are restricted to using Signal-branded client software.
Even if they amended it to do so, there is no technical grounds for enforcement, and while I am not a lawyer, I don't think there is much in the way of legal grounds either.