-={ 2021-03-07 20:49:13.981079736+00:00 }=-

Hey August!

 AA> Looks good on Telegram!

That is only a start since I can see by your quote that the utf-8 characters got grunged.  That is the same with golded and msged as they both display properly but cannot reproduce utf-8 characters.  Even an old DOS editor can reproduce utf-8 characters it just cannot display them properly seeing they know nothing about multibyte characters.

 AA> BTW.. since this message would go through Stas' system, my
 AA> Latvian chars above may not translate.

Note that I am not quoting them back as they are defective and I opt out putting 8-bit characters into a utf-8 msg.  That is why my packer calls up iconv to convert utf-8 charaters to whatever 8-bit character set so that only the packed msg has the targeted encoding and the original msg is unscathed as I can verify by looking down at the utf-8 Old English tagline.  However in this case iconv isn't part of the equation as far as these particular exchages are concerned.

 AA> I will confirm with my nntp connection later where Thunderbird
 AA> seems to handle utf-8 automatically.

I don't use thunderbird myself but I'd be willing to bet it has absolutely no problem with utf-8 characters, including the Latvian ones.

Life is good,
Maurice

... še wes molde imynt, er šu of moder come.
    For you the dust was intended, before you came from your mother.
--- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)