[ SmokeDetector | MS ] Blacklisted website in body, link following arrow in body, potentially bad ns for domain in body, potentially bad keyword in body (199): Cyber Security in 2019? by vardhanvarma on superuser.com
@Undo It looks like they think the abuse report @tripleee filed with AWS about that domain was actually about metasmoke.erwaysoftware.com. Frankly, the abuse email could be read that way. From the abuse record, it appears that there's additional context when reporting (e.g. a form indicating the actual domain). But, just the text from the report could be read such that MS is the report target.
@Das_Geek well, I mainly use SO from the SE network, but I feel like SO probably has the most attention when it comes to quality control, not sure how much the smaller sites gets flags, vtc's etc. etc. - would like to try and apply network-wide efforts if I have the time :)
@treyBake It helps get the spam deleted faster. Many of us have created such accounts. If interested, there's a SEDE query which lists the site on which you don't have an account. As to "worth it": I'm unsure of what you consider the downside, so it's not possible for me to evaluate if it's a net positive.
@treyBake I personally join all communities with spam posts that get reported here. Even with one post removed, I'd say that's worth it. Especially if you have autoflags set up
@Das_Geek 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.
@Das_Geek 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.
@Makyen ouch, sorry, that's crazy ... I'll try to be more careful when composing these abuse reports
^ cc @Undo
@treyBake I used to abstain from voting on Drupal spam because having a PHP site in my profile felt ... dirty. But in the end the sites broadly speaking all get the same spam, and if you want to deter the spammers, you want to flag and eventually delete it everywhere
SO gets comparatively little spam because the volume of (nominally) legitimate traffic is so huge; many of the smaller sites definitely need and deserve flags from all of us
@tripleee np. I'm assuming there was a form entry that explicitly said what domain you were reporting, which should have prevented the confusion. Unfortunately, the email @Undo showed implies that at some point AWS disconnect the form entry from the text, which could have lead to the confusion.
That might help. It's unclear if the report will be considered negative for MS (e.g. they only act after N reports). But, overall, the wording they used in replying to you tends to indicate they don't really do much wrt. such reports.
@Makyen Meh. AWS reports are only taken seriously after consist reports. We got into hot water when Russians found our contact form echoed the request, so they were sending spam until I found it and cut them off. I explained it all to AWS and nothing bad happened
@Machavity That sounds like a good resolution. I can understand AWS requiring multiple reports to actually do something. At their scale, they probably get a variety of spurious reports. OTOH, it would be nice if they were a bit less blasé.
but they probably have a model for the complainers too; if we can get chalked up as a good source of feedback they just might start to take us seriously
I'm afraid my frustration probably shows through though
@ThomasWard Yep, it's been stable over the last 5 days. Prior to that, there were some stability issues with Anubis and @iBug's SandyShores. While the problems were also intermixed with some issues which affected all SD instances, the problems which appeared instance-specific were prevalent enough such that I was concerned about failing over when I did so ~5 days ago.
A good portion of the general issue with SD instances was that our CI testing was silently failing for a month. I've also put effort into squashing some of the bugs which were causing some of the exceptions/reboots, but there are others which haven't been identified/fixed. [This reminds me I need to finish testing the general fix for the issue that was causing the silent CI failures.]
@treyBake @Das_Geek I wouldn't consider the mere fact that the person is from the same country as the service to be sufficient to believe there's undisclosed affiliation. However, when someone posts a link to a blog that was posted on the same day, it's nearly always due to affiliation of some type, unless the blog is very popular and the topic is about a widely-known current event. It's not enough to be sure, but it certainly makes me very suspicious.
OTOH, just based on the Q&A, I can see how someone might consider the recommendation of an "Asterisk billing system with PHP" to be something the question is asking for. I haven't checked to see if the recommended software fulfills that requirement.
@Machavity No, that's actually my bad. The feedback should be TP, because we would want a system level block, but it shouldn't be red-flagged (i.e. flag as NAA).
@double-beep What does FIRE say as an error (i.e. in the toastr message and/or in the console)? It looks like MS is raising autoflags for you, so it's more likely to be an issue with configuring FIRE's authorization with MS.
!!/report stackoverflow.com/a/58940756/11384392 "'four head' -> 4Head, a common Twitch emote used to connote sarcasm or hilarity. Combined with the unhelpfulness of the message, this post is certainly not fit for respectful discourse."
@double-beep Possible, although those shouldn't be intermittent. It depends on why it failed. Could be a generic networking issue (much more likely to be intermittent).
@double-beep Yes. the GraphiQL link is the one we want there. It used to work, but is now broken. It's a much better UI. The GraphQL link link at least loads a page, but I'm unsure if it's actually working, and doesn't have some needed features. The link was changed away from /api/graphiql in the commit prior to that one.
@double-beep Basically, I wanted to leave something that was working, but also didn't want to indicate we're moving away from having GraphiQL functional. There's a GitHub issue about the problem.
@Makyen 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.
A group of SE users and I are collaborating on an open-source project similar to the SE network (basically an alternative for frustrated users), and I would like to get the word out to interested SE users. I am currently using my profile description to advertise, but my profile doesn't get a lot ...
