Whoa. UTF-8 is older now than ASCII was when UTF-8 was invented.

[alper@rls.social]

@tek MySQL will still happily mangle it.

[loke@functional.cafe]

@enno @tek @vathpela I'd go as far as saying it's actively harmful. There are exactly zero cases when it's useful, and it will actively mess things up in most cases.

But, of course windows applications tend to add them at times.

[vathpela@infosec.exchange]

@glent @ahltorp @mxk @tek do y'all just not believe people still have to deal with actual UARTs, or what?

[mxk@hachyderm.io]

@vathpela @glent @ahltorp @tek I do work with actual uarts but only for debugging purposes as a fallback when ssh fails.
That doesn't stop me from considering using utf-8 a net benefit.

[ahltorp@mastodon.nu]

@vathpela @glent @mxk But even if it’s raw UART with no layer in between, it’s no more of a problem than with Ascii or ISO 8859, if you don’t count the larger surface area of a wide character, which is sort of unavoidable.

[vathpela@infosec.exchange]

@mxk @glent @ahltorp @tek I agree, but I also think it could and should have improved.

[vathpela@infosec.exchange]

@ahltorp @glent @mxk we could have made the whole situation better, but we didn't.