|
| ▲ | whilenot-dev 3 hours ago | parent | next [-] |
| I don't quite get this take... I can't know what's actually running on any production system out there (except my own), because giving anyone access would be a fatal choice. What can Signal do to annihilate your concerns without giving you access to their system? |
| |
| ▲ | m4rtink 3 hours ago | parent | next [-] | | The actively fight against self hosted Signal servers and clients - like those where you can know what it is running because it is you (or your friends) running it! | | |
| ▲ | tredre3 an hour ago | parent [-] | | Unless you have some examples, both your statements seem false. At best they (very) passively fight against third party clients connecting to their official servers. At best they (very very very) passively fight against self-hosting the server by not providing elaborate guides and having the public repo lag behind production. |
| |
| ▲ | mfro 3 hours ago | parent | prev [-] | | This is a great point and I wonder if we could see some sort of remote attestation for consumer messaging apps. It would do a lot for my confidence. |
|
|
| ▲ | nicce 2 hours ago | parent | prev | next [-] |
| Signal is one of the first apps with fully reproducible builds. Source code matches perfectly the android app and you can get byte identical by yourself. And if client crypto and protocols hold, backend does not matter. |
| |
|
| ▲ | vlovich123 3 hours ago | parent | prev | next [-] |
| If only Signal was zero trust and then any server implementation would be irrelevant from the security and privacy guarantees it offers. |
| |
|
| ▲ | lawn 3 hours ago | parent | prev [-] |
| They could open source it and you still wouldn't know what's actually running on their servers. |
| |