Peergos VS TextSecure

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

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.