maxtaco

I built FOKS as a fully open-source, fully federated successor to Keybase. All refs, blobs, packs, and other server-side resources are end-to-end encrypted. Also, all encryption is PQ-secure, unlike Keybase.

Thanks for the feedback! From the server's perspective, all git objects are stored as encrypted key-value pairs. The names (i.e. the sha-1 hashes) of the objects are encrypted, as are the values. This means the server can't see branch names and refs. It can likely infer timestamps from access patterns, but it hasn't done so, and if you run the server yourself, it's an added layer of protection. There is no sever-side merging, since the server can't see enough plaintext to help there. So those features you indicate that leak content weren't attempted. For key backup and recovery, there's a pretty good discussion in the white paper (see https://foks.pub). For build transparency, everyone is welcome to build their own clients from our git repo, but you're right, we can invest more efforts here on making builds reproducible and sticking them in transparency logs. For migration, we support the obvious pathways (git pull --all && git push --all), but nothing more sophisticated. There are no identity proofs yet and they aren't really needed for the applications we have so far. But they could be useful to build other features.

I the mean time, we do encourage you to create a team!