3 ms·
That then means you can't communicate with others running the normal Signal client. Signal is not a federated protocol.
by j-james 6y ago
That then means you can't communicate with others running the normal Signal client. Signal is not a federated protocol.
- toast0 6y agoI would phrase that differently. You can't use your (forked) client to communicate with others who are not running your client. With a forked server, and a forked client, you're welcome to add federation, but Signal doesn't want it. But then again, the complaint is that people don't like how the Signal project is doing things. Maybe running your own network will help explain why they do things the way you don't like. Maybe running your own network will help explain how running things the way you like can actually work.
- growse 6y ago> That then means you can't communicate with others running the normal Signal client. Signal is not a federated protocol. You also can't communicate with WhatsApp users directly either. If your fork of Signal in better, then you should have no difficulty it convincing people to switch to it. Just because the software is open source, you're not entitled to connect to and use someone else's service in any way you like.
- j-james 6y agoRight, but the idea and comment I'm addressing is "If you don't like it, create a fork". This "do it yourself" mantra doesn't apply to Signal, and they have a history of rejecting community work. It's much more valuable to advocate for changes and fixes to the main app. > If your fork of Signal in better, then you should have no difficulty it convincing people to switch to it. This isn't true. Signal has a marketing budget and millions of downloads of inertia.