TextSecure VS Signal-Desktop

Moxie's reasons for disallowing Signal distribution via F-droid always rang a little flat to me ( https://github.com/signalapp/Signal-Android/issues/127 ). Lots of chatter about the supposedly superior security model of Google Play Store, and as a result fewer eyes independently building and testing the Signal code base. Everyone is entitled to their opinions, but independent and reproducible builds seem like a net positive for everyone. Always struggled to understand releasing code as open source without taking advantage of the community's willingness to build and test. Looking at it in a new light after the XZ backdoor, and Jia Tan's interactions with other FOSS folk.

Signal has documentation on how to reproduce their Play Store builds and compare them with what you've installed locally:

https://github.com/signalapp/Signal-Android/blob/main/reprod...

There's nothing on Signal blog as of yet, but Signal's git repository was tagged with v7.0.0 yesterday and we can see from the commit history since the previously tagged version (v6.74.4) that there will be a setting to hide one's phone number [1], as well as disabling the previous default behavior of advertising that one is on Signal to all their contacts already using it [2].

[1] https://github.com/signalapp/Signal-Android/commit/8797236b5... (PNP stands for "Phone Number Privacy")

[2] https://github.com/signalapp/Signal-Android/commit/6097e6c30...

Signal works the same but without the user tracking from Meta/Facebook. Many people use it as well but I'm surprised that a majority sticks to WhatsApp.

Telegram and Signal solve this.

Sadly yes: Looks like an open issue 13290 for Signal, sounds like they were/are indeed still interacting through google's push notification service, wat, and per a link at that issue it was a chore for Tutanota to break away once they realised it was a problem some years ago (though at least they thought about it years ago? wtf Signal...)

Here is one: https://github.com/signalapp/Signal-Android/tree/main/reprod...

Rule 1: Posts to r/signal must relate to Signal.

2: https://github.com/signalapp/Signal-Desktop/issues/1862

For more Information on how to proceed kindly connect with the HR on Signal app. Download (Signal ) on your mobile device https://signal.org/download/ and connect now with the HR ON +13093936282

It does, see [0]. Fun fact: Signal desktop, which uses Electron under the hood, is running without sandbox on Linux [1][2].

[0] https://github.com/electron/electron/pull/39824

[1] https://github.com/signalapp/Signal-Desktop/issues/5195

[2] https://github.com/signalapp/Signal-Desktop/pull/4381

There was a issue opened on GitHub a while back apparently but that was closed due to inactivity. What you might want to do is either open a new issue directly in GitHub (provide as much information as possible and include debug logs) or just send them a support ticket via the support form (and include debug logs).

Desktop will have it https://github.com/signalapp/Signal-Desktop/commit/9bfbee464bc307a9133ccf43042987343722afe9

Issues have been ongoing for the past couple weeks. It's not clear if this is the client or backend. Dual stack works again with v6.20.2, but IPv6-only with NAT64 still doesn't. Actively being worked on, and hopefully some good learnings. Issue link thread: https://github.com/signalapp/Signal-Desktop/issues/6439

Alive again with 6.20.2 on Windows dual stack. Directly downloaded from https://signal.org/download/

Fix1, Fix2, Fix3, Fix4