Move Migadu to blog website

2 files changed, 16 insertions, 21 deletions

diff --git a/blog/content/notes/index.gmi b/blog/content/notes/index.gmi
index 50cb6dac..03e3d9f8 100644
--- a/blog/content/notes/index.gmi
+++ b/blog/content/notes/index.gmi
@@ -18,6 +18,7 @@ Notes about some books I like:
 => tech/document-formats Document formats
 => tech/internet-communication-channels Internet communication channels
 => tech/ledger Ledger
+=> tech/migadu Migadu
 
 ### Gadgets
 
diff --git a/misc/migadu.md b/blog/content/notes/tech/migadu.gmi
index b4abc992..9fc5a80e 100644
--- a/misc/migadu.md
+++ b/blog/content/notes/tech/migadu.gmi
@@ -1,44 +1,41 @@
 # Migadu
 
-<https://migadu.com/>
+=> https://migadu.com/
 
 ## A strategy to handle email addresses
 
 Email addresses can be "vanity" or "non-vanity".
-Vanity email addresses are meant to be public and memorable, for example `firstname@lastname.tld`.
+Vanity email addresses are meant to be public and memorable, for example firstname@lastname.tld.
 
 Set up any vanity domains that you want, and a non-vanity domain.
 
 ### Non-vanity email addresses
 
-In the non-vanity domain, you create the `{me}{code}@nonvanity.tld` mailbox.
+In the non-vanity domain, you create the {me}{code}@nonvanity.tld mailbox.
 
-`{me}` identifies you, you can have multiple users with different `{me}` identifiers in a single non-vanity domain.
+{me} identifies you, you can have multiple users with different {me} identifiers in a single non-vanity domain.
 
-This strategy uses `{code}` to obfuscate email addresses.
-When you use `{code}` in an email address, you should be able to identify if the `{code}` is valid or not.
+This strategy uses {code} to obfuscate email addresses. When you use {code} in an email address, ideally you should be able to identify if the {code} is valid or not.
 
-For example, you could use a four-digit `{code}` and store what code you have used for each address.
-If you use `x3452` and store this code, when you receive an email that does not match, such as `x3453`, you know the code is incorrect.
+For example, you could use a four-digit {code} and store what code you have used for each address. If you use x3452 and store this code, when you receive an email that does not match, such as x3453, you know the code is incorrect.
 
 Alternatively, you can use hashing so that you do not have to store all codes.
 
-No one except you should know about `{me}{code}@nonvanity.tld`.
+No one except you should know about {me}{code}@nonvanity.tld.
 
-Then you create a pattern rewrite from `{me}.*@nonvanity.tld` to `{me}{code}@nonvanity.tld`.
+Then you create a pattern rewrite from {me}.*@nonvanity.tld to {me}{code}@nonvanity.tld.
 
-When you need a non-vanity email address, you create a new `{me}.{entity}{code}@nonvanity.tld`, where `{entity}` is the entity that communicates with this email address and `{code}` is a **new** code.
+When you need a non-vanity email address, you create a new {me}.{entity}{code}@nonvanity.tld, where {entity} is the entity that communicates with this email address and {code} is a new code.
 
-Mails received at `{me}@nonvanity.tld` are incorrect.
-Mails received without the correct code are incorrect.
+Mails received at {me}@nonvanity.tld are incorrect. Mails received without the correct code are incorrect.
 
 ### Vanity email addresses
 
-Create any needed `{id}@vanity.tld` addresses.
+Create any needed {id}@vanity.tld addresses.
 
 Different from non-vanity email addresses, vanity email addresses can be guessed and you cannot identify invalid email.
 
-See [email forwarding via IMAP](../linux/misc.md#email-forwarding-via-imap) for notes about forwarding between different email servers.
+=> misc-linux-stuff See "email forwarding via IMAP" for notes about forwarding between different email servers.
 
 ### TODO Filing
 
@@ -50,18 +47,15 @@ Because each vanity email address and entity has a different email address, you
 imapsync --user1 xxx@gmail.com -passfile1 gmailpass --user2 a@a.com --host2 imap.a.com --passfile2 pass --gmail1
 ```
 
-To move mail, add `--delete1`.
-But this seems to make `imapsync` much slower!
+To move mail, add --delete1. But this seems to make `imapsync` much slower! (IIRC, also this didn't remove the emails from GMail!)
 
 ### Preventing issues with multiple tags
 
-An email message can have multiple "tags" in Gmail that correspond to IMAP folders.
-If you have messages with multiple tags, then the migration will duplicate messages in multiple folders or file mails to one folder at "random".
+An email message can have multiple "tags" in Gmail that correspond to IMAP folders. If you have messages with multiple tags, then the migration will duplicate messages in multiple folders or file mails to one folder at "random".
 
 imapsync has features to control this, and avoid problems with the "all mail" and "sent mail" Gmail folders, but for further control, you can refile emails to have a single tag.
 
-I have an mbsync replica of my Gmail account for backup purposes.
-This replica can be used to find messages with multiple tags:
+I have an mbsync replica of my Gmail account for backup purposes. This replica can be used to find messages with multiple tags:
 
 ```
 find . -path './\[Gmail\]/All Mail' -prune -o -not -name index -type f -exec grep -H ^Message-ID: {} \; >index