asciilifeform: it's been there since 1st day of new logtron
asciilifeform: trinque: apropos -- i took the liberty to put piz banner on http://logs.nosuchlabs.com/ ( btw open to improvements, if someone knows how to draw... )
asciilifeform: phf: i see blank line in both client and log
asciilifeform: mp_en_viaje when you wake up, plox to reissue the barfologies if you still have'em handy. whole episode may easily be 'coarse error of pilotage' of asciilifeform
asciilifeform: lobbes plox to move your bot here, where it belongs, lol
asciilifeform: for some reason i thought he had multichan support, but apparently moved it wholesale to #a-test , lol
asciilifeform: phf: this -- worx . this is not the problem. problem happens when the re-encoded string is fed to postgres.
asciilifeform: the phf-style variant is currently sitting in #asciilifeform-test , btw, and can be diddled , put turd there and try to search for it, if it's in the test bot's log, search will return correct res
asciilifeform: (cuz it's specifically a postgres query boojum)
asciilifeform: btw just as i thought, lobbes's searchtron fails if fed the liquishit in question.
asciilifeform: and if someone wants to write 100,000 lines of shitython to write 'dwim', let him fucking scroll to the bottom of the log page, click 'get source', grab the fucking vtree, and write.
asciilifeform: let the people who smeared the 58 acres of shit on cardboard, stuffed it into their modem, and sent it to fleanode, clean it up.
asciilifeform: grudgingly i built in utf8 so that can say кто ты по жизни and τὰ γὰρ ὀψώνια τῆς ἁμαρτίας θάνατος etc. but , for all that has been said re utf8, it is at least supported by postgres . whereas i am not about to spend rest of life trying to write 'dwim ai' to eat erry possible microshit encoding that someone may have at whatever point excreted .
asciilifeform: and whoever doesn't like it, can write own logger. and if mp_en_viaje wants to tear off my epaulettes and make own logger in cobol, he can.
asciilifeform: unless someone supplies, in next coupla days, a simple AND WORKING pill, i'ma do this : anything coming into the bot that dun decode cleanly as utf8, will have the offending chars (i.e. any with 8th bit set) replaced with that glyph that depicts a steaming pile of shit.
asciilifeform: 'I mean literally, the guy's from Washitistan, they write things with their own excrement there, and the Unicode Foundation introduced actual excrement in the standard so now whenever someone asks for the networking code in your project they are delivered physical faeces on cardboard. About fifty eight acres of it. Where would you like this put, sir ?' (tm)(r)(mp)
asciilifeform: why the fuck is this even a good idea ? to support arbitrary liquishit in logs ? imho the Right Thing would be 'if you want yer logs imported or echoed, put'em into utf8 or stuff up arse' .
asciilifeform: ~pasting~ e.g. '2000000 ÷ (154 × 1088 × 1.25) = 9.549274255x' dun trigger the barfolade, btw. cuz on civilized box, lobbes's txt is ALREADY utf8 when yer viewing it. only triggering lobbes's echo , where it pisses the malcoded garbage straight into irc, triggers.
asciilifeform burned entire evening on this, and is no closer to a ~lead~ to a solution (not even speaking of actual solution) than before.
