diff --git a/index.php b/index.php index 24d8ca2..c084c54 100644 --- a/index.php +++ b/index.php @@ -1,32 +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 . +?> . - -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 . - --> +. +// +// 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 20f12b9..bbd13cb 100644 --- a/views/encrypt.php +++ b/views/encrypt.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
diff --git a/views/faq.php b/views/faq.php index 63c0ceb..c71f2f3 100644 --- a/views/faq.php +++ b/views/faq.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
diff --git a/views/guide.php b/views/guide.php index cb8a804..66dfc0c 100644 --- a/views/guide.php +++ b/views/guide.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
diff --git a/views/guides.php b/views/guides.php index 8256d5b..dfbdc4e 100644 --- a/views/guides.php +++ b/views/guides.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
diff --git a/views/guides/contributing.content.php b/views/guides/contributing.content.php index 8b54de3..9c4050b 100644 --- a/views/guides/contributing.content.php +++ b/views/guides/contributing.content.php @@ -1,32 +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 . +?>

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 cb67f8a..30c816f 100644 --- a/views/guides/contributing.title.php +++ b/views/guides/contributing.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Contributing to Keyoxide diff --git a/views/guides/devto.content.php b/views/guides/devto.content.php index 9628da3..924c9b8 100644 --- a/views/guides/devto.content.php +++ b/views/guides/devto.content.php @@ -1,32 +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 . +?>

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 0277e50..343cdff 100644 --- a/views/guides/devto.title.php +++ b/views/guides/devto.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a dev.to proof diff --git a/views/guides/discourse.content.php b/views/guides/discourse.content.php index cc69604..bcc40c7 100644 --- a/views/guides/discourse.content.php +++ b/views/guides/discourse.content.php @@ -1,32 +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 . +?>

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 3522d31..37a82ab 100644 --- a/views/guides/discourse.title.php +++ b/views/guides/discourse.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Discourse proof diff --git a/views/guides/dns.content.php b/views/guides/dns.content.php index f0b7caf..7eaa37e 100644 --- a/views/guides/dns.content.php +++ b/views/guides/dns.content.php @@ -1,32 +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 . +?>

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 9f64349..aaad4bf 100644 --- a/views/guides/dns.title.php +++ b/views/guides/dns.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a DNS proof diff --git a/views/guides/encrypt.content.php b/views/guides/encrypt.content.php index dc928ff..1b2a62d 100644 --- a/views/guides/encrypt.content.php +++ b/views/guides/encrypt.content.php @@ -1,32 +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 . +?>

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 f3283e4..737e3d5 100644 --- a/views/guides/encrypt.title.php +++ b/views/guides/encrypt.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Encrypting a message diff --git a/views/guides/feature-comparison-keybase.content.php b/views/guides/feature-comparison-keybase.content.php index 98522e3..cfd8590 100644 --- a/views/guides/feature-comparison-keybase.content.php +++ b/views/guides/feature-comparison-keybase.content.php @@ -1,32 +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 . +?>

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 a344d6d..6abf001 100644 --- a/views/guides/feature-comparison-keybase.title.php +++ b/views/guides/feature-comparison-keybase.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Feature comparison with Keybase diff --git a/views/guides/github.content.php b/views/guides/github.content.php index 285f666..bafcfca 100644 --- a/views/guides/github.content.php +++ b/views/guides/github.content.php @@ -1,32 +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 . +?>

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 b471bc6..b6da803 100644 --- a/views/guides/github.title.php +++ b/views/guides/github.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Github proof diff --git a/views/guides/hackernews.content.php b/views/guides/hackernews.content.php index 72a9ba3..5cd12bd 100644 --- a/views/guides/hackernews.content.php +++ b/views/guides/hackernews.content.php @@ -1,32 +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 . +?>

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 ccacdcc..7839be7 100644 --- a/views/guides/hackernews.title.php +++ b/views/guides/hackernews.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Hackernews proof diff --git a/views/guides/lobsters.content.php b/views/guides/lobsters.content.php index b6a708b..4701bd6 100644 --- a/views/guides/lobsters.content.php +++ b/views/guides/lobsters.content.php @@ -1,32 +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 . +?>

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 4f4727e..5eef758 100644 --- a/views/guides/lobsters.title.php +++ b/views/guides/lobsters.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Lobste.rs proof diff --git a/views/guides/managing-proofs-deleting.content.php b/views/guides/managing-proofs-deleting.content.php index a196e2a..f397895 100644 --- a/views/guides/managing-proofs-deleting.content.php +++ b/views/guides/managing-proofs-deleting.content.php @@ -1,32 +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 . +?>

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 c656c4e..19040a5 100644 --- a/views/guides/managing-proofs-deleting.title.php +++ b/views/guides/managing-proofs-deleting.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Deleting Proofs using GnuPG diff --git a/views/guides/managing-proofs-listing.content.php b/views/guides/managing-proofs-listing.content.php index c1895f1..1e5682e 100644 --- a/views/guides/managing-proofs-listing.content.php +++ b/views/guides/managing-proofs-listing.content.php @@ -1,32 +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 . +?>

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 f869e75..a819fe3 100644 --- a/views/guides/managing-proofs-listing.title.php +++ b/views/guides/managing-proofs-listing.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Listing Proofs using GnuPG diff --git a/views/guides/mastodon.content.php b/views/guides/mastodon.content.php index fed925e..0b10611 100644 --- a/views/guides/mastodon.content.php +++ b/views/guides/mastodon.content.php @@ -1,32 +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 . +?>

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 c65d52e..8d6e727 100644 --- a/views/guides/mastodon.title.php +++ b/views/guides/mastodon.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Mastodon proof diff --git a/views/guides/migrating-from-keybase.content.php b/views/guides/migrating-from-keybase.content.php index c440394..3ea3763 100644 --- a/views/guides/migrating-from-keybase.content.php +++ b/views/guides/migrating-from-keybase.content.php @@ -1,32 +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 . +?>

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 330fa5f..cccab0f 100644 --- a/views/guides/migrating-from-keybase.title.php +++ b/views/guides/migrating-from-keybase.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Migrating from Keybase diff --git a/views/guides/openpgp-proofs.content.php b/views/guides/openpgp-proofs.content.php index 99de832..932f5cc 100644 --- a/views/guides/openpgp-proofs.content.php +++ b/views/guides/openpgp-proofs.content.php @@ -1,32 +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 . +?>

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 915e7cb..33c49d6 100644 --- a/views/guides/openpgp-proofs.title.php +++ b/views/guides/openpgp-proofs.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> How OpenPGP identity proofs work diff --git a/views/guides/pixelfed.content.php b/views/guides/pixelfed.content.php index 207111f..cce1f78 100644 --- a/views/guides/pixelfed.content.php +++ b/views/guides/pixelfed.content.php @@ -1,32 +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 . +?>

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 f58c249..5f9c5a8 100644 --- a/views/guides/pixelfed.title.php +++ b/views/guides/pixelfed.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Pixelfed proof diff --git a/views/guides/pleroma.content.php b/views/guides/pleroma.content.php index 75ec8fe..86a0e02 100644 --- a/views/guides/pleroma.content.php +++ b/views/guides/pleroma.content.php @@ -1,32 +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 . +?>

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 0233832..e43bcfe 100644 --- a/views/guides/pleroma.title.php +++ b/views/guides/pleroma.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Pleroma proof diff --git a/views/guides/proofs.content.php b/views/guides/proofs.content.php index 3092158..9ae7faf 100644 --- a/views/guides/proofs.content.php +++ b/views/guides/proofs.content.php @@ -1,32 +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 . +?>

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 67356b9..24f9eee 100644 --- a/views/guides/proofs.title.php +++ b/views/guides/proofs.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Verifying identity proofs diff --git a/views/guides/reddit.content.php b/views/guides/reddit.content.php index c5296c3..241e9db 100644 --- a/views/guides/reddit.content.php +++ b/views/guides/reddit.content.php @@ -1,32 +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 . +?>

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 a056121..8905a41 100644 --- a/views/guides/reddit.title.php +++ b/views/guides/reddit.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Reddit proof diff --git a/views/guides/self-hosting-keyoxide.content.php b/views/guides/self-hosting-keyoxide.content.php index 58a374c..c648667 100644 --- a/views/guides/self-hosting-keyoxide.content.php +++ b/views/guides/self-hosting-keyoxide.content.php @@ -1,32 +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 . +?>

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 84e4310..7a68760 100644 --- a/views/guides/self-hosting-keyoxide.title.php +++ b/views/guides/self-hosting-keyoxide.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Self-hosting Keyoxide diff --git a/views/guides/service-provider.content.php b/views/guides/service-provider.content.php index 0b63681..4cb2adf 100644 --- a/views/guides/service-provider.content.php +++ b/views/guides/service-provider.content.php @@ -1,32 +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 . +?>

If you have:

    diff --git a/views/guides/service-provider.title.php b/views/guides/service-provider.title.php index 3e0a57a..f6dd961 100644 --- a/views/guides/service-provider.title.php +++ b/views/guides/service-provider.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Are you a service provider? diff --git a/views/guides/twitter.content.php b/views/guides/twitter.content.php index 4ddfbc1..85ab198 100644 --- a/views/guides/twitter.content.php +++ b/views/guides/twitter.content.php @@ -1,32 +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 . +?>

    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 33192f3..7dec5fa 100644 --- a/views/guides/twitter.title.php +++ b/views/guides/twitter.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a Twitter proof diff --git a/views/guides/verify.content.php b/views/guides/verify.content.php index 5ac232d..9b67a1f 100644 --- a/views/guides/verify.content.php +++ b/views/guides/verify.content.php @@ -1,32 +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 . +?>

    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 2ece31e..0f14f40 100644 --- a/views/guides/verify.title.php +++ b/views/guides/verify.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Verifying a signature diff --git a/views/guides/web-key-directory.content.php b/views/guides/web-key-directory.content.php index 1727d0e..16b18ef 100644 --- a/views/guides/web-key-directory.content.php +++ b/views/guides/web-key-directory.content.php @@ -1,32 +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 . +?>

    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 14a6d18..b83b792 100644 --- a/views/guides/web-key-directory.title.php +++ b/views/guides/web-key-directory.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Uploading keys using web key directory diff --git a/views/guides/xmpp.content.php b/views/guides/xmpp.content.php index 78d9028..a32a397 100644 --- a/views/guides/xmpp.content.php +++ b/views/guides/xmpp.content.php @@ -1,32 +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 . +?>

    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 e5139c7..f27dbf7 100644 --- a/views/guides/xmpp.title.php +++ b/views/guides/xmpp.title.php @@ -1,30 +1,30 @@ - +. +// +// 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 . +?> Adding a XMPP proof diff --git a/views/index.php b/views/index.php index b2f43d8..f29d1f1 100644 --- a/views/index.php +++ b/views/index.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
    diff --git a/views/profile.php b/views/profile.php index 33a59c4..338e8c2 100644 --- a/views/profile.php +++ b/views/profile.php @@ -1,32 +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 . +?> diff --git a/views/proofs.php b/views/proofs.php index 9cb61ca..2783706 100644 --- a/views/proofs.php +++ b/views/proofs.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
    diff --git a/views/template.base.php b/views/template.base.php index 9ae08fb..37803a6 100644 --- a/views/template.base.php +++ b/views/template.base.php @@ -1,32 +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 . +?> diff --git a/views/util/profile-url.php b/views/util/profile-url.php index adadcff..92f2fd8 100644 --- a/views/util/profile-url.php +++ b/views/util/profile-url.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
    diff --git a/views/util/qr.php b/views/util/qr.php index b3388f1..d3c1c64 100644 --- a/views/util/qr.php +++ b/views/util/qr.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
    diff --git a/views/util/qrfp.php b/views/util/qrfp.php index a13792a..3a1f06e 100644 --- a/views/util/qrfp.php +++ b/views/util/qrfp.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
    diff --git a/views/util/wkd.php b/views/util/wkd.php index 6b57c60..e440282 100644 --- a/views/util/wkd.php +++ b/views/util/wkd.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>
    diff --git a/views/verify.php b/views/verify.php index 50f242c..e31afd2 100644 --- a/views/verify.php +++ b/views/verify.php @@ -1,32 +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 . +?> layout('template.base', ['title' => $title]) ?>