posts: encrypted_XMPP: update date

src/pages/about.html

@@ -4,7 +4,7 @@ layout: post
 lang: 'en'
 
 title: 'about'
-description: 'General info about this website and the author'
+description: 'General info about this website and the author.'
 
 ---
 
@@ -25,7 +25,7 @@ description: 'General info about this website and the author'
 </div>
 
 <p>
-  I'm a&nbsp;front-end developer and a&nbsp;big fan of&nbsp;open-source,
+  I’m a&nbsp;front-end developer and a&nbsp;big fan of&nbsp;open-source,
   customization, and minimalist software.<br>
   Member of&nbsp;the
   <a href='https://t.me/barbadbar' target='_blank'>BadBar</a> crew,

src/pages/about/keys.md

@@ -2,12 +2,13 @@
 
 layout: post
 lang: 'en'
-date: '2026-04-05'
-section: 'about'
 
 title: 'keys'
 description: 'Public keys and fingerprints.'
 
+section: 'about'
+date: '2026-04-05'
+
 ---
 
 # Public Keys and Fingerprints

src/pages/index.ejs

@@ -1,6 +1,7 @@
 ---
 
-description: 'My own private fanzine'
+description: 'My own private fanzine.'
+
 css:
   - index
 

src/pages/lost+found.md

@@ -200,7 +200,7 @@ in the middle of a conversation.
     </header>
     <section class='description'>
       Interactive articles about physics, math, and engineering.
-      It's probably the best website on&nbsp;the entire internet.<br>
+      It’s probably the best website on&nbsp;the entire internet.<br>
       My&nbsp;favorite post is&nbsp;the one about
       <a href='https://ciechanow.ski/bicycle/' target='_blank'>bicycles</a>.
     </section>
@@ -245,7 +245,7 @@ in&nbsp;the middle of&nbsp;a&nbsp;conversation.
     <section class='description'>
       Torrenting can leave traces.<br>
       Check torrent downloads and distributions
-      for your own or&nbsp;your neighbor's IP&nbsp;address.
+      for your own or&nbsp;your neighbor’s IP&nbsp;address.
     </section>
   </article>
 
@@ -300,7 +300,7 @@ in&nbsp;the middle of&nbsp;a&nbsp;conversation.
     <header>
       <strong>
         <a href='https://news.ycombinator.com/item?id=42492508' target='_blank'>
-          Ask HN: Programmers who don't use autocomplete/LSP, how do&nbsp;you do&nbsp;it?
+          Ask HN: Programmers who don’t use autocomplete/LSP, how do&nbsp;you do&nbsp;it?
         </a>
       </strong>
     </header>
@@ -314,7 +314,7 @@ in&nbsp;the middle of&nbsp;a&nbsp;conversation.
     <header>
       <strong>
         <a href='https://sneak.berlin/20201112/your-computer-isnt-yours/' target='_blank'>
-          Your Computer Isn't Yours
+          Your Computer Isn’t Yours
         </a>
       </strong>
     </header>
@@ -411,7 +411,7 @@ in&nbsp;the middle of&nbsp;a&nbsp;conversation.
       </strong>
     </header>
     <section class='description'>
-      Most software tutorials suck. Here's how to&nbsp;make one that doesn't.
+      Most software tutorials suck. Here’s how to&nbsp;make one that doesn’t.
     </section>
   </article>
 

src/pages/posts.md

@@ -4,7 +4,7 @@ layout: post
 lang: 'en'
 
 title: 'posts'
-description: 'Сomplete list of posts'
+description: 'Сomplete list of posts.'
 
 ---
 

src/pages/posts/2020/initial_post.md

@@ -1,16 +1,15 @@
 ---
 
 layout: post
-
 lang: 'ru'
-date: '2020-11-08'
-
-year: '2020'
-section: 'posts'
 
 title: 'initial post'
 description: 'Первый пост в этом фэнзине, рассказывающий о его внутреннем устойстве.'
 
+section: 'posts'
+year: '2020'
+date: '2020-11-08'
+
 ---
 
 # Initial Post

src/pages/posts/2020/typographic_linter.md

@@ -1,16 +1,15 @@
 ---
 
 layout: post
-
 lang: 'ru'
-date: '2020-11-18'
-
-year: '2020'
-section: 'posts'
 
 title: 'typographic linter'
 description: 'Prettier для текста. Автоматизация рутинной типографики.'
 
+section: 'posts'
+year: '2020'
+date: '2020-11-18'
+
 ---
 
 # Типографика как code style

src/pages/posts/2024.md

@@ -4,4 +4,3 @@ layout: redirect
 redirectTarget: '/posts/#2024'
 
 ---
-

src/pages/posts/2024/selfhosted_llm.md

@@ -1,16 +1,15 @@
 ---
 
 layout: post
-
 lang: 'ru'
-date: '2024-01-15'
-
-year: '2024'
-section: 'posts'
 
 title: 'selfhosted LLM'
 description: 'Персональные LLM в docker-контейнере на твоём компьютере.'
 
+section: 'posts'
+year: '2024'
+date: '2024-01-15'
+
 ---
 
 # Your Own Private Large Language Models

src/pages/posts/2024/wrapped_bw_ru.md

@@ -1,15 +1,15 @@
 ---
 
 layout: post
-
 lang: 'ru'
-date: '2024-07-27'
-
-year: '2024'
-section: 'posts'
 
 title: 'wrapped bw'
 description: 'Превращаем fully-featured Bitwarden command-line interface в удобный.'
+
+section: 'posts'
+year: '2024'
+date: '2024-07-27'
+
 ---
 
 # Интеграция Bitwarden CLI с fzf и буфером обмена

src/pages/posts/2026.md

@@ -0,0 +1,6 @@
+---
+
+layout: redirect
+redirectTarget: '/posts/#2026'
+
+---

src/pages/posts/2026/encrypted_XMPP.md

@@ -2,346 +2,418 @@
 
 layout: post
 lang: 'en'
-year: '2026'
-date: '2026-04-07'
-section: 'posts'
 
-title: 'encrypted_XMPP'
+title: 'encrypted XMPP'
 description: 'Secure and private messaging with XMPP and OMEMO encryption.'
 
+section: 'posts'
+year: '2026'
+date: '2026-04-16'
+
 ---
 
-# End-to-End Encryption in XMPP with OMEMO
+# End-to-End Encryption in XMPP with OMEMO
 
-I find it funny that twenty years ago I was already trying
+I find it funny that twenty years ago I was already trying
-to promote XMPP over ICQ to my classmates.
+to get people to switch to XMPP.
-At the time, the proprietary messenger kept making life harder
-for users of alternative clients.
-That’s when I realized that I prefer protocols over services.
 
-I didn’t have much success back then,
+For a long time, ICQ was extremely popular around me,
-but fortunately, XMPP (and I hope I have too)
+but the proprietary messenger kept breaking things for people
+using alternative clients, which was quite annoying.
+After yet another round of this pointless battle
+I realized clearly that I prefer protocols over services.
+
+I didn’t have much success back then,
+but fortunately, XMPP (and I hope I have too)
 has continued moving forward over the past two decades.
-It has developed slowly, sometimes awkwardly, but steadily.
+It has developed slowly, sometimes awkwardly, but steadily.
 
-Here I won’t talk about why XMPP is great or how to use it.
+Here, I won’t talk about why XMPP is great or how it works.
 You can check
 <a
   href='https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html'
   target='_blank'>
   this guide</a>
-(one of many) and I’d rather not write another one.
+(one of&nbsp;many) and I’d rather not write another one.
-In this post, I want to focus specifically on end-to-end encryption
+In&nbsp;this post,
-and the practical aspects of using it.
+I&nbsp;want to&nbsp;focus specifically on&nbsp;end-to-end encryption
+and the practical aspects of&nbsp;using it.
 
 ## Short Glossary
 
-**End-to-end encryption** is a way to keep your chats truly private.<br>
+**End-to-end encryption** is&nbsp;a&nbsp;way
+to&nbsp;keep your chats truly private.<br>
 Only you and the person you’re messaging can read the messages.
-Not even the server owner has the keys needed to decrypt or modify them.
+Not even the server owner has the keys
+needed to&nbsp;decrypt or&nbsp;modify them.
 
-**XMPP** is an extensible protocol for instant messaging.
+**XMPP** is&nbsp;an&nbsp;extensible protocol for instant messaging.
-It's open, decentralized, and mature.
+It’s open, decentralized, and mature.
 
-**OMEMO** is a widely supported XMPP Extension Protocol (XEP)
+**OMEMO** is&nbsp;a&nbsp;<a
+  href='https://omemo.top/'
+  target='_blank'>widely supported</a>
+XMPP Extension Protocol (XEP)
 for secure multi-client end-to-end encryption.
 You can read more about
-it on a&nbsp;<a
+it&nbsp;on&nbsp;a&nbsp;<a
-  href='https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html'
+  href='https://conversations.im/omemo/'
-  target='_blank'>dedicated page by Daniel Gultsch</a>.
+  target='_blank'>dedicated page by&nbsp;Daniel Gultsch</a>.
 
-**Client**, in this post,
+**Client**, in&nbsp;this post,
-means a specific instance of an XMPP application on a user device.
+means a&nbsp;specific instance
+of&nbsp;an&nbsp;XMPP application on&nbsp;a&nbsp;user device.
 <br>OMEMO-related documentation uses the term Device,
-but I find it potentially confusing:
+but I&nbsp;find it&nbsp;potentially confusing:
-in practice, a single physical device can run multiple independent clients.
+in&nbsp;practice, a&nbsp;single physical device
+can run multiple independent clients.
 
 ## Basic Concepts
 
-This section introduces some basic ideas behind end-to-end encryption.
+This section introduces some basics of&nbsp;end-to-end encryption.
 
-If you're already familiar with the concepts and terminology,
+If&nbsp;you’re already familiar with the concepts and terminology,
 you can skip ahead to&nbsp;<a
-  href='#'>how end-to-end encryption affects the XMPP user experience</a>
+  href='#practical-aspects-of-omemo-and-xmpp'>how end-to-end encryption
-or jump straight to the <a
+  affects the XMPP user experience</a>,
-  href='#'>step-by-step workflow</a>&nbsp;I personally use.
+or&nbsp;jump straight to&nbsp;the <a
+  href='#step-by-step-guide'>step-by-step workflow</a> I&nbsp;personally use.
 
 ### Trade-offs Between Safety and Convenience
 
 Unfortunately, things that are truly secure are rarely convenient.
-They often require some initial efforts and a bit of ongoing attention.
+They often require some initial efforts
+and a&nbsp;bit of&nbsp;ongoing attention.
 
-Telegram, which used to be a benchmark for messenger usability
+Telegram, which used to&nbsp;be&nbsp;a&nbsp;benchmark for messenger usability
 before its long dive into enshitification,
 really draws the line between convenience and security.
 Regular chats are easy and flexible,
-but "secret" chats come with a full set of limitations:
+but “secret” chats come with a&nbsp;full set of&nbsp;limitations:
 they’re one-on-one only,
-can’t be synced to another device,
+can’t be&nbsp;synced to&nbsp;another device,
-aren’t available on desktop at all,
+aren’t available on&nbsp;desktop at&nbsp;all,
-and so on.
+and so&nbsp;on.
 
-All commercial so-called "secure" messengers, like Signal or WhatsApp,
+All commercial so-called “secure” messengers, like Signal or&nbsp;WhatsApp,
-end up with pretty similar limitations,
+end up&nbsp;with pretty similar limitations,
-because it's tricky to make end-to-end encrypted chats
+because it’s tricky to&nbsp;make end-to-end encrypted chats
 work the way users expect.
 
 Luckily, protocols and cryptography don’t care about
-convenience or user expectations.
+convenience or&nbsp;user expectations.
-Many XMPP clients let you do almost anything you’re trying to do.
+Many XMPP clients let you do&nbsp;almost anything you’re trying to&nbsp;do.
 Sometimes it’s clunky and unintuitive,
-sometimes it’s the kind of freedom that lets you shoot yourself in the foot.
+sometimes it’s the kind of&nbsp;freedom
-At the end of the day, you’d better understand what you’re doing.
+that lets you shoot yourself in&nbsp;the foot.
+At&nbsp;the end of&nbsp;the day, you’d better understand what you’re doing.
 
-It might sound messy, but for that price, XMPP actually
+It&nbsp;might sound messy, but for that price, XMPP actually
-gives you a lot of handy features:
+gives you a&nbsp;lot of&nbsp;handy features:
 your chats are secured with Signal-grade end-to-end encryption,
-and you can use as many devices as you want,
+and you can use as&nbsp;many devices as&nbsp;you want,
-all at the same time,
+all at&nbsp;the same time,
-without being tied to any proprietary service.
+without being tied to&nbsp;any proprietary service.
-This post is here to show how to use it intentionally and safely.
 
-In general, the XMPP experience today
+In&nbsp;general, the XMPP experience today
-could be described as a "WhatsApp with benefits and frictions".
+could be&nbsp;described as&nbsp;a&nbsp;“WhatsApp with benefits and frictions”.
-It's kinda ironic, considering that WhatsApp’s protocol
+It’s kinda ironic, considering that WhatsApp’s protocol
-is actually based on XMPP, but incompatibly altered and defederated.
+is&nbsp;actually based on&nbsp;XMPP, but incompatibly altered and defederated.
 
 ### Keys, Fingerprints and Trust
 
-OMEMO is based on the Double Ratchet Algorithm.
+OMEMO is&nbsp;based on&nbsp;the <a
+  href='https://en.wikipedia.org/wiki/Double_Ratchet_Algorithm'
+  target='_blank'>
+  Double Ratchet Algorithm</a>.
 While the internal details are quite interesting,
-for practical purposes it's enough to know that
+for practical purposes it’s enough to&nbsp;know that
 each client stores some cryptographic keys
-and can derive a hash from them, commonly called a fingerprint.
+and can derive a&nbsp;hash from them, commonly called a&nbsp;fingerprint.
 
-Keys are usually managed automatically by the XMPP client,
+Keys are usually managed automatically by&nbsp;the XMPP client,
-and in normal use you should never need to handle them manually.
+and in&nbsp;normal use you should never need to&nbsp;handle them manually.
-In fact, you probably don’t even need to know what they look like.
+In&nbsp;fact, you probably don’t even need to&nbsp;know what they look like.
 
-A fingerprint lets you identify a specific client of your contact
+A&nbsp;fingerprint lets you identify
-and verify that it hasn’t been spoofed.
+a&nbsp;specific client of&nbsp;your contact
-Fingerprints for an account are not secret:
+and verify that it&nbsp;hasn’t been spoofed.
-clients publish their own fingerprints to the XMPP server
+Fingerprints for an&nbsp;account are not secret:
-and automatically receive the fingerprints of others.
+clients publish their own fingerprints to&nbsp;the XMPP server
-Only fingerprints you explicitly mark as trusted are relevant.
+and automatically receive the fingerprints of&nbsp;others.
+Only fingerprints you explicitly mark as&nbsp;trusted are relevant.
 
-In an ideal scenario, the contact should confirm in person
+In&nbsp;an&nbsp;typical scenario, the contact should confirm in&nbsp;person
-or through an already trusted and secure communication channel
+or&nbsp;through an&nbsp;already trusted and secure communication channel
-that the fingerprint belongs to their device,
+that the fingerprint belongs to&nbsp;their device,
-and only then you mark it as trusted.
+and only then you mark it&nbsp;as&nbsp;trusted.
-In most XMPP clients this is simply done by ticking a checkbox
-or by scanning a QR code.
 
-The list of trusted fingerprints is used at the moment a message is sent.
+The list of&nbsp;trusted fingerprints
-Behind the scenes, OMEMO performs a certain amount of key management,
+is&nbsp;used at&nbsp;the moment a&nbsp;message is&nbsp;sent.
-and only the clients that are present in the trusted list
+Behind the scenes,
-at the time of encryption will be able to decrypt the message later.
+OMEMO performs a&nbsp;certain amount of&nbsp;key management,
+and only the clients that are present in&nbsp;the trusted list
+at&nbsp;the time of&nbsp;encryption
+will be&nbsp;able to&nbsp;decrypt the message later.
 
-It's important to understand that trust cannot be applied retroactively:
+It’s important to&nbsp;understand
-it's not possible to "extend" trust to new clients
+that trust cannot be&nbsp;applied retroactively:
-after a message has already been encrypted and sent.
+it’s not possible to&nbsp;“extend” trust to&nbsp;new clients
+after a&nbsp;message has already been encrypted and sent.
 
-## Practical Aspects of OMEMO and XMPP
+<h2 id='practical-aspects-of-omemo-and-xmpp'>
+  Practical Aspects of&nbsp;OMEMO and XMPP
+</h2>
 
 ### Chat History
 
-In theory, XMPP supports server-side message history storage via
+In&nbsp;theory, XMPP supports server-side message history storage via
 **XEP-0313: Message Archive Management**.
 
-In practice, support for this XEP,
+In&nbsp;practice, support for this XEP,
-as well as retention policies and message lifetime,
+as&nbsp;well as&nbsp;retention policies and message lifetime,
-depends on the specific server.
+depends on&nbsp;the specific server.
 You should never assume that all conversations are stored
-indefinitely by default.
+indefinitely by&nbsp;default.
-From a practical standpoint,
+From a&nbsp;practical standpoint,
-the server-side MAM archive is better considered a cache:
+the server-side MAM archive is&nbsp;better considered a&nbsp;cache:
-it can help you handle recent messages after a short period offline
+it&nbsp;can help you handle recent messages after a&nbsp;short period offline
-or synchronize conversations across multiple devices.
+or&nbsp;synchronize conversations across multiple devices.
 
-At the end of the day, keeping your chat history is your responsibility,
+At&nbsp;the end of&nbsp;the day,
-and this is a good place to apply a local-first approach.
+keeping your chat history is&nbsp;your responsibility,
+and this is&nbsp;a&nbsp;good place to&nbsp;apply a&nbsp;local-first approach.
 
 
 ### Synchronisation
 
-Seamless switching between clients is handled by
+Seamless switching between clients is&nbsp;handled by
 **XEP-0280: Message Carbons**.
 Before its introduction, only incoming messages were synced between devices,
 while your own outgoing messages were not.
-Protocol-level mirroring of your own messages
+Protocol-level mirroring of&nbsp;your own messages
-is a rather non-obvious feature :D
+is&nbsp;a&nbsp;rather non-obvious feature :D
 
-It's important to note that with end-to-end encryption,
+It’s important to&nbsp;note that with end-to-end encryption,
-the concept of trusted fingerprints also applies to your own clients.
+the concept of&nbsp;trusted fingerprints also applies to&nbsp;your own clients.
-For seamless synchronisation of outgoing messages,
+For seamless synchronisation of&nbsp;outgoing messages,
-all your clients must trust each other's fingerprints.
+all your clients must trust each other’s fingerprints.
-A new client,
+A&nbsp;new client,
-or an old one that was not trusted at the time messages were sent,
+or&nbsp;an&nbsp;old one that was not trusted
-will receive the full history from MAM but will not be able to decrypt it.
+at&nbsp;the time messages were sent,
+will receive the full history from MAM
+but will not be&nbsp;able to&nbsp;decrypt it.
 <br>Yes, even your own messages.
 
-In theory, re-encrypting messages on already trusted clients
+In&nbsp;theory, re-encrypting messages on&nbsp;already trusted clients
-could solve this issue, but no XMPP client implements it yet.
+could solve this issue, but no&nbsp;XMPP client implements it&nbsp;yet.
-So in practice you may need to manually resend
+So&nbsp;in&nbsp;practice you may need to&nbsp;manually resend
-some data to a new device.
+some data to&nbsp;a&nbsp;new device.
 
 ### Message Correction
 
-It’s worth keeping in mind that
+It’s worth keeping in&nbsp;mind that
-features that seem simple and straightforward at first glance,
+features that seem simple and straightforward at&nbsp;first glance,
-such as message editing and deletion,
+such as&nbsp;message editing and deletion,
-actually rely on client-side implementation
+actually rely on&nbsp;client-side implementation
 and may not behave for your recipient the way you expect.
 
-They’re fine to use and are well supported in some clients,
+They’re fine to&nbsp;use and are well supported in&nbsp;some clients,
-but you shouldn’t rely on them to hide anything.
+but you shouldn’t rely on&nbsp;them to&nbsp;hide anything.
 
 ### Maintenance
 
-OMEMO was designed as a set-it-and-forget-it solution,
+OMEMO was designed as&nbsp;a&nbsp;set-it-and-forget-it solution
-and it mostly succeeds in that goal.
+and mostly succeeds in&nbsp;that goal.
-If you have a basic understanding of how the protocol works
+If&nbsp;you have a&nbsp;basic understanding of&nbsp;how the protocol works
-and check in online from time to time,
+and check in&nbsp;online from time to&nbsp;time,
-there shouldn’t be any surprises.
+there shouldn’t be&nbsp;any surprises.
 
-All maintenance comes down to making regular backups
+All maintenance comes down to&nbsp;making regular backups
 and notifying your contacts
-when fingerprints are added or no longer valid
+when fingerprints are added or&nbsp;no&nbsp;longer valid
-so they can keep their trust list up to date.
+so&nbsp;they can keep their trust list up&nbsp;to&nbsp;date.
 
-## Step-by-step Guide
+## Step-by-Step Guide
 
-Let’s say I have a XMPP account, me@some.server,
+Let’s say I&nbsp;have a&nbsp;XMPP account, `me@some.server`,
-and a few devices: a phone, a laptop, and a desktop computer.
+and a&nbsp;few devices:
-First I’ll describe my mindset at a high level,
+a&nbsp;phone, a&nbsp;laptop, and a&nbsp;desktop computer.
+First I’ll describe my&nbsp;mindset at&nbsp;a&nbsp;high level,
 then I’ll add some notes about specific clients.
 
 ### Client Roles
 
-On the one hand, I have my phone.
+On&nbsp;the one hand, I&nbsp;have my&nbsp;phone.
-It’s almost always with me and almost always online.
+It’s almost always with me&nbsp;and almost always online.
-That’s where I keep the full chat history and get real-time notifications.
+That’s where I&nbsp;keep the full chat history
+and get real-time notifications.
 
-On the other hand, I have a couple of desktop applications.
+On&nbsp;the other hand, I&nbsp;have a&nbsp;couple of&nbsp;desktop applications.
-I only open them when I need to discuss something using my keyboard
+I&nbsp;only open them
-or move some text between devices.
+when I&nbsp;need to&nbsp;discuss something using my&nbsp;keyboard
-I like to think of them as ad-hoc or satellite clients.
+or&nbsp;share some text between devices.
+I&nbsp;like to&nbsp;think of&nbsp;them as&nbsp;satellite clients.
 
 ### Before the Start
 
-First, enable OMEMO encryption on every client if it isn't enabled by default.
+First, enable OMEMO encryption
-The client will usually generate the keys and fingerprint automatically.
+on&nbsp;every client if&nbsp;it&nbsp;isn’t enabled by&nbsp;default.
 
-The next step is to add all clients to the trust list on each device:
+The next step is&nbsp;to&nbsp;add
-my phone should trust all my computers,
+all clients to&nbsp;the trust list on&nbsp;each device:
-and my computers should trust each other as well as my phone.
+my&nbsp;phone should trust all my&nbsp;computers,
+and my&nbsp;computers should trust each other
+as&nbsp;well as&nbsp;my&nbsp;phone.
 
-Fingerprints do not have to be secret, so they can be published on
+Fingerprints do&nbsp;not have to&nbsp;be&nbsp;secret,
-your website or even on social media profiles.
+so&nbsp;they can be&nbsp;published on
-Here is my page with the fingerprints:
+your website or&nbsp;even on&nbsp;social media profiles.
+Here is&nbsp;my&nbsp;page with the fingerprints, for example:
+<br><a href='https://oddsquat.org/about/keys/' target='_blank'>
   https://oddsquat.org/about/keys/
+</a>
 
-### Start the Conversation in Person
+### Start the Conversation in&nbsp;Person
 
-Let’s say I meet Alice,
+Let’s say I&nbsp;meet Alice,
-we start talking, and decide to continue the conversation online.
+we&nbsp;start talking,
+and then decide to&nbsp;continue the conversation online.
 
-I open a special QR code on my phone, and Alice scans it with her client.
+I&nbsp;open a&nbsp;special QR&nbsp;code on&nbsp;my&nbsp;phone,
-This QR code already contains the fingerprints of all my devices,
+and Alice scans it&nbsp;with her client.
-so no extra steps are needed.
+This QR&nbsp;code already contains
+the fingerprints of&nbsp;all my&nbsp;devices,
+so&nbsp;no&nbsp;extra steps are needed on&nbsp;her phone.
+After that, I&nbsp;do&nbsp;the same
+and scan her QR&nbsp;code as&nbsp;well.
 
-Then I do the same and scan the QR code from Alice’s screen
+Later at&nbsp;home,
-with my mobile client.
+I&nbsp;manually mark her devices as&nbsp;trusted on&nbsp;my&nbsp;computers
+using the trusted list on&nbsp;my&nbsp;phone, and she does the same.
 
-Now we are both sure that it’s really us in the conversation,
+Now we&nbsp;are both sure
-and that all messages will be available on all our devices and only on them.
+that it&nbsp;is&nbsp;really us&nbsp;in&nbsp;the conversation,
+and that all messages will be&nbsp;available
+on&nbsp;all our devices and only on&nbsp;them.
 
 ### Start the Conversation Online
 
-Let’s say Bob and I start discussing something
+Let’s say Bob and I&nbsp;start discussing something
-on a forum or in the Fediverse,
+on&nbsp;a&nbsp;forum or&nbsp;in&nbsp;the Fediverse,
-and then decide to move to XMPP.
+and then decide to&nbsp;continue the discussion on&nbsp;XMPP.
 
-Bob starts the chat. I trust the first device he messages me from,
+Before starting the chat,
-and then we exchange fingerprints for our other devices, if we have any.
+Bob can confirm it’s really me&nbsp;using my&nbsp;page with fingerprints.
-This approach is called TOFU (Trust On First Use).
+I&nbsp;can confirm it’s really him
+by&nbsp;asking him to&nbsp;send his fingerprints
+in&nbsp;a&nbsp;private message on&nbsp;the same forum or&nbsp;via email.
 
-Bob can confirm it’s really me using my page with fingerprints.
+Ideally, Bob also has a&nbsp;public page with his fingerprints.
-I can confirm it’s really him by asking him to send his fingerprints
+That way, we&nbsp;can both independently verify
-in a private message on the same forum or via email.
+that we&nbsp;are who we&nbsp;say we&nbsp;are.
 
-Ideally, Bob also has a public page with his fingerprints.
+In&nbsp;an&nbsp;alternative scenario,
-That way, we can both independently verify
+where there has been no&nbsp;prior communication or&nbsp;public pages
-that we are who we say we are.
+and only a&nbsp;single JID&nbsp;is known,
+things play out a&nbsp;bit differently:
+Bob starts the chat,
+I&nbsp;trust the first device he&nbsp;messages me&nbsp;from,
+and then we&nbsp;exchange fingerprints for our other devices,
+if&nbsp;we&nbsp;have any.
+This approach is&nbsp;called TOFU (Trust On&nbsp;First Use).
 
-### New or Lost Devices
+### New or&nbsp;Lost Devices
 
-If I start using a new device or install another client application,
+If&nbsp;I&nbsp;start using a&nbsp;new device
-the first thing I do is add it to the list of trusted clients
+or&nbsp;install another client application,
-on my existing devices.
+the first thing I&nbsp;do&nbsp;is&nbsp;add it&nbsp;to&nbsp;the list
+of&nbsp;trusted clients on&nbsp;my&nbsp;existing devices.
 
-If I lose one of my devices or delete any private keys,
+If&nbsp;I&nbsp;lose one of&nbsp;my&nbsp;devices
-the first thing I do is remove the corresponding client
+or&nbsp;delete any private keys,
-from the trusted list on my other devices.
+the first thing I&nbsp;do&nbsp;is&nbsp;remove the corresponding client
+from the trusted list on&nbsp;my&nbsp;other devices.
 
-Once I’ve updated all my personal lists,
+Once I’ve updated all my&nbsp;personal lists,
-I should inform my contacts about changes via trusted channels.
+I&nbsp;should inform my&nbsp;contacts about changes via trusted channels.
 
-I can simply ask Alice to scan my new QR code the next time we meet,
+I&nbsp;can simply ask Alice to&nbsp;scan
-and send Bob a message introducing my new client or letting him know
+my&nbsp;new QR&nbsp;code the next time we&nbsp;meet,
-that the lost device is no longer trusted
+and send Bob a&nbsp;message introducing
-and that no real messages will ever come from it again.
+my&nbsp;new client or&nbsp;letting him know
+that the lost device is&nbsp;no&nbsp;longer trusted
+and that no&nbsp;real messages will ever come from it&nbsp;again.
 
 ## Client Applications
 
-This section describes how OMEMO is used in specific client applications
+This section describes
-that I personally use.
+how OMEMO is&nbsp;used in&nbsp;specific client applications
+that I&nbsp;personally use.
 
 ### Conversations and Forks
 
-Conversations is a modern, fully featured chat application for Android.
+<a
-It supports everything a messaging app should support:
+  href='https://conversations.im/'
-chats, voice calls, and sharing photos and files.
+  target='_blank'>
+  Conversations</a> is&nbsp;a&nbsp;modern,
+fully featured chat application for Android.
+It&nbsp;supports everything a&nbsp;messaging app should support:
+chats, voice calls, video calls, and sharing files of&nbsp;any kind.
 
-There are several forks of it where the UI or UX may differ,
+There are several forks of&nbsp;it&nbsp;where
+the UI&nbsp;or&nbsp;UX&nbsp;may differ,
 but the core features work exactly the same.
-I personally use Monocles Chat.
+I&nbsp;personally use <a
+  href='https://codeberg.org/monocles/monocles_chat'
+  target='_blank'>
+  Monocles Chat</a>.
 
-On the Contact Details screen (including your own account),
+On&nbsp;the Contact Details screen (including your own account),
-you can see a list of published fingerprints
+you can see a&nbsp;list of&nbsp;published fingerprints
-and manually mark them as trusted or revoke trust.
+and manually mark them as&nbsp;trusted or&nbsp;revoke trust.
 
-To simplify all these routine operations, a QR-code-based system is used:
+To&nbsp;simplify all these routine operations,
-You can show your own QR code or scan other people’s codes
+a&nbsp;QR-code-based system is&nbsp;used:
+you can show your own QR&nbsp;code or&nbsp;scan other people’s codes
 directly from the main screen.
-This makes device verification during in-person meetings simple and effortless.
+This makes device verification during in-person meetings
+simple and effortless.
 
 ### Dino
 
-Dino is a lightweight GTK-based GUI client.
+<a
+  href='https://dino.im/'
+  target='_blank'>
+  Dino</a> is&nbsp;a&nbsp;lightweight GTK-based GUI client.
 
-It can be considered a fully functional one,
+It&nbsp;can be&nbsp;considered a&nbsp;fully functional one,
-although some non-essential features are still not supported or implemented.
+although some non-essential features are still not implemented.
 For example,
-it is not possible to clear local chat history using built-in methods :D
+it&nbsp;is&nbsp;not possible to&nbsp;clear local chat history
+using built-in methods :D
 
-Trust and untrust decisions can be easily managed
+Trust and untrust decisions can be&nbsp;easily managed
-in the Encryption tab of the Conversation Details window.
+in&nbsp;the Encryption tab of&nbsp;the Conversation Details window.
 
-It is important to note that, by default, Dino is configured
+It&nbsp;is&nbsp;important to&nbsp;note that,
-to automatically trust new fingerprints.
+by&nbsp;default, Dino is&nbsp;configured
-I recommend disabling this feature.
+to&nbsp;automatically trust new fingerprints.
+I&nbsp;recommend disabling this feature.
 
 ### Profanity
 
-Profanity is a powerful TUI client
+<a
-where everything is controlled through a built-in command system.
+  href='https://profanity-im.github.io/'
+  target='_blank'>
+  Profanity</a> is&nbsp;a&nbsp;powerful TUI client
+where everything is&nbsp;controlled through a&nbsp;built-in command system.
 
-If you somehow intend to use it,
+If&nbsp;you somehow intend to&nbsp;use it,
-below you will find a small cheat sheet for using OMEMO.
+you can find a&nbsp;small cheat sheet for the `omemo` command below.
-However, I strongly recommend reading the full documentation.
+However, I&nbsp;strongly recommend reading the full documentation.
 
-- Generate a key and add your other clients:
+- Generate a&nbsp;key and add your other clients:
   ```text
   /omemo gen
   /omemo trust me@some.server some-cool-fingerprint-01
@@ -349,26 +421,43 @@ However, I strongly recommend reading the full documentation.
   /omemo qrcode
   ```
 
-- View the list of your own or someone else’s fingerprints:
+- View the list of&nbsp;your own or&nbsp;someone else’s fingerprints:
   ```text
   /omemo fingerprint me@some.server
   /omemo fingerprint alice@another.server
   ```
-  Trusted ones will be marked as `trusted`.
+  Trusted ones will be&nbsp;marked as&nbsp;`trusted`.
 
-- Start an encrypted conversation:
+- Start an&nbsp;encrypted conversation:
   ```text
   /omemo start alice@another.server
   ```
 
-- Add fingerprints to the trusted list:
+- Add fingerprints to&nbsp;the trusted list:
   ```text
   /omemo trust alice@another.server some-cool-fingerprint-02
   /omemo trust alice@another.server some-cool-fingerprint-03
   /omemo trust bob@another.server some-cool-fingerprint-04
   ```
 
-- Revoke trust for a specific client:
+- Revoke trust for a&nbsp;specific client:
   ```text
   /omemo untrust alice@another.server some-cool-fingerprint-02
   ```
+
+## Late Disclaimer
+
+This post was originally intended
+as&nbsp;a&nbsp;collection of&nbsp;answers to&nbsp;questions
+I&nbsp;had when I&nbsp;first started using XMPP with OMEMO.
+
+It&nbsp;isn’t meant to&nbsp;be&nbsp;exhaustive or&nbsp;formal,
+but rather to&nbsp;clarify the practical side of&nbsp;things
+and reduce that initial feeling of&nbsp;being lost
+when you keep running into
+“The message was not encrypted for this device”
+over and over again.
+
+From now on, I&nbsp;hope you won’t encounter such errors
+or&nbsp;any other issues
+connected to&nbsp;end-to-end encryption in&nbsp;XMPP.

src/pages/posts/2026/ugly_keyboards_ru.md

@@ -2,12 +2,13 @@
 
 layout: post
 lang: 'ru'
+
+title: 'ugly keyboards'
+description: 'Почему нас окружают уродливые клавиатуры и что с этим можно сделать.'
+
+section: 'posts'
 year: '2026'
 date: '2026-03-18'
-section: 'posts'
-
-title: 'ugly_keyboards'
-description: 'Почему нас окружают уродливые клавиатуры и что с этим можно сделать.'
 
 ---
 

src/pages/projects.md

@@ -123,7 +123,7 @@ Incomplete list of my projects and experiments.
 - <article class='entry'>
     <header>
       <strong>
-        Cantor MX Tastatura
+        Cantor MX&nbsp;Tastatura
       </strong>
     </header>
     <section class='description'>
@@ -141,7 +141,7 @@ Incomplete list of&nbsp;my&nbsp;projects and experiments.
       </strong>
     </header>
     <section class='description'>
-      Huge custom ergonomic mechanical Dactyl-Manuform (5&times;6) keyboard.
+      Huge custom ergonomic mechanical Dactyl-Manuform (5×6) keyboard.
     </section>
     <section>
       <a href='https://github.com/He4eT/oddkb' target='_blank'>repository</a>

src/pages/test.md

@@ -1,16 +1,15 @@
 ---
 
 layout: post
-
 lang: 'en'
-date: '2020-10-30'
-
-year: '2020'
-section: 'posts'
 
 title: 'markdown test page'
 description: 'A test document written using the Markdown language.'
 
+section: 'posts'
+year: '2020'
+date: '2020-10-30'
+
 ---
 
 # Markdown: Syntax

tools/typograf.js

@@ -25,6 +25,7 @@ const tp = new Typograf({
 
 const enabledRules = [
   'common/nbsp/*',
+  'common/punctuation/apostrophe',
   'common/punctuation/quote',
   'en-US/dash/main',
   'ru/dash/main',