@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.
@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.
@Mast 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.
@Mast There's a large task of moving older watches of numbers into the watched number list. The better way to do this is to create a PR which moves them in bulk and retains all the information about who added each watch and when.
@Mast For the simple ones, it's literally just copying the line from one file into another. However, there are also a lot of ones which are definitely not simple. There are also numeric watches which are completely number, but which represent things like URL paths, which shouldn't be moved to the number list.
I saw their posts disappear inside of a few seconds on Software Engineering.SE and figured that some higher power nuked 'em. Thanks for being around for when that goldmine was unearthed :D
@SmokeDetector @VictorVosMottor Had a recent influx of spam on this domain, their MO is to post a seemingly legitimate answer and then shoe in a spam link at the end. See the domain history.
Yeah, they essentially just attacked SO and SoftwareEngineering a few hours ago.
@VictorVosMottor I am aware of 8 admins. Currently in this room: Makyen, thesecretmaster, ArtOfCode. Not currently in this room: Thomas Ward, angussidney, tripleee, Andy, Undo.
Yeah, @Victor I think Rob would prefer to only ping who's around right now, rather than people who have been away for awhile. More polite that way, ya know? :)
For example, Art is last seen a minute ago; but hasn't actually visited an SE site for a week; so probably ping someone else - and I checked almost everyone else - so don't ping.
teward/Osiris: In getting MS post information, recovered from requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Read timed out. (read timeout=10.0)
