If a title contains a "<", XML complains because it's a shitty format that uses
<tags>.

Instead of stringifying and parsing, censor directly from the raw message

* Now the from is directly censored (or not) direcly when the email is read,
  and not on the template itself. This implies Message.From is now a string

Implements: https://todo.sr.ht/~arielcostas/archigo/16

It shows the first three characters of user and domain, and full TLD. The rest
is filled with *.

* Emailify only "censored" addresses, but nameOrAddress returns either the name
  or the address, whichever is available, and in case of addresses it 'censors'
  them.

* Move body parsing to a different function

* Move the output generator outside the main

* Write comments explaining WHY instead of HOW

Some messages include "(message from someone on sometime)" after the
in-reply-to message, which caused some problems when creating thread map

This caused the input to try and write to a new directory because of unix.  For
example "<foo/barbaz@computer>" would try to write to non-existent directory
"<foo/" instead of foo.

Replacing / with %2F (URL-encoded) fixes the issue. Also, in-reply-to is
replaced for threading purposes.

It happens sometimes, and it would cause a fatal error. It now returns error to
main whichs skips to the next message and warns the user.

* Takes into account the possibility of someone including their own HTML, and
  thus cleans it beforehand

* Allows http, https and gemini, and shows the whole URL to prevent possible
  abuse

* Handles one or more links in a single line.

Implements: https://todo.sr.ht/~arielcostas/archigo/20

This way we don't repeat ourselves by having the listId outside of the list
itself.

This was caused by quoted-printable messages being shown as-is, instead of
correctly rendered as text.

Fixes: https://todo.sr.ht/~arielcostas/archigo/21

I tried using man.sr.ht but I didn't like the idea of having code and docs
tracked separately. So, we keep it all together.

Implements: https://todo.sr.ht/~arielcostas/archigo/19

Will permit readonly lists that don't show the reply options

Navigation links (reply, subscribe) ought to be used more than once, and the
title one too.

This way new users can easily figure out how to write a message to the list.

That way we can link to the submission address for each list

Before, it would make it so the whole screen would scroll. We now break the
message onto shorter lines. This only happens when the user has the phone in
vertical.

Fixes: https://todo.sr.ht/~arielcostas/archigo/15

For this, we pass the full list to the rendering template, we create a
richMessage which basically contains the message and a .RenderId attribute
containging the message actually being rendered (to prevent linking to itself).

WE REALLY NEED TO REFACTOR THIS CRAP

Implements: https://todo.sr.ht/~arielcostas/archigo/10

That way, recursive threading works

Before it had it only on the left, which was wrong and looked weird

This should make archigo more maintainable long-term, because we no longer have
the repository folder clogged with source code, configurations and stuff.

* output folder is now public/ by default (relative to the PWD)

* output is no longer hardcoded but rather is a config.toml option, or by default public/

Implements: https://todo.sr.ht/~arielcostas/archigo/11

Under 600 bytes of vanilla CSS that converts a horrible HTML onto a pleasant
simple and fast website.

Implements: https://todo.sr.ht/~arielcostas/archigo/14

Implements: https://todo.sr.ht/~arielcostas/archigo/12

Implements: https://todo.sr.ht/~arielcostas/archigo/6

Before, a misconfiguration would lead to a crash, not it should be handled properly