Skip to content

Instantly share code, notes, and snippets.

@ArtOfCode-
Last active April 2, 2016 19:05
Show Gist options
  • Save ArtOfCode-/11917e1c3ad2156e704016fa62c0e7f5 to your computer and use it in GitHub Desktop.
Save ArtOfCode-/11917e1c3ad2156e704016fa62c0e7f5 to your computer and use it in GitHub Desktop.
- [SV] Self-vandalism
Cases where the OP is unaware of how to delete their post, or where a user ragequits, and replaces the entire post
content with a stream of gibberish.
- [GB] Gibberish (16585)
Cases where the original post is simply a string of gibberish.
- [HE] Asking for help via email (16216, {"tp": ["Undo"], "fp": ["rekire"]} )
Cases where an OP posts their situation and asks for responses to <email address>, either knowingly or not of the SE
policies on such posting.
- [PG] "Padding" gibberish (15729, {"tp": ["Kevin Guan"], "fp": ["Brock Adams"]} )
Cases where the OP posts an answer (or non-answer) that is shorter than the (30?) character requirement, and fills out
the rest of that requirement with gibberish.
- [US] Unclear spam (15639, {"tp": ["intboolstring", "Brock Adams"], "fp": ["intboolstring"]} )
Cases where a product has been recommended in response to a question, but the OP's affiliation to it is unclear. Links
may or may not be present; it's unclear whether it's a genuine recommendation or plain spam. 15639 is a good case.
- [OA] Offensive answer (15515, {"tp": ["Kevin Guan"], "fp": ["Brock Adams"]} )
Cases where an answer is posted and contains a curse or two, triggering Smokey's offensive answer filter. Curses are
not ad-hominem, rather are used as part of normal speech.
============================================================
ALSO WORTH MENTIONING
- People should be reading these policies; there are a number of cases of conflicted feedback on MS that I really think
should have been clear-cut. It might be worth giving gentle reminders to those who consistently get it wrong; any
further steps (warnings, removal) should be done case-by-case.
- Admins can nuke feedback. If you get it wrong, that's fine - is it worth also pinging an admin (Undo, ArtOfCode,
hichris123) to remove the incorrect feedback? It's probably insignificant in the grand scheme, but it'd be nice to
keep as accurate as we can (conflicted posts show orange, rather than clear-cut green or red).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment