UTF-8

He wants to talk about that layer.

The modern standard is UTF-8.

The predecessor is ASCII.

And he's seen firsthand the kind of crazy-inducing failure modes that show up when people collaborate on documents without paying attention to the system.

Distributed team, Israel, the UK, New York, all working out of a Google Sheets attendee list full of names from Norway, Spain, France, accents and diacritics everywhere.

He eventually standardized the backend on Airtable.

But by then, he was left with the hopeless task of trying to sanitize a CRM export that some program had standardized on UTF-8 and, in the process, mangled the names of a lot of people who were about to get an email.

Hopeless is the right word for it.

I'm sure a lot of people would hate it, but I would love it.

So there is such an important and useful use case for that, which is when you're compiling Rust to Wasm and you're interacting with JavaScript, and all the strings in JavaScript are UTF-16, or sometimes UCS2, which is even worse, but anyway, don't think about that, then if all your strings in Rust are UTF-8, which is what they are, then every time you interact with something that's in the browser DOM or something like that, there's a conversion happening.

So yeah, let's have a program-wide thing that just says all the strings in quotes are UTF-16.

Oh, that'd be great.

And after two years, you finally fix it.

And you trace it to a buffer overflow in libUV using file events on Windows for extra long UTF-8 UNC parts where there's a file being renamed.

It's just the number of things you have to chain together.

It's kind of like security, but exploits backwards.

IoT Hub requires the telemetry payload to contain valid JSON.

The message content type must be set to application JSON, and the content encoding must be UTF-8.

If those fields aren't set correctly, IoT Hub can't present the telemetry payload to event grid in the expected structure.

That can seem annoyingly strict when you first meet it, but it forces a useful question.

The dataset properties page lets users modify.

Case sensitivity, normalization, UTF-8 only.

ZFS promptly rejected the operation because those properties are creation only.

Naturally, WebZFS did not expose them on the dataset creation page, which is one place they actually work.

So the name is...

UTF-8 smuggling, UTF-16 smuggling, actually, in most cases.

Yeah.

yes but yeah that's i mean i i shocked dan with that one in the past when i showed him like utf-8 and like unicode my favorite is when you do split javascript split on uh on emoji and then you turn for example the family into four emoji and these kind of things it's just yeah it's it's a mixture of text and binary that is very confusing for people

However, with FileMaker 26, they changed the encoding.

So it's UTF-8.

So it's going to be much smaller.

So it's much more compact.

Do this.

Yeah.

And this version addresses also the fact that FileMaker 26 is UTF-8 and version 9 doesn't process the UTF-8 stuff.

So people are waiting to get their hands on version 10 because it has support for both UTF-16 and UTF-8.