@SmokeDetector tp 6th time I've seen that domain in the last 24 hours, on two different accounts. All posts were rubbish, merely posted to advertise the domain
@tripleee I was referring to the point earlier this year when it was decided that the minimum required number of feedbacks should change from 1 to 2. Instead of jamming a large quantity of posts into review, it was chosen to duplicate the already existing feedback. IIRC, all of the duplicated feedback was assigned to "System".
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@tripleee One question. I try to configure AF to give feedback to Smokey. I am privileged to give feed back from sobotics room. but when I try to get key I get a message Your account is not approved to use the write API. What I am missing here.
@Makyen That pattern looks like it's already caught by Potentially bad ns for domain in body and Potentially bad ns for domain in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@tripleee That pattern looks like it's already caught by Mostly non-latin answer and Mostly non-latin body; append -force if you really want to do that.
^ borderline, question really asks vaguely for information about taxis in Taiwan, but there is a comment saying this doesn't really qualify as a valid answer anyway
@Magisch yeah, it's been going on for several years and I was hoping it would go the same way as previous ICANN proposals to reform whois but this one looks threateningly like it may actually become reality, perhaps because of the timing coincidence with the EU GPDR legislation
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@Shree I can understand that. NAA is the more conservative choice. In fact, I originally provided NAA feedback on the first one of these. However, once the user was seen to be posting multiple, nearly identical non-answers across multiple sites, using different accounts, but all promoting their blog (and I went to the blog & found out their username matched the listed author), it became clear that they were just spamming. At which point, I changed my feedback to tpu & flagged as spam.
:45394463 Changing your feedback on the two you provided feedback for would be helpful. Personally, I'd retract any NAA I'd raised and re-flag as spam, which will help get them deleted faster, but doing so is a personal choice.
@Makyen in FIRE you can click again and Metasmoke will hopefully catch that and change your feedback. As a fallback, you can visit the Metasmoke post and click the (clear) link up next to the title
@tripleee That pattern looks like it's already caught by Potentially bad ns for domain in body, Pattern-matching website in answer, Pattern-matching website in body, and Potentially bad ns for domain in answer; append -force if you really want to do that.
@RobertLongson Another time, it's helpful to use !!/scan first, which causes SD to scan the posts to see if it detects it as spam. This allows autoflags to be placed if the post qualifies (this one would have). If it's not detected as spam when !!/scaned, then go for a !!/report. Basically, !!/scan often gets the post deleted faster.
It's not useless, but when it should be used changed when !!/scan was recently added. I was just thinking that we might want to change things so !!/report does a scan first (falls back to a report if not detected), but also have a !!/report-no-scan (or something like that) for the times when the user just wants to report w/o scanning.
@RobertLongson I agree, it would be better. I'm assuming that there might be a use-case for !!/report-no-scan. In part, that will depend on if !!/report keeps the semantics which allow you to add a custom reason by enclosing it in double-quotes at the end of the !!/report message. But, there shouldn't be much harm/extra work in keeping it available.
@tripleee 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.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, +5 more: TRIAL@>> vipsupplement.com/kara-keto/ by apkfughfhd on superuser.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, +4 more: TRIAL@>> vipsupplement.com/kara-keto/ by apkfughfhd on superuser.com
whatever is convenient for you, we don't have a way to say "we are Charcoal, resistance is futile" so you report on your own accord but coordinate by opening an abuse ticket in Metasmoke
if you don't want to reveal too much personal information, e.g. Protonmail.com allows you to create a free email address for this purpose
Ideally we could consolidate the process, have a special email adress that gets mirrored to everyone who cares, and use that as official point of contact
@tripleee It might also put charcoal on the map some more, like if some site notices "we've gotten like 100 suffcessful abuse reports from this email adress, maybe we should check that out"
@tripleee My main problem has been that not waiting for the 5TP/0FP has appeared to become the norm, rather than remain an exception, which is considered carefully, with the choice made based on how unique the string/domain is counterbalanced with the benefit of having it as a blacklist in order to have more weight/exposure.
Another part has been that having things on the watchlist for some relatively significant time allows us to run the regex against the real world data to see if there's FP out there about which we're not aware.
you can currently go from a report to a reported item but not in the other direction, I have an issue open about making this visible in the other direction too
perhaps in the meantime we should add #reported or something like that to at least make it clear that there is a report?
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, bad pattern in URL body, blacklisted website in body, +2 more: Vivrax Male Enhancement Reviews by Vivrax on superuser.com
