@ThomasWard With the 2.3 SE API, there wouldn't be significant additional SE API cost, because we can get the SE account number in the same request with the post data. Adding the account_id to the shallow_user type, which is used for users in the question, answer, and post responses, was one of the changes made from 2.2 to 2.3.
With the 2.2 version of the SE API, you're right that the additional SE API cost would be substantial (as in about double what we currently use).
There's a GitHub issue for adding retrieving it during SE API accesses for posts and forwarding it to MS. I've written the code for the SD side of that, but need to test it.
I was actually thinking that the user-blacklist command would, at the time it was issued, fetch all network accounts for the specified user, and add each those to the blacklist as if it was done manually. That way, it would require only one additional SE API call when the command was issued. The downside, of course, is that newly-created network accounts wouldn't be dynamically added, but I felt like that was a small price to pay for the convenience. It would be no worse than we have now.
Makyen's solution, with the new field added to v2.3 of the SE API, is even better. I had not connected those dots. The apps I maintain haven't updated from v2.2, so I hadn't evaluated what was new in v2.3.
@CodyGray I've done that before, but this time I used the green checkmark on Metasmoke... is there a way to configure that to give tpu instead of tp...?
Good question. I have run into that same thing before myself. I don't think so. I don't know if there's a workaround to add the "u" portion when giving feedback via the MS dashboard.
Would anyone else find it helpful if the title of the post were bolded in SD report chat messages? Given the unpredictable wrapping, I will often inadvertently click on the user name when I meant to click through to the post.
@CodyGray Post 2: That does not look like a valid post URL.
@CodyGray You can execute the !!/report command again in 21 seconds. To avoid one user sending lots of reports in a few commands and slowing SmokeDetector down due to rate-limiting, you have to wait 30 seconds after you've reported multiple posts in one go.
@SmokeDetector Still up. (I guess that the sites which are less frequented have less users who see the spam posts and know what to do. This is probably the case for most of the spam posts posted on per-site-metas.)
OTOH I understand that if a site doesn't have many visitors (such as MathOverflow Meta), the spam post only get a few views - so not much harm there from this POV.. At the same time, I would not be surprised if stuff posted on any SE site and on any meta would be indexed by Google about one or two hours since posting.
Most of the spam that gets caught by Charcoal is removed by Charcoal members, not by regular members of the site seeing it "organically". That's even true on Stack Overflow, which vastly outnumbers the other sites in terms of regular users and views.
Re: if that's the case, I am a bit surprised. I meant if more flags come from here than from regular users. (At the same time, I do not know how one can say whether or not this is the case. Basically I don't see other way than a "guesstimate".)
I'd suppose that there are some sites which have their mods around almost 24/7. So a lingering spam posts - which did not get enough spam flags from Charcoal and from the regular users - would be removed by the mods maybe in an hour or two.
Anyway, this is probably not that relevant - basically all that can be done to help removing this spam post was already done. (It was reported here, I have mentioned it in a local chatroom and also left a comment under the post explaining what to do with spam posts.)
It's almost time for me to go to work. See you later!
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in username (297): 22 Reading and Writing Activities here by Eduauraa on askubuntu.com
@CodyGray 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 if you really want to add the pattern you entered.
@CodyGray This is a real name. It appeared once on a spam post back in February, but hasn't appeared since, and just showed up in a FP. I see no compelling reason to keep this watched; the spam post associated with it would have been detected for a variety of other reasons.
@CodyGray 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 if you really want to add the pattern you entered.
@CodyGray 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 if you really want to add the pattern you entered.
@CodyGray This watch has only ever resulted in FPs for user names and only 3 times resulted in a TP for bodies (the most recent of which was 2 years ago). All of those TPs would be caught for other reasons, if they were posted today.
There are way too many questions about masturbation on Islam.SE. I don't know if these are subtle trolling, or if Muslims are just that obsessed with masturbation...
sdc report stackoverflow.com/a/71612403/4657412 "user name on YouTube video suggests undisclosed affiliation, plus video is only hours old (so unlikely to be discovered organically)"
@CodyGray I have routinely flagged these as VLQ as of late, it seems they are almost certainly duplicates at the very least; I have a few declined but the recent ones seem all to be accepted as helpful and the posts deleted
That pattern may be a North American number. If it is, please use a format which starts with an optional `1` followed by possible separator text and has the main number in the format `923-434-2575` where `-` could be a single alpha character or any `[\W_]*+`. Alternately, you can add the comment `(?#IS NorAm)` to the end of the pattern to force also using the alternate normalized form, or `(?#NO NorAm)` if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try
^ This is TP... It was copy-pasta from another answer on the same page, with garbage text added to the end. I missed it myself, until rene pointed it out. (cc @tripleee)
@SmokeDetector Copy-pasta from another answer on the same question, with garbage text added to the bottom.
@CodyGray 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 if you really want to add the pattern you entered.
@tripleee 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 if you really want to add the pattern you entered.
