@RyanM 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 this pattern.
@cigien 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 this pattern.
@SmokeDetector google translation looks like nonsense: "Teach me, I don’t know how to woo la la la ula ula, I love to take a bath, my skin is good, there are so many bubbles all over my body,"
@tripleee 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 this pattern.
@SmokeDetector I find these types of Feedbacks misleading and unhelpful. It says that the post is from "à deleted user" when in fact it is "by Frank" (as a result of a migrated question, he has no account on that site). In addition the question has answers and a positive comment from the moderator, it's unlikely to be deleted. - It would be better Feedback if it were styled similar to the other Feedbacks, if it said: "by Frank on" (without a link to
@Mast Other than manual reports, SD uses the SE WebSocket to get information about activity. If the SE WebSocket isn't working (i.e. isn't reporting edits/new posts, then SD won't know about them. The message from SD above is SD reporting that there hasn't been any activity posted on the main SE question activity WebSocket for a period of time longer than SD feels is "normal".
So, we do detect SE being down as an absence of activity, but leave it up to humans to determine if any action is needed. In general, a lack of activity can be: A) Activity on SE is just really slow, which does rarely happen; B) SE is down; C) the SE WebSocket is malfunctioning (which may or may not be fixed by SD attempting to reconnect and/or rebooting).
@Mast they don't. You could sniff the key and access token from one of the apps; otherwise, the only way to get write access with the API is to post a Stack Apps question...
@Rob It's styled that way because the SE API doesn't return any information for the user, which is normally included in the request for question/answer/post data. That data isn't included when there's no account for the user/ I'm not seeing anything to distinguish between a deleted user and one who hasn't made an account, yet, at least not without additional API accesses.
Even with additional SE API accesses, I don't believe there would be a way to distinguish between "hasn't created profile, yet" and "profile was created, but is deleted".
