A rust peergos client? No, but that would be great. Happy to advise on this, just message in our matrix chat room, or email us.

The Java sync client is agnostic as to what the two endpoints are among a local dir, and a peergos dir, as long as it implements this interface: github.com/Peergos/Peer... (We have implementations for a local dir, an android dir using SAF, and a peergos dir)

Thank you! the sync client just speaks the normal peergos protocol if it syncs to peergos. It is is just a peergos client with a simple sync algorithm (few hundred lines of code). Most of it is in this method: github.com/Peergos/Peer...

p.s. We're still working on iOS ;-)

It's been a huge year, with 14 releases (compared to 8 last year), with first release of the Android app, Desktop apps, and sync engine. We are just getting started! Come and join the future of the web. peergos.net

Client side it scales with the number of people you follow. If you follow more than 10,000 you'll probably have a bad time. Beyond 10,000 recipients there isn't much point in practice for privacy and it should probably be public. But the network as a whole can trivially scale to twitter size.

So far, to our surprise, we haven't needed indexing, as search client side is fast enough. With more advanced search our plan is to build the index client side and store that encrypted.

We've already solved these problems in Peergos. Apps can be given permission to store app private data, read private user data, or write private user data, on a per file/dir granularity. Everything is stored E2EE on your PDS in Peergos. We treat your PDS *and* apps as current adversaries.

We believe that for truly portable accounts your data should be E2EE, then you really don't need to trust the host, because they can't misuse or sell your data.

Custom apps are described here: book.peergos.org/features/app...
They can also (with permission) send E2EE messages to your friends. These apps don't need login, auth, or even storage! That's all handled by peergos. They don't even need an sdk, it's all just basic REST calls.

This is our proposal for atproto: github.com/bluesky-soci...

We've already solved these problems in Peergos. Apps can be given permission to store app private data, read private user data, or write private user data, on a per file/dir granularity. Everything is stored E2EE on your PDS in Peergos. We treat your PDS *and* apps as current adversaries.

The approach we took here is to put everything in an exfiltration proof sandbox, and gate read and writes to your data and other APIs.