Conversation
Notices
-
@drymer i've enables logs and waiting for it to happen again. maybe it's a badly configured html purifier library
-
@hannes2peer may be unrelated but there's a sporadic character set issue on @Vinilox Classic. Some posts R good,some not http://qttr.at/1671
-
@hannes2peer @mcscx I have experienced something similar but couldn't really understand why. It only affected the social.umeahackerspace.se instance on incoming/outgoing stuff. I didn't really get to grips with what, why and when the issues occurred and stopped looking. This one for example:
https://social.umeahackerspace.se/notice/375852
https://quitter.is/notice/937376 -
@mmn funny, one time your post is affected and the other time sanstheskeleton's post is. I guess it's also in Classic and clients, right?
-
@mcscx The incoming notice is correct in the log, so it is most likely only when the notice enters an instance that the encoding is corrupted. I tried running common_purify() on the text directly but that worked just fine.
cc: @hannes2peer -
@mmn did you notice in my Vinilox example: Nidron's 1st post is ok but the 2nd is affected. Same user, same instance, same client.
-
@mcscx Yes, but one had tags and one didn't, which is a pretty distinct difference. So it could be HTMLPurifier (as hannes suggested) that does something. For example in the one without tags, it had no HTML to modify so it could perhaps be that the string was left entirely untouched.
That of course would mean that all other notices with tags and non-ascii characters should be affected as well.
I'm just rambling here and won't bother looking up any support for my theories tonight :] -
@mcscx @hannes2peer Btw, I get ??? for the profile name of \@takePotato Knishesakenji@quitter.se - so it has to be something that also touches the "fullname" when receiving an Ostatus_profile.
-
@mcscx @hannes2peer I _sometimes_ get ;)
-
