Latin1 was the early default character set for encoding documents delivered via HTTP for MIME types beginning with /text . Today, only around only 1.1% of websites on the internet use the encoding, along with some older applications. However, it is still the most popular single-byte character encoding scheme in use today. A funny thing about Latin1 encoding is that it maps every byte from 0 to 255 to a valid character. This means that literally any sequence of bytes can be interpreted as a valid string. The main drawback is that it only supports characters from Western European languages. The same is not true for UTF8. Unlike Latin1, UTF8 supports a vastly broader range of characters from different languages and scripts. But as a consequence, not every byte sequence is valid. This fact is due to UTF8's added complexity, using multi-byte sequences for characters beyond the general ASCII range. This is also why you can't just throw any sequence of bytes at it and ex...
While lurking on the internet, I stumbled across a post from 2019 by @literalbanana on Twitter/X outlining different modes of communication.
It seems both balanced and concise in a way that strikes me as "Wow, now I can't unsee that." I want to share it here.
- Information transfer along a channel of high shared context
- Channel maintenance (phatic, e.g. communicating for social function rather than to convey information)
- Context onboarding (FAQs, lurking)
- Information transfer along a channel of shared unknown context (alarms, shrieking)
Side-channel leaks? "Every context-rich information channel is simultaneously fighting with every other such channel."
Comments
Post a Comment