@Stormblessed You can use online tools like regex101.com to give you syntax highlighting (and tooltips) when creating queries - or use a reference (I use this as I mainly use .NET RegEx - though for most things all RegEx variants are the same).
This is several days late and I am really, really, really thankful much of what's been going on hasn't spilled into this room. I've given up keeping up on transcripts in a few other rooms because it's just to much to read and process.
Regarding actions anyone here wishes to take to express their agreement/disagreement with policies, I don't believe I have the right to stop you. Express your opinions, but also remember that others may disagree with those opinions. This room will remain civil.
This room, this community, is awesome. Our work has been acknowledged to be important to keeping the network's spam rates so low. Regardless of everything else going on, everyone here should be proud of that accomplishment.
@iBug As long as you have the instance's Git repository with the origin as a "https://github.com/...", SD will use the GitHub credentials which are stored in the config file. SD shouldn't need your SSH key for any of its operations.
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (fetch first) error: failed to push some refs to '[email protected]:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the remote contains work that you do hint: not have locally. This is usually caused by another repository pushing hint: to the same ref. You may want to first integrate the remote changes hint: (e.g., 'git pull ...') before pushing again.
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (fetch first) error: failed to push some refs to '[email protected]:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the remote contains work that you do hint: not have locally. This is usually caused by another repository pushing hint: to the same ref. You may want to first integrate the remote changes hint: (e.g., 'git pull ...') before pushing again.
@Machavity The only reason I did a scan was because the user's only two posts were that exact link, and in each answer he said they did different things. It was enough to be suspicious imo
@Machavity How worth it is it for me to add to the watch/blacklist, if admins like you are currently active? I'd assume having to review a PR is less desirable than checking the logs
Got it, thanks. Makes sense that I'd need a history of passed PRs before moving past that. Just wanted to make sure me doing so wouldn't be too much of a bother if there were already people on it
@rene That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Few unique characters in body, mostly punctuation marks in body, mostly punctuation marks in title, repeating characters in body, repeating characters in title (286): ------------------------------- ✏️ by shipy on ru.stackoverflow.com
I was suspended from reviewing until February because I said this answer looked okay:
https://stackoverflow.com/review/low-quality-posts/24199630
It appeared to give useful information as to why the user was having issues and I wasn't sure why it was incorrect to mark it as ok. Could anyone exp...
@Kulfy (re this MS post) Just FYI: We normally use tp for self-vandalism instead of tpu. Most people who vandalize their posts only vandalize one or two. They also tend to stop when a comment is placed on their post asking them not to make extra work for other people by vandalizing. Thus, blacklisting the user is usually not needed or desirable.
We generally only use tpu for vandalism in relatively rare cases where the user appears to be on a spree of vandalism over multiple posts (or multiple times), and where the vandalism that they are doing isn't already caught by SD. For such users, a custom mod-flag should be raised informing the mods about the vandalism, so they can correct it (if no one around has the rollback privilege on the site) and so they can suspend the user to give the user time to cool off.
Go and upvote the question now
