Is this spam? stackoverflow.com/a/79328471 It sort of answers the question, but is full of links and has weird, weird capitalization suggesting spam filter evasion.
It's highly likely to be the same issue as has happened a few/several times before when such characters are involved in a field on MS, which is that the database field doesn't support those characters in that field, so trying to add the report fails. I haven't verified that's actually the problem, but it's what's been the issue a few/several times now with various fields.
@ThomasWard I'd have to look at what is currently used in that field and what the solution was last time this happened with respect to doing a database migration. As I recall, it's not that difficult.
@ThomasWard Don't. There's a very specific, correct, way to do it automagically using the software and packaging that we use. If you change it manually, that might just @#($* it up wrt. continuing to use the system we're using.
@ThomasWard As I recall, based on the last time, it's currently a subset of UTF-8, with like 10 different variations available for UTF approximations, and not that great documentation as to what each one is, with none just stock UTF-8, 16, or 32.
@DavidW You can execute the !!/report command again in 13 seconds. To avoid one user sending lots of reports in a few commands and slowing SmokeDetector down due to rate-limiting, you have to wait 30 seconds after you've reported multiple posts in one go.
