ianopolous

Minor clarifications, but libp2p also uses TLS ALPN for protocol negotiation, and also uses native quic streams - there is no additional muxer layer when using quic.

Iroh is still awesome.

There is Peergos: https://peergos.org (disclaimer: I am the creator)

@lxpz It would be great to do a follow up to this blog post with the latest Peergos. All the issues with baseline bandwidth and requests have gone away, even with federation on. The baseline is now 0, and even many locally initiated requests will be served directly from a Peergos cache without touching S3.

https://garagehq.deuxfleurs.fr/blog/2022-ipfs/

Let's talk!

You might be interested in Peergos [0][1] (creator here) which has official Linux apps, is E2EE, fully open source (including the server), and self-hostable. It's also recommended by privacy guides: https://www.privacyguides.org/en/cloud/#peergos

[0] https://peergos.org

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

You might be interested in Peergos [0][1] which is E2EE, fully open source (including the server), and self hostable. We've been audited by Cure53 and Radically Open Security.

[0] https://peergos.org

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

You might like Peergos, which is E2EE as well. Disclosure (I work on it).

https://peergos.org

You can try it out easily here: https://peergos-demo.net

Our iOS app is still in the works still though.

There is a built-in mirror function in peergos you can use to mirror your user, or an entire server you control to another server yes: https://github.com/peergos/peergos?tab=readme-ov-file#mirror and we recently add this to the ui itself you can request/pay for a live mirror on another server: https://peergos.net

At the moment if your client accesses a server with a mirror, and your primary is offline, then you can read, but not write. Writes are proxied to your primary, and thus need your primary to be accessible.

Yes your files stay on your server, unless you share them with a friend on another server. It basically just uses libp2p as an internode communication protocol, and you need auth to retrieve ciphertext blocks.

You might be interested in Peergos (https://peergos.org) - creator here.

An old write up is here: https://itsfoss.com/peergos/

Thanks! I'll send you an email.

The good news is Peergos also has serializable transactional modifications. This comes from us storing signed roots in a db on your home server (not ipns). We also have our own minimal ipfs implementation that uses 1000x fewer resources than kubo, aka go-ipfs.

Thanks! You can play around with it on https://peergos-demo.net

We should talk. This very similar to how apps use E2EE data in Peergos. Maybe we can join forces. https://peergos.org/posts/a-better-web

You may like Peergos (creator here) https://peergos.org/posts/decentralized-social-media

I love this. It is close to what we've built with Peergos [0].

1. People have to accept you as a follower, and the default is bi-directional.

2. There are no visible follower/friend counts.

3. Chronological feed which has an end (no infinite scroll)

4. No arbitrary character limit

5. No analytics (enforced by E2EE)

We don't have a max friends/number of posts per day though.

[0] https://peergos.org/posts/decentralized-social-media

Peergos has a private data solution that is compatible with (and predates) atproto (dag-cbor, portable data and accounts and social graph).

You're absolutely right. We need a big push on marketing and PR (Peergos founder here). We are self, grant and customer funded and a not-for-profit so we necessarily need to grow more slowly than a VC backed company, but that lets us keep our incentives aligned with our users. Our aim is absolutely ease of use, there shouldn't be a usability tradeoff for privacy in our view. We do already have some very non-technical users who love it.

You might be interested in Peergos which lets you easily live mirror to another instance and everything is E2EE.

Yep, if that's possible for your service that works. If the service doesn't want your email and/or doesn't have access to your data, e.g. an E2EE service where account reset is impossible, then that's not an option.

The supposition for all this is that the service wants to use passwords for whatever reason. In that case, generate them for the user.

People should absolutely be using password managers where possible.

A website doesn't have control over whether you are using a password manager though. This is about stopping the human from generating a password themselves, which will be terrible.

Humans shouldn't generate passwords. ~0 people are good at that. Websites should just generate a password for a user, letting them regenerate as many times as they like until they get one they like (without breaking password manager based generation). A bit like this: https://peergos-demo.net/?signup=true

You have some similar ideas to the encrypted social network in the Peergos protocol. We'd love to chat and see if there is scope for collaboration.

You might be interested in Peergos (lead here). It is E2EE, built on a P2P protocol (libp2p) and thus self hostable. We don't have onion routing yet though.

https://peergos.org

G'day mempko, I remember firestr! Very nice! You might remember around the same time (2013) I started Peergos. We're still working on it!

https://peergos.org

If anyone’s looking for open-source, self-hostable, E2EE storage then checkout Peergos (disclaimer: lead here):

https://peergos.org

Yes, legally requiring open APIs and interop beyond X users is the best way forward. There is some tension with allowing product changes and deprecating old APIs though. Maybe something like mandate versioned APIs, and keep old versions around for at least 2 years after newer version is released.

1. It depends on the time scale. The question is if you can outlive their VC funding.

2. How do you fix the incentives short of fixing capitalism to remove software VCs?

Very well said. This is the approach we're taking with peergos, paid accounts unless you self host. I wrote some of our thoughts on this here:

https://peergos.org/posts/the-social-dilemma

Sure it is: https://peergos.org/posts/decentralized-social-media

It is social media where only the end users' devices can decrypt the posts and comments. Then surveillance is not possible. Targeted ads are not possible.

We really need e2ee social media that's designed to protect, not addict people.

You might be interested in Peergos for the storage and access control part. We have a profile where you can control access (and revoke) to each field individually. E2EE because most people wont want to self host.

https://peergos.org/posts/social-profile