ContactDiscoveryService VS Peergos

[1] https://signal.org/blog/private-contact-discovery/

Signal uses SGX for remote attestation, which presumably lets the client verify that the code running on the server is a build of the OSS code and not a modified version. But I don't know the details or if this is reliable.

SGX and remote attestation described here:

https://signal.org/blog/private-contact-discovery/

Signal does private contact discovery and the effort they've gone to to do this is quite impressive.

TEEs have numerous privacy-enhancing applications that may benefit users. One of them is, as discussed earlier, private contact discovery; the Signal application uses a contact discovery service enhanced using Intel SGX, a TEE technology, to protect its users' privacy. A similar application of TEEs is performing malware analysis in a remote cloud service, so that the service may not identify users by the contents of their devices, such as the applications they have installed, especially important as 98.93% of users may be uniquely identified by the list of applications they have installed.

Signal (or, more accurately, one of its predecessors) used to use client-side private set intersection for contact discovery, but this scales poorly [1].

Now they use a solution based on Intel SGX and server-side trusted computing [2].

[1] https://signal.org/blog/contact-discovery/

[2] https://signal.org/blog/private-contact-discovery/

Would love to hear your thoughts on Peergos - https://peergos.org

https://github.com/peergos/peergos

A good Dropbox alternative is Peergos (founder here). Peergos is an E2EE P2P storage, sharing and application protocol. Fully open source, including the server, self-hostable, no VCs.

https://peergos.org

You can do that with peergos [1]- mount a peergos folder locally using FUSE. Or login to the web interface and share easily and privately.

[1] https://github.com/peergos/peergos

You might be interested in the p2p design of Peergos. You sign up to Peergos[0]. Your initial server is just responsible for storing your data (although you can run as many live mirrors as you like), and clients verify all updates. You can automatically move server (by running a command) and all your data is moved, and old links continue to work, and you keep your social graph and identity.

You can also log in through any instance, including localhost. Links also work on any server because they include a capability to the content in the link.

This is the beauty of content addressing plus public key based addressing.

[0] https://peergos.org

Totally agree! Shameless self promotion: have a look a Peergos - https://github.com/peergos/peergos

Our tech book might be a better starting point for this group: https://book.peergos.org

https://peergos.org

https://book.peergos.org

https://github.com/peergos/peergos

Features:

* audited by Cure53

* protects metadata (directory structure, file name and properties, file sizes, social graph)

* fine grained capability-based access control

* built-in social media

* sandboxed 3rd-party apps: e.g. word doc viewer, calendar, text editor, games etc.

* FUSE bindings

* CLI

* cross platform

* browser client