@ted @gytis @rysiek @h3artbl33d @PINE64 signal's policy is irrelevant. the client is GPL. you can fork it and talk to signal servers just like you can fork chromium and talk to google servers.

@sneak @ted @gytis @h3artbl33d @PINE64 it is relevant, because if they wanted to, they could block your client. Signal is actively hostile to third-party client developers.

The right to fork is there, the right to use their servers is not.

@rysiek @sneak @ted @gytis @h3artbl33d @PINE64 Signal was hostile to a fork of the Android client they developed. They are not hostile to independently developed clients. github.com/signalapp/libsignal

Follow

@be @rysiek @ted @gytis @h3artbl33d @PINE64

most upstreams that get forked in open source are hostile and/or unreasonable. that's why people fork them.

upstream being hostile to forks is not a signal thing. fork away.

@sneak @be @rysiek @ted @gytis @PINE64 Unfortunately, that is true. I can name dozens of examples where hostility and/or rogue behaviour against forks happened. It's sad.

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!