@Shree That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@SmokeDetector This answer was edited during the grace period. The Markdown would have likely shown that there was some text which was stripped and latter edited to be code.
!!/test-a It has to be alternate all the time, except for instances when the team's other partner is on wheelchair. There are a lot of strategies though when playing doubles. Here's a list: gametableplanet.com/5-winning-table-tennis-doubles-strategies/
!!/test-a You will find all the official ruling on the ITTF (International Table Tennis Federation) website. You'll find there that yes, a partner has to alternately receive the ball. When you serve, it has to reach diagonally across to the other table and the receiver should return it... and more. For some tips on how to WIN, check out: gametableplanet.com/5-winning-table-tennis-doubles-strategies/
What's the guidance on something like this? I moved it to meta and it's not a valid post for main. It also overlaps heavily with the typical spam attack on our site so I'm loathe to mark it fp. Is this what "ignore" is for? https://workplace.stackexchange.com/questions/156991/why-are-so-many-offensive-questions-here-allowed-past-screening
@Lilienthal The question is not something which should be blocked if SmokeDetector was implemented as a system level service, so it's FP. If it looks like it's going to be an active question (i.e. get a couple/few answers), then ignore is also reasonable. ignore tells the current SD instance to not report the post anymore.
Without telling SD to ignore, SD would report the post if it continues to match any detections and there's an event which results in the question being rescanned (an edit to the question or answer, or new answer is posted). However, given that the question has not yet been reported as the question on MTWP, telling SD to ignore the old report won't do any good.
@Makyen And the "implemented as a system" would then mean a silent block that's absolutely invisible to the community? I.e. a very black-or-white nuke it or allow it (regardless of whether it needs close votes, migration, etc.)
@Lilienthal Yes, as if SE took the code for SmokeDetector and implemented it within the system such that flagging was no longer the mechanism which was used (i.e. TP posts just wouldn't be permitted on the network).
It appears the /api/v2.0/posts/uid/:api_param/:native_id endpoint is having problems with the workspace.meta API param, as the route works fine with just workplace.
The same request produces a valid response if the key is placed at the end of the query string.
After playing around with the request, it looks like MS is just dropping the first parameter. For example this request complains that urls is missing when it's the first parameter in the query string.
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in title (103): Data Science Course in Houston by Data Science Program on stats.SE
[ SmokeDetector | MS ] Url-only title, bad ip for hostname in body, bad ip for hostname in title, blacklisted website in body, blacklisted website in title, +4 more (697): allpills4u.com/testo-xp360/ by Dreembelliy on askubuntu.com
@ArtOfCode Thanks. Sorry about that. I thought I'd checked for proper format when hand editing to test, but clearly failed. I should have actually used a real editor to manipulate the URL, rather than trying to do so in the URLbar. So, problem #2 is on me and not actually a problem. :-;
However, Problem 1 (/api/v2.0/posts/uid/:api_param/:native_id not handling the workspace.meta API param), does appear to be an issue. Actually, the route doesn't appear to be working for any Meta site, other than MSE. If you want additional URLs, SIM uses this route and currently fails on any Meta site (at least all the ones I've tried).
It's relatively easy to change SIM to just use the /api/v2.0/posts/urls endpoint, so that's an option too.
