Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"Built for individuals, I recently launched Keyoxide which uses cryptographic keypairs to accomplish decentralized identity verification."

So this is about the introduction of a new identity service. From what I get looking into Keyoxide it basically strives to be what Keybase originally intended to be.

From their Keybase migration guide [1]:

"Keyoxide as a partial replacement for Keybase

It's important to moderate expectations and state that Keyoxide only replaces the subset of Keybase features that are considered the "core" features: message encryption, signature verification and identity proofs.

Message decryption and signing are not supported features: they would require you to upload your secret key to a website which is a big no-no.

Encrypted chat and cloud storage are not supported features: there are plenty of dedicated alternative services.

If you need any of these Keybase-specific supports, Keyoxide may not be a full Keybase replacement for you but you could still generate a profile and take advantage of distributed identity proofs."

[1] https://keyoxide.org/guides/migrating-from-keybase



The key difference is that instead of the Keybase server storing verifications, it looks like they tell you to add the link to the proof directly to your key as a notation.

This means the proof isn't dependent on a central server, which seems like a significant improvement.


Yes, I noticed that too. So yes, I believe that this improves on Keybase. Even without the Zoom fail.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: