Client-side encryption really decreases the attack surfaces of cloud storage solutions.
It’s really sad that Keybase failed at building a business around this. Hopefully someone else is going to make another attempt.
It’s really sad that Keybase failed at building a business around this. Hopefully someone else is going to make another attempt.
The problem is that encryption adds an extra layer of complexity.
Having native, non-web app would help here, but I don't think this is ever going to happen.
They should rename end-to-end encryption to client-side encryption or something else because it is not very clear what it means
Keybase as it's core was that it's a key directory that's publicly auditable. Everyone could verify the chain of verification of each other in Keybase. On top of that infrastructure, files and chat was added.
Peergos doesn't seem to show any chains or in fact auditable information at all. You can add/remove friends that is supposedly cryptographically verified, but there is no information about it, nor is there any information about where the data is actually stored, how you can get it to your local machine, how to re-verify the claims, how to add devices that have access.
You can also verify keys in person using the same protocol as Signal (via QR codes or number groups).
There are no private keys stored on any devices, so adding devices is not a thing. It is a pure capability based system.
Unlike keybase, we are fully open source and self-hostable.
There are a lot more details in our booklet- https://book.peergos.org