Tbsync's caldav/carddav backend is no longer compatible with recent
versions of Thunderbird and so this method doesn't work anymore.

This was super not obvious when I needed to test connecting there at
first. Let's hope this'll make it more obvious to others in the future.

reading json logs is not natural and jq can be complicated to use
sometimes.

Because of discussions today around issue team#41675 and from
what I read in this wiki page, I somehow thought that only the .mbox
archive would be kept around and that the web archive would become
offline upon deletion.

But what happens is rather more to-the-letter what is said in this page:
the archive is kept around, html files visible on the web included.

I'm just clearing out the possible questions that I'll have (and
possibly others?) when I won't remember this detail by adding a quick
note about the web archive remaining online.

The main tor website is not manage by the www rotation (anymore?) it's
now getting auto-deployed by CI, except for prod.

The current text is confusing in that regards.

I had to do this again today for team#41667 and it was really
useful to have this around. I also noticed I was missing the `amtool`
invocation, even from the other ticket, so it was kind of important to
add this to the wiki immediately after all.

Alertmanager is now publishing alerts to the newly-registerd #tor-alerts
channel.

We've decided to change the channel name since the new monitoring system
is not related to nagios anymore. We prefer having a more generic name.

See team#41631

The linter I use locally (markdownlint) is set to be very strict and
there are many other issues that I didn't fix. The other issues are
almost all about lines being too short or bullet lists being indented by
one space. I just wanted to fix the easiest details that surely won't
have an impact on the content.

the output of `trocla --help` is really not helpful. With the README
file at least we can see what other subcommands exist and how they're
used.

There was a URL defined for "Trocla" but it wasn't used, so I just
linked it up on the first appearance of the software name.

service/ci: expand on workaround for team#41621

See merge request !50

Normal chunks are okay to backup without any special snapshotting, but
WAL files are written on the fly by Prometheus, and doing a backup
with Bacula will lead to inconsistencies in the storage which can make
recovery more difficult. See also https://github.com/prometheus/prometheus/pull/14317

this should make it easier to jump to the section we want to see.

The anchor has changed, probably because the section was renamed

We seem to be converging over something that covers both flow and
architecture, but even including other mail hosts. It's pretty neat!

See team#41009

Now we have two models: one of email delivery flow, the other of the
redundancy architecture.

Turns out the latter might be clear enough on its own; the main
difference is it omits other mail host snowflakes like lists and the
other mail hosts (gitlab, rt, etc).

See team#41009

This is better, but still hard to read, I'm starting to think I just
need to split this in two diagrams: one to display redundancy and
location, the other for message flow.

This really tells me our naming convention sucks and we should have
picked example0 instead of example-01... But anyway.

This is clunky and overcrowded, but a necessary step to realize we
just can't draw all the lines.