@SmokeDetector @Shree I think that post was definitely spam. It's not an NAA post asking about showing something pertaining to that address on a website, it's just a totally unrelated spam post.
@SmokeDetector naa- Although this definitely not an answer and shouldn't have been posted, I don't think this is intended as an insult against the OP, or any particular person or people.
@EliahKagan That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Das_Geek It was a Twitter username. I really should've put (?#twitter) after it. Actually, I'll do that. (The full domain, which also looks like a spelling mistake, appears to be their actual spam domain, though.)
@EliahKagan That pattern looks like it's already caught by Pattern-matching email in answer and Pattern-matching email in body; append -force if you really want to do that.
@EliahKagan That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen Sorry about that -- this was due to my mistake. I added a comment to the end of the pattern I blacklisted, which caused it not to be identical to the pattern on the watchlist, so blacklisting it didn't automatically unwatch the original. I'll try to keep this effect in mind in the future, when blacklisting patterns with even nonfunctional modifications.
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (3): Ways to deduplicate files by Zainmrkt on superuser.com
