Tekniquelly correctMar 7
Whoa. UTF-8 is older now than ASCII was when UTF-8 was invented.
Show threadFarce MajeureMar 7
@tek and it still sucks
Show threadTekniquelly correctMar 7
@vathpela Awww, I like UTF-8! I can pretend it's ASCII most of the time.
Show threadFarce MajeureMar 7
@tek I have complaints about recoverability on a mildly corrupted bitstream, but it's much too late in the evening to articulate this well.
Show threadmxkMar 7
@vathpela @tek I would argue that in modern times this really shouldn't be an issue to be concerned about. It's not like telnet and plain serial connections are still most central communication protocols. And if your storage is causing bit flips you have other issues than readable plain text.
Show threadMagnus AhltorpMar 7
@mxk @vathpela @tek I don’t know any way to run telnet over a non-checksummed connection.
Show threadGlen T, heated, not stirredMar 10

@ahltorp @mxk @vathpela @tek You could in theory run UTF-8 in syslog over non-checksummed UDP packets.

But in practice DNS operations folk apply the clue-by-four to kernel programmers who turn UDP checksums off, as that allows corrupted DNS answers, which are then cached.

Show threadFarce Majeure
@glent @ahltorp @mxk @tek do y'all just not believe people still have to deal with actual UARTs, or what?
Mar 10 at 10:28amWeb
Show threadmxkMar 10
@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.
Show threadFarce MajeureMar 12
@mxk @glent @ahltorp @tek I agree, but I also think it could and should have improved.
Show threadMagnus AhltorpMar 10
@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.
Show threadFarce MajeureMar 12
@ahltorp @glent @mxk we could have made the whole situation better, but we didn't.