[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at beginning of body, potentially bad ip for hostname in body, potentially bad keyword in body (235): virtual phone egan to want foo by flashhaver on ethereum.SE
@gnat It's possible to do most things. There are no current detections for what you're describing. 7,500 titles is a bit large, but not unacceptably so, depending on what type of matching you're wanting to do. However, you'd need to define what you're wanting to do on each site; if it's to be a dynamic list; etc. If you're wanting 7,500 titles for each site, that's ~ 1.35M titles, which is too much.
If you change "new account" to "1 rep account", then the latter thing that you're describing is fairly easy to detect. Actually detecting that the account is new would require additional SE API accesses (accesses could be grouped to some extent, but would at least double the number of requests we make). OTOH, an account being "new" could be inferred from the user's SE or site account ID and reputation, rather than actually fetching the account/profile creation date.
Given your mention of plagiarism, it's unclear to me if you're wanting to detect plagiarism, generally problematic posts, or actual spam/R/A. In general, Charcoal's detection goals are for spam/R/A, rather than other issues.
@Makyen That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@Ethan That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@tripleee That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer Append -force to the command word(s) if you really want to add the pattern you provided.
Makyen/EC2-linux received failover signal. <-- This probably shouldn't have happened. Check if Thoth is operational (e.g. !!/location) and consider executing !!/standby Makyen/EC2-linux to put this instance back in standby. (@Makyen)
Restart: API quota is 79998.
Notice: Makyen/EC2-linux: Last 2 connection(s) to metasmoke succeeded. Setting metasmoke status to up.
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Makyen Regarding amount of titles, it can be made somewhat less than 7,5K (though not orders of magnitude) - other viable options I checked are questions with over 600K, 700K, 800K views having about 5300, 4000, 3000 titles respectively (at Stack Overflow). The type of matching I'm wanting to do is: when title of a new question contains (exact match) the title of an old one.
The only site that looks worthy of suggested check seems to be SO because at smaller sites such issues are essentially guaranteed to be found and handled without any automation. List of popular titles can be static - if refreshing it once a year is an option, that would be nice (though not necessary). Change "new account" to "1 rep account" looks totally acceptable, maybe even an improvement over what I initially asked for.
Flaggable plagiarism in troublesome questions of this kind that I've seen so far was maybe in about 1/3 cases. Issues in most of these questions were of the kind typically reported by "repeated characters" heuristics. And just in case if this matters, almost all of them looked like immediately closeable as duplicates of the questions where titles were copied from, although unclear or too-broad close reasons were better fit.
[ SmokeDetector | MS ] Blacklisted username, blacklisted website in answer, potentially bad ns for domain in answer, potentially bad keyword in username, username similar to website in answer (255): Different types of APK by Dai Software on stackoverflow.com
SELECT * FROM p_posts where user_link like "%/19955222/%"
or user_link like "%/1630300&/%" or user_link like "%/490943/%"
or user_link like "%/983612/%" or user_link like "%/1252937/%"
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, body starts with title and ends in url, link at end of body, +3 more (553): research paper writing service by HIGS on workplace.SE
