@AaronHall Do you have some examples? Would you mind making a post on meta with those examples? Putting that kind of banner on other people's answers is never ok, and such edits should be rolled back without hesitation. It might also be appropriate to flag it to moderators so that they can keep an eye on users who are doing this multiple times.
3
If a user doesn't agree with an answer, he should just downvote it, and if he feels very strongly about it (or even otherwise) he can post a comment or even a separate answer explaining why he thinks that answer is bad advice. Vandalizing other people's answers with banners because he doesn't agree with should not be accepted here. Besides, why should we just trust the banner and assume that the answer is bad advice?
I refer you to one user's exceptionally exciting life:
Jan 17: Gets fired by an intoxicated boss, but just went back to
work anyway to find out he has a new manager
Jan 26: Wasted a lot of time at work making an inappropriate
video about themselves as a "joke" for their new manager
...
@ArtOfCode oh I probably was unclear sorry. I meant non-drinking bartender has the same account as a developer who likes whiskey. Guy having exceptionally exciting life from meta question has different account. Though one never knows, same user can in theory operate both accounts
@gnat Yeah. My point was that you're linking that meta question as if to say "no the same user has more outrageous questions", which clearly ain't true :)
Well as answerers we must attempt to suspend disbelief and provide wise answers without questioning the credibility of the asker, with all the credulity we can muster.
Anyways, I can't find where making up a question is actually against the terms of service: stackexchange.com/legal
At least not with about a five minute scan or so...
@AaronHall And, in fact, whether or not said situations actually happened is far less relevant than whether those situations might plausibly happen to other people some day.
it doesn't explicitly say no sharing accounts, though I thought it did - but it does say that you are responsible for ensuring the confidentiality of your password
which isn't quite the same thing but has a similar effect
What that probably means is that Stack Overflow can kill a badly behaved account without worrying too much even if someone claims it was a shared account and no fair.
I wonder if that guy who "trolled" server fault actually thought he didrm -rf root, and then played it off as a hoax to save face.
He claimed he did it to advertise his business. How likely is that?
No way. He thought he deleted from root, posted his question, figured out how to recover, when the story went viral, regretted using his real name when his clients started calling, then claimed it was a hoax.
At least, that's the version of events that makes the most sense to me. I'm not claiming some otherwise special insight or inside info on it.
I'm going to forward the comments to the CM's and let them deal with it.