Timeline for What can we do to fix the "Reasonable management practices" close reason?
Current License: CC BY-SA 3.0
16 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 1, 2015 at 8:09 | comment | added | Jenny D | @Hyppy There's already a text about it in the help center; specifically "[if your question] is not about [...] unauthorized use or misuse of IT systems". I'm not sure it's a frequent enough occurrence that it needs its own custom close reason; we can still VTC with a comment pointing at that reason. | |
Jan 14, 2015 at 18:30 | comment | added | Katherine Villyard | Yeah, I was in that thread. I wasn't sure whether that needed to be closed as "Don't circumvent policy" or as "Ask your sysadmin to fix it for you." (His workstation was allowed to access those subnets, after all.) Either way, it was clearly unsuitable. | |
Jan 14, 2015 at 17:44 | comment | added | Hyppy | I had a similar issue recently, on a thread I think you were on. Someone asked how to use Windows ICS to create a tunnel through an existing VPN so they could access restricted subnets. I probed in comments about why they didn't just configure their VPN to allow access to the subnet, and discovered that they were just trying to circumvent corporate security policy on a system they weren't allowed to administer. I wonder if we need to incorporate a "We won't help you do bad things" reason too. | |
Jan 11, 2015 at 3:30 | comment | added | Katherine Villyard | Exactly, @SamB. It would probably be better to come back in a comment and say, "What problem are you trying to solve?" but if the answer to that comment is, "I just want a list of users' passwords," the answer is, "Please don't do that." | |
Jan 11, 2015 at 3:27 | comment | added | SamB | @kasperd: How can I store passwords in plaintext ... | |
Jan 10, 2015 at 16:25 | comment | added | kasperd | @MichaelHampton If a person asks: "How can I do A?" and somebody answers "You you should not do A", they are really not answering the question. Are you proposing that we are cool with answers saying don't do that, instead of answering how to do what was asked for? Or would it be better to edit the question such that instead of saying "How can I do A?" it says "I am considering doing A, are there any pitfalls I need to look out for?", and then answer that question. | |
Jan 9, 2015 at 18:29 | comment | added | user15323 | @KatherineVillyard Devil's advocate: what if you're running a Minecraft hosting service? | |
Jan 9, 2015 at 15:16 | comment | added | Katherine Villyard | Yeah, I agree. It's not "suitable for a business setting," though. Not unless you want productivity to plummet. ;) | |
Jan 9, 2015 at 15:00 | comment | added | Rob Moir | "I'm setting up a minecraft server" might actually be a professional business question of course. It still might not mean that we're the best site to provide an answer of course... | |
Jan 8, 2015 at 14:05 | history | edited | Katherine Villyard | CC BY-SA 3.0 |
added 444 characters in body
|
Jan 7, 2015 at 22:21 | comment | added | EEAA | @MichaelHampton I agree. But. In my experience, even when applying great effort to be understanding and gentle with our correction, it seems the vast majority of OPs we say "You're doing it wrong" to respond negatively. That's not to say that we ought not give answering those questions a good college try... | |
Jan 7, 2015 at 21:00 | comment | added | Katherine Villyard | Good point, yeah. | |
Jan 7, 2015 at 20:52 | comment | added | Michael Hampton Mod | "You're doing it wrong" is an opportunity to share how to do it right. I don't think questions like that should always be closed. | |
Jan 7, 2015 at 20:27 | comment | added | Katherine Villyard | Indeed! :) I'm trying to avoid "you're doing it wrong" as a close reason, though. Also, "Questions where the OP refuses to listen to any answer may be unsuitable to Server Fault." ;) | |
Jan 7, 2015 at 20:19 | comment | added | user9517 | One man's best practice is another's wtf did you just do there. | |
Jan 7, 2015 at 20:00 | history | answered | Katherine Villyard | CC BY-SA 3.0 |