Just a quick blog post about Wordpress configuration, mostly as a reminder to myself.
If you manage a public website, you probably want it to include some HTML metadata: it is important for referencing your website in search engines, as well as to provide a nice "preview miniature" on social …
Useful Firefox addon
If you don't want people to save things to Pinterest from your website, just paste this code into the
<head>section of any page on your site:
<meta name="pinterest" content="nopin" />When someone tries to save things to Pinterest from your site, they'll see: "This site doesn't allow saving to Pinterest. Please contact the owner with any questions. Thanks for visiting!"
There already are multiple blogging solutions which are part of the Fediverse.
ActivityPub, the network protocol behind the Fediverse can only be fully implemented by means of an active server component: Among other things, incoming messages delivered to inboxes have to be processed. Sometimes they need to be forwarded, and outgoing messages need to be signed.
Nevertheless I wanted to figure out, which parts of the ActivityPub protocol can be implemented in a purely static website, and how well other servers in the Fediverse interact with it. My goal was to attach this blog to the Fediverse. The blog is generated using the static site generator software Pelican.
Key point: this isn’t (just) about PGP or SMTP, it’s email as a whole system:
Even after we replace PGP, encrypted email will remain unsafe. Here’s why:
- If messages can be sent in plaintext, they will be sent in plaintext.
- Metadata is as important as content, and email leaks it.
- Every archived message will eventually leak.
- Every long term secret will eventually leak.
Every element I use for the basic structure of a HTML document, with explanations why.