News for hackers. Stuff that matters.
Re:Signal Fork with WhatsApp Migration by t0astbread on Tuesday January 12, 2021 @01:17PM (#25750976)
Not 100% on-topic since this is designed for ephemeral use but what is Signal's general stance towards forks on their server? I've considered switching to it but I don't like their official APK distributions.
Re:Signal Fork with WhatsApp Migration by seebye on Tuesday January 12, 2021 @01:49PM (#25751512)
They don't tolerate third party clients. See: https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
Re:Signal Fork with WhatsApp Migration by tptacek on Tuesday January 12, 2021 @02:05PM (#25751746)
They can't; part of the premise of the project is that they come up with privacy advances that are deployed network-wide by controlling both the client and the server. See Matrix for an example of how hard it is to get very basic privacy controls up and running when you don't control the client.

(I always come across sounding like I'm dunking on Matrix; I like Matrix. Different project, different goals.)

Re:Signal Fork with WhatsApp Migration by jeroenhd on Tuesday January 12, 2021 @01:19PM (#25751012)
I haven't seen any evidence to indicate that alternative clients are supported or even tolerated. I don't think Signal will start blocking custom clients, but I don't think the Signal project will aid or cooperate with any development of an alternative client.
Re:Signal Fork with WhatsApp Migration by josteink on Tuesday January 12, 2021 @01:48PM (#25751504)
> I don't think Signal will start blocking custom clients

Bridging Signal to Matrix has been notoriously difficult because Signal is actively hostile to all non-official clients.

So yeah. Open source, but no open values was gained from that.