diff --git a/views/guides/migrating-from-keybase.content.php b/views/guides/migrating-from-keybase.content.php index e25bb5c..e08a257 100644 --- a/views/guides/migrating-from-keybase.content.php +++ b/views/guides/migrating-from-keybase.content.php @@ -2,21 +2,20 @@

Claim your Keyoxide profile

-

Have you made your public key accessible through web key directory (WKD) on your website or uploaded it to keys.openpgp.org? Congratulations, you now have your very own Keyoxide profile!

+

Go to the profile URL generator, set Keybase as Source and follow the Keybase specific instructions. Has a profile URL been generated? Congratulations, you now have your very own Keyoxide profile!

-

Link to your Keyoxide profile

+

Actually migrating to Keyoxide

-

- Append your OpenPGP key's fingerprint to the domain as such:
- https://keyoxide.org/FINGERPRINT
and there's your profile page with the public key fetched from keys.openpgp.org. -

+

Unfortunately, you get very little control when using your Keybase key directly. You will need to generate your own PGP keypair (use guides like this one for help) to unlock the full potential of distributed identity proofs.

-

- If you wish to use WKD instead, simply append your email address as such:
- https://keyoxide.org/USER@DOMAIN.ORG -

+

Have you generated a keypair and made the public key accessible through web key directory (WKD) or uploaded it to keys.openpgp.org? Use the profile URL generator to get your own profile URL and start adding identity proofs.

-

- Lastly, if you still wish your key to be fetched from keys.openpgp.org but using your email address instead of the key's fingerprint, simply override by using the following URL:
- https://keyoxide.org/hkp/USER@DOMAIN.ORG -

+

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.