Kit Bashir
Excerpt from the blog post “Falsehoods programmers believe about True Names”:
* All True Names can be represented in UTF-8
* All True Names can be represented in UTF-16
* Identical twins share the same True Name
* True Names can be safely stored in databases using encryption
* True Names can be safely stored in databases
* True Names can be safely stored
* A bcrypt hash of a True Name cannot be used to construct an effective pain effigy (often incorrectly known as a “voodoo doll”)
Ryan Castellucci :nonbinary_flag:
@Unixbigot I'm deeply concerned about the UTF-8 vs UTF-16 distinction being drawn here.
Ryan Castellucci :nonbinary_flag:
@Unixbigot All strings representable as UTF-8 are representable in UTF-16 and vice versa. They both encode a series of Unicode scalar values in the ranges ([0, 0xD7FF], [0xE000, 0x10FFFF]).
Some things falsely call themselves UTF-16 which can encode a superset of this, namely scalar values in the range [0xDC00, 0xDFFF] not preceded by a value in the range [0xD800, 0xDBFF] and scalar values in the range [0xD800, 0xDBFF] not followed by a value in the range [0xDC00, 0xDFFF].
This encoding exists where systems were originally designed to use UCS-2 (which encodes scalar values in the range [0, 0xFFFF]), but then updated to treat this as UTF-16, while retaining compatibility with UCS-2 strings. This is known as "potentially ill-formed UTF-16" or "WTF-16", and is used by JavaScript, at least some versions of Java, and various Windows APIs.
Kit Bashir
@ryanc but you’re ok with the rest?
Ryan Castellucci :nonbinary_flag:
@Unixbigot this might be good copypasta if it were zalgofied a bit as it progressed.
Ryan Castellucci :nonbinary_flag:
@words_number Basically everything in the 90s did this shit, but yeah.
words_number
@ryanc While reading through this I thought "wow this is absolutely horrendous, I bet it's used by Windows". Glad I was right and not at all surprised JS is also on that list!
Ryan Castellucci :nonbinary_flag:
@words_number Some backwards compatibility is worth razing.
words_number
@ryanc Makes sense. Sometimes I think we are taking backwards compatibility too far. I mean it's obviously necessary and important, otherwise we would do nothing else than fix stuff that broke over night 24/7, but keeping every mistake around for ever also can't be the solution.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.