Conversation:
Notices
-
@hannes2peer Speculating: I don't think so. But it has to get sanitised somewhere, no?
I will check the direct database entry next time it occurs.
-
@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
-
@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
-
"enters an instance" as in during PHP's processing, not before.
-
@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 sh…
-
@mcscx @hannes2peer Btw, I get ??? for the profile name of \@takeshitakenji@quitter.se - so it has to be something that also touches the "fullname" when receiving an Ostatus_profile.
-
@mcscx @hannes2peer I _sometimes_ get ;)
-
Yeeeeeeeeep, the profile table has question marks in the fullname field.