
jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:
finally killed a nasty & obscure client text-rendering bug… after trying off-and-on for a couple of months. it took me examining hex representations of the data payloads flowing to a service POST operation & then back as results to the client. fooooooook.
the web-based client for my seekrit project service is now properly rendering non-ASCII UTF8 glyphs (like ñ & ű) instead of filtering them out & throwing them away like a barbarian (aka: the “Brute Force & Bloody Ignorance” approach to coding)