Timeline for What questions belong on Super User vs Server Fault?
Current License: CC BY-SA 2.5
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2020 at 13:30 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 13, 2017 at 12:14 | history | edited | CommunityBot |
replaced http://serverfault.com/ with https://serverfault.com/
|
|
| Mar 20, 2017 at 10:17 | history | edited | CommunityBot |
replaced http://superuser.com/ with https://superuser.com/
|
|
| Mar 27, 2014 at 21:35 | comment | added | John Thompson | Instead of just merging the two sites, which would be the sensible thing to do, we end up arguing about what belongs where... | |
| Nov 5, 2009 at 17:48 | comment | added | Jim B | @Rich Power Users are consumers if they are not running in an enterprise. If they are running in an enterprise they won't (and probably shouldn't) come to SO or SF for help they would come to SU (if any). More likely though they will ask they local admins to tell them why they system had the issue. | |
| Nov 3, 2009 at 14:49 | comment | added | GEOCHET | @Jim: Consumers != power users. | |
| Nov 3, 2009 at 3:46 | comment | added | Jim B | I would have to disagree- a. most consumers would just reboot and chalk it up to microaoft. Most enterprise desktop people would want to troubleshoot it even if it was their own personal PC | |
| Nov 2, 2009 at 23:06 | comment | added | squillman | @Rich: No, not a domain issue if it only affects one or two PC's. At that point it's a PC issue but you need to know more than a general power user, thus appropriate for SF. That's all, just not so cut and dry. | |
| Nov 2, 2009 at 22:34 | comment | added | Helvick | @Rich B. I've no pointers to specific questions that has been asked but I've plenty of examples of BSOD's where the root cause is related to Enterprise imaging procedures, GPO's gone haywire, poorly tested security apps... Enthusiast\Power User types have zero experience with this class of problem. Sorry 10 years as an Enterprise Client Systems Admin. | |
| Nov 2, 2009 at 22:30 | comment | added | GEOCHET | @squillman: But that is not the same question. That is troubleshooting what happened with a domain change. | |
| Nov 2, 2009 at 22:30 | comment | added | squillman | @Rich: don't get me wrong. I agree that a LOT of the PC things we get on SF are fluff. Just not always the case! | |
| Nov 2, 2009 at 22:29 | comment | added | squillman | @Rich: I'll argue to keep a BSOD question on SF when, for example, one machine on the floor is BSOD'ing after a change was made on the domain when other machines are referenced in the question as not having the same problem. Or when a couple imaged machines are doing something similar. | |
| Nov 2, 2009 at 22:24 | comment | added | GEOCHET | @Squillman: Ok, provide the example question you feel is not in the power user domain but is about troubleshooting BSODs in XP. | |
| Nov 2, 2009 at 22:21 | comment | added | squillman | Yes. I will concede "very likely". But not "clearly in the power user domain". | |
| Nov 2, 2009 at 22:19 | comment | added | GEOCHET | @squillman: It all depends on the question, but a BSOD in XP is very likely SU territory. | |
| Nov 2, 2009 at 22:15 | comment | added | squillman | There are definitely times when troubleshooting a BSOD in XP is appropriate for SF. | |
| Nov 2, 2009 at 20:24 | history | answered | GEOCHET | CC BY-SA 2.5 |