diff --git a/Makefile b/Makefile
index 8389dbc..f67ce77 100644
--- a/Makefile
+++ b/Makefile
@@ -35,6 +35,7 @@ install: index.html $(PAGES) themegallery.html $(BLOG_POSTS_OUT) $(BLOG_POST_OU
install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_TOP_DIR) $(BLOG_POST_OUT_TOP_DIR)/index.html
install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_DIR) $(BLOG_POST_OUT_DIR)/*.html
install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_DIR)/img $(BLOG_POST_OUT_DIR)/img/*.png
+ install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_DIR)/img $(BLOG_POST_OUT_DIR)/img/*.jpeg
install -m0444 -p -D -t $(PREFIX)/$(CONTRIBUTORS_OUT_DIR) $(CONTRIBUTORS_OUT_DIR)/*.html
install -m0444 -p -D -t $(PREFIX)/$(CONTRIBUTORS_OUT_DIR)/img $(CONTRIBUTORS_OUT_DIR)/img/*jpg
cp -p -r css $(PREFIX)
diff --git a/blogsource/content/post/distrobox.md b/blogsource/content/post/distrobox.md
index 87fccc3..de296a4 100644
--- a/blogsource/content/post/distrobox.md
+++ b/blogsource/content/post/distrobox.md
@@ -40,6 +40,7 @@ profanity-on-tw
```
We can now enter this container and install profanity in it via:
+
```
host$ distrobox-enter profanity-on-tw
Container profanity-on-tw is not running.
@@ -142,6 +143,7 @@ Type `exit` to get out.
# Usage
Each time you want to start profanity you now have to do enter the container and start it there:
+
```
host$ distrobox-enter profanity-on-tw
profanity-on-tw$ profanity
diff --git a/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md b/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md
index 38d27a1..48c6627 100644
--- a/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md
+++ b/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md
@@ -1,7 +1,7 @@
---
title: How to run profanity instances within tmux
date: 2020-03-03T14:49:55+01:00
-authors: debxwoody
+authors: debxwoody
---
If you have more than one XMPP account, you may run one profanity process per
diff --git a/blogsource/content/post/lmc.md b/blogsource/content/post/lmc.md
index 7e1062f..4fc32e3 100644
--- a/blogsource/content/post/lmc.md
+++ b/blogsource/content/post/lmc.md
@@ -1,14 +1,13 @@
---
title: "Last Message Correction"
date: 2020-02-14T11:34:38+01:00
-authors:
- - jubalh
+authors: jubalh
---
-From 10th to 14th February 2020 we had [Hackweek 19](https://hackweek.suse.com/19/projects) at SUSE.
+From 10th to 14th February 2020 we had [Hackweek 19](https://web.archive.org/web/20210728133610/https://hackweek.suse.com/19/projects) at SUSE.
Part of that time I used to finally implement the long (since 2016!) [sought after](https://github.com/profanity-im/profanity/issues/805) Last Message Correction feature, aka [XEP-0308](https://xmpp.org/extensions/xep-0308.html).
-See my [Hackweek project](https://hackweek.suse.com/projects/implement-xep-0308-last-message-correction-in-profanity) and the corresponding [pull request](https://github.com/profanity-im/profanity/pull/1267).
+See my [Hackweek project](https://web.archive.org/web/20210423141452/https://hackweek.suse.com/projects/implement-xep-0308-last-message-correction-in-profanity) and the corresponding [pull request](https://github.com/profanity-im/profanity/pull/1267).
## Usage
To enable incoming and outgoing corrections users need to enable it with `/correction on`, see `/help correction` for more details.
diff --git a/blogsource/content/post/new-mailing-list.md b/blogsource/content/post/new-mailing-list.md
index eaf4dd8..951cff1 100644
--- a/blogsource/content/post/new-mailing-list.md
+++ b/blogsource/content/post/new-mailing-list.md
@@ -4,8 +4,8 @@ date: 2020-04-19T22:50:18+02:00
authors: jubalh
---
-I would like to announce that thanks to [toogley](https://github.com/toogley) we have a new mailing list.
-You can register on https://lists.notraces.net/mailman/listinfo/profanity
+I would like to announce that thanks to [toogley](https://web.archive.org/web/20210512220718/https://github.com/toogley) we have a new mailing list.
+You can register on [https://lists.notraces.net/mailman/listinfo/profanity](https://web.archive.org/web/20221019152740/https://lists.notraces.net/mailman/listinfo/profanity)
The list is hosted by [datenkollektiv](https://www.datenkollektiv.net/).
diff --git a/blogsource/content/post/omemo.md b/blogsource/content/post/omemo.md
index 5c9db70..54fd513 100644
--- a/blogsource/content/post/omemo.md
+++ b/blogsource/content/post/omemo.md
@@ -1,7 +1,7 @@
---
title: OMEMO
date: 2020-11-27T17:14:07+01:00
-authors: debxwoody
+authors: debxwoody
---
OMEMO with profanity.
diff --git a/blogsource/content/post/profanity-on-pinephone.md b/blogsource/content/post/profanity-on-pinephone.md
index 5e915d9..14885d4 100644
--- a/blogsource/content/post/profanity-on-pinephone.md
+++ b/blogsource/content/post/profanity-on-pinephone.md
@@ -25,7 +25,7 @@ I also decided to check profanity as I use it on my home server and it works per
But, I still had a trouble scrolling the main window in profanity
-[video: ppkb keyboard issue](https://kraut.zone/w/6jG9F41Z7nNUZLFdHE43cN)
+[video: ppkb keyboard issue (video unavailable)](https://kraut.zone/w/6jG9F41Z7nNUZLFdHE43cN)
I looked at [profanity keybindings](http://www.profanity.im/keybindings.html) and in the `User Interface Navigation` section I found that I should use `PageUp/PageDown` keys, but looking at [Pinephone wiki](https://wiki.pine64.org/wiki/PinePhone_(Pro)_Keyboard#Keyboard_layout) this keyboard does not have `PageUp/PageDown` keys.
@@ -49,7 +49,7 @@ After starting profanity, I was able to scroll window with content using followi
- `C-j` - scroll up
- `C-k` - to scroll down
-[video: ppkb keyboard scroll](https://kraut.zone/w/fA2LeeRRmonkHVB5d3NMYe)
+[video: ppkb keyboard scroll (video unavailable)](https://kraut.zone/w/fA2LeeRRmonkHVB5d3NMYe)
Here you can see some photos.
diff --git a/blogsource/content/post/release-0100.md b/blogsource/content/post/release-0100.md
index 4b04229..64d91aa 100644
--- a/blogsource/content/post/release-0100.md
+++ b/blogsource/content/post/release-0100.md
@@ -16,13 +16,13 @@ I also would like to express my gratitude to my sponsors [mdosch](https://github
This release bumped a few dependencies. Namely: libstrophe/libmesode >= 0.10.0, glib >= 2.62 sqlite >= 3.22 and gtk3 >= 3.24 (or gtk2 >= 2.24.10).
## Roadmap
-The roadmap for 0.10.0 was announced on our [mailing list](https://lists.notraces.net/pipermail/profanity/2020/000018.html). The goal was mainly cleanupg and fixes.
+The roadmap for 0.10.0 was announced on our [mailing list](https://web.archive.org/web/20201020033248/https://lists.notraces.net/pipermail/profanity/2020/000018.html). The goal was mainly cleanup and fixes.
## Contributing to Profanity
-To make it easier for newcomers to contribue to Profanity we added a [Contributing](https://github.com/profanity-im/profanity/blob/master/CONTRIBUTING.md) file which has, as we hope, some quite important information on how to get started. And about our workflow.
+To make it easier for newcomers to contribute to Profanity we added a [Contributing](https://github.com/profanity-im/profanity/blob/master/CONTRIBUTING.md) file which has, as we hope, some quite important information on how to get started. And about our workflow.
## NetBSD
-It is also the first official Proanity release that got NetBSD support.
+It is also the first official Profanity release that got NetBSD support.
## OMEMO
You can now sent OMEMO encrypted files via `/sendfile`.
diff --git a/blogsource/content/post/release-080.md b/blogsource/content/post/release-080.md
index 6eda28c..f3f3fc0 100644
--- a/blogsource/content/post/release-080.md
+++ b/blogsource/content/post/release-080.md
@@ -13,7 +13,7 @@ It's released five months after 0.7.0 and has 295 commits since then.
Also more and more people contribute to Profanity's development. A big thanks to:
[@paulfariello](https://github.com/paulfariello), [@svensp](https://github.com/svensp), [@aaptel](https://github.com/aaptel), [@aszlig](https://github.com/), [@mdosch](https://github.com/mdosch), [@pasis](https://github.com/pasis), [@mzagozen](https://github.com/mzagozen), [@quite](https://github.com/quite), [@weiss](https://github.com/weiss), [@Misaflo](https://github.com/Misaflo) and [@jubalh](https://github.com/).
-
+
## New features
We got fingerprint autocompletion for the `/omemo trust` command.
diff --git a/blogsource/content/post/release-090.md b/blogsource/content/post/release-090.md
index 5a316d3..4d8bd4d 100644
--- a/blogsource/content/post/release-090.md
+++ b/blogsource/content/post/release-090.md
@@ -6,7 +6,7 @@ authors: jubalh
Four months and 350 commits after 0.8.1 we are happy to release [0.9.0](https://github.com/profanity-im/profanity/releases/tag/0.9.0).
-7 people contributed code to it: [pasis](https://github.com/pasis), [wstrm](https://github.com/wstrm), [DebXWoody](https://github.com/DebXWoody), [toogley](https://github.com/toogley), [pmaziere](https://github.com/pmaziere), [moppman](https://github.com/moppman) and [jubalh](https://github.com/jubalh).
+7 people contributed code to it: [pasis](https://github.com/pasis), [wstrm](https://github.com/wstrm), [DebXWoody](https://github.com/DebXWoody), [toogley](https://web.archive.org/web/20210512220718/https://github.com/toogley), [pmaziere](https://github.com/pmaziere), [moppman](https://github.com/moppman) and [jubalh](https://github.com/jubalh).
Thanks to everybody who was involved, be it testing, writing documentation, updating the website or whatever you did!
I also would like to express my gratitude to my sponsors [mdosch](https://github.com/mdosch) and [wstrm](https://github.com/wstrm)!
@@ -31,7 +31,7 @@ Hopefully this is useful for our testers!
The new `-t` option will let you select a theme right at startup: `/profanity -t bios`.
This is useful if you run multiple instances of Profanity. Maybe you have multiple accounts and want to visually destinguish between them.
-Did you know we have a [blogpost](https://profanity-im.github.io/blog/post/how-to-run-profanity-instances-within-tmux/) that should help you create such a setup with tmux?
+Did you know we have a [blogpost](https://profanity-im.github.io/blog/post/how-to-run-profanity-instances-within-tmux.html) that should help you create such a setup with tmux?
## Titlebar
Previously you could choose whether to display the MUC name or MUC title in the titlebar. Now you can choose to do both or neither.
diff --git a/css/profanity.css b/css/profanity.css
index 2d52098..83a5f16 100644
--- a/css/profanity.css
+++ b/css/profanity.css
@@ -716,7 +716,7 @@ article#manual ol,article#manual ul{
list-style:none
}
#Zoomer{
- background:rgba(0,0,0,.5) url(../images/stripey-dark.png) repeat;
+ background:rgba(0,0,0,.5);
display:none;
height:100%;
margin-left:-1.8em;
@@ -739,17 +739,6 @@ article#manual ol,article#manual ul{
max-width:100%;
width:auto
}
-#Zoomer .control-icon{
- background:url(../images/close-button.svg);
- background-size:contain;
- height:5em;
- opacity:.8;
- position:absolute;
- right:10%;
- top:2.5em;
- width:5em;
- z-index:30
-}
#Zoomer .control-icon:hover{
opacity:1
}
diff --git a/guide/0100/install.html b/guide/0100/install.html
index 07d27f6..8c40788 100644
--- a/guide/0100/install.html
+++ b/guide/0100/install.html
@@ -133,7 +133,7 @@ Linux/*BSD
To add to this list, submit a pull request to the website
+ href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
source, or email the Mailing list with details.
diff --git a/guide/0100/omemo.html b/guide/0100/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0100/omemo.html
+++ b/guide/0100/omemo.html
@@ -78,7 +78,7 @@ Generating Crypto Materials
If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as haveged, to increase the available entropy.
- 
+ 
Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
@@ -98,12 +98,12 @@ Fingerprint authentication
You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
/omemo fingerprint
- 
+ 
To view the fingerprint of a contact use the following command:
/omemo fingerprint bob
- 
+ 
If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
@@ -127,7 +127,7 @@ Starting a private conversation
If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
/omemo start bob
- 
+ 
The [OMEMO] shown in the titlebar indicates that the conversation is now encrypted.
@@ -159,25 +159,25 @@ User Interface options
By default, an indicator is displayed in the titlebar when no encryption is being used.
- 
+ 
This indicator can be removed using the /encwarn command.
/encwarn off
- 
+ 
Both incoming and outgoing plaintext messages are always preceeded by the '-' character.
- 
+ 
By default OMEMO encrypted messages are preceeded by the '*' character.
- 
+ 
This character can be changed using the /omemo char command.
/omemo char O
- 
+ 
diff --git a/guide/0100/otr.html b/guide/0100/otr.html
index 93a64d6..0361955 100644
--- a/guide/0100/otr.html
+++ b/guide/0100/otr.html
@@ -95,7 +95,7 @@ Generating a private key
If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
haveged, to increase the available entropy.
- 
+ 
Once you have generated a key, you will not need to do so again.
@@ -116,7 +116,7 @@ Starting a private conversation
the same command omitting the contact:
/otr start
- 
+ 
The [untrusted] shown in the titlebar indicates that although this conversation is
encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@
Question and answer
A message will be displayed showing that the authentication process has started.
- 
+ 
If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
- 
+ 
If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
- 
+ 
Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
question, and prompting her to answer. Alice may answer using the /otr answer command:
/otr answer red
- 
+ 
Note that question and answer authentication is a way for one contact to verify the identity of another.
If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@
Shared secret
Bob enters the same secret using his client, Alice and Bob now trust each other.
- 
+ 
If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
secret using the /otr secret command:
/otr secret 5up3r53cr3t
- 
+ 
Manual fingerprint authentication
@@ -210,12 +210,12 @@ Manual fingerprint authentication
display your fingerprint, use the following command:
/otr myfp
- 
+ 
To view the fingerprint of a contact whilst in an OTR session, use the following command:
/otr theirfp
- 
+ 
If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
authenticate the contact with the following command:
@@ -300,26 +300,26 @@
User Interface options
By default, an indicator is displayed in the titlebar when no encryption is being used (including PGP and OMEMO).
- 
+ 
This indicator can be removed using the /encwarn
command.
/encwarn off
- 
+ 
Both incoming and outgoing plaintext messages are always preceeded by the '-' character.
- 
+ 
By default OTR encrypted messages are preceeded by the '~' character.
- 
+ 
This character can be changed using the /otr char command.
/otr char O
- 
+ 
@@ -374,4 +374,4 @@ Importing OTR keys
-