. // // Also add information on how to contact you by electronic and paper mail. // // If your software can interact with users remotely through a computer network, // you should also make sure that it provides a way for users to get its source. // For example, if your program is a web application, its interface could display // a "Source" link that leads users to an archive of the code. There are many // ways you could offer source, and different solutions will be better for different // programs; see section 13 for the specific requirements. // // You should also get your employer (if you work as a programmer) or school, // if any, to sign a "copyright disclaimer" for the program, if necessary. For // more information on this, and how to apply and follow the GNU AGPL, see . ?>

Let's add a decentralized Pixelfed proof to your OpenPGP keys.

Update the Pixelfed account

Log in to your Pixelfed instance and add the following lines to your Bio (make sure to replace FINGERPRINT):

This is an OpenPGP proof that connects my OpenPGP key to this Pixelfed account. For details check out https://keyoxide.org/guides/openpgp-proofs

[Verifying my OpenPGP key: openpgp4fpr:FINGERPRINT]

Update the PGP key

First, edit the key (make sure to replace FINGERPRINT):

gpg --edit-key FINGERPRINT

Add a new notation:

notation

Enter the notation (make sure to update the link):

proof@metacode.biz=https://INSTANCE.ORG/users/USERNAME

Please note that the /users/ part of the URL is mandatory for the proof to work.

Save the key:

save

Upload the key to WKD or use the following command to upload the key to keys.openpgp.org (make sure to replace FINGERPRINT):

gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT

And you're done! Reload your profile page, it should now show a verified Fediverse account (Pixelfed is part of the Fediverse).