diff --git a/.drone.yml b/.drone.yml index a747163..53b7518 100644 --- a/.drone.yml +++ b/.drone.yml @@ -1,3 +1,30 @@ +# Copyright (C) 2020 Yarmo Mackenbach +# +# This program is free software: you can redistribute it and/or modify it under +# the terms of the GNU Affero General Public License as published by the Free +# Software Foundation, either version 3 of the License, or (at your option) +# any later version. +# +# This program is distributed in the hope that it will be useful, but WITHOUT +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS +# FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more +# details. +# +# You should have received a copy of the GNU Affero General Public License along +# with this program. If not, see . +# +# 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 . --- kind: pipeline diff --git a/.gitignore b/.gitignore index c9fee6c..bd4a047 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,30 @@ +# Copyright (C) 2020 Yarmo Mackenbach +# +# This program is free software: you can redistribute it and/or modify it under +# the terms of the GNU Affero General Public License as published by the Free +# Software Foundation, either version 3 of the License, or (at your option) +# any later version. +# +# This program is distributed in the hope that it will be useful, but WITHOUT +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS +# FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more +# details. +# +# You should have received a copy of the GNU Affero General Public License along +# with this program. If not, see . +# +# 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 . vendor node_modules server/secrets.php diff --git a/.licenseignore b/.licenseignore index 53af85b..f781cf3 100644 --- a/.licenseignore +++ b/.licenseignore @@ -1,3 +1,30 @@ +# Copyright (C) 2020 Yarmo Mackenbach +# +# This program is free software: you can redistribute it and/or modify it under +# the terms of the GNU Affero General Public License as published by the Free +# Software Foundation, either version 3 of the License, or (at your option) +# any later version. +# +# This program is distributed in the hope that it will be useful, but WITHOUT +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS +# FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more +# details. +# +# You should have received a copy of the GNU Affero General Public License along +# with this program. If not, see . +# +# 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 . **/\.git **/*.md diff --git a/assets/scripts.js b/assets/scripts.js index 2b40b75..55c06c7 100644 --- a/assets/scripts.js +++ b/assets/scripts.js @@ -1,3 +1,32 @@ +/* +Copyright (C) 2020 Yarmo Mackenbach + +This program is free software: you can redistribute it and/or modify it under +the terms of the GNU Affero General Public License as published by the Free +Software Foundation, either version 3 of the License, or (at your option) +any later version. + +This program is distributed in the hope that it will be useful, but WITHOUT +ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS +FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more +details. + +You should have received a copy of the GNU Affero General Public License along +with this program. If not, see . + +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 . +*/ async function verifySignature(opts) { // Init const elRes = document.body.querySelector("#result"); diff --git a/assets/styles.css b/assets/styles.css index 4fe271b..89e68af 100644 --- a/assets/styles.css +++ b/assets/styles.css @@ -1,3 +1,32 @@ +/* +Copyright (C) 2020 Yarmo Mackenbach + +This program is free software: you can redistribute it and/or modify it under +the terms of the GNU Affero General Public License as published by the Free +Software Foundation, either version 3 of the License, or (at your option) +any later version. + +This program is distributed in the hope that it will be useful, but WITHOUT +ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS +FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more +details. + +You should have received a copy of the GNU Affero General Public License along +with this program. If not, see . + +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 . +*/ * { box-sizing: border-box; } diff --git a/index.php b/index.php index 90817b4..24d8ca2 100644 --- a/index.php +++ b/index.php @@ -1,3 +1,32 @@ + . + +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 . + --> . + +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 . + --> . + +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 . + --> . + +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 . + --> . + +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 . + --> . + +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 . + --> . + +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 . + --> layout('template.base', ['title' => $title]) ?>
diff --git a/views/encrypt.php b/views/encrypt.php index 31e5875..20f12b9 100644 --- a/views/encrypt.php +++ b/views/encrypt.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
diff --git a/views/faq.php b/views/faq.php index e458c11..63c0ceb 100644 --- a/views/faq.php +++ b/views/faq.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
diff --git a/views/guide.php b/views/guide.php index aa783d1..cb8a804 100644 --- a/views/guide.php +++ b/views/guide.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
diff --git a/views/guides.php b/views/guides.php index bdb0b82..8256d5b 100644 --- a/views/guides.php +++ b/views/guides.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
diff --git a/views/guides/contributing.content.php b/views/guides/contributing.content.php index d9d4c24..8b54de3 100644 --- a/views/guides/contributing.content.php +++ b/views/guides/contributing.content.php @@ -1,3 +1,32 @@ +

Keyoxide is more than this website. It's a project that aims to make cryptography more accessible to everyone. Keyoxide is part of a larger community of people working hard to develop tools that add privacy and security to our digital online lives. Remember: privacy is not a luxury.

As a developer

diff --git a/views/guides/contributing.title.php b/views/guides/contributing.title.php index fd1b64e..cb67f8a 100644 --- a/views/guides/contributing.title.php +++ b/views/guides/contributing.title.php @@ -1 +1,30 @@ + Contributing to Keyoxide diff --git a/views/guides/devto.content.php b/views/guides/devto.content.php index 4b5ef30..9628da3 100644 --- a/views/guides/devto.content.php +++ b/views/guides/devto.content.php @@ -1,3 +1,32 @@ +

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

Post a dev.to proof message

diff --git a/views/guides/devto.title.php b/views/guides/devto.title.php index 2a88923..0277e50 100644 --- a/views/guides/devto.title.php +++ b/views/guides/devto.title.php @@ -1 +1,30 @@ + Adding a dev.to proof diff --git a/views/guides/discourse.content.php b/views/guides/discourse.content.php index c842917..cc69604 100644 --- a/views/guides/discourse.content.php +++ b/views/guides/discourse.content.php @@ -1,3 +1,32 @@ +

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

Update the Discourse account

diff --git a/views/guides/discourse.title.php b/views/guides/discourse.title.php index f8016e3..3522d31 100644 --- a/views/guides/discourse.title.php +++ b/views/guides/discourse.title.php @@ -1 +1,30 @@ + Adding a Discourse proof diff --git a/views/guides/dns.content.php b/views/guides/dns.content.php index aa6fc08..f0b7caf 100644 --- a/views/guides/dns.content.php +++ b/views/guides/dns.content.php @@ -1,3 +1,32 @@ +

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

Update DNS records for your website

diff --git a/views/guides/dns.title.php b/views/guides/dns.title.php index d246865..9f64349 100644 --- a/views/guides/dns.title.php +++ b/views/guides/dns.title.php @@ -1 +1,30 @@ + Adding a DNS proof diff --git a/views/guides/encrypt.content.php b/views/guides/encrypt.content.php index 188db5f..dc928ff 100644 --- a/views/guides/encrypt.content.php +++ b/views/guides/encrypt.content.php @@ -1,3 +1,32 @@ +

Let's see how to encrypt a message.

Obtain a public key for encryption

diff --git a/views/guides/encrypt.title.php b/views/guides/encrypt.title.php index 3e98564..f3283e4 100644 --- a/views/guides/encrypt.title.php +++ b/views/guides/encrypt.title.php @@ -1 +1,30 @@ + Encrypting a message diff --git a/views/guides/feature-comparison-keybase.content.php b/views/guides/feature-comparison-keybase.content.php index 1c25664..98522e3 100644 --- a/views/guides/feature-comparison-keybase.content.php +++ b/views/guides/feature-comparison-keybase.content.php @@ -1,3 +1,32 @@ +

Let's see how Keyoxide's features compare to those of Keybase.

Encrypt and verify

diff --git a/views/guides/feature-comparison-keybase.title.php b/views/guides/feature-comparison-keybase.title.php index 604a124..a344d6d 100644 --- a/views/guides/feature-comparison-keybase.title.php +++ b/views/guides/feature-comparison-keybase.title.php @@ -1 +1,30 @@ + Feature comparison with Keybase diff --git a/views/guides/github.content.php b/views/guides/github.content.php index 9fdc0fe..285f666 100644 --- a/views/guides/github.content.php +++ b/views/guides/github.content.php @@ -1,3 +1,32 @@ +

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

Post a Github proof message

diff --git a/views/guides/github.title.php b/views/guides/github.title.php index c607227..b471bc6 100644 --- a/views/guides/github.title.php +++ b/views/guides/github.title.php @@ -1 +1,30 @@ + Adding a Github proof diff --git a/views/guides/hackernews.content.php b/views/guides/hackernews.content.php index 678754a..72a9ba3 100644 --- a/views/guides/hackernews.content.php +++ b/views/guides/hackernews.content.php @@ -1,3 +1,32 @@ +

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

Update the Hackernews account

diff --git a/views/guides/hackernews.title.php b/views/guides/hackernews.title.php index a968901..ccacdcc 100644 --- a/views/guides/hackernews.title.php +++ b/views/guides/hackernews.title.php @@ -1 +1,30 @@ + Adding a Hackernews proof diff --git a/views/guides/lobsters.content.php b/views/guides/lobsters.content.php index 831b3d1..b6a708b 100644 --- a/views/guides/lobsters.content.php +++ b/views/guides/lobsters.content.php @@ -1,3 +1,32 @@ +

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

Update the Lobste.rs account

diff --git a/views/guides/lobsters.title.php b/views/guides/lobsters.title.php index 5837a75..4f4727e 100644 --- a/views/guides/lobsters.title.php +++ b/views/guides/lobsters.title.php @@ -1 +1,30 @@ + Adding a Lobste.rs proof diff --git a/views/guides/managing-proofs-deleting.content.php b/views/guides/managing-proofs-deleting.content.php index 1e8c99c..a196e2a 100644 --- a/views/guides/managing-proofs-deleting.content.php +++ b/views/guides/managing-proofs-deleting.content.php @@ -1,3 +1,32 @@ +

Over time, you may need to delete proofs. Changing proofs can be achieved by deleting proofs and adding new ones.

Delete all proofs

diff --git a/views/guides/managing-proofs-deleting.title.php b/views/guides/managing-proofs-deleting.title.php index 62440b4..c656c4e 100644 --- a/views/guides/managing-proofs-deleting.title.php +++ b/views/guides/managing-proofs-deleting.title.php @@ -1 +1,30 @@ + Deleting Proofs using GnuPG diff --git a/views/guides/managing-proofs-listing.content.php b/views/guides/managing-proofs-listing.content.php index 2765799..c1895f1 100644 --- a/views/guides/managing-proofs-listing.content.php +++ b/views/guides/managing-proofs-listing.content.php @@ -1,3 +1,32 @@ +

Let's list the identity proofs stored in our OpenPGP keys.

Listing notations in GnuPG

diff --git a/views/guides/managing-proofs-listing.title.php b/views/guides/managing-proofs-listing.title.php index 33308f0..f869e75 100644 --- a/views/guides/managing-proofs-listing.title.php +++ b/views/guides/managing-proofs-listing.title.php @@ -1 +1,30 @@ + Listing Proofs using GnuPG diff --git a/views/guides/mastodon.content.php b/views/guides/mastodon.content.php index 0610f30..fed925e 100644 --- a/views/guides/mastodon.content.php +++ b/views/guides/mastodon.content.php @@ -1,3 +1,32 @@ +

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

Update the Mastodon account

diff --git a/views/guides/mastodon.title.php b/views/guides/mastodon.title.php index d720d5b..c65d52e 100644 --- a/views/guides/mastodon.title.php +++ b/views/guides/mastodon.title.php @@ -1 +1,30 @@ + Adding a Mastodon proof diff --git a/views/guides/migrating-from-keybase.content.php b/views/guides/migrating-from-keybase.content.php index e08a257..c440394 100644 --- a/views/guides/migrating-from-keybase.content.php +++ b/views/guides/migrating-from-keybase.content.php @@ -1,3 +1,32 @@ +

Let's see how easy it is to get a Keyoxide profile when you already have a Keybase account.

Claim your Keyoxide profile

diff --git a/views/guides/migrating-from-keybase.title.php b/views/guides/migrating-from-keybase.title.php index 1a0ecfb..330fa5f 100644 --- a/views/guides/migrating-from-keybase.title.php +++ b/views/guides/migrating-from-keybase.title.php @@ -1 +1,30 @@ + Migrating from Keybase diff --git a/views/guides/openpgp-proofs.content.php b/views/guides/openpgp-proofs.content.php index 80eba2f..99de832 100644 --- a/views/guides/openpgp-proofs.content.php +++ b/views/guides/openpgp-proofs.content.php @@ -1,3 +1,32 @@ +

Decentralized OpenPGP identity proofs

Decentralized OpenPGP identity proofs are the brainchild of Wiktor who wrote the original guide on his website (a suggested read to get first-hand information).

diff --git a/views/guides/openpgp-proofs.title.php b/views/guides/openpgp-proofs.title.php index ee02576..915e7cb 100644 --- a/views/guides/openpgp-proofs.title.php +++ b/views/guides/openpgp-proofs.title.php @@ -1 +1,30 @@ + How OpenPGP identity proofs work diff --git a/views/guides/pixelfed.content.php b/views/guides/pixelfed.content.php index f833cd3..207111f 100644 --- a/views/guides/pixelfed.content.php +++ b/views/guides/pixelfed.content.php @@ -1,3 +1,32 @@ +

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

Update the Pixelfed account

diff --git a/views/guides/pixelfed.title.php b/views/guides/pixelfed.title.php index 943c44f..f58c249 100644 --- a/views/guides/pixelfed.title.php +++ b/views/guides/pixelfed.title.php @@ -1 +1,30 @@ + Adding a Pixelfed proof diff --git a/views/guides/pleroma.content.php b/views/guides/pleroma.content.php index 7ad3835..75ec8fe 100644 --- a/views/guides/pleroma.content.php +++ b/views/guides/pleroma.content.php @@ -1,3 +1,32 @@ +

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

Update the Pleroma account

diff --git a/views/guides/pleroma.title.php b/views/guides/pleroma.title.php index 23b0fef..0233832 100644 --- a/views/guides/pleroma.title.php +++ b/views/guides/pleroma.title.php @@ -1 +1,30 @@ + Adding a Pleroma proof diff --git a/views/guides/proofs.content.php b/views/guides/proofs.content.php index 2fcf41c..3092158 100644 --- a/views/guides/proofs.content.php +++ b/views/guides/proofs.content.php @@ -1,3 +1,32 @@ +

Let's see how to verify identity proofs.

Obtain a public key for verification

diff --git a/views/guides/proofs.title.php b/views/guides/proofs.title.php index 3a62919..67356b9 100644 --- a/views/guides/proofs.title.php +++ b/views/guides/proofs.title.php @@ -1 +1,30 @@ + Verifying identity proofs diff --git a/views/guides/reddit.content.php b/views/guides/reddit.content.php index 091e6de..c5296c3 100644 --- a/views/guides/reddit.content.php +++ b/views/guides/reddit.content.php @@ -1,3 +1,32 @@ +

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

Post a Reddit proof message

diff --git a/views/guides/reddit.title.php b/views/guides/reddit.title.php index d8c6d90..a056121 100644 --- a/views/guides/reddit.title.php +++ b/views/guides/reddit.title.php @@ -1 +1,30 @@ + Adding a Reddit proof diff --git a/views/guides/self-hosting-keyoxide.content.php b/views/guides/self-hosting-keyoxide.content.php index 942d3db..58a374c 100644 --- a/views/guides/self-hosting-keyoxide.content.php +++ b/views/guides/self-hosting-keyoxide.content.php @@ -1,3 +1,32 @@ +

Though it's not a fully supported use case yet, anyone can take the source code and put it on their own server. The idea is that Keyoxide.org is not special in itself. After all, all the heavy lifting is done by the browser. So the role of any individual Keyoxide server is to get the tool in the hands of the end user.

The few supporting roles the server has can easily be performed by any other (PHP) server.

diff --git a/views/guides/self-hosting-keyoxide.title.php b/views/guides/self-hosting-keyoxide.title.php index 2be94ce..84e4310 100644 --- a/views/guides/self-hosting-keyoxide.title.php +++ b/views/guides/self-hosting-keyoxide.title.php @@ -1 +1,30 @@ + Self-hosting Keyoxide diff --git a/views/guides/service-provider.content.php b/views/guides/service-provider.content.php index 4673932..0b63681 100644 --- a/views/guides/service-provider.content.php +++ b/views/guides/service-provider.content.php @@ -1,3 +1,32 @@ +

If you have:

    diff --git a/views/guides/service-provider.title.php b/views/guides/service-provider.title.php index 4e52f7b..3e0a57a 100644 --- a/views/guides/service-provider.title.php +++ b/views/guides/service-provider.title.php @@ -1 +1,30 @@ + Are you a service provider? diff --git a/views/guides/twitter.content.php b/views/guides/twitter.content.php index 8d7c3ba..4ddfbc1 100644 --- a/views/guides/twitter.content.php +++ b/views/guides/twitter.content.php @@ -1,3 +1,32 @@ +

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

    Post a Twitter proof message

    diff --git a/views/guides/twitter.title.php b/views/guides/twitter.title.php index b06e8d2..33192f3 100644 --- a/views/guides/twitter.title.php +++ b/views/guides/twitter.title.php @@ -1 +1,30 @@ + Adding a Twitter proof diff --git a/views/guides/verify.content.php b/views/guides/verify.content.php index 19e1473..5ac232d 100644 --- a/views/guides/verify.content.php +++ b/views/guides/verify.content.php @@ -1,3 +1,32 @@ +

    Let's see how to verify an OpenPGP signature.

    Obtain a signature

    diff --git a/views/guides/verify.title.php b/views/guides/verify.title.php index 1d01185..2ece31e 100644 --- a/views/guides/verify.title.php +++ b/views/guides/verify.title.php @@ -1 +1,30 @@ + Verifying a signature diff --git a/views/guides/web-key-directory.content.php b/views/guides/web-key-directory.content.php index ecc5059..1727d0e 100644 --- a/views/guides/web-key-directory.content.php +++ b/views/guides/web-key-directory.content.php @@ -1,3 +1,32 @@ +

    Web key directory

    Web key directory or WKD refers to the method of uploading one's public key to their website in a specific location to make it easily accessible by other services supporting WKD. The key will be discoverable using an identifier similar to an email address: username@domain.org.

    diff --git a/views/guides/web-key-directory.title.php b/views/guides/web-key-directory.title.php index 4fb4a59..14a6d18 100644 --- a/views/guides/web-key-directory.title.php +++ b/views/guides/web-key-directory.title.php @@ -1 +1,30 @@ + Uploading keys using web key directory diff --git a/views/guides/xmpp.content.php b/views/guides/xmpp.content.php index 21a4db1..78d9028 100644 --- a/views/guides/xmpp.content.php +++ b/views/guides/xmpp.content.php @@ -1,3 +1,32 @@ +

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

    Add a message to your XMPP vCard

    diff --git a/views/guides/xmpp.title.php b/views/guides/xmpp.title.php index 4ba3347..e5139c7 100644 --- a/views/guides/xmpp.title.php +++ b/views/guides/xmpp.title.php @@ -1 +1,30 @@ + Adding a XMPP proof diff --git a/views/index.php b/views/index.php index 16e5b53..b2f43d8 100644 --- a/views/index.php +++ b/views/index.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
    diff --git a/views/profile.php b/views/profile.php index 874985c..33a59c4 100644 --- a/views/profile.php +++ b/views/profile.php @@ -1,3 +1,32 @@ + diff --git a/views/proofs.php b/views/proofs.php index 134708e..9cb61ca 100644 --- a/views/proofs.php +++ b/views/proofs.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
    diff --git a/views/template.base.php b/views/template.base.php index 1842623..9ae08fb 100644 --- a/views/template.base.php +++ b/views/template.base.php @@ -1,3 +1,32 @@ + diff --git a/views/util/profile-url.php b/views/util/profile-url.php index 824952c..adadcff 100644 --- a/views/util/profile-url.php +++ b/views/util/profile-url.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
    diff --git a/views/util/qr.php b/views/util/qr.php index 8b5a2af..b3388f1 100644 --- a/views/util/qr.php +++ b/views/util/qr.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
    diff --git a/views/util/qrfp.php b/views/util/qrfp.php index b542128..a13792a 100644 --- a/views/util/qrfp.php +++ b/views/util/qrfp.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
    diff --git a/views/util/wkd.php b/views/util/wkd.php index fbb747f..6b57c60 100644 --- a/views/util/wkd.php +++ b/views/util/wkd.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>
    diff --git a/views/verify.php b/views/verify.php index 914b6e4..50f242c 100644 --- a/views/verify.php +++ b/views/verify.php @@ -1,3 +1,32 @@ + layout('template.base', ['title' => $title]) ?>