[:61181919] Registered question as true positive and blacklisted user. [:61181902] <skipped> [:61181891] Registered question as true positive and blacklisted user.
A random Bitcoin address for a title a meaningless body is till up after four hours…? Sigh. Please flag as spam. A random Bitcoin address in the title makes it spam. It really ought to have been nuked already, though
I also left a comment reminding viewers to flag it as spam
I am really not seeing the advantage of making the "ketosis" watch case-sensitive. There's no reason to expect that spammers would write that word in all lower-case, and it's missing several posts (not anything critical, just speaking of all-time stats) that have different capitalization. On the other hand, it adds only 1 additional FP. So, I'm going to go ahead and make that case-insensitive.
I had looked into this with the expectation of not watching something that is a standard chemical process, but... this watch is quite effective. (Although, again, not essential or critical, since most of the posts it catches would be caught for other reasons. But the FPs are still quite manageably low.)
[ SmokeDetector | MS ] Link at beginning of body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially problematic ns configuration in body (44): What Is Gemstone Mookaite Color? by Nathalia Young on meta.SE (@Ollie)
@JeffSchaller A normalized version, {'18088000449', '8088000449'}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number 18088000449 to determine which entries on the number lists match that pattern.
@SmokeDetector fp- The garbage title was present in the original revision, and is not something we want to block, given there's a valid question being asked (akin to filler text in questions). If the title were added in an edit, then it would be something we would block.
@OlegValteriswithUkraine I've patched MS to avoid the issue, so the "/post" page on MS is working again. However, I haven't found the actual cause for the value of the post's cached post_comments_count, which should be a minimum of 0, being -1. What appears to have happened is that, for some reason, when Redis generated its cache of this report something ended up messed up sufficient for the cached count of comments to be -1, which, obviously, isn't legit. I was also able to cause Redis to re-generate its cache for that post, which has resolved the remaining display issue on "/posts". I am, however, a bit surprised that the cached copy wasn't automatically expired from Redis, as I thought that should happen after an hour.
@SmokeDetector tpu- This answer is plagiarized from askubuntu.com/a/310 and given the "Thanks for sharing your answer", and the user's previous spam serverfault.com/questions/1033122/…, and the fact that the answer is irrelevant to the question, this looks like a failed spam attempt. Custom flagged.
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (5): Passive and active heat sinks for Xeon 5472 by Shuvro Halder on superuser.com (@Ollie)
@Makyen thanks for letting me know! Seems fixed indeed. I have no idea why exactly this happened either - examined the source after we last spoke, but I just not see how post_comments_count ended as -1. Seems like it should not be possible. Any clues as for what could cause the cache to not expire so far?
@OlegValteriswithUkraine What took a while was my unsuccessful attempt to determine why the post_comments_count value would be negative. A patch to prevent an error when it happens was fairly obvious, but I was hoping to identify a cause and fix the underlying issue.
The quota_remaining property was not in the API response. Error: no method found with this name at 18:18:27 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
