@SurajRao Which one? - One was a personal attack on the user with swearing and grossly disparaging comments (abusive) and the other was a (possible or intentional) miss-spelling of the word "shift" (rude). I used "abusive" and "rude" to clearly distinguish between the type of complaint even if they alias the same way. Thanks for asking.
It's probably not and the edit hides what might have been the intended post, spoiling our detection and recording of the incident - if I had an account there I would custom Mod flag and explain, so it sits as-is. Moving on.
@Rob IMO, this post should be FP? That just looks like a typo, which is repairable. Repairable offensive posts are FP, unless it was an edit that specifically added in primarily offensive material.
@Makyen - Thanks for the link. Many hands make light work (even autocorrect had that lined up for me, and it might be my first use of the expression). I left it hoping that someone would read it and review it for themselves and decide what they thought appropriate. I generally frown on joining every site and not being a participant. As one can see from my site list I don't just join for the sake of joining nor to score 100 Flair Rep. All my joins are legit.
Later in the conversation it is agreed that the edit wasn't useful as the answer wasn't a solution.
@Rob OK. I guess we have different views. Joining so you're able to help moderate the site to get rid of spam/rude/abusive content, as is reported here is, IMO, a completely legit reason. I agree that joining just to get the association bonus is not that great. However, while you do gain the association bonus for each site you join, that's just a consequence of how the system works, and allows you to minimally participate based on your already existing knowledge of how SE works.
@Makyen - Yes, force of habit - to try to avoid doing the wrong thing. --- But on that basis I'd be better off joining WordPress.SE (instead/in addition).
@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.
@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 Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@Makyen - Earlier today Shog9 sent a 'sd command' from The Tavern and (surprisingly) it said that it was his first time using SD and sent 'helpful read the rules reply'. His complaint is that Smokey replied in the wrong room. Should I file a Bug Report or is that the expected behavior. Thanks.
@Rob Go ahead and file a bug, if you'd like. From what I've seen SD/MS sends that notification once for each time the user first gives feedback per chat server. If it's not appearing in the room in which the user has given feedback, then it's not, necessarily, going to be effective. Arguably, the criteria for when that notification is sent should be changed to be based on the person's overall feedback history, including both in-chat and via API, and not be on a per chat server basis.
