We're working on some back end JavaScript stuff and that may have caused this - in the interim it seems to have been fixed, so I'm marking this status-compelted.

Sorry, I was trying to get a more detailed explanation from someone that would be able to estimate the work required for what you're asking but I seem to have failed - @Mokubai I understand what you're saying and if it were possible, I'd do it in a second but, right now, the choices are between the two sides of "allow entirely" and "block entirely" - as far as I can tell. We could try blocking Korean in titles only - which is an option but if the spammers figure that out, they can get around it by writing English titles.

@Mokubai So... yeah. The fact that there's one minimum (no weeks have zero attempts) does seem a bit odd... it could be a bot testing the block weekly... but lots of sites get foreign-language spam without it being a "spam wave" that needs an outright block on the language being posted. Charcoal tests for posts that are primarily non-English characters, so any such spam should get quickly caught and deleted by them. The fact there's spam is kinda less important than that it's deleted and if there are users who want to post content that uses Korean characters, we should allow that if possible.

That's correct. It's not the full Korean character set but it seems to be enough that it catches most of the content. We can rewrite the regex matching but we can't have it check for a percentage. We do this for other languages, too, like Cyrillic. :)

That'd be super awesome but our system isn't set up to do that. It's a simple block/allow so we can't count content or anything like that. Y'all could certainly make a FR for it but I don't know that the need is high enough that we'd build it in the near future. :)

The change is documented here, in the edit from Kristina - meta.stackexchange.com/a/332502/284336 It includes the explanation for why we made the decision we did. We can revisit but there is a technical reason for it.