I have been a Wikipedian since 2001 and a MediaWiki developer since 2002. I was Chief Research Officer of the Foundation from May to August 2005. I initiated two of Wikimedia's projects, Wikinews and the Wikimedia Commons, and have made vital contributions to both. I have made roughly 15,000 edits to the English Wikipedia, and uploaded about 15,000 files to Wikimedia Commons. A list of my overall contributions can be found at
http://meta.wikimedia.org/wiki/User:Eloquence
and the linked to pages; this does not include my numerous international activities such as conference speeches, as well as my book and articles about Wikipedia. I have never been blocked before, nor have I ever been subject to an Arbitration Committee ruling (in fact, I was one of Jimmy's original suggestions for the first ArbCom, and one of the people who proposed that very committee).
I have just been indefinitely blocked from the English Wikipedia, and desysopped, by user Danny, under the new nickname "Dannyisme", as an "Office Action" for alleged "reckless endangerment" which was not specified further. I have called Danny on the phone, but he said that he was not willing to discuss the issue, and that I should instead talk to the Foundation attorney instead. To my knowledge, this is the first time office authority has been used to indefinitely block and desysop a user.
What happened?
Yesterday, Danny radically shortened and protected two pages, [[Newsmax.com]] and [[Christopher Ruddy]]. The protection summary was "POV qualms" (nothing else), and there was only the following brief comment on Talk:NewsMax.com:
"This article has been stubbed and protected pending resolution of POV issues. Danny 19:26, 17 April 2006 (UTC)"
There was no mention of WP:OFFICE in the edit summary or on the talk page. Danny did not apply the special Office template, {{office}}, nor did he use the "Dannyisme" account that he created for Foundation purposes, nor did he list the page on WP:OFFICE. Instead, he applied the regular {{protected}} template.
Given that Danny has now more explicitly emphasized this distinction between his role as a Foundation employee and a regular wiki user, I assumed he was acting here as a normal sysop and editor, and unprotected the two pages, with a brief reference to the protection policy. I also asked Danny, on [[Talk:NewsMax.com]], to make it explicit whether the protection was under WP:OFFICE. I would not have reprotected, of course, if he had simply said that they were, and left it at that.
I apologize if this action was perceived as "reckless", but I must emphasize that I was acting in good faith, and that I would much appreciate it if all office actions would be labeled as such. I was under the impression that this was the case given past actions. In any case, I think that the indefinite block and desysopping is very much an overreaction, and would like to hereby publicly appeal to Danny, the community and the Board (since Danny's authority is above the ArbCom) to restore my editing privileges as well as my sysop status. I pledge to be more careful in these matters in the future.
Thanks for reading,
Erik
On Apr 19, 2006, at 11:56 AM, Erik Moeller wrote:
I have been a Wikipedian since 2001 and a MediaWiki developer since 2002. I was Chief Research Officer of the Foundation from May to August 2005....
Clearly a trusted good faith user...
I have just been indefinitely blocked from the English Wikipedia, and desysopped, by user Danny, under the new nickname "Dannyisme", as an "Office Action" for alleged "reckless endangerment" which was not specified further. I have called Danny on the phone, but he said that he was not willing to discuss the issue, and that I should instead talk to the Foundation attorney instead. To my knowledge, this is the first time office authority has been used to indefinitely block and desysop a user.
Who has been kicked off Wikipedia due to an office action...
...There was no mention of WP:OFFICE in the edit summary or on the talk page. Danny did not apply the special Office template, {{office}}, nor did he use the "Dannyisme" account that he created for Foundation purposes, nor did he list the page on WP:OFFICE. Instead, he applied the regular {{protected}} template. Given that Danny has now more explicitly emphasized this distinction between his role as a Foundation employee and a regular wiki user, I assumed he was acting here as a normal sysop and editor, and unprotected the two pages...
...due to interfering with an office action that was not adequately stated as such.
I apologize if this action was perceived as "reckless", but I must emphasize that I was acting in good faith, and that I would much appreciate it if all office actions would be labeled as such.
Agreed. This seems like a simple misunderstanding, and I advise that if the facts that Eric provides are correct, that he be reinstated in full.
As much as I don't want to get into this, and as much as I respect and appreciate Danny's work answering the phones and handling complaints, this is not right.
Further explanation *is needed*.
From what I understand, Danny, wanting to keep things from being unnecessarily dramatic, did not invoke the WP:OFFICE policy with regards to [[Newsmax.com]] and [[Christopher Ruddy]], even though, in fact, that was what was intended - someone had called the office, and complained about the articles. This is OK - although it is troubling that Danny feels the WP:OFFICE policy can't be used whenever it is needed.
What is not acceptable is to retroactively claim that the WP:OFFICE policy *was* invoked, and to then desysop and ban Eloquence on that basis. That's plainly and simply wrong. If it is required in some case that an action by Danny not be reversed, we *have* a policy for that. If Danny does not use it, it's a justified assumption that the action in question *can* be reversed, like any other action on the 'pedia, and immediate banning is not an acceptable response.
I urge that Jimbo, someone else from the Board, and/or Danny further explain and/or apologize for this apparent mistake. We have WP:OFFICE for a reason.
Jesse Weinstein
Jesse W wrote:
As much as I don't want to get into this, and as much as I respect and appreciate Danny's work answering the phones and handling complaints, this is not right.
Further explanation *is needed*.
From what I understand, Danny, wanting to keep things from being unnecessarily dramatic, did not invoke the WP:OFFICE policy with regards to [[Newsmax.com]] and [[Christopher Ruddy]], even though, in fact, that was what was intended - someone had called the office, and complained about the articles. This is OK - although it is troubling that Danny feels the WP:OFFICE policy can't be used whenever it is needed.
What is not acceptable is to retroactively claim that the WP:OFFICE policy *was* invoked, and to then desysop and ban Eloquence on that basis. That's plainly and simply wrong. If it is required in some case that an action by Danny not be reversed, we *have* a policy for that. If Danny does not use it, it's a justified assumption that the action in question *can* be reversed, like any other action on the 'pedia, and immediate banning is not an acceptable response.
I urge that Jimbo, someone else from the Board, and/or Danny further explain and/or apologize for this apparent mistake. We have WP:OFFICE for a reason.
Jesse Weinstein
While I agree...I sense a disturbance in the force. Sean Barrett (The Epopt) just unblocked Erik. *sits back and waits for shit to hit the fan*
John
On 4/19/06, Erik Moeller eloquence@gmail.com wrote:
I pledge to be more careful in these matters in the future.
Hi Erik,
it woudn't surprise you when people describe you as "stubborn" in some way. And yes, I am very much for flexibility in handling rules. After all, I live "be bold" many times.
Speaking of principles... Forgive and forget, please.
And make [[NewsMax.com]] a featured article after extensive review and sourcing. :)
Mathias
On 4/19/06, Mathias Schindler mathias.schindler@gmail.com wrote:
And make [[NewsMax.com]] a featured article after extensive review and sourcing. :)
Mathias
Tricky. The subject would have POV issues the size of GWB and the subject itself is likely to take a serious interest.
-- geni
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Erik Moeller stated for the record:
<snip>
I have just been indefinitely blocked from the English Wikipedia, and desysopped, by user Danny, under the new nickname "Dannyisme", as an "Office Action" for alleged "reckless endangerment" which was not specified further. I have called Danny on the phone, but he said that he was not willing to discuss the issue, and that I should instead talk to the Foundation attorney instead. To my knowledge, this is the first time office authority has been used to indefinitely block and desysop a user.
<snip>
I have unblocked Eloquence on the English Wikipedia. Blocking him was clearly inappropriate. Blocking him indefinitely was astoundingly stupid. Desysopping is equally insane, but resysopping him can wait for the wheels to grind.
- -- Sean Barrett | I've had a perfectly wonderful evening. sean@epoptic.org | But this wasn't it. --Groucho Marx
Sean Barrett wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Erik Moeller stated for the record:
<snip>
I have just been indefinitely blocked from the English Wikipedia, and desysopped, by user Danny, under the new nickname "Dannyisme", as an "Office Action" for alleged "reckless endangerment" which was not specified further. I have called Danny on the phone, but he said that he was not willing to discuss the issue, and that I should instead talk to the Foundation attorney instead. To my knowledge, this is the first time office authority has been used to indefinitely block and desysop a user.
<snip>
I have unblocked Eloquence on the English Wikipedia. Blocking him was clearly inappropriate. Blocking him indefinitely was astoundingly stupid. Desysopping is equally insane, but resysopping him can wait for the wheels to grind.
Danny reverted the block, but didn't use the OFFICE account (Dannyisme). This is getting interesting...
John
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
John Lee stated for the record:
Sean Barrett wrote:
I have unblocked Eloquence on the English Wikipedia. Blocking him was clearly inappropriate. Blocking him indefinitely was astoundingly stupid. Desysopping is equally insane, but resysopping him can wait for the wheels to grind.
Danny reverted the block, but didn't use the OFFICE account (Dannyisme). This is getting interesting...
John
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I eagerly wait an explanation of why Eloquence was indefinitely blocked.
- -- Sean Barrett | I've had a perfectly wonderful evening. sean@epoptic.org | But this wasn't it. --Groucho Marx
I think that lately Danny has not been using the OFFICE tag because people tend to raise a fuss over things protected under this specific policy, and more publicity to/furor over an issue that's already very sensitive is a thorny thing to deal with. My guess, anyway.
k
On 4/19/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
John Lee stated for the record:
Sean Barrett wrote:
I have unblocked Eloquence on the English Wikipedia. Blocking him was clearly inappropriate. Blocking him indefinitely was astoundingly stupid. Desysopping is equally insane, but resysopping him can wait for the wheels to grind.
Danny reverted the block, but didn't use the OFFICE account (Dannyisme). This is getting interesting...
John
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I eagerly wait an explanation of why Eloquence was indefinitely blocked.
Sean Barrett | I've had a perfectly wonderful evening. sean@epoptic.org | But this wasn't it. --Groucho Marx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFERqCaMAt1wyd9d+URAqH0AJ9JoPQGzwIrVrDLCmr3DRntIi114ACfS0/o KhQrCdBJ808M/Dtt3UD6UOk= =n7SA -----END PGP SIGNATURE----- _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
Katefan0 katefan0wiki@gmail.com:
I think that lately Danny has not been using the OFFICE tag because people tend to raise a fuss over things protected under this specific policy, and more publicity to/furor over an issue that's already very sensitive is a thorny thing to deal with. My guess, anyway.
Forgive me if I haven't understood this correctly, but: OFFICE actions are unreversible on pain of dire consequences (e.g. desysopping and indefinite banning), yet anything that Danny does could be an OFFICE action even though not identified as such? This seems very problematic; is there now a class of editor (Danny) whose actions noone can now dare risk undoing in case the action turns out to be an OFFICE action? Surely not.
-- Matt
Why is it problematic? It's a simple enough thing to simply ask Danny first before undoing something he's done, whether or not he's acted on behalf of the foundation. I've done it before (and gotten a "yes but I'd rather this stay low profile" answer very quickly).
Everybody who's an administrator knows -- or ought to know -- that any of Danny's actions could be undertaken on behalf of the foundation. To me, this suggests -- in fact, demands -- a lot more caution with undoing his admin actions than otherwise, and at the very least warrants a discreet "what's this about?" before taking action.
k
On 4/19/06, Matt R matt_crypto@yahoo.co.uk wrote:
Katefan0 katefan0wiki@gmail.com:
I think that lately Danny has not been using the OFFICE tag because
people
tend to raise a fuss over things protected under this specific policy,
and
more publicity to/furor over an issue that's already very sensitive is a thorny thing to deal with. My guess, anyway.
Forgive me if I haven't understood this correctly, but: OFFICE actions are unreversible on pain of dire consequences (e.g. desysopping and indefinite banning), yet anything that Danny does could be an OFFICE action even though not identified as such? This seems very problematic; is there now a class of editor (Danny) whose actions noone can now dare risk undoing in case the action turns out to be an OFFICE action? Surely not.
-- Matt
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
Are we ment to be afraid of danny?
On 4/19/06, Katefan0 katefan0wiki@gmail.com wrote:
Why is it problematic? It's a simple enough thing to simply ask Danny first before undoing something he's done, whether or not he's acted on behalf of the foundation. I've done it before (and gotten a "yes but I'd rather this stay low profile" answer very quickly).
Everybody who's an administrator knows -- or ought to know -- that any of Danny's actions could be undertaken on behalf of the foundation. To me, this suggests -- in fact, demands -- a lot more caution with undoing his admin actions than otherwise, and at the very least warrants a discreet "what's this about?" before taking action.
k
On 4/19/06, Matt R matt_crypto@yahoo.co.uk wrote:
Katefan0 katefan0wiki@gmail.com:
I think that lately Danny has not been using the OFFICE tag because
people
tend to raise a fuss over things protected under this specific policy,
and
more publicity to/furor over an issue that's already very sensitive is
a
thorny thing to deal with. My guess, anyway.
Forgive me if I haven't understood this correctly, but: OFFICE actions
are
unreversible on pain of dire consequences (e.g. desysopping and
indefinite
banning), yet anything that Danny does could be an OFFICE action even
though
not identified as such? This seems very problematic; is there now a
class of
editor (Danny) whose actions noone can now dare risk undoing in case the action turns out to be an OFFICE action? Surely not.
-- Matt
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On 19/04/06, Katefan0 katefan0wiki@gmail.com wrote:
Everybody who's an administrator knows -- or ought to know -- that any of Danny's actions could be undertaken on behalf of the foundation. To me, this suggests -- in fact, demands -- a lot more caution with undoing his admin actions than otherwise, and at the very least warrants a discreet "what's this about?" before taking action.
There is something very problematic about: - creating a special user account to use for "official business" - creating a special template to use for "unreversible legal-issue official business" - (deliberately?) not using either when in fact legal-issue official business is exactly what's being done
Sort of like how there's a convention of waving a white flag to surrender, and in the middle of a warzone, someone leaves the white flag on the ground and comes out holding a gun. The very fact of flouting the convention speaks loudly...
Disclaimer: I obviously know nothing of the specifics of this case, nor do I know Erik or Danny. But on the basis of what has been presented here, Katefan0's comments do not follow logically from the stated sequence of events.
Steve
On 4/19/06, Katefan0 katefan0wiki@gmail.com wrote:
Everybody who's an administrator knows -- or ought to know -- that any of Danny's actions could be undertaken on behalf of the foundation. To me, this suggests -- in fact, demands -- a lot more caution with undoing his admin actions than otherwise, and at the very least warrants a discreet "what's this about?" before taking action.
First of all, I appreciate the support that has been expressed in this thread. I hope we can put this episode behind us quickly and move on.
In response to the above: Danny had _explicitly_ labeled this page as a regular protected page, and _explicitly_ removed the {{office}} template. This is why I believed it was his point that it was _not_ a WP:OFFICE action, but one of his many ongoing contributions to Wikipedia as an editor and admin (over 30,000 edits on en.wp, only a tiny, tiny fraction of which are office-related). Please note that I assumed good faith on Danny's part, which is why I did not revert the "stubbification" itself. I trusted him, as an editor, on the content issue, but I objected to the act of protecting the article, if taken as a regular administrative action. I would _never_ revert a WP:OFFICE action that is labeled as such, but again, here the opposite was the case; it was labeled as a non-office action.
Apparently (I'm still not sure), the protection was a _sensitive_ Office Action which is not meant to be publicized as such. That idea did not occur to me. I'm not sure if this approach is at all viable (if anything, this episode may show that it is not), and I am not very fond of the idea of mixing regular editorial/sysop tasks with Office Actions which cannot be clearly distinguished, and whose reversal is, effectively, treated with the Wikipedia equivalent of the [[Usenet Death Penalty]]. However, please understand that I will from now on remain largely silent on this issue, and will wait for the Board to clarify things.
Again, I apologize if my actions were rash, but I believed them to be justified based on the information available to me. As of this point in time, I am banned for 48 hours; this is a punishment I can accept. I am also still indefinitely blocked on Meta and desysopped. I would like to kindly request that the remaining indefinite block and the desysopping will be reversed. Again, I will do my best to follow policy, even if the policy is that "Anything Danny does is unusual and should be treated differently from what regular admins/editors do". However, I do believe it needs to be clear _exactly_ what the situation is.
Thanks,
Erik
On 4/20/06, Katefan0 katefan0wiki@gmail.com wrote:
Everybody who's an administrator knows -- or ought to know -- that any of Danny's actions could be undertaken on behalf of the foundation. To me, this suggests -- in fact, demands -- a lot more caution with undoing his admin actions than otherwise, and at the very least warrants a discreet "what's this about?" before taking action.
I agree, and I think this is really the point to take out of this. We should all operate on the presumption that when Danny does something, he's doing it for a Good Reason, and that one shouldn't undo it unless one has checked the reason behind it with Danny first (that's if it should even be undone at all). A little communication solves alot of problems.
-- Stephen Bain stephen.bain@gmail.com
Stephen Bain wrote:
On 4/20/06, Katefan0 katefan0wiki@gmail.com wrote:
Everybody who's an administrator knows -- or ought to know -- that any of Danny's actions could be undertaken on behalf of the foundation. To me, this suggests -- in fact, demands -- a lot more caution with undoing his admin actions than otherwise, and at the very least warrants a discreet "what's this about?" before taking action.
I agree, and I think this is really the point to take out of this. We should all operate on the presumption that when Danny does something, he's doing it for a Good Reason, and that one shouldn't undo it unless one has checked the reason behind it with Danny first (that's if it should even be undone at all). A little communication solves alot of problems.
But Danny has explicitly said (on this list) that he is also a normal editor, and only his actions that are accompanied with a statement that they are WP:OFFICE actions should be treated as such. So if he does something and does not tag it WP:OFFICE, we should all operate on the presumption that he is doing it in his capacity as a normal Wikipedian.
-Mark
On 4/20/06, Delirium delirium@hackish.org wrote:
But Danny has explicitly said (on this list) that he is also a normal editor, and only his actions that are accompanied with a statement that they are WP:OFFICE actions should be treated as such. So if he does something and does not tag it WP:OFFICE, we should all operate on the presumption that he is doing it in his capacity as a normal Wikipedian.
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard. WP:OFFICE has nothing to do with that; wheel warring is still wheel warring.
Kelly
Kelly Martin wrote:
On 4/20/06, Delirium delirium@hackish.org wrote:
But Danny has explicitly said (on this list) that he is also a normal editor, and only his actions that are accompanied with a statement that they are WP:OFFICE actions should be treated as such. So if he does something and does not tag it WP:OFFICE, we should all operate on the presumption that he is doing it in his capacity as a normal Wikipedian.
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard. WP:OFFICE has nothing to do with that; wheel warring is still wheel warring.
He didn't revert Danny's edits or wheel war. Danny stubbed and protected the page; Erik noted that he was willing to give Danny the benefit of the doubt on stubbing, but that the protection was contrary to the protection policy (a correct observation), so unprotected the page but left it stubbed. It is quite acceptable and even encouraged to unprotect pages that have been inappropriately protected.
If Danny had reprotected and Erik had unprotected again, that would be a wheel war. A single correction of a presumably mistaken admin action is not wheel-warring, especially when it doesn't even involve completely reversal of the action, just the problematic part.
In addition, blocking another user yourself after you personally have had an altercation with him has always been regarded as inappropriate, so Danny's block was inappropriate by any reasonable standard.
-Mark
On 4/20/06, Delirium delirium@hackish.org wrote:
He didn't revert Danny's edits or wheel war.
Yes, he did. He reverted another admin's protection within a very short time of when it was imposed, without discussion. That, by definition, is the open salvo in a wheel war.
Kelly
Since Danny didn't apply the WP:OFFICE tag, does that warrant an immediate desysoping and indefinite ban? I've seen such measures only after an arbitration case. Nowhere did Danny say he was applying WP:OFFICE. If Erik got into a wheel war, fine. I've seen wheel-warring admins get desysoped (or cautioned, or whatever), but only after an arbitration case was held against them. An indef ban should certainly only come after an arbitration case.
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Delirium delirium@hackish.org wrote:
He didn't revert Danny's edits or wheel war.
Yes, he did. He reverted another admin's protection within a very short time of when it was imposed, without discussion. That, by definition, is the open salvo in a wheel war.
Kelly _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Death Phoenix stated for the record:
Since Danny didn't apply the WP:OFFICE tag, does that warrant an immediate desysoping and indefinite ban? I've seen such measures only after an arbitration case. Nowhere did Danny say he was applying WP:OFFICE. If Erik got into a wheel war, fine. I've seen wheel-warring admins get desysoped (or cautioned, or whatever), but only after an arbitration case was held against them. An indef ban should certainly only come after an arbitration case.
Minor correction: even the ArbComm cannot impose an indefinite ban.
Don't let the issue here get buried under discussion of OFFICE. The issue is that Danny, while apparently acting as a common or garden variety admin, -- and not just without discussion, but rather while /actively refusing to discuss/ -- imposed a lifetime ban from Wikipedia.
Indefinite block.
While /actively refusing to discuss/.
- -- Sean Barrett | I've had a perfectly wonderful evening. sean@epoptic.org | But this wasn't it. --Groucho Marx
On 4/20/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Death Phoenix stated for the record:
Since Danny didn't apply the WP:OFFICE tag, does that warrant an immediate desysoping and indefinite ban? I've seen such measures only after an arbitration case. Nowhere did Danny say he was applying WP:OFFICE. If Erik got into a wheel war, fine. I've seen wheel-warring admins get desysoped (or cautioned, or whatever), but only after an arbitration case was held against them. An indef ban should certainly only come after an arbitration case.
Minor correction: even the ArbComm cannot impose an indefinite ban.
Don't let the issue here get buried under discussion of OFFICE. The issue is that Danny, while apparently acting as a common or garden variety admin, -- and not just without discussion, but rather while /actively refusing to discuss/ -- imposed a lifetime ban from Wikipedia.
Indefinite block.
While /actively refusing to discuss/.
Precisely. Trying to defend Danny's desysopping and ban by crying wheel-war is just wikilawyering in my opinion.
--Oskar
On 4/20/06, Oskar Sigvardsson oskarsigvardsson@gmail.com wrote:
Minor correction: even the ArbComm cannot impose an indefinite ban.
Don't let the issue here get buried under discussion of OFFICE. The issue is that Danny, while apparently acting as a common or garden variety admin, -- and not just without discussion, but rather while /actively refusing to discuss/ -- imposed a lifetime ban from Wikipedia.
Indefinite block.
While /actively refusing to discuss/.
Precisely. Trying to defend Danny's desysopping and ban by crying wheel-war is just wikilawyering in my opinion.
I don't know about wikilawyering, but at the very least, it shows an inconsistent use and enforcement of WP:OFFICE and normal admin actions.
On 4/20/06, Oskar Sigvardsson oskarsigvardsson@gmail.com wrote:
On 4/20/06, Sean Barrett sean@epoptic.org wrote:
Death Phoenix stated for the record:
Since Danny didn't apply the WP:OFFICE tag, does that warrant an immediate desysoping and indefinite ban? I've seen such measures only after an
<
Minor correction: even the ArbComm cannot impose an indefinite ban.
Both the ban and the desysopping were indefensible. Editors should not be punished for violating nonexistent policies.
Desysopping on more than one project was unprecedented and outrageous.
It is perfectly legitimate to have legal reasons for actions to remain secret. It is not legitimate to pretend that such reasons don't exist -- and then punish editors because they really do.
Don't let the issue here get buried under discussion of OFFICE. The issue is that Danny, while apparently acting as a common or garden variety admin, -- and not just without discussion, but rather while /actively refusing to discuss/ -- imposed a lifetime ban from Wikipedia.
Right. This is not an OFFICE issue, except insofar as that was the source of a misunderstanding. This is an issue of misuse of authority and refusal to communicate, once the misunderstanding had taken place.
-- ++SJ
Indefinite block.
While /actively refusing to discuss/.
Precisely. Trying to defend Danny's desysopping and ban by crying wheel-war is just wikilawyering in my opinion.
--Oskar
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Delirium delirium@hackish.org wrote:
He didn't revert Danny's edits or wheel war.
Yes, he did. He reverted another admin's protection within a very short time of when it was imposed, without discussion. That, by definition, is the open salvo in a wheel war.
Kelly
So you condem this action?:
http://en.wikipedia.org/w/index.php?title=Special%3ALog&type=protect&...
-- geni
"Delerium",
In regards to:
[Erik] didn't revert Danny's edits or wheel war. Danny stubbed and protected the page; Erik noted that he was willing to give Danny the benefit of the doubt on stubbing, but that the protection was contrary to the protection policy (a correct observation), so unprotected the page but left it stubbed. It is quite acceptable and even encouraged to unprotect pages that have been inappropriately protected.
While we're engaging in this critique of Danny's response, it might make sense to ask whether or not Danny, and the other office people, are aware that there exists some large segment of the admin population who regard it as routine to undo other admin actions without discussion because they were "out of process", or "obviously wrong", or whatever. Can we imagine the possibility that some people might interpret that as inexplicable, or even hostile, interference, if they aren't used to this?
Jkelly
On 4/20/06, jkelly@fas.harvard.edu jkelly@fas.harvard.edu wrote:
"Delerium",
In regards to:
[Erik] didn't revert Danny's edits or wheel war. Danny stubbed and protected the page; Erik noted that he was willing to give Danny the benefit of the doubt on stubbing, but that the protection was contrary to the protection policy (a correct observation), so unprotected the page but left it stubbed. It is quite acceptable and even encouraged to unprotect pages that have been inappropriately protected.
While we're engaging in this critique of Danny's response, it might make sense to ask whether or not Danny, and the other office people, are aware that there exists some large segment of the admin population who regard it as routine to undo other admin actions without discussion because they were "out of process", or "obviously wrong", or whatever. Can we imagine the possibility that some people might interpret that as inexplicable, or even hostile, interference, if they aren't used to this?
Jkelly
You are suggesting that there are admins on wikipedia who are not aware that stuff done on wikipedia may be undone?
-- geni
Geni,
You are suggesting that there are admins on wikipedia who are not aware that stuff done on wikipedia may be undone?
I'm not clear on whether or not you're just goofing around here. There are a lot of things that "may" potentially be done on a wiki that would surprise or alarm experienced users if they were actually put into practice. If you were just goofing, I didn't get the joke.
Jkelly
On 4/20/06, jkelly@fas.harvard.edu jkelly@fas.harvard.edu wrote:
Geni,
You are suggesting that there are admins on wikipedia who are not aware that stuff done on wikipedia may be undone?
I'm not clear on whether or not you're just goofing around here. There are a lot of things that "may" potentially be done on a wiki that would surprise or alarm experienced users if they were actually put into practice. If you were just goofing, I didn't get the joke.
Jkelly
It's a wiki. Actions get reversed. The only way to prevent that is to proive masses of justification or cite WP:OFFICE.
-- geni
On 4/20/06, jkelly@fas.harvard.edu jkelly@fas.harvard.edu wrote:
While we're engaging in this critique of Danny's response, it might make sense to ask whether or not Danny, and the other office people, are aware that there exists some large segment of the admin population who regard it as routine to undo other admin actions without discussion because they were "out of process", or "obviously wrong", or whatever. Can we imagine the possibility that some people might interpret that as inexplicable, or even hostile, interference, if they aren't used to this?
Perhaps the real problem is that a large segment of our admin population needs not to be admins anymore.
Kelly
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, jkelly@fas.harvard.edu jkelly@fas.harvard.edu wrote:
While we're engaging in this critique of Danny's response, it might make sense to ask whether or not Danny, and the other office people, are aware that there exists some large segment of the admin population who regard it as routine to undo other admin actions without discussion because they were "out of process", or "obviously wrong", or whatever. Can we imagine the possibility that some people might interpret that as inexplicable, or even hostile, interference, if they aren't used to this?
Perhaps the real problem is that a large segment of our admin population needs not to be admins anymore.
Kelly
If you have gripes with some of our admins, start an RfC on them. As soon as there are legitimate issues, even borderline-looney barely legitimate issues, someone always starts an RfC.
We have, what, 4000 new articles a day, something like that. Something like half gets speedied, and a chunk goes to Afd or gets {{prod}}ed. We need every single admin we can get.
Simply disagreeing with someone, or thinking that they break some policies are not enough for desysopping. Such an action is never punitive, which means that an admin can (and should) only lose their status for misuse of their priviliges. Can you name anyone lately? I mean, other than Eloquence. If you can't then stop writing these inflammatory messages, that serve no point whatsoever. If you can, then do something about it, and stop writing these inflammatory messages that serve no point whatsoever.
--Oskar
On 4/20/06, Oskar Sigvardsson oskarsigvardsson@gmail.com wrote:
We have, what, 4000 new articles a day, something like that. Something like half gets speedied, and a chunk goes to Afd or gets {{prod}}ed. We need every single admin we can get.
No, we don't. 50% of admin actions in March 2006 were performed by 29 of our nearly 900 admins; 90% by 170. We could probably lose 500 admins without any real impact on our ability to get administrative work done. Note also that sending articles to AfD or prod doesn't require an admin.
Simply disagreeing with someone, or thinking that they break some policies are not enough for desysopping. Such an action is never punitive, which means that an admin can (and should) only lose their status for misuse of their priviliges. Can you name anyone lately?
Karmafist. Ed Poor. Guanaco. Stevertigo. There's others; do you pay any attention to the Arbitration Committee's docket lately?
Kelly
On 20/04/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
work done. Note also that sending articles to AfD or prod doesn't require an admin.
You can send them there, but they don't go anywhere much afterwards :)
Fwiw, I agree with you, but when this point was brought up at RfA, some admins made the point that there are useful things they can do without showing up on the radar, and even an admin who only does 2 or 3 "admin actions" per month may still be very valuable in other ways. Hell, how often does Jimbo perform an "admin action"?
Would it be worth asking less active admins to consider handing in their mops, on the understanding that they can ask for them back without having to go through RfA again? Just to keep the number of mops out there down a bit?
Steve
On 4/20/06, Steve Bennett stevage@gmail.com wrote:
Would it be worth asking less active admins to consider handing in their mops, on the understanding that they can ask for them back without having to go through RfA again? Just to keep the number of mops out there down a bit?
I really don't see any need for that. Most of the low-activity admins aren't the ones causing trouble, just a few of them. My point is that we should not be that concerned about lopping off problematic admins; we're not running short on them by any means.
Kelly
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Steve Bennett stevage@gmail.com wrote:
Would it be worth asking less active admins to consider handing in their mops, on the understanding that they can ask for them back without having to go through RfA again? Just to keep the number of mops out there down a bit?
I really don't see any need for that. Most of the low-activity admins aren't the ones causing trouble, just a few of them. My point is that we should not be that concerned about lopping off problematic admins; we're not running short on them by any means.
The practical question here is how we go about determining which admins are "problematic".
Kirill Lokshin
On 4/20/06, Kirill Lokshin kirill.lokshin@gmail.com wrote:
The practical question here is how we go about determining which admins are "problematic".
Indeed.
Kelly
On 21/04/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Kirill Lokshin kirill.lokshin@gmail.com wrote:
The practical question here is how we go about determining which admins are "problematic".
Indeed.
It is probably worth remembering that this whole sorry argument began with one of the few dozen people least likely to get desysopped by any such test...
-- - Andrew Gray andrew.gray@dunelm.org.uk
On 4/20/06, Andrew Gray shimgray@gmail.com wrote:
On 21/04/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Kirill Lokshin kirill.lokshin@gmail.com wrote:
The practical question here is how we go about determining which admins are "problematic".
Indeed.
It is probably worth remembering that this whole sorry argument began with one of the few dozen people least likely to get desysopped by any such test...
If you mean the unprotect/desysop/block mess, certainly.
If we make some (possibly quite incorrect) assumptions about why Danny moved in the way he did -- to wit, that at least a partial reason for keeping office actions less visible is the leaking of deleted information -- it becomes less clear. Would desysopping the (assumed) admin(s) passing this information to wikitruth -- ignoring for the moment the question of whether we can catch them -- help in avoiding the need for this sort of secrecy in the future? Or will office actions need to be kept under wraps even if there's no danger of admins interfering?
Kirill Lokshin
On 4/21/06, Kirill Lokshin
kirill.lokshin@gmail.com wrote:
On 4/20/06, Andrew Gray shimgray@gmail.com wrote:
On 21/04/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Kirill Lokshin kirill.lokshin@gmail.com wrote:
The practical question here is how we go about determining which admins are "problematic".
Indeed.
It is probably worth remembering that this whole sorry argument began
with one of the few dozen people least likely to get desysopped by any such test...
If you mean the unprotect/desysop/block mess, certainly.
If we make some (possibly quite incorrect) assumptions about why Danny moved in the way he did -- to wit, that at least a partial reason for keeping office actions less visible is the leaking of deleted information -- it becomes less clear. Would desysopping the (assumed) admin(s) passing this information to wikitruth -- ignoring for the moment the question of whether we can catch them -- help in avoiding the need for this sort of secrecy in the future? Or will office actions need to be kept under wraps even if there's no danger of admins interfering?
Kirill Lokshin _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
Folks,
Why should we worry about Wikitruth? They claim to be the "Scandal Sheet that anyone can edit." It will probably be a ghost site within a year.
If we need to use Office for whatever reasons, we need to use Office. The fact is that if an article meets out standards such as NPOV, no original research and verifiability, it shouldn't have problems with Office. It is the articles which don't comply with these standards that run into problems. If we have an article which is a stub for a day or so, we have plenty of time to expand it in a way consistent with our policies
We shouldn't worry about what Wikitruth thinks or says.
We should take notice of considered criticism from whatever source whether it be Nature, the Guardian, USA Today or the blogger who raised concerns about some of our biographies such as Jane Fonda. I have seen nothing on Wikitruth that indicates that we should consider its criticisms seriously. We certainly should not change our policies because of them.
A brief inspection of Wikitruth has given me no reason to consider its comments to be considered criticism. It is a derivative of Wikipedia and of little interest to the wider world.
Regards
*Keith Old*
I don't
I really don't see any need for that. Most of the low-activity admins aren't the ones causing trouble, just a few of them. My point is that we should not be that concerned about lopping off problematic admins; we're not running short on them by any means.
The practical question here is how we go about determining which admins are "problematic".
You are approaching the problem the wrong way. You only need to determine which _actions_ are problematic. Wikipedia has a number of policies for doing that. Then you only need to act on it.
-- mvh Björn
Steve Bennett wrote:
Fwiw, I agree with you, but when this point was brought up at RfA, some admins made the point that there are useful things they can do without showing up on the radar, and even an admin who only does 2 or 3 "admin actions" per month may still be very valuable in other ways. Hell, how often does Jimbo perform an "admin action"?
Not to mention that counting "admin actions" is about as useful a metric as counting edits. I can easily make a hundred or two admin actions a day, if I put my mind to it, by clearing out some of the more monotonous backlogs. Or I can spend the time carefully editing a MediaWiki page, which won't even show up as an admin action in most statistics. Neither action is intrinsically more valuable than the other, but their effect on the statistics is completely different.
On Apr 20, 2006, at 3:49 PM, Steve Bennett wrote:
Would it be worth asking less active admins to consider handing in their mops, on the understanding that they can ask for them back without having to go through RfA again? Just to keep the number of mops out there down a bit?
What's the point? Are we running out of mops?
On 22/04/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 20, 2006, at 3:49 PM, Steve Bennett wrote:
Would it be worth asking less active admins to consider handing in their mops, on the understanding that they can ask for them back without having to go through RfA again? Just to keep the number of mops out there down a bit?
What's the point? Are we running out of mops?
Yep. Or more to the point, the mop-provider is saying "when people start actually using the mops, I'll give out some more" or something. People make false assumptions based on the fact that we have 800 or so admins. If we only had 100 admins, apparently we would still get nearly as much work done, but people would make different judgments about them.
Fwiw, I don't have a problem with having marginally active admins. But you do relatively often see comments like "we already have 800 admins, we don't really need any more", to which someone always replies "see the copyvio backlog". That discussion *would* work better if there were only 100...
Steve
On 4/22/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 20, 2006, at 3:49 PM, Steve Bennett wrote:
Would it be worth asking less active admins to consider handing in their mops, on the understanding that they can ask for them back without having to go through RfA again? Just to keep the number of mops out there down a bit?
What's the point? Are we running out of mops?
It might reduce the risk of abuse of administrator powers such as that which is apparently taking place on wikitruth. I'm not convinced that it's feasible, though.
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote: <snip>
Karmafist. Ed Poor. Guanaco. Stevertigo. There's others; do you pay any attention to the Arbitration Committee's docket lately?
Ofcourse I've been paying attention. Those admins misused adminship, they got deadminned. You said "Perhaps the real problem is that a large segment of our admin population needs not to be admins anymore." That's four people out of 800. Half of a percent. It's not what anyone would call a large segment. The vast, vast majority perform their duty admirably, without anyone complaining.
So how, in what way, was your comment anything other than inflammatory? Please tell me, I really want to know.
On Apr 20, 2006, at 2:53 PM, Kelly Martin wrote:
No, we don't. 50% of admin actions in March 2006 were performed by 29 of our nearly 900 admins; 90% by 170. We could probably lose 500 admins without any real impact on our ability to get administrative work done. Note also that sending articles to AfD or prod doesn't require an admin.
Here's an interesting question: assuming those statistics are the same each month, is it the same 29 admins each month, or does it turn over? Some months/days I really dig into CSD and PROD backlog, other months/days I'm too busy with real life to devote that much time.
On 4/22/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 20, 2006, at 2:53 PM, Kelly Martin wrote:
No, we don't. 50% of admin actions in March 2006 were performed by 29 of our nearly 900 admins; 90% by 170. We could probably lose 500 admins without any real impact on our ability to get administrative work done. Note also that sending articles to AfD or prod doesn't require an admin.
Here's an interesting question: assuming those statistics are the same each month, is it the same 29 admins each month, or does it turn over? Some months/days I really dig into CSD and PROD backlog, other months/days I'm too busy with real life to devote that much time.
The top group are probably those killing pictures.
-- geni
geni geniice@gmail.com wrote: On 4/22/06, Philip Welch wrote:
On Apr 20, 2006, at 2:53 PM, Kelly Martin wrote:
No, we don't. 50% of admin actions in March 2006 were performed by 29 of our nearly 900 admins; 90% by 170. We could probably lose 500 admins without any real impact on our ability to get administrative work done. Note also that sending articles to AfD or prod doesn't require an admin.
Here's an interesting question: assuming those statistics are the same each month, is it the same 29 admins each month, or does it turn over? Some months/days I really dig into CSD and PROD backlog, other months/days I'm too busy with real life to devote that much time.
The top group are probably those killing pictures.
-- geni
What do you mean, "Killing pictures"....? Massive image deletions...?- Zero _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
--------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.
Zero wrote:
geni geniice@gmail.com wrote: On 4/22/06, Philip Welch wrote:
On Apr 20, 2006, at 2:53 PM, Kelly Martin wrote:
No, we don't. 50% of admin actions in March 2006 were performed by 29 of our nearly 900 admins; 90% by 170. We could probably lose 500 admins without any real impact on our ability to get administrative work done. Note also that sending articles to AfD or prod doesn't require an admin.
Here's an interesting question: assuming those statistics are the same each month, is it the same 29 admins each month, or does it turn over? Some months/days I really dig into CSD and PROD backlog, other months/days I'm too busy with real life to devote that much time.
The top group are probably those killing pictures.
What do you mean, "Killing pictures"....? Massive image deletions...?- Zero
See http://en.wikipedia.org/wiki/CAT:ORFU et al.
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source. I figure it should be impossible to write an article without a third party reference, as per [[WP:V]], [[WP:NOR}] and [[WP:NPOV]], and so I hope that people will consider using that as the level for notability in areas where no other guidance exists.
Thoughts welcomed at [[Wikipedia:Notability/Proposals]].
On Apr 23, 2006, at 4:21 PM, Steve Block wrote:
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
----- Original Message ---- From: Philip Welch
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...)
in particular number 7: Free the Maps!
I would say absolute yes that information should be in a Wikimedia project that seamlessly integrates into Wikipedia.
Pete
Perhaps, but a map is not an encyclopedia. It should all be free, but not everything should necesserilly be put in this particular project.
Mgm
On 4/25/06, Pete Bartlett pcb21@yahoo.com wrote:
----- Original Message ---- From: Philip Welch
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...)
in particular number 7: Free the Maps!
I would say absolute yes that information should be in a Wikimedia project that seamlessly integrates into Wikipedia.
Pete
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
MGM wrote:
On 4/25/06, Pete Bartlett pcb21@yahoo.com wrote: ----- Original Message ----
From: Philip Welch
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...)
in particular number 7: Free the Maps!
I would say absolute yes that information should be in a Wikimedia project that seamlessly integrates into Wikipedia.
Pete
Perhaps, but a map is not an encyclopedia. It should all be free, but not everything should necesserilly be put in this particular project. Mgm
The free encyclopedia, the free dictionary, the free news reports, the free media repositry, the free documents and quotes repositries, the free textbooks, the free species directory, <redlink>the free thesaurus</redlink> and <redlink>the free atlas</redlink>
are all different sides of the same coin. With the technology provided by the Web we should be mixing and integrating these much much more than we are. It is a great shame that there is very little cross-project co-operation. A further frustrating aspect of a large community directing a project is that it is very conservative and keen to maintain the status quo.
Why is that as a community we haven't been badgering the board to do anything dramatic since Wikinews was set up /18/ months ago.
Pete
On 4/25/06, Pete Bartlett pcb21@yahoo.com wrote:
MGM wrote:
On 4/25/06, Pete Bartlett pcb21@yahoo.com wrote: ----- Original Message ----
From: Philip Welch
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...)
in particular number 7: Free the Maps!
I would say absolute yes that information should be in a Wikimedia project that seamlessly integrates into Wikipedia.
Pete
Perhaps, but a map is not an encyclopedia. It should all be free, but not everything should necesserilly be put in this particular project. Mgm
The free encyclopedia, the free dictionary, the free news reports, the free media repositry, the free documents and quotes repositries, the free textbooks, the free species directory, <redlink>the free thesaurus</redlink> and <redlink>the free atlas</redlink>
are all different sides of the same coin. With the technology provided by the Web we should be mixing and integrating these much much more than we are. It is a great shame that there is very little cross-project co-operation. A further frustrating aspect of a large community directing a project is that it is very conservative and keen to maintain the status quo.
Why is that as a community we haven't been badgering the board to do anything dramatic since Wikinews was set up /18/ months ago.
Pete
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
What I was trying to say that even if a intersection should be covered, it shouldn't necessarily be in Wikipedia.
Mgm
On 4/25/06, Pete Bartlett pcb21@yahoo.com wrote:
MGM wrote:
On 4/25/06, Pete Bartlett pcb21@yahoo.com wrote: ----- Original Message ----
From: Philip Welch
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...)
in particular number 7: Free the Maps!
I would say absolute yes that information should be in a Wikimedia project that seamlessly integrates into Wikipedia.
Pete
Perhaps, but a map is not an encyclopedia. It should all be free, but not everything should necesserilly be put in this particular project. Mgm
The free encyclopedia, the free dictionary, the free news reports, the free media repositry, the free documents and quotes repositries, the free textbooks, the free species directory, <redlink>the free thesaurus</redlink> and <redlink>the free atlas</redlink>
are all different sides of the same coin. With the technology provided by the Web we should be mixing and integrating these much much more than we are. It is a great shame that there is very little cross-project co-operation. A further frustrating aspect of a large community directing a project is that it is very conservative and keen to maintain the status quo.
Wikimaps sadly isn't really practicle. A lot of work goes into makeing a map and a lot of that has to be done on the ground. If you want free maps you may just have to wait for the copyright on OS maps and the like to expire and then work from those.
Why is that as a community we haven't been badgering the board to do anything dramatic since Wikinews was set up /18/ months ago.
Pete
Because wikiversity din't really get the support some people were expecting. -- geni
From: "geni" geniice@gmail.com
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...) in particular number 7: Free the Maps!
Perhaps, but a map is not an encyclopedia. It should all be free, but not everything should necesserilly be put in this particular project. Mgm
<redlink>the free atlas</redlink>
Wikimaps sadly isn't really practicle. A lot of work goes into makeing a map and a lot of that has to be done on the ground.
With the spread of consumer GPS devices, from Garmin/Magellan and others, "free map" is getting more practical. A wiki method of creating the maps would split "trackers" who uploads the tracks of roads and other features, and "mappers" who trace over the tracks and storing/compiling in useable formats format.
Exactly the above methodology is used by the trackers and mappers on http://www.malsingmaps.com . The maps there covering Malaysia and Singapore are free. Online version of the map at http://www.malsingmaps.net .
I remember there is already a sort of wiki map project by someone in UK. Lets see, googling "wiki map". Here it is, http://www.openstreetmap.org/ "OpenStreetMap is a free editable map of the whole world. It is made by people like you. OpenStreetMap allows you to view, edit and use geographical data in a collaborative way from anywhere on Earth."
regards, sabre23t =^.^=
On 25/04/06, S.M.Sabri S.M.Ismail sms@sabre23t.com wrote:
With the spread of consumer GPS devices, from Garmin/Magellan and others, "free map" is getting more practical. A wiki method of creating the maps would split "trackers" who uploads the tracks of roads and other features, and "mappers" who trace over the tracks and storing/compiling in useable formats format.
See also http://en.wikipedia.org/wiki/Mashup_%28web_application_hybrid%29#Mapping_mas...
Steve
On 4/25/06, Pete Bartlett pcb21@yahoo.com wrote:
Why is that as a community we haven't been badgering the board to do anything dramatic since Wikinews was set up /18/ months ago.
Wikiversity is in the works: http://meta.wikimedia.org/wiki/Wikiversity/Modified_project_proposal
However, a good project needs time. There's no point in advocating a WikiAtlas if you don't know what software you're going to use to edit it. As for "free thesaurus", take a look at the WiktionaryZ prototype at http://www.wiktionaryz.org/ ; we have imported the full GEMET thesaurus, and will have some surprises coming soon.
But there's a _LOT_ we can do to make our existing projects work more smoothly. As important as it is to take on world-changing new ideas, it's crucial to follow up on the ones you've started.
Erik
MGM, Geni and Erik wrote about:
WikiAtlas
As it was the specific example of mapping data that spurred my mini-rant, I wanted to quickly reply on that aspect. The more general stuff I hope to say something more coherent on later.
To Geni: Yes copyright isn't on our side here. But the situation in the US is better than many other places, so we could push ahead there.
To MGM: I want to encourage more general thinking than a binary "this is in" /"this is out". Of course if we are writing about Pullman, Washington, to write in prose about every junction would be tedious beyond belief. But on the hand, why shouldn't (in an ideal Free world) the user have the possibility to open a sidebar with a map of the area to the standard of Google Maps, with other places with a Wikipedia article marked on. etc etc. We should have useful integration, not standalone barely-speaking-to-one-another projects.
If that's a bit blue sky here's another example, if you go to the http://en.wikipedia.org/wiki/London article you will see some co-ordinates in the top-right corner (at least in Monobook skin - not sure about the rest). Click those co-ordinates and you get a list of map resources - it is an extension modelled on clicking on an ISBN. That is a simple idea, but is really effective. I'd like to see that spread across all geographical articles just as a simple start. Also, is there a show-stopping reason why the extension is not turned on MediaWiki? (I'll try the other list for that)
Pete
On Apr 25, 2006, at 4:58 AM, Pete Bartlett wrote:
Why is that as a community we haven't been badgering the board to do anything dramatic since Wikinews was set up /18/ months ago.
Cuz Wikinews isn't good yet, Wikipedia is only good in one language (German) and usable in a couple more (English, etc.), Wiktionary is just there, Wikibooks is a mess, and Wikiversity doesn't even know what it is yet.
It would be best if we didn't subdivide our efforts even more than they are now, or we won't get anything done!
Why is that as a community we haven't been badgering the board to do anything dramatic since Wikinews was set up /18/ months ago.
Cuz Wikinews isn't good yet, Wikipedia is only good in one language (German) and usable in a couple more (English, etc.), Wiktionary is just there, Wikibooks is a mess, and Wikiversity doesn't even know what it is yet.
It would be best if we didn't subdivide our efforts even more than they are now, or we won't get anything done!
Well "dramatic" didn't have to mean a new project!
Why is de: better than en: is a great question. They appear to have covered classic encyclopedic topics much better than en: and their proportion of Exzellente Artikeler is double that of our FAs, despite standards. How to learn from de would be a great thing to discuss.
You also note that other projects are stumbling along and that they are cause a sub-division of effort. We should change things so that projects collaborate routinely. You can click on any word in Britannica Online and get a dictionary definition for example. Why not have this in Wikipedia?
Why not have extensions that auto-detect the existence of quotations or source material by or about a person and even drag a snippet of it into the sidebar?
Yep there is lots to do, but recently the unimaginative debates about notability seem to be dominating.
Pete
On 4/26/06, Pete Bartlett pcb21@yahoo.com wrote:
You also note that other projects are stumbling along and that they are cause a sub-division of effort. We should change things so that projects collaborate routinely. You can click on any word in Britannica Online and get a dictionary definition for example. Why not have this in Wikipedia?
Why not have extensions that auto-detect the existence of quotations or source material by or about a person and even drag a snippet of it into the sidebar?
Because our Devs are already hopelessly overloaded with feature requests.
-- geni
Because our Devs are already hopelessly overloaded with feature requests.
Yes I am aware how easily this could become "Request A Feature" thread. I think the devs we have do a fabulous job and do not want to pound on them.
One wonderful thing Brion has done recently is get the Foundation signed up for the Google Summer of Code. Let's make sure the community tells the devs what is important to us. There are a list of possible projects at
http://meta.wikimedia.org/wiki/Summer_of_Code_2006
Pete
Pete Bartlett wrote:
Why is de: better than en: is a great question. They appear to have covered classic encyclopedic topics much better than en: and their proportion of Exzellente Artikeler is double that of our FAs, despite standards. How to learn from de would be a great thing to discuss.
In a word: "Ordnung".
The full range of connotation is not easily translated into English, but the disambig for de:'s [[Ordnung]] connects to lots of telling things, such as en:'s [[social structure]] and the like. At the risk of playing amateur sociologist and offending everybody, I'll opine that while the German cultural liking for "Ordnung" sounds to USians and Brits an awful lot like a compulsion to "follow orders", in the WP context I think it translates to a greater sense of duty to help achieve communal goals.
For instance, while I will likely will get tired of writing about a proper topic like fish anatomy and impulsively shift over to something trivial like old D&D modules, the German editor will tend to feel bound to finish with the fish anatomy first. Multiply that by thousands of editors, and you can see where the one would end up with lots of good articles, and the other with lots of new articles.
So I think the difference is reflective of some deep cultural differences, and not easily changed. Still, it wouldn't hurt to use de: as a real-life example of how en: can do better - it's not the wiki software or process that is limiting us, but our own lack of discipline.
Stan
Stan Shebs schrieb:
Pete Bartlett wrote:
Why is de: better than en: is a great question. They appear to have covered classic encyclopedic topics much better than en: and their proportion of Exzellente Artikeler is double that of our FAs, despite standards. How to learn from de would be a great thing to discuss.
In a word: "Ordnung".
The full range of connotation is not easily translated into English, but the disambig for de:'s [[Ordnung]] connects to lots of telling things, such as en:'s [[social structure]] and the like. At the risk of playing amateur sociologist and offending everybody, I'll opine that while the German cultural liking for "Ordnung" sounds to USians and Brits an awful lot like a compulsion to "follow orders", in the WP context I think it translates to a greater sense of duty to help achieve communal goals.
As a german Wikipedian, I would dispute this. It is definitely not Ordnung and a sense of duty which makes the difference between English and German Wikipedia. And even if this claim comes up again and again, I'm not even sure that German Wikipedia is really better than English Wikipedia. They are different and have different strengthes.
Now...let me collect some differences, I leave it to the reader to draw his own conclusions.
On 2nd April 2006 the category:Living people on en contained 81.930 entries while the number of _all_ german articles tagged with Personendaten (=almost all wikified biographies) was 86.830. I was surprised.
When I compare RfA on en and de, I count support votes on en: 31, 53, 45, 48, 61, 81, 28, 76, 50 on de: 72 (loosing candidate), 6 (loosing candidate), 93, 143 (loosing candidate!), 92, 55 It seems rather strange to me that the bigger community has less participation on such an important topic as is "who should become admin". I didn't look at the criteria voters use on en, but they might be also a bit different. On de candidates who really do a lot of useful cleanup work are regularly turned down if they are not able to show that they are also good authors. Other no-nos are bad behaviour, ignorance and especially ignorance and wrong actions in image right questions.
Social structure. The german wikipedia has a geographical advantage here because it covers a smaller area than the english. I may be a bit exceptional but my estimate is that I've met at least 150 wikipedians in person. Those 150 wikipedians know others who know others... there is a rather close network of personal relationships among german wikipedians (including of course the wikipedians from Austria and Switzerland). This becomes especially important in case of conflicts: a good editor in wikistress, deleting his userpage and quitting? He'll be flooded with emails and maybe a calm discussion with one of his friends on the phone will sort the problem out.
Let's look at the structure of the IRC channels now. English wikipedia has the general channel #wikipedia with an extremely low signal to noise ratio, the a bit more quiet #wikipedia-en and - I may be mistaken on the following: a closed admin channel, a bootcamp, mediation, probation and esperanza (whatever this is).
German wikipedia has: the general channel #wikipedia-de for socializing, coordinating general work on the wiki, discussing events on wp, calling an admin for quick vandal bans etc. Rarely people who chat too much off topic (=not wikipedia related) receive a friendly kick. Other channels: #hist.wikipedia where most historians hang out. #phil.wikipedia - meeting channel for the philosophers. #bio.wikipedia - home of the biologists. Some people frequent only the topic channels and not the general one. The biology channel was the first topic channel set up and reflects the strength of the german wikipedia in biology. The Projekt:Lebewesen (living beings) is the most active project on de and they fill one whole column on featured articles alone (the historians are catching up).
General atmosphere. It's difficult to get hard data on this, but the thing I hear most often is: atmosphere on the English Wikipedia is much more relaxed and people are friendlier and politer. There are even a few users who left the German Wikipedia with this reason and work only on en. So it might be true. This feeling is often connected to the behaviour on AfD. Hurtful comments are frequent there, combined with a much lower threshold for AfD: articles which are tagged as stub on en are usually proposed for deletion on de (and either expanded or deleted).
One group of prominent editors sticks to the maxims on the page "Be cruel" (http://de.wikipedia.org/wiki/Wikipedia:Sei_grausam ). This is not meant literally, but in the sense of Larry Sanger: To attract and retain the participation of experts, there would have to be little patience for those who do not understand or agree with Wikipedia's mission, or even for those pretentious mediocrities who are not able to work with others constructively and recognize when there are holes in their knowledge (collectively, probably the most disruptive group of all). A less tolerant attitude toward disruption would make the project more polite, welcoming, and indeed open to the vast majority of intelligent, well-meaning people on the Internet. --Larry Sanger
Refering to this "meme" (it's not a guideline), users have - undisputed by the community - been blocked for "disturbing good authors from writing articles". Leads to blocking and banning customs. The german wikipedia has no arbitration committee. A poll to establish one has not reached a necessary majority, the community divided about the question. Long term bans are decided by a community vote, short term bans are pronounced at the individual admin's own discretion. If another admins thinks a ban too harsh, he may shorten or lift it. Wheel wars about such issues are rare, though.
Wikipedia namespace. This topic probably comes closest to Stan's assumption of "Ordnung". Personally, I love the Wikipedia namespace in the English Wikipedia. There is so much to discover, so many obscure, interesting or funny pages. However, without counting, I have the impression that en has many many more pages in this namespace than de. When I look in http://en.wikipedia.org/wiki/Category:Wikipedia_style_guidelines I find a huge number of good advices, guides for almost everything (hey, even a whole page for how to set dashes). The number of german pages is much lower. Pages in the Wikipedia namespace are routinely scrutinized if they are really necessary and often merged into existing ones or deleted. http://de.wikipedia.org/wiki/Wikipedia:WikiProjekt_Usability/%C3%9Cbersicht is a rather complete overview of all important documentation pages.
Last point of this long mail: the impressive german projects like the printed wikireaders, the DVD, the writing contest with big media echo etc. In my opinion, these are due to several factors: 1) the independence of the german community from Jimbo and the Wikimedia Foundation. The English Wikipedia is very much a monarchy, with people looking to Jimbo for advice and guidance. The german wikipedia had and has nobody with Jimbo's authority. People had to deal with the fact that there is no ultimate appeal. This has consequences for the social structure (which evolved to what I'd characterize as a meritocracy with a few prominent and influential editors) but also for the possibility to realize such projects. People had to act on their own, so they did it. 2) Personal dedication and leadership of individual Wikipedians. Most projects were team work, but there was usually one person who invested much more work than the others. The driving force behind Wikipedia academy in June is one editor, Frank. The driving force behind many successful initiatives like the writing contest is Achim Raschka. The driving force behind the Wikipedia exhibition were Frank for the organisation and me for the realization. The WikiReaders were produced by individuals. etc. 3) For the DVD and WikiPress: the luck to find a good partner company which is crazy enough to take up the accompanying risks and whose bosses and employees "grok" the Wiki way. The first thing Vlado, one of the Directmedians, did after the first CD was finally ready for production was to expand the article Reggae to double its size - at 3 o'clock at night. Just to relax...
So much for a comparison between English and German Wikipedia. I noticed that I wrote much more about de, as I know the project much better. Maybe someone else could add more facts about en. I'm placing this text also on http://en.wikipedia.org/wiki/User:Elian/comparison - feel free to edit and add comments there (and of course fix my bad english ;-).
greetings, elian
First, I dispute the notion that the German Wikipedia is "better" than the English one in terms of overall quality. Featured article count on de: reflects, to a large degree, a much stronger drive on de: to that particular process (which was on de: first - I copied it to en: from there) from various pages. en: is also more inclusive, meaning many more articles on obscure subjects which will never get featured. de: tends towards agglomeration where en: maintains separate articles. This all obviously affects the FA ratio in de's favor.
There's no doubt that de: has been very innovative when it comes to quality drives and similar measures; however, en: has adopted most of these and invented some new variants. There are some good ideas which we should take from de: (and the other way around -- it was the redesign of the en: Main Page that led many others to redesign theirs in a similar fashion, including de:), but there are also ideas which I definitely do not want to see copied because of some fallacious notion of "de: is better than en:".
I want to comment on three specific points Elian made:
German wikipedia has: the general channel #wikipedia-de for socializing, coordinating general work on the wiki, discussing events on wp, calling an admin for quick vandal bans etc. Rarely people who chat too much off topic (=not wikipedia related) receive a friendly kick. Other channels: #hist.wikipedia where most historians hang out. #phil.wikipedia - meeting channel for the philosophers. #bio.wikipedia - home of the biologists.
This is an excellent idea which should be copied in all languages. Right now.
One group of prominent editors sticks to the maxims on the page "Be cruel" (http://de.wikipedia.org/wiki/Wikipedia:Sei_grausam ).
Bad meme; die, die, die. If that gets copied to en:, I will do whatever I can to get rid of it. It is the opposite of WikiLove and promotes an atmosphere of suspicion -- whatever the page text says, the title invites usage to justify any violation of policy. There's a reason for all that wiki culture of "Assume good faith", "Don't bite the newbies", etc. No reason to throw it out the window just yet.
We have "Be bold" as a way to add flexibility, and "Don't disrupt" as a general policy to deal with troublemakers. There's no need for "Be cruel".
The german wikipedia has no arbitration committee. A poll to establish one has not reached a necessary majority, the community divided about the question.
As a consequence, there is very little flexibility in dealing with problem users, and when you have one, you often end up with an indefinite block. My observation is that you have more sock puppetry and more extreme aggression as a result. It's a simple fact that bad users can and will evade blocks, so indefinite blocks against the worst ones often accomplish very little indeed. And those who respect blocks may be amenable to reason, so they should not be indef blocked either.
The flexibility of admins you mention may have led de: to become the leader in long term page protections, with some articles being protected as stubs for almost a year. At least that was the situation when I last ran a query on page protections: http://meta.wikimedia.org/wiki/Longest_page_protections%2C_September_2005
de: is, I think, a good example of the consequences some extreme proposals in the "wheel warring" thread would have. Having an admin class that becomes increasingly reluctant to question itself can be just as problematic as one which is constantly flighting over what to do.
I welcome this discussion. We need to understand better what consequences certain decisions had in the histories of different Wikipedias. Like Carl Sagan touted Venus and Mars as examples of climate developments that could affect Earth, Wikipedias in other languages have a lot to teach us.
Erik
On en: vs de:
From my experience, two (rather unrelated) differences
are most striking:
(A) On de: the argument "no real (convential) encyclopedia would write this" is by and large honored (or at least considered). On en: this argument is ignored, or even considered trollish.
(B) On de: all articles are expected to be accessable to a general audience (the horrible and horribly named "Oma-Test" -- "grandmother test"). On en: there are a lot of articles in mathematics and physics addressed to users definitively having some education in the area. I assume most experts are flocking to en: anyway, as it seems pointless to have advanced articles in other languages than English.
Regars, Peter [[User:Pjacobi]]
---- Original Message ---- From: Peter Jacobi peter_jacobi@gmx.net
(A) On de: the argument "no real (convential) encyclopedia would write this" is by and large honored (or at least considered). On en: this argument is ignored, or even considered trollish.
As detail to include in a particular topic, or whether to include a particular topic area at all?
They must have some cruft right, after all they have nigh on 400k articles :-) However it does fit with my colloquial observation from working on the missing topics project that time and again de: (and perhaps more oddly sv: and sl:) will have article on fairly famous historical British and American figures that we don't, but I don't see the converse that often. Not sure how to reconcile this Elisabeth's data about [[Category:Biographies]] and Persondata though.
(B) On de: all articles are expected to be accessable to a general audience (the horrible and horribly named "Oma-Test" -- "grandmother test").
That is one idea I prefer we _didn't_ import.
On en: there are a lot of articles in mathematics and physics addressed to users definitively having some education in the area. I assume most experts are flocking to en: anyway, as it seems pointless to have advanced articles in other languages than English
Well English being the "global language" has some effects. Not least that it becomes a hub for ideas for other languages to choose from. As Erik said, kust need to make sure we pick the best ideas from all the others too!
Pete Bartlett wrote:
----- Original Message ---- From: Philip Welch
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...)
in particular number 7: Free the Maps!
I would say absolute yes that information should be in a Wikimedia project that seamlessly integrates into Wikipedia.
Perhaps when we are faced with information about such an obscure intersection the question should be, "Where does it belong?" and not "Wat's the quickest way to get rid of it?"
Ec
On 4/26/06, Ray Saintonge saintonge@telus.net wrote:
Pete Bartlett wrote:
----- Original Message ---- From: Philip Welch
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
Recalling Jimbo's "Ten Things That Should Be Free" (http://many.corante.com/archives/2005/08/05/jimbos_problems_a_free_culture_m...)
in particular number 7: Free the Maps!
I would say absolute yes that information should be in a Wikimedia project that seamlessly integrates into Wikipedia.
Perhaps when we are faced with information about such an obscure intersection the question should be, "Where does it belong?" and not "Wat's the quickest way to get rid of it?"
Ec
Having a wiki incubator or other catch-all project where such things can be "dumped" until a home can be located would go a long way toward that.
Anthony
On 4/24/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 23, 2006, at 4:21 PM, Steve Block wrote:
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
According to his proposal, yes, it does.
Of course, to be realistic you'd have to add in [[Wikipedia:Article size]]. An article just about a four-way stop would probably be better off merged with another article and redirected, unless it was a particularly interesting four-way stop.
Anthony
On Apr 25, 2006, at 2:39 PM, Anthony DiPierro wrote:
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
According to his proposal, yes, it does.
Of course, to be realistic you'd have to add in [[Wikipedia:Article size]]. An article just about a four-way stop would probably be better off merged with another article and redirected, unless it was a particularly interesting four-way stop.
So [[Pullman, Washington]] would have detailed prose about each and every single intersection? That's absurd.
On 4/25/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 25, 2006, at 2:39 PM, Anthony DiPierro wrote:
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
According to his proposal, yes, it does.
Of course, to be realistic you'd have to add in [[Wikipedia:Article size]]. An article just about a four-way stop would probably be better off merged with another article and redirected, unless it was a particularly interesting four-way stop.
So [[Pullman, Washington]] would have detailed prose about each and every single intersection? That's absurd.
Strawman. I never said anything about [[Pullman, Washington]] *or* every intersection.
Anthony
On 26/04/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 25, 2006, at 2:39 PM, Anthony DiPierro wrote:
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
According to his proposal, yes, it does.
Of course, to be realistic you'd have to add in [[Wikipedia:Article size]]. An article just about a four-way stop would probably be better off merged with another article and redirected, unless it was a particularly interesting four-way stop.
So [[Pullman, Washington]] would have detailed prose about each and every single intersection? That's absurd.
-- Philip L. Welch http://en.wikipedia.org/wiki/User:Philwelch
There's little need to deliberately present such absurd options, that obviously aren't being suggested by others.
The logical place to merge a sentence or two about an intersection is into the article for that route.
More major routes should have each and every intersection mentioned already.
Zoney
-- ~()____) This message will self-destruct in 5 seconds...
On May 2, 2006, at 3:18 AM, Zoney wrote:
According to his proposal, yes, it does.
Of course, to be realistic you'd have to add in [[Wikipedia:Article size]]. An article just about a four-way stop would probably be better off merged with another article and redirected, unless it was a particularly interesting four-way stop.
So [[Pullman, Washington]] would have detailed prose about each and every single intersection? That's absurd.
There's little need to deliberately present such absurd options, that obviously aren't being suggested by others.
The logical place to merge a sentence or two about an intersection is into the article for that route.
Great. Now every city street has its own article. Imagine:
---
From [[Merman Drive, Pullman, Washington]]:
The drive goes past several apartment complexes, a coffee shop, and a bar. The vast majority of the street's population consists of [[Washington State University]] students.
Merman Drive intersects [[Terre View Drive, Pullman, Washington]] at a [[four-way stop]]. This stop is at the same intersection as Zoe's Cafe, the aforementioned coffee shop.
---
Shoot me now.
On 03/05/06, Philip Welch wikipedia@philwelch.net wrote:
Shoot me now.
If it was done well, and linked to Google Maps or something, it would actually be kind of cool.
Steve
On 5/2/06, Steve Bennett stevage@gmail.com wrote:
On 03/05/06, Philip Welch wikipedia@philwelch.net wrote:
Shoot me now.
If it was done well, and linked to Google Maps or something, it would actually be kind of cool.
Steve
Personally, I think this sort of thing would lead to a Wiktionary-like thing, in which valid but extremely numerous data is moved to its own project. Philip, would a Wikimap make you want to shoot yourself as well?
~maru
On May 2, 2006, at 4:06 PM, maru dubshinki wrote:
Shoot me now.
If it was done well, and linked to Google Maps or something, it would actually be kind of cool.
Steve
Personally, I think this sort of thing would lead to a Wiktionary-like thing, in which valid but extremely numerous data is moved to its own project. Philip, would a Wikimap make you want to shoot yourself as well?
If it was a separate wiki, it would just make me feel a slight malaise over our already-too-divided efforts.
Philip Welch wrote:
Great. Now every city street has its own article. Imagine:
From [[Merman Drive, Pullman, Washington]]:
The drive goes past several apartment complexes, a coffee shop, and a bar. The vast majority of the street's population consists of [[Washington State University]] students.
Merman Drive intersects [[Terre View Drive, Pullman, Washington]] at a [[four-way stop]]. This stop is at the same intersection as Zoe's Cafe, the aforementioned coffee shop.
Shoot me now.
I think you forgot to link [[Zoe's Cafe]].
-- Neil
On 5/2/06, Philip Welch wikipedia@philwelch.net wrote:
On May 2, 2006, at 3:18 AM, Zoney wrote:
According to his proposal, yes, it does.
Of course, to be realistic you'd have to add in [[Wikipedia:Article size]]. An article just about a four-way stop would probably be better off merged with another article and redirected, unless it was a particularly interesting four-way stop.
So [[Pullman, Washington]] would have detailed prose about each and every single intersection? That's absurd.
There's little need to deliberately present such absurd options, that obviously aren't being suggested by others.
The logical place to merge a sentence or two about an intersection is into the article for that route.
Great. Now every city street has its own article. Imagine:
That would be incredible, but somehow I doubt there are that many dedicated Wikipedians that it's going to happen.
Anyway, I look forward to the day when I can use Wikipedia to find out about the local coffee shops and Linux User Groups and radio stations and indie artists. If that means I have to stop myself from clicking on a link to [[Harrisburg Street, St. Petersburg]] and reading about the width of the sidewalks, it's well worth it.
Otherwise, if you can think of some way that Wikipedia can allow what's interesting to me but not allow what I personally find to be "cruft", without boring me with the nearly impossible task of going through every VFD discussion myself, I'd love to hear it.
Anthony
On 3 May 2006, at 12:38, Anthony DiPierro wrote:
That would be incredible, but somehow I doubt there are that many dedicated Wikipedians that it's going to happen.
Anyway, I look forward to the day when I can use Wikipedia to find out about the local coffee shops and Linux User Groups and radio stations and indie artists. If that means I have to stop myself from clicking on a link to [[Harrisburg Street, St. Petersburg]] and reading about the width of the sidewalks, it's well worth it.
The problem I have with all this stuff is the people who dont understand that an encyclopaedia is a historic record, and that just try to write this stuff about what things are now. Unless people are prepared to write from a historical perspective it is a guidebook not an encyclopaedia.
So a history of the Linux User Groups on your street, referenced with the CVS checkin histories from the street's IP addresses, yes; "There is a Linux User group in my street" or "this street is mostly inhabited by students and my friends and has a coffee shop on the crossroadds" is just cruft in the most derogatory sense, and should be deleted, or transwikied to a guidebook.
Justinc
On 5/3/06, Justin Cormack justin@specialbusservice.com wrote:
On 3 May 2006, at 12:38, Anthony DiPierro wrote:
That would be incredible, but somehow I doubt there are that many dedicated Wikipedians that it's going to happen.
Anyway, I look forward to the day when I can use Wikipedia to find out about the local coffee shops and Linux User Groups and radio stations and indie artists. If that means I have to stop myself from clicking on a link to [[Harrisburg Street, St. Petersburg]] and reading about the width of the sidewalks, it's well worth it.
The problem I have with all this stuff is the people who dont understand that an encyclopaedia is a historic record, and that just try to write this stuff about what things are now. Unless people are prepared to write from a historical perspective it is a guidebook not an encyclopaedia.
Well, I intentionally included a list of things which *can* be written about historically, and not just as a guidebook. I agree with you that it's important that the articles we have focus on presenting timeless depictions. Sure, some instances of these things will be short lived, but there are usually natural parent articles to put them in when that's the case.
So a history of the Linux User Groups on your street, referenced with the CVS checkin histories from the street's IP addresses, yes; "There is a Linux User group in my street" or "this street is mostly inhabited by students and my friends and has a coffee shop on the crossroadds" is just cruft in the most derogatory sense, and should be deleted, or transwikied to a guidebook.
Justinc
In the extreme case of "There is a Linux User group in my street", yes. But that sentence doesn't even allow one to identify what the person is talking about, so that's an extreme example.
Better than deleting less extreme examples, in my opinion, would be to drop a note on the talk page of the person who created the article and tell them that information added to the encyclopedia needs to be verifiable and timeless ([[Wikipedia:Avoid statements that will date quickly]] is the best link I could come up with right now, if that's the best there is then it should probably be improved, though). Then sprinkle it with {{fact}}, cut out any dubious statements, and put it on some list along the lines of ([[Wikipedia:horrible articles which will be removed if they don't shape up really soon]]) for a couple weeks and delete it if it doesn't get improved to where it's verifiable and from a perspective of history (or have a chance of quickly getting there).
By the way, [[LUG]]s generally aren't attached to streets, they're usually attached to entire metropolitan areas. In fact, I suspect a well-written article on the [[Suncoast Linux Users Group]], for example, would survive a VFD vote today.
Anthony
On 03/05/06, Anthony DiPierro wikilegal@inbox.org wrote:
sprinkle it with {{fact}}, cut out any dubious statements, and put it on some list along the lines of ([[Wikipedia:horrible articles which will be removed if they don't shape up really soon]]) for a couple weeks and delete it if it doesn't get improved to where it's verifiable and from a perspective of history (or have a chance of quickly getting there).
Why do we delete "horrible" articles if they don't shape up "really soon"? What's soon? Why don't we want horrible articles hanging around for 2 years? Are "horrible" articles better or worse than stubs on the same topics?
By the way, [[LUG]]s generally aren't attached to streets, they're usually attached to entire metropolitan areas. In fact, I suspect a well-written article on the [[Suncoast Linux Users Group]], for example, would survive a VFD vote today.
I'm sad to hear that well-writtenness is a criteria in AfDs. If it's not well-written someone should just fix it.
Steve
On 03/05/06, Steve Bennett stevage@gmail.com wrote:
By the way, [[LUG]]s generally aren't attached to streets, they're usually attached to entire metropolitan areas. In fact, I suspect a well-written article on the [[Suncoast Linux Users Group]], for example, would survive a VFD vote today.
I'm sad to hear that well-writtenness is a criteria in AfDs. If it's not well-written someone should just fix it.
Agreed. On the other side of the coin, though...sometimes it takes a mite of brilliant prose to make people realise that it's worth replicating the effort throughout a page.
Rob Church
On 5/3/06, Steve Bennett stevage@gmail.com wrote:
Why do we delete "horrible" articles if they don't shape up "really soon"? What's soon? Why don't we want horrible articles hanging around for 2 years? Are "horrible" articles better or worse than stubs on the same topics?
They can often be worse
By the way, [[LUG]]s generally aren't attached to streets, they're usually attached to entire metropolitan areas. In fact, I suspect a well-written article on the [[Suncoast Linux Users Group]], for example, would survive a VFD vote today.
I'm sad to hear that well-writtenness is a criteria in AfDs. If it's not well-written someone should just fix it.
Someone?
See http://en.wikipedia.org/wiki/Category:Cleanup_by_month
15000 articles.
Looks like anyone who might be that someone has enough work on their hands already. -- geni
On 03/05/06, geni geniice@gmail.com wrote:
Someone?
See http://en.wikipedia.org/wiki/Category:Cleanup_by_month
15000 articles.
Looks like anyone who might be that someone has enough work on their hands already.
Yep. But the vast majority of those articles are good enough that they're better than a conspicuous hole where they used to be. I don't object to us aiming for higher standards, but I do object to us nuking anything that's trying to get there - if slowly.
Steve
On 5/3/06, Steve Bennett stevage@gmail.com wrote:
On 03/05/06, geni geniice@gmail.com wrote:
Someone?
See http://en.wikipedia.org/wiki/Category:Cleanup_by_month
15000 articles.
Looks like anyone who might be that someone has enough work on their hands already.
Yep. But the vast majority of those articles are good enough that they're better than a conspicuous hole where they used to be. I don't object to us aiming for higher standards, but I do object to us nuking anything that's trying to get there - if slowly.
Steve
For my part I think there's a bare minimum of effort which the authors of an article need to perform before they can expect someone else to fix things. Verifiability - pointing to a source where someone can find out more information, is a big part of that bare minimum of effort.
Of course not everyone knows about verifiability, so you should generally give them a chance to correct their own mistake first unless it's plainly obvious they are simply abusing the system.
Anthony
Steve Bennett wrote:
On 03/05/06, geni geniice@gmail.com wrote:
See http://en.wikipedia.org/wiki/Category:Cleanup_by_month 15000 articles. Looks like anyone who might be that someone has enough work on their hands already.
Yep. But the vast majority of those articles are good enough that they're better than a conspicuous hole where they used to be.
That's true almost by definition; if they were worse than a conspicuous hole, most of them would already have been replaced by one.
On 5/3/06, Steve Bennett stevage@gmail.com wrote:
On 03/05/06, Anthony DiPierro wikilegal@inbox.org wrote:
sprinkle it with {{fact}}, cut out any dubious statements, and put it on some list along the lines of ([[Wikipedia:horrible articles which will be removed if they don't shape up really soon]]) for a couple weeks and delete it if it doesn't get improved to where it's verifiable and from a perspective of history (or have a chance of quickly getting there).
Why do we delete "horrible" articles if they don't shape up "really soon"? What's soon? Why don't we want horrible articles hanging around for 2 years? Are "horrible" articles better or worse than stubs on the same topics?
By a horrible article I mean one with no verifiable content whatsoever. Depending whether or not the person creating the article seems to be acting in good faith I'd say it should stay around between no time at all and two weeks or so.
And IMO yes, an article which is not verifiable is worse than nothing at all. It should be corrected as soon as possible, and keeping it around in the main namespace for very long is not acceptable (still IMO, of course).
By the way, [[LUG]]s generally aren't attached to streets, they're usually attached to entire metropolitan areas. In fact, I suspect a well-written article on the [[Suncoast Linux Users Group]], for example, would survive a VFD vote today.
I'm sad to hear that well-writtenness is a criteria in AfDs. If it's not well-written someone should just fix it.
Steve
I agree with that point to some extent (at some point you've gotta just stop feeding the trolls though). In any case, how well written an article is *does* tend to affect the outcome of votes on deletion.
Anthony
On 03/05/06, Anthony DiPierro wikilegal@inbox.org wrote:
By a horrible article I mean one with no verifiable content whatsoever. Depending whether or not the person creating the article seems to be acting in good faith I'd say it should stay around between no time at all and two weeks or so.
Ah, so you mean an article with no claim to notability, or a suspected hoax? Both candidates for speedy deletion :) If all the content is unverifiable, it could always be trimmed down without going through AfD at all.
And IMO yes, an article which is not verifiable is worse than nothing at all. It should be corrected as soon as possible, and keeping it around in the main namespace for very long is not acceptable (still IMO, of course).
How about stubbing it and moving the content to the talk page, gently redirecting the newbie there? I'm just speculating a bit here...
I agree with that point to some extent (at some point you've gotta just stop feeding the trolls though). In any case, how well written an article is *does* tend to affect the outcome of votes on deletion.
Pity.
Steve
On 5/3/06, Steve Bennett stevage@gmail.com wrote:
On 03/05/06, Anthony DiPierro wikilegal@inbox.org wrote:
By a horrible article I mean one with no verifiable content whatsoever. Depending whether or not the person creating the article seems to be acting in good faith I'd say it should stay around between no time at all and two weeks or so.
Ah, so you mean an article with no claim to notability, or a suspected hoax? Both candidates for speedy deletion :) If all the content is unverifiable, it could always be trimmed down without going through AfD at all.
Well, a suspected hoax would be on the "no time at all" end of the scale. A non-verifiable article submitted by a regular contributor would be on the "two weeks or so" end. A non-verifiable article submitted by a relative newbie might be somewhere in between.
As for "an article with no claim to notability", I actually have no idea what that phrase means.
And as for trimming down an article without going through AfD at all, that's only possible if there's *some* verifiable content (along with enough information to tell us how to verify it).
And IMO yes, an article which is not verifiable is worse than nothing at all. It should be corrected as soon as possible, and keeping it around in the main namespace for very long is not acceptable (still IMO, of course).
How about stubbing it and moving the content to the talk page, gently redirecting the newbie there? I'm just speculating a bit here...
Stubbing only works if there's something there you can verify in the first place. Stubbing an article without verifying that your stub is accurate first is a very bad idea IMO, because it gives false credibility to the possibly inaccurate statement.
I agree with that point to some extent (at some point you've gotta just stop feeding the trolls though). In any case, how well written an article is *does* tend to affect the outcome of votes on deletion.
Pity.
Steve
On 03/05/06, Anthony DiPierro wikilegal@inbox.org wrote:
As for "an article with no claim to notability", I actually have no idea what that phrase means.
An article has to establish the notability of its subject. If it doesn't do that, it's subject to speedy deletion.
...I recite.
Stubbing only works if there's something there you can verify in the first place. Stubbing an article without verifying that your stub is accurate first is a very bad idea IMO, because it gives false credibility to the possibly inaccurate statement.
Heh: '''John Smith''' was a rap singer [citation needed].
Steve
On 5/3/06, Steve Bennett stevage@gmail.com wrote:
On 03/05/06, Anthony DiPierro wikilegal@inbox.org wrote:
As for "an article with no claim to notability", I actually have no idea what that phrase means.
An article has to establish the notability of its subject. If it doesn't do that, it's subject to speedy deletion.
...I recite.
Seems like circular reasoning to me. An article which doesn't show any reason why it shouldn't be deleted, is subject to speedy deletion.
If that's a criteria for speedy deletion, I'm not sure why there's a need for any others!
Stubbing only works if there's something there you can verify in the first place. Stubbing an article without verifying that your stub is accurate first is a very bad idea IMO, because it gives false credibility to the possibly inaccurate statement.
Heh: '''John Smith''' was a rap singer [citation needed].
Steve
I used to modify AfD nominations to say something like "John Smith might be a person". Got reverted half the time though, to the original article with all the unverifiable statements in it.
But if an article really does say nothing more than "John Smith was a rap singer [citation needed]", I think the encyclopedia would be better off purging it after a few weeks of begging for a citation. If John Smith really is a rap singer and someone can prove it, it's easy enough to re-add the information later.
Anthony
On May 3, 2006, at 4:48 AM, Justin Cormack wrote:
The problem I have with all this stuff is the people who dont understand that an encyclopaedia is a historic record, and that just try to write this stuff about what things are now. Unless people are prepared to write from a historical perspective it is a guidebook not an encyclopaedia.
In this case, the coffee shop used to be a Hi-Co, and the bar was only built in the last couple of months.
On 3 May 2006, at 17:50, Philip Welch wrote:
On May 3, 2006, at 4:48 AM, Justin Cormack wrote:
The problem I have with all this stuff is the people who dont understand that an encyclopaedia is a historic record, and that just try to write this stuff about what things are now. Unless people are prepared to write from a historical perspective it is a guidebook not an encyclopaedia.
In this case, the coffee shop used to be a Hi-Co, and the bar was only built in the last couple of months.
Thats not a historical perspective, its what you remember. Unless you are going to write about the economic shifts in coffee shop viability in this area, and the architecture of the bar its still just guidebook stuff.
There are serious scholarly guides to tiny details (eg [[Pevsner]]'s architectural guidebooks to the UK) that could be used to build a detailed infrastructure of small scale place articles, and its a potentially interesting project, but there must not be a guide book mentality to it, there must be sources, history, and *reasons why* not just lists.
Justinc
On May 3, 2006, at 4:38 AM, Anthony DiPierro wrote:
That would be incredible, but somehow I doubt there are that many dedicated Wikipedians that it's going to happen.
Anyway, I look forward to the day when I can use Wikipedia to find out about the local coffee shops and Linux User Groups and radio stations and indie artists. If that means I have to stop myself from clicking on a link to [[Harrisburg Street, St. Petersburg]] and reading about the width of the sidewalks, it's well worth it.
Otherwise, if you can think of some way that Wikipedia can allow what's interesting to me but not allow what I personally find to be "cruft", without boring me with the nearly impossible task of going through every VFD discussion myself, I'd love to hear it.
Actually, it would be not too bad to put together city guides and such, either within Wikipedia or within a separate project. But there is so much more content of such wider interest waiting to be developed that we shouldn't divide our efforts.
On 5/3/06, Philip Welch wikipedia@philwelch.net wrote:
On May 3, 2006, at 4:38 AM, Anthony DiPierro wrote:
That would be incredible, but somehow I doubt there are that many dedicated Wikipedians that it's going to happen.
Anyway, I look forward to the day when I can use Wikipedia to find out about the local coffee shops and Linux User Groups and radio stations and indie artists. If that means I have to stop myself from clicking on a link to [[Harrisburg Street, St. Petersburg]] and reading about the width of the sidewalks, it's well worth it.
Otherwise, if you can think of some way that Wikipedia can allow what's interesting to me but not allow what I personally find to be "cruft", without boring me with the nearly impossible task of going through every VFD discussion myself, I'd love to hear it.
Actually, it would be not too bad to put together city guides and such, either within Wikipedia or within a separate project. But there is so much more content of such wider interest waiting to be developed that we shouldn't divide our efforts.
The same could be said of *any* category of articles. Why write about presidents, or hurricanes, or rock stars, or fortune 500 companies, when there is so much else to do? I'd personally rather read about coffee shops and indie artists than fortune 500 companies and rock stars anyway.
Anthony
On May 3, 2006, at 10:12 AM, Anthony DiPierro wrote:
Actually, it would be not too bad to put together city guides and such, either within Wikipedia or within a separate project. But there is so much more content of such wider interest waiting to be developed that we shouldn't divide our efforts.
The same could be said of *any* category of articles. Why write about presidents, or hurricanes, or rock stars, or fortune 500 companies, when there is so much else to do? I'd personally rather read about coffee shops and indie artists than fortune 500 companies and rock stars anyway.
I'm going to take a wild guess and say that [[Zoe's Cafe, Pullman, Washington]] will be of interest to fewer readers than [[Hurricane Katrina]].
There are probably some fascinating and unique coffee shops that we can have articles on, but the one down the street from me probably isn't one of them.
On 5/3/06, Philip Welch wikipedia@philwelch.net wrote:
On May 3, 2006, at 10:12 AM, Anthony DiPierro wrote:
Actually, it would be not too bad to put together city guides and such, either within Wikipedia or within a separate project. But there is so much more content of such wider interest waiting to be developed that we shouldn't divide our efforts.
The same could be said of *any* category of articles. Why write about presidents, or hurricanes, or rock stars, or fortune 500 companies, when there is so much else to do? I'd personally rather read about coffee shops and indie artists than fortune 500 companies and rock stars anyway.
I'm going to take a wild guess and say that [[Zoe's Cafe, Pullman, Washington]] will be of interest to fewer readers than [[Hurricane Katrina]].
And I bet you [[Pokémon Crystal]] is interesting to more people than [[Huelva (province)]]. Going with whatever is the most popular is not something I think Wikipedia should do.
There are probably some fascinating and unique coffee shops that we can have articles on, but the one down the street from me probably isn't one of them.
-- Philip L. Welch http://en.wikipedia.org/wiki/User:Philwelch
Anthony
Philip Welch wrote:
Great. Now every city street has its own article. Imagine:
From [[Merman Drive, Pullman, Washington]]:
The drive goes past several apartment complexes, a coffee shop, and a bar. The vast majority of the street's population consists of [[Washington State University]] students.
Merman Drive intersects [[Terre View Drive, Pullman, Washington]] at a [[four-way stop]]. This stop is at the same intersection as Zoe's Cafe, the aforementioned coffee shop.
At least you could say who it's named after. Two US streets that I've been on and have wondered about are Chef Menteur Highway in New Orleans and Last Chance Gulch in Helena. MT
Ec
On 4/24/06, Philip Welch wikipedia@philwelch.net wrote:
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
-- Philip L. Welch http://en.wikipedia.org/wiki/User:Philwelch
By the way, just out of curiousity, what would those sources be? Remember not to violate [[WP:NOR]].
I found one arguably "reliable source" at http://www.wmel.wsu.edu/directions/directions.html. It's a website, but it's a .edu website. Google Book Search finds nothing for the names of the two roads in quotes. Maybe if it's a particularly busy road there would be some mention in newspapers...
Anthony
On Apr 25, 2006, at 2:54 PM, Anthony DiPierro wrote:
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
-- Philip L. Welch http://en.wikipedia.org/wiki/User:Philwelch
By the way, just out of curiousity, what would those sources be? Remember not to violate [[WP:NOR]].
I found one arguably "reliable source" at http://www.wmel.wsu.edu/directions/directions.html. It's a website, but it's a .edu website. Google Book Search finds nothing for the names of the two roads in quotes. Maybe if it's a particularly busy road there would be some mention in newspapers...
Maps, Pullman Transit schedules, driving directions.
Here's some more information that is verifiable from third party reliable sources: there is a "Turney Hitler" living in Lakeside California, and his phone number is 619-390-9009. The third party reliable source in question is anywho.com, an online telephone directory. I don't think poor Mr. Hitler deserves mention in Wikipedia, however.
On 4/25/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 25, 2006, at 2:54 PM, Anthony DiPierro wrote:
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
-- Philip L. Welch http://en.wikipedia.org/wiki/User:Philwelch
By the way, just out of curiousity, what would those sources be? Remember not to violate [[WP:NOR]].
I found one arguably "reliable source" at http://www.wmel.wsu.edu/directions/directions.html. It's a website, but it's a .edu website. Google Book Search finds nothing for the names of the two roads in quotes. Maybe if it's a particularly busy road there would be some mention in newspapers...
Maps, Pullman Transit schedules, driving directions.
I thought of these, but I didn't think they'd have the fact that there was a four-way stop sign.
Here's some more information that is verifiable from third party reliable sources: there is a "Turney Hitler" living in Lakeside California, and his phone number is 619-390-9009. The third party reliable source in question is anywho.com, an online telephone directory. I don't think poor Mr. Hitler deserves mention in Wikipedia, however.
Well, that begs the question, now doesn't it?
Anthony
On 4/25/06, Philip Welch wikipedia@philwelch.net wrote:
. I don't think poor Mr. Hitler deserves mention in Wikipedia, however.
Does he know Brian Peppers?
Philip Welch wrote:
On Apr 23, 2006, at 4:21 PM, Steve Block wrote:
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
What this guideline is trying to do is define notability within the verifiability chain.
It attempts to close the door on the possibility of allowing wikipedians to decide what is and isn't notable, something I believe is against both the original research and POV policies. We should seek to summarise claims of importance, where those claims are verifiable.
If there are no outside sources, how do we write an encyclopedic article on the topic, how do we quantify the value of the topic, without breaking the original research policy? Yes, I could write an article on my street, for which verifiability exists in many sources, as do the businesses and houses upon it. I could detail, through land registry searches, phone books and electoral rolls, the history of the street. But this violates original research; I have compiled a new narrative. I have summarised something which does not actually exist, and for someone to verify it they would have to repeat the research. Jimbo prescribed against this way back, stating that something is encyclopedic if "it is information which is verifiable and which can be easily presented in an NPOV fashion."
Verifiability, NOR and NPOV do not mean we can write articles on topics we happen to feel should have them, they mean we should write articles on topics for which we have good sources, the summation of which do not amount to the original research through creating a novel narrative, and which does not impart greater weight to the topic than exists in the wider world, represented by the reliable sources we seek.
If we source only from the primary source, the topic itself, we cannot do anything but present information from a biased point of view. Yes, it is disappointing that there exists categories of information for which Wikipedia would be a wonderful repository, but for which no other sources exist for us to summate. However, that cannot be something we should seek to remedy. Wikipedia is not a place for original research. To me, that means Wikipedia cannot be a place to make claims of importance for any topic. Such claims should already be established within reliable sources, before we can attempt to document them. It is unfortunate that closers in afd discussions are not mindful of this, but it is the case that Wikipedia is a tertiary source. Wikipedia is not a repository for primary research.
So is your four way stop worthy of an article? On the strength of your description, I would say no, because you are imparting undue weight to it by creating such an article, you are presenting information for your own point of view rather than summarising someone else's, and if the article states only that four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington then I'd consider speedying it per A1.
Steve Block
I don't know if streets were your best example. Streets rarely survive an AfD (on grounds of notability).
Joe
On 4/30/06, Steve Block steve.block@myrealbox.com wrote:
Philip Welch wrote:
On Apr 23, 2006, at 4:21 PM, Steve Block wrote:
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
What this guideline is trying to do is define notability within the verifiability chain.
It attempts to close the door on the possibility of allowing wikipedians to decide what is and isn't notable, something I believe is against both the original research and POV policies. We should seek to summarise claims of importance, where those claims are verifiable.
If there are no outside sources, how do we write an encyclopedic article on the topic, how do we quantify the value of the topic, without breaking the original research policy? Yes, I could write an article on my street, for which verifiability exists in many sources, as do the businesses and houses upon it. I could detail, through land registry searches, phone books and electoral rolls, the history of the street. But this violates original research; I have compiled a new narrative. I have summarised something which does not actually exist, and for someone to verify it they would have to repeat the research. Jimbo prescribed against this way back, stating that something is encyclopedic if "it is information which is verifiable and which can be easily presented in an NPOV fashion."
Verifiability, NOR and NPOV do not mean we can write articles on topics we happen to feel should have them, they mean we should write articles on topics for which we have good sources, the summation of which do not amount to the original research through creating a novel narrative, and which does not impart greater weight to the topic than exists in the wider world, represented by the reliable sources we seek.
If we source only from the primary source, the topic itself, we cannot do anything but present information from a biased point of view. Yes, it is disappointing that there exists categories of information for which Wikipedia would be a wonderful repository, but for which no other sources exist for us to summate. However, that cannot be something we should seek to remedy. Wikipedia is not a place for original research. To me, that means Wikipedia cannot be a place to make claims of importance for any topic. Such claims should already be established within reliable sources, before we can attempt to document them. It is unfortunate that closers in afd discussions are not mindful of this, but it is the case that Wikipedia is a tertiary source. Wikipedia is not a repository for primary research.
So is your four way stop worthy of an article? On the strength of your description, I would say no, because you are imparting undue weight to it by creating such an article, you are presenting information for your own point of view rather than summarising someone else's, and if the article states only that four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington then I'd consider speedying it per A1.
Steve Block
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.1/327 - Release Date: 28/04/06
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
"Steve Block" wrote
It attempts to close the door on the possibility of allowing wikipedians to decide what is and isn't notable, something I believe is against both the original research and POV policies. We should seek to summarise claims of importance, where those claims are verifiable.
Err ... why? This may be what we resort to in some cases (garage bands). But it is a bad idea in other cases (e.g. academics). And I think we all should be allowed to express opinions on notability. In some areas, for example the arts, poetry, if you go by tallying up awards and honours and suchlike 'objective' credits, you will only reproduce the contours of the 'academic art' of the time. Thus missing what is coming up, for example.
Further, there could hardly be a better example of how 'original research', launched by Jimbo as a way to deal with crank theories, has been spandexed as an argument.
Charles
It's dangerous to apply the notion of "original research" too literally outside of its original context (dealing with crackpot theories, or simply novel ones, student essays, and so on). Beyond that context, I'm not literalistic, and I don't need a lot of guidlines. I think I know it when I see it, and I think I know what is not intended to be covered by the expression when I see it, even if it could be brought under the literal description that is used. Common sense has to prevail, I think, which is why we have all these processes involving shared community perceptions.
An example of something that is probably NOT "original research": "Bloggs has approvingly cited the work of Derrida to attack the philosophy of bohemian snarkism. According to Bloggs, it is all 'words, words, words.' <reference, Joe Bloggs, Anti-Snark, p. 300>"
An example of something that certainly IS original research: "Bloggs, who has attacked the philosophy of bohemian snarkism, could have found further support for his view by applying certain claims famously made by Derrida. <reference, Jacques Derrida, Words/ Words/ Words, p. 300>"
We all make these kinds of distinctions reasonably confidently, don't we? When in doubt, at the margins, we do indeed want to call on our collective wisdom. The process seems straightforward enough to me, though I suppose I might change my mind if I got caught in an edit war over it.
As for notability, I'm not sure I properly understand the argument. It seems to me that we have a (loose and largely unofficial) body of criteria to apply to decide whether or not something is notable. We don't apply novel theories, we just find the facts and apply the criteria. The facts should be publicly available ones. The criteria themselves get clarified and developed from case to case, with commonsense input from the community to resolve doubts in individual hard cases. That seems like the right way to go about it to me. I'm not sure whether I'm in disagreement with anyone here or not, but it just doesn't seem all that complicated at my end.
Russell Blackford (a.k.a. Metamagician3000)
----- Original Message ----- From: "charles matthews" charles.r.matthews@ntlworld.com To: "English Wikipedia" wikien-l@Wikipedia.org Sent: Monday, May 01, 2006 7:35 PM Subject: Re: [WikiEN-l] Verifiability equating to notability
"Steve Block" wrote
It attempts to close the door on the possibility of allowing wikipedians to decide what is and isn't notable, something I believe is against both the original research and POV policies. We should seek to summarise claims of importance, where those claims are verifiable.
Err ... why? This may be what we resort to in some cases (garage bands). But it is a bad idea in other cases (e.g. academics). And I think we all should be allowed to express opinions on notability. In some areas, for example the arts, poetry, if you go by tallying up awards and honours and suchlike 'objective' credits, you will only reproduce the contours of the 'academic art' of the time. Thus missing what is coming up, for example.
Further, there could hardly be a better example of how 'original research', launched by Jimbo as a way to deal with crank theories, has been spandexed as an argument.
Charles
Russell Blackford wrote:
It's dangerous to apply the notion of "original research" too literally outside of its original context (dealing with crackpot theories, or simply novel ones, student essays, and so on). Beyond that context, I'm not literalistic, and I don't need a lot of guidlines. I think I know it when I see it, and I think I know what is not intended to be covered by the expression when I see it, even if it could be brought under the literal description that is used. Common sense has to prevail, I think, which is why we have all these processes involving shared community perceptions.
An example of something that is probably NOT "original research": "Bloggs has approvingly cited the work of Derrida to attack the philosophy of bohemian snarkism. According to Bloggs, it is all 'words, words, words.' <reference, Joe Bloggs, Anti-Snark, p. 300>"
An example of something that certainly IS original research: "Bloggs, who has attacked the philosophy of bohemian snarkism, could have found further support for his view by applying certain claims famously made by Derrida. <reference, Jacques Derrida, Words/ Words/ Words, p. 300>"
We all make these kinds of distinctions reasonably confidently, don't we? When in doubt, at the margins, we do indeed want to call on our collective wisdom. The process seems straightforward enough to me, though I suppose I might change my mind if I got caught in an edit war over it.
I think we're in broad agreement. The trouble is, at the thin edge, you get people arguing that because everyone says "Foo", we can have an article on "Foo", and note all the blogs and people who have said "Foo", especially on "XYZ message boards", because Bloggs has set up a website documenting the history of XYZ message board, and also the posts are all archived and you can clearly see where Bleggs said "Foo" to Blaggs and Bliggs banned him.
Apparently, because this can all be sourced it isn't original research, because there are no sources disputing it it isn't a point of view, and it's all sourced so it's verifiable. The issue is that it is original research because the particular documentation of these things create a novel narrative which exists nowhere but on Wikipedia. But that doesn't seem to hold sway over people. To me, no original research means we can't personally see it, we need someone to see it for us and then we can summarise them. So if nobody else has commented on Bleggs saying "Foo" to Blaggs in a reliable source, it's original research for us to document it. The problem is that there is an issue as to whether things recorded on the internet as they happen exist in the same sense as a tree, a cat and that four stop Phil mentioned. Is the internet a reliable source in and of itself?
Notability is an issue in the sense that everyone mentions it an no-one agrees on what it means. I was attempting to cut through various discussions which were attempting to allow, for example, memes which have existed for a year to be recordable. Given there's not much of a definition of a meme to start with, a meme pretty much being an idea which catches on, it seems like allowing any idea which catches on to be documentable after having caught on for a year a little mad. To me. For starters, how would we define whether a meme has caught on or not?
And then, why can't we allow website X to be added, it's been online for a year, why isn't that allowed, and so on and so forth. The idea was to base notability within the three policies we have already, which as they stand, would also allow Phil's Four Stop article. I was kind of seeing a lower tier triumvirate of notability, deletion policy and Wikipedia is not.
Steve block
I find it difficult to set rules in the abstract - all the more so from being a lawyer by training, with a good knowledge of how slippery language can get once you try to apply it to an unforeseen situation. Thankfully we only have policies and guidelines to worry about, not things that are supposed to be binding laws. I'd agree with you about the Foo case, though. I would vote to delete such an article unless I saw evidence that other people with some profile were already commenting on the "Foo" meme (e.g. op.ed. pieces, editorials, or well-known blogs (but what is "well-known"?). Without that, I'd consider the article original research. (Put aside whether there's a dicdef issue; I'm assuming the article could be expanded beyond a mere definition of "Foo").
In other cases I'm not so sure. What about all those articles on fictional characters who may not have been discussed much in critical sources? I wouldn't necessarily want to say that these characters are non-notable, even though I sometimes think we give too much importance to them and not enough to real people who are important in the adult world. I think they are notable because they often just do have a cultural impact that we can all sort of take judicial notice of without dreaming up novel theories. If we accept that much, I'm then happy for someone to say: "Sammy Snark gets killed at the end of the first-series story arc of Blogsville" with a citation to the actual episode rather than to a secondary source. In this sort of context, some easily replicable putting together of a narrative doesn't worry me, and I don't interpret the original research proscription as covering this kind of thing in spirit. What's your take on this kind of example?
Russell (a.k.a Metamagician3000)
----- Original Message ----- From: "Steve Block" steve.block@myrealbox.com To: "English Wikipedia" wikien-l@Wikipedia.org Sent: Monday, May 01, 2006 11:41 PM Subject: Re: [WikiEN-l] Verifiability equating to notability
Russell Blackford wrote:
It's dangerous to apply the notion of "original research" too literally outside of its original context (dealing with crackpot theories, or simply novel ones, student essays, and so on). Beyond that context, I'm not literalistic, and I don't need a lot of guidlines. I think I know it when I see it, and I think I know what is not intended to be covered by the expression when I see it, even if it could be brought under the literal description that is used. Common sense has to prevail, I think, which is why we have all these processes involving shared community perceptions.
An example of something that is probably NOT "original research": "Bloggs has approvingly cited the work of Derrida to attack the philosophy of bohemian snarkism. According to Bloggs, it is all 'words, words, words.' <reference, Joe Bloggs, Anti-Snark, p. 300>"
An example of something that certainly IS original research: "Bloggs, who has attacked the philosophy of bohemian snarkism, could have found further support for his view by applying certain claims famously made by Derrida. <reference, Jacques Derrida, Words/ Words/ Words, p. 300>"
We all make these kinds of distinctions reasonably confidently, don't we? When in doubt, at the margins, we do indeed want to call on our collective wisdom. The process seems straightforward enough to me, though I suppose I might change my mind if I got caught in an edit war over it.
I think we're in broad agreement. The trouble is, at the thin edge, you get people arguing that because everyone says "Foo", we can have an article on "Foo", and note all the blogs and people who have said "Foo", especially on "XYZ message boards", because Bloggs has set up a website documenting the history of XYZ message board, and also the posts are all archived and you can clearly see where Bleggs said "Foo" to Blaggs and Bliggs banned him.
Apparently, because this can all be sourced it isn't original research, because there are no sources disputing it it isn't a point of view, and it's all sourced so it's verifiable. The issue is that it is original research because the particular documentation of these things create a novel narrative which exists nowhere but on Wikipedia. But that doesn't seem to hold sway over people. To me, no original research means we can't personally see it, we need someone to see it for us and then we can summarise them. So if nobody else has commented on Bleggs saying "Foo" to Blaggs in a reliable source, it's original research for us to document it. The problem is that there is an issue as to whether things recorded on the internet as they happen exist in the same sense as a tree, a cat and that four stop Phil mentioned. Is the internet a reliable source in and of itself?
Notability is an issue in the sense that everyone mentions it an no-one agrees on what it means. I was attempting to cut through various discussions which were attempting to allow, for example, memes which have existed for a year to be recordable. Given there's not much of a definition of a meme to start with, a meme pretty much being an idea which catches on, it seems like allowing any idea which catches on to be documentable after having caught on for a year a little mad. To me. For starters, how would we define whether a meme has caught on or not?
And then, why can't we allow website X to be added, it's been online for a year, why isn't that allowed, and so on and so forth. The idea was to base notability within the three policies we have already, which as they stand, would also allow Phil's Four Stop article. I was kind of seeing a lower tier triumvirate of notability, deletion policy and Wikipedia is not.
Steve block
On 4/30/06, Steve Block steve.block@myrealbox.com wrote:
Philip Welch wrote:
On Apr 23, 2006, at 4:21 PM, Steve Block wrote:
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
What this guideline is trying to do is define notability within the verifiability chain.
It attempts to close the door on the possibility of allowing wikipedians to decide what is and isn't notable, something I believe is against both the original research and POV policies. We should seek to summarise claims of importance, where those claims are verifiable.
I've always considered NOR to be *part of* the verifiability rules. It is a description of what sources count toward verifiability. For that matter, both rules are really an explanation of what NPOV means - "assert facts, including facts about opinions — but don't assert opinions themselves". NOR and V go on to describe what is meant by "facts".
I guess what I'm saying is you can't really eliminate any of those three rules without significantly affecting the interpretation of the other one, or to quote NPOV: "Because the three policies are complementary, they should not be interpreted in isolation from one other, and editors should therefore try to familiarize themselves with all three."
Verifiability, NOR and NPOV do not mean we can write articles on topics we happen to feel should have them, they mean we should write articles on topics for which we have good sources, the summation of which do not amount to the original research through creating a novel narrative, and which does not impart greater weight to the topic than exists in the wider world, represented by the reliable sources we seek.
I don't see how V, NOR, and NPOV imply that we should not impart greater weight to a topic than exists in the wider world. For that matter I don't even understand what that means.
If we source only from the primary source, the topic itself, we cannot do anything but present information from a biased point of view. Yes, it is disappointing that there exists categories of information for which Wikipedia would be a wonderful repository, but for which no other sources exist for us to summate. However, that cannot be something we should seek to remedy. Wikipedia is not a place for original research. To me, that means Wikipedia cannot be a place to make claims of importance for any topic. Such claims should already be established within reliable sources, before we can attempt to document them. It is unfortunate that closers in afd discussions are not mindful of this, but it is the case that Wikipedia is a tertiary source. Wikipedia is not a repository for primary research.
To this point I still can't really figure out what you're trying to say. That paragraph above is pretty much indisputable.
So is your four way stop worthy of an article? On the strength of your description, I would say no, because you are imparting undue weight to it by creating such an article, you are presenting information for your own point of view rather than summarising someone else's, and if the article states only that four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington then I'd consider speedying it per A1.
I'd say it needs to be expanded if that's all it says. Using those secondary sources provided by the person adding the information I'm sure you could come up with a nice little article on the subsection of Pullman where the street is located, or maybe on [[Streets and intersections in Pullman, Washington]], or something like that. Right now it's far too hypothetical, so I don't know exactly what the best solution would be, though.
But as I pointed out when the comment was first made, it's not clear whether or not the four-way stop on that intersection is verifiable without resorting to original research. It might be, and it might not be. It would, of course, be the job of the person adding the information to show that it is.
Speedy deletion of such true information doesn't make any sense to me though. At the least move the information into the talk page of the Pullman, Washington article, please.
Anthony
I find [[WP:V]] and [[WP:NOR]] all to be very linked together.
[[Streets and intersections in Pullman, Washington]] would be seen as listcruft.
Joe
On 5/1/06, Anthony DiPierro wikilegal@inbox.org wrote:
On 4/30/06, Steve Block steve.block@myrealbox.com wrote:
Philip Welch wrote:
On Apr 23, 2006, at 4:21 PM, Steve Block wrote:
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source.
I can provide multiple third party reliable sources as evidence that there is a four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington. Does that mean that aforementioned four way stop is worthy of mention in Wikipedia?
What this guideline is trying to do is define notability within the verifiability chain.
It attempts to close the door on the possibility of allowing wikipedians to decide what is and isn't notable, something I believe is against both the original research and POV policies. We should seek to summarise claims of importance, where those claims are verifiable.
I've always considered NOR to be *part of* the verifiability rules. It is a description of what sources count toward verifiability. For that matter, both rules are really an explanation of what NPOV means - "assert facts, including facts about opinions — but don't assert opinions themselves". NOR and V go on to describe what is meant by "facts".
I guess what I'm saying is you can't really eliminate any of those three rules without significantly affecting the interpretation of the other one, or to quote NPOV: "Because the three policies are complementary, they should not be interpreted in isolation from one other, and editors should therefore try to familiarize themselves with all three."
Verifiability, NOR and NPOV do not mean we can write articles on topics we happen to feel should have them, they mean we should write articles on topics for which we have good sources, the summation of which do not amount to the original research through creating a novel narrative, and which does not impart greater weight to the topic than exists in the wider world, represented by the reliable sources we seek.
I don't see how V, NOR, and NPOV imply that we should not impart greater weight to a topic than exists in the wider world. For that matter I don't even understand what that means.
If we source only from the primary source, the topic itself, we cannot do anything but present information from a biased point of view. Yes, it is disappointing that there exists categories of information for which Wikipedia would be a wonderful repository, but for which no other sources exist for us to summate. However, that cannot be something we should seek to remedy. Wikipedia is not a place for original research. To me, that means Wikipedia cannot be a place to make claims of importance for any topic. Such claims should already be established within reliable sources, before we can attempt to document them. It is unfortunate that closers in afd discussions are not mindful of this, but it is the case that Wikipedia is a tertiary source. Wikipedia is not a repository for primary research.
To this point I still can't really figure out what you're trying to say. That paragraph above is pretty much indisputable.
So is your four way stop worthy of an article? On the strength of your description, I would say no, because you are imparting undue weight to it by creating such an article, you are presenting information for your own point of view rather than summarising someone else's, and if the article states only that four way stop on the intersection between Merman Drive and Terre View Drive in Pullman, Washington then I'd consider speedying it per A1.
I'd say it needs to be expanded if that's all it says. Using those secondary sources provided by the person adding the information I'm sure you could come up with a nice little article on the subsection of Pullman where the street is located, or maybe on [[Streets and intersections in Pullman, Washington]], or something like that. Right now it's far too hypothetical, so I don't know exactly what the best solution would be, though.
But as I pointed out when the comment was first made, it's not clear whether or not the four-way stop on that intersection is verifiable without resorting to original research. It might be, and it might not be. It would, of course, be the job of the person adding the information to show that it is.
Speedy deletion of such true information doesn't make any sense to me though. At the least move the information into the talk page of the Pullman, Washington article, please.
Anthony _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On 5/1/06, Joe Anderson computerjoe.mailinglist@googlemail.com wrote:
I find [[WP:V]] and [[WP:NOR]] all to be very linked together.
[[Streets and intersections in Pullman, Washington]] would be seen as listcruft.
Joe
What's listcruft?
Anthony
Listcruft is a term on AfD used for the deletion of lists. Generally, it is used for pointless lists.
On 5/1/06, Anthony DiPierro wikilegal@inbox.org wrote:
On 5/1/06, Joe Anderson computerjoe.mailinglist@googlemail.com wrote:
I find [[WP:V]] and [[WP:NOR]] all to be very linked together.
[[Streets and intersections in Pullman, Washington]] would be seen as listcruft.
Joe
What's listcruft?
Anthony _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Joe Anderson
[[User:Computerjoe]] on en, fr, de, simple, Meta and Commons.
Based on just the title [[Streets and intersections in Pullman, Washington]], I don't see how such an article would necessarily be pointless or a list.
I suppose that wouldn't necessarily stop it from being deleted as "listcruft", though...
Anthony
On 5/1/06, Joe Anderson computerjoe.mailinglist@googlemail.com wrote:
Listcruft is a term on AfD used for the deletion of lists. Generally, it is used for pointless lists.
On 5/1/06, Anthony DiPierro wikilegal@inbox.org wrote:
On 5/1/06, Joe Anderson computerjoe.mailinglist@googlemail.com wrote:
I find [[WP:V]] and [[WP:NOR]] all to be very linked together.
[[Streets and intersections in Pullman, Washington]] would be seen as listcruft.
Joe
What's listcruft?
Anthony _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Joe Anderson
[[User:Computerjoe]] on en, fr, de, simple, Meta and Commons. _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
BTW, you could look at [[cruft]] :D
On 5/1/06, Anthony DiPierro wikilegal@inbox.org wrote:
Based on just the title [[Streets and intersections in Pullman, Washington]], I don't see how such an article would necessarily be pointless or a list.
I suppose that wouldn't necessarily stop it from being deleted as "listcruft", though...
Anthony
On 5/1/06, Joe Anderson computerjoe.mailinglist@googlemail.com wrote:
Listcruft is a term on AfD used for the deletion of lists. Generally, it
is
used for pointless lists.
On 5/1/06, Anthony DiPierro wikilegal@inbox.org wrote:
On 5/1/06, Joe Anderson computerjoe.mailinglist@googlemail.com
wrote:
I find [[WP:V]] and [[WP:NOR]] all to be very linked together.
[[Streets and intersections in Pullman, Washington]] would be seen
as
listcruft.
Joe
What's listcruft?
Anthony _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Joe Anderson
[[User:Computerjoe]] on en, fr, de, simple, Meta and Commons. _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Joe Anderson
[[User:Computerjoe]] on en, fr, de, simple, Meta and Commons.
Joe Anderson wrote:
Listcruft is a term on AfD used for the deletion of lists. Generally, it is used for pointless lists.
It is a particularly uncivil term generally used to abbreviate "I never heard of this stuff, and I can't imagine ever wanting to know it, so anybody who would is obviously stupid: it should be cleared out of Wikipedia now to make room for my stuff".
AfD is becoming a cesspit which can only be recovered by draining, dynamiting and redigging.
On 03/05/06, Phil Boswell phil.boswell@gmail.com wrote:
AfD is becoming a cesspit which can only be recovered by draining, dynamiting and redigging.
RfA too please. Everytime I read either the talk page or the project page I sigh with sadness...
Oppose. Doesn't meet my admin standards. Also, I'm biased against disruptively formatted signatures. Also, some concerns about civility. Also, the number of comments on people's oppose votes seems to be bordering on harassment of opposition voters.
Oppose. As Mackensen points out, MoP doesn't have a lot of main article contributions. The work you do is important for Wikipedia as a community, but I'm not convinced you need admin tools. I would also recommend that you use edit summaries more often.
Oppose. I can't possibly support a user who averages 10+ edits per page, no matter how good those edits are. Furthermore, this list gives me a heart attack. 5,615 article-space edits per Interiot's tool looks good on the surface, but 4,273 of them (76.1%) are to his ten favorite articles,
Oppose: too hung up on user boxes. See his user page.
Militantly Oppose - JoshuaZ seems to be a bright guy and very level-headed - I'm sure he'll be a great admin here. But with all sincerity, I cannot do anything but oppose someone who has lowered themselves to the reprehensible depths of posting "Questions" on WP:RfA pages. The Q/A grandstanding has nothing to do with anything.
Weak Oppose. Three odd months is too soon to become an admin, in my view at least six are required. I am also concerned that this user sometimes fails to understand that proper sourcing actually requires a footnote or other direct reference
Oppose (for now) - no valid email address on file, thus no way to contact privately, which is essential for admins. [this one is especially unfathomable - opposing adminship on the grounds that they haven't yet validated their email address?]
sigh...grr...sigh...
Why can't people just raise their concerns directly with the candidates, rather than using these petty concerns as a cudgel to bludgeon them over the head with when they're at their most vulnerable - asking for acceptance from the community?
Steve
On May 3, 2006, at 1:42 AM, Steve Bennett wrote:
RfA too please. Everytime I read either the talk page or the project page I sigh with sadness...
<examples snipped>
sigh...grr...sigh...
Why can't people just raise their concerns directly with the candidates, rather than using these petty concerns as a cudgel to bludgeon them over the head with when they're at their most vulnerable
- asking for acceptance from the community?
Trial by fire. If someone can't take the "abuse" of a standard RfA, they can't take the ongoing abuse that admins take all the time from vandals, trolls, and other trouble-makers.
Personally, I went through RfA just like a lot of people here. You don't see me whining about how I was bludgeoned over the head. RfA is supposed to be a tough process to get through.
On 03/05/06, Philip Welch wikipedia@philwelch.net wrote:
Trial by fire. If someone can't take the "abuse" of a standard RfA, they can't take the ongoing abuse that admins take all the time from vandals, trolls, and other trouble-makers.
Personally, I went through RfA just like a lot of people here. You don't see me whining about how I was bludgeoned over the head. RfA is supposed to be a tough process to get through.
Oh, I'm not objecting to it being rough. I'm objecting to someone actually being opposed for RfA for petty reasons
Steve
On May 3, 2006, at 10:39 AM, Steve Bennett wrote:
Trial by fire. If someone can't take the "abuse" of a standard RfA, they can't take the ongoing abuse that admins take all the time from vandals, trolls, and other trouble-makers.
Personally, I went through RfA just like a lot of people here. You don't see me whining about how I was bludgeoned over the head. RfA is supposed to be a tough process to get through.
Oh, I'm not objecting to it being rough. I'm objecting to someone actually being opposed for RfA for petty reasons
That seems fair, but RfA is a community based process, not a policy based process. With a community based process, you have to allow people to use criteria you disagree with in exchange for allowing consensus. With a policy based process, criteria might be more rational, but you might lose consensus.
I'm not saying the problem is insoluble, but there's always going to be people using criteria you don't like to vote on RfA.
Philip Welch wrote:
On May 3, 2006, at 10:39 AM, Steve Bennett wrote:
Trial by fire. If someone can't take the "abuse" of a standard RfA, they can't take the ongoing abuse that admins take all the time from vandals, trolls, and other trouble-makers.
Personally, I went through RfA just like a lot of people here. You don't see me whining about how I was bludgeoned over the head. RfA is supposed to be a tough process to get through.
Oh, I'm not objecting to it being rough. I'm objecting to someone actually being opposed for RfA for petty reasons
That seems fair, but RfA is a community based process, not a policy based process. With a community based process, you have to allow people to use criteria you disagree with in exchange for allowing consensus. With a policy based process, criteria might be more rational, but you might lose consensus.
The community is full of trolls - to the point where they claim that they've been made admins. Of course, they could just be trolling, but if that doesn't say that RFA needs a sanity check, I don't know /what/ does.
On Wed, 3 May 2006 10:42:12 +0200, you wrote:
Militantly Oppose - JoshuaZ seems to be a bright guy and very level-headed - I'm sure he'll be a great admin here. But with all sincerity, I cannot do anything but oppose someone who has lowered themselves to the reprehensible depths of posting "Questions" on WP:RfA pages. The Q/A grandstanding has nothing to do with anything.
They said that about Joshua? Where's that wet trout? Joshua is a very calm and levelheaded person, ideal admin material IMO.
Guy (JzG)
On 03/05/06, Guy Chapman aka JzG guy.chapman@spamcop.net wrote:
On Wed, 3 May 2006 10:42:12 +0200, you wrote:
Militantly Oppose - JoshuaZ seems to be a bright guy and very level-headed - I'm sure he'll be a great admin here. But with all sincerity, I cannot do anything but oppose someone who has lowered themselves to the reprehensible depths of posting "Questions" on WP:RfA pages. The Q/A grandstanding has nothing to do with anything.
They said that about Joshua? Where's that wet trout? Joshua is a very calm and levelheaded person, ideal admin material IMO.
Your opinion is that; and neither wrong nor right. I'd fight for your right to have it, but I would fight you before it was thrust upon another.
Rob Church
On 03/05/06, Rob Church robchur@gmail.com wrote:
Your opinion is that; and neither wrong nor right. I'd fight for your right to have it, but I would fight you before it was thrust upon another.
Without going into specifics, this is the problem with things like RfA and AfD. We have a set of principles that decisions are meant to be based on. But ultimately, the most flawed reasning is worth pretty much as much as the best reasoning.
Except that in the case of RfA, we don't even have agreed principles that decisions should be based on, so all reasoning is good reasoning.
Steve
On Thu, 4 May 2006 00:17:58 +0200, you wrote:
Except that in the case of RfA, we don't even have agreed principles that decisions should be based on, so all reasoning is good reasoning.
For some values of good, obviously.
My problem here is with the assertion that asking questions of candidates for adminship is in some way bad. I really can't see how that could be a valid viewpoint. One of the most pertinent questions I've seen asked of an admin candidate recently was whether they saw the role of admin more as that of policeman or janitor. Asking that question is entirely consistent with adminship being no big deal, also entirely consistent with knowing in advance to whom we are giving the tools, and what they will do with them. For my money we don't need policemen, but this is of course also just one person's view.
Guy (JzG)
On May 3, 2006, at 1:07 AM, Phil Boswell wrote:
Listcruft is a term on AfD used for the deletion of lists. Generally, it is used for pointless lists.
It is a particularly uncivil term generally used to abbreviate "I never heard of this stuff, and I can't imagine ever wanting to know it, so anybody who would is obviously stupid: it should be cleared out of Wikipedia now to make room for my stuff".
AfD is becoming a cesspit which can only be recovered by draining, dynamiting and redigging.
Careful, Phil, you're being uncivil towards everyone who uses AfD and towards Joe in particular here.
Not that it's unprecedented for people on this list to be civility hypocrites.
On 03/05/06, Philip Welch wikipedia@philwelch.net wrote:
Not that it's unprecedented for people on this list to be civility hypocrites.
Eep, let's chill, everyone, please?
Steve
On 5/1/06, Anthony DiPierro wikilegal@inbox.org wrote:
What's listcruft?
On *fD, <foo>cruft is shorthand for 'articles about <foo> that are below my personal notability threshold'. Thus its application is generally tautological and only serves to denigrate the subject matter.
-Matt
On 01/05/06, Matt Brown morven@gmail.com wrote:
On 5/1/06, Anthony DiPierro wikilegal@inbox.org wrote:
What's listcruft?
On *fD, <foo>cruft is shorthand for 'articles about <foo> that are below my personal notability threshold'. Thus its application is generally tautological and only serves to denigrate the subject matter.
And/or discredit the person using the term. It really is a pretty offensive term, but I don't know if most people using it realise that.
Steve
On 5/1/06, Steve Bennett stevage@gmail.com wrote:
And/or discredit the person using the term. It really is a pretty offensive term, but I don't know if most people using it realise that.
I think some do and use it intentionally so. Which appears to be rather contrary to civility and treating other contributors with respect, I feel.
-Matt
On 01/05/06, Steve Bennett stevage@gmail.com wrote:
On 01/05/06, Matt Brown morven@gmail.com wrote:
On *fD, <foo>cruft is shorthand for 'articles about <foo> that are below my personal notability threshold'. Thus its application is generally tautological and only serves to denigrate the subject matter.
And/or discredit the person using the term. It really is a pretty offensive term, but I don't know if most people using it realise that.
Some people use 'cruft' (me, for example) in the original sense - it's the word for that dust and fluff you pull out from under furniture. It is, outside of Wikipedia, most commonly applied to badly written and messy programming. Back in Wiki context, the term (when used in this sense, at least) makes no assertion of notability, but rather suggests that the article is in need of a major rewrite and/or cleanup.
So 'listcruft' implies a poorly-written list, probably in need of a loving Wikipedian to take it in and foster it back to full health. However, some 'cruft' is beyond redemption, and the best remedy for that is a brand new stub to take its place.
Can you tell I don't regularly take part in AfDs?
--Sam
When I'm using the term listcruft it is not intended to offend the author. Look at [[Wikipedia:Articles for deletion/List of PS2 DVD9 Games]].
On 5/1/06, Sam Pointon free.condiments@gmail.com wrote:
On 01/05/06, Steve Bennett stevage@gmail.com wrote:
On 01/05/06, Matt Brown morven@gmail.com wrote:
On *fD, <foo>cruft is shorthand for 'articles about <foo> that are below my personal notability threshold'. Thus its application is generally tautological and only serves to denigrate the subject matter.
And/or discredit the person using the term. It really is a pretty offensive term, but I don't know if most people using it realise that.
Some people use 'cruft' (me, for example) in the original sense - it's the word for that dust and fluff you pull out from under furniture. It is, outside of Wikipedia, most commonly applied to badly written and messy programming. Back in Wiki context, the term (when used in this sense, at least) makes no assertion of notability, but rather suggests that the article is in need of a major rewrite and/or cleanup.
So 'listcruft' implies a poorly-written list, probably in need of a loving Wikipedian to take it in and foster it back to full health. However, some 'cruft' is beyond redemption, and the best remedy for that is a brand new stub to take its place.
Can you tell I don't regularly take part in AfDs?
--Sam _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Joe Anderson
[[User:Computerjoe]] on en, fr, de, simple, Meta and Commons.
[[Wikipedia:Articles for deletion/List of PS2 DVD9
Games]]
How sad. Lots of votes to delete. And none of them presenting a cogent argument. Uses of the word "-cruft" as some sort of excuse to avoid having to do so.
The one user who presents an argument is the one who created the list, and you play the man not the ball by arguing about the few edits he has in the Wikipedia: namespace. He has few edits there because he spends his time trying to create content!
Pete
p.s. The information should be merged into the broader list of games.
----- Original Message ---- From: Joe Anderson computerjoe.mailinglist@googlemail.com To: English Wikipedia wikien-l@wikipedia.org Sent: Tuesday, 2 May, 2006 8:04:36 AM Subject: Re: [WikiEN-l] Verifiability equating to notability
When I'm using the term listcruft it is not intended to offend the author. Look at [[Wikipedia:Articles for deletion/List of PS2 DVD9 Games]].
On 5/1/06, Sam Pointon free.condiments@gmail.com wrote:
On 01/05/06, Steve Bennett stevage@gmail.com wrote:
On 01/05/06, Matt Brown morven@gmail.com wrote:
On *fD, <foo>cruft is shorthand for 'articles about <foo> that are below my personal notability threshold'. Thus its application is generally tautological and only serves to denigrate the subject matter.
And/or discredit the person using the term. It really is a pretty offensive term, but I don't know if most people using it realise that.
Some people use 'cruft' (me, for example) in the original sense - it's the word for that dust and fluff you pull out from under furniture. It is, outside of Wikipedia, most commonly applied to badly written and messy programming. Back in Wiki context, the term (when used in this sense, at least) makes no assertion of notability, but rather suggests that the article is in need of a major rewrite and/or cleanup.
So 'listcruft' implies a poorly-written list, probably in need of a loving Wikipedian to take it in and foster it back to full health. However, some 'cruft' is beyond redemption, and the best remedy for that is a brand new stub to take its place.
Can you tell I don't regularly take part in AfDs?
--Sam _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Joe Anderson
[[User:Computerjoe]] on en, fr, de, simple, Meta and Commons. _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
Joe Anderson wrote:
When I'm using the term listcruft it is not intended to offend the author. Look at [[Wikipedia:Articles for deletion/List of PS2 DVD9 Games]].
I did and that deletion discussion is a catalogue of newbie biting and nastiness of the kind which has given AFD its poor reputation.
You quote [[Wikipedia:Listcruft]], a personal essay, as if it were policy. You have failed to note, furthermore, that the essay itself says that holding a similar opinion should not be a *sole* reason for deletion...I fail to see any other proffered by you or indeed any other "delete voter".
You then proceed to bite the newbie on the grounds that his request to keep his article is his first edit to the Wikipedia namespace. Obviously this will spur him on to edit that namespace further in the future, knowing that he will receive such a warm and friendly reception...
You then say "IMO, listcruft is not uncivil"...well, I could make comments about your appearance, your family and your personal habits...if they were not uncivil "in my opinion", would that make them less offensive to you? Once again, read the essay you quote as your justification for nomination, which makes this exact point.
Quite frankly this nomination has made me quite annoyed, and I fail to understand why you would open yourself to comment in this way...maybe you simply cannot understand why anybody would be annoyed that their article should be nominated for deletion on the somewhat shaky grounds of "I wouldn't ever want to read it so get rid of it".
On 02/05/06, Sam Pointon free.condiments@gmail.com wrote:
Some people use 'cruft' (me, for example) in the original sense - it's the word for that dust and fluff you pull out from under furniture. It is, outside of Wikipedia, most commonly applied to badly written and messy programming. Back in Wiki context, the term (when used in this sense, at least) makes no assertion of notability, but rather suggests that the article is in need of a major rewrite and/or cleanup.
You probably wouldn't use the term to describe a bunch of articles recently written by an enthusiastic young contributor to Wikipedia, who simply needs to be guided towards areas of Wikipedia more in need of his energy, then.
It's really hard to avoid causing offense when you're nominating an article for deletion, or even supporting a nomination. Pity that some people don't even try :/
Steve
G'day Sam,
Some people use 'cruft' (me, for example) in the original sense - it's the word for that dust and fluff you pull out from under furniture. It is, outside of Wikipedia, most commonly applied to badly written and messy programming. Back in Wiki context, the term (when used in this sense, at least) makes no assertion of notability, but rather suggests that the article is in need of a major rewrite and/or cleanup.
In computing terms, "cruft" is often used as a synonym for Phillip K Dick's "kipple" --- the little errors that build up in Windows over time. Entropy in action. Likewise "cruft" can refer to the encyclopaedia holding more crap than not as people's enthusiasm overwhelms their common sense. Sadly, what is and is not crap is subject to hot debate.
Describing someone's good-faith contributions as "cruft" can be quite offensive, and the mere fact that people see it as having value makes the "cruft" moniker likely to be improperly applied. Then again, there are some contributions that simply cannot be defended. There used to be an "... in popular culture" section in our article on DEFCON that said something like "In /Buffy the Vampire Slayer/, Faith says 'we're at DEFCON 2!', or words to that effect" ...
So 'listcruft' implies a poorly-written list, probably in need of a loving Wikipedian to take it in and foster it back to full health. However, some 'cruft' is beyond redemption, and the best remedy for that is a brand new stub to take its place.
Can you tell I don't regularly take part in AfDs?
-cruft is coming to mean "I don't want this here", and has therefore changed in meaning from insulting the person who wrote an up-for-deletion article into the new, and more disturbing, form of insulting the person who uses it, and the intelligence of the person who reads it.
Anthony DiPierro wrote:
On 4/30/06, Steve Block steve.block@myrealbox.com wrote:
Verifiability, NOR and NPOV do not mean we can write articles on topics we happen to feel should have them, they mean we should write articles on topics for which we have good sources, the summation of which do not amount to the original research through creating a novel narrative, and which does not impart greater weight to the topic than exists in the wider world, represented by the reliable sources we seek.
I don't see how V, NOR, and NPOV imply that we should not impart greater weight to a topic than exists in the wider world. For that matter I don't even understand what that means.
What I mean is I'm trying to figure out the answer to the following question, is an article written about foo, using only foo as a source, written from a npov? My main line of thinking has been that to use foo as the only source in an article on foo imparts undue weight to foo; there are no other sources to use in writing an article, so by writing the article I am asserting a point of view that the article should exist. Is that the reason articles should exist, or should articles exist because there are external sources we can use to write from a neutral point of view?
Can we write an article which basically says:
Foo is a website which allows you to create a blog. You do that by visiting this link, filling out this form and then you have a blog. Foo also hosts forums, which are broken down into sub-forums focussing on such topics as films, music and eggs. Foo doesn't have a chat room, but a lot of people who use foo use the same chat room at this link. Recently users of foo had a contest on foo's message boards and voted this film the best ever film.
Because I don't seem to be able to work out, through the various policies, why we can't. Because primary sources are allowed to be used as sources for information on themselves, and this is the argument I don't understand, because it seems to mean I can create an article on my self using my blog as a source. If I can't do that, why can people game Wikipedia by creating articles on forums and websites which have no external sourcing simply through sheer weight of numbers?
But as I pointed out when the comment was first made, it's not clear whether or not the four-way stop on that intersection is verifiable without resorting to original research. It might be, and it might not be. It would, of course, be the job of the person adding the information to show that it is.
But what, in this instance, is original research? Is sourcing from public archives original research? Is reading a book original research? Is looking at a map original research?
Steve block
On 02/05/06, Steve Block steve.block@myrealbox.com wrote:
But what, in this instance, is original research? Is sourcing from public archives original research? Is reading a book original research? Is looking at a map original research?
Original research is doing research in an "original" (or novel, or imaginative, non-standard, creative...) way. We've discussed this quite a lot on this list. It's generally hard to interpret a map creatively. It's much easier to claim that a book supports your proposition.
Basically it comes down to: your source should say exactly what you want it to say. You shouldn't have to interpret it, read between the lines, take context into account, bear in mind that the author was homosexual, or that he was running for president at the time. If any of that stuff is required, you should be using a secondary source to perform that interpretation for you.
Steve
The first half of your post answered my questions. I haven't decided if I agree yet :), but it does make sense.
On 5/2/06, Steve Block steve.block@myrealbox.com wrote:
But as I pointed out when the comment was first made, it's not clear whether or not the four-way stop on that intersection is verifiable without resorting to original research. It might be, and it might not be. It would, of course, be the job of the person adding the information to show that it is.
But what, in this instance, is original research? Is sourcing from public archives original research? Is reading a book original research? Is looking at a map original research?
Steve block
The way I see original research is basically any text which can't be derived trivially from a published source. That's my understanding, without looking at any Wikipedia pages.
Now I suppose "derived trivially" is subject to some dispute there. I like the way Steve Bennett explained this, though I think we have to allow interpretation (including context) to the extent that no one would reasonably dispute the interpretation.
And that's another factor that has to be kept in mind. NOR is, more than anything, a fallback for when there is a disagreement. If no one (who isn't banned, anyway) has a problem with the text as its written, then NOR can safely be ignored. NOR comes into place when someone, (anyone acting in good faith), reads a statement in a Wikipedia article, then reads the source or sources, and isn't *convinced* that the statement is true.
To answer your questions... The main source of original research in the four-way-stop case would be direct observation. Interviews would also qualify as original research, to give another example. Sourcing from public archives wouldn't be original research as far as I'm concerned. Reading a book, assuming a published book, would be fine. Looking at a map, assuming a published map, would be fine too.
What counts as published? I'm sure there's grey area, but the main distinction is that copies are available to the public, for free or for a fee.
Anthony
Anthony DiPierro wrote:
The first half of your post answered my questions. I haven't decided if I agree yet :), but it does make sense.
On 5/2/06, Steve Block steve.block@myrealbox.com wrote:
But as I pointed out when the comment was first made, it's not clear whether or not the four-way stop on that intersection is verifiable without resorting to original research. It might be, and it might not be. It would, of course, be the job of the person adding the information to show that it is.
But what, in this instance, is original research? Is sourcing from public archives original research? Is reading a book original research? Is looking at a map original research?
Steve block
The way I see original research is basically any text which can't be derived trivially from a published source. That's my understanding, without looking at any Wikipedia pages.
Now I suppose "derived trivially" is subject to some dispute there. I like the way Steve Bennett explained this, though I think we have to allow interpretation (including context) to the extent that no one would reasonably dispute the interpretation.
And that's another factor that has to be kept in mind. NOR is, more than anything, a fallback for when there is a disagreement. If no one (who isn't banned, anyway) has a problem with the text as its written, then NOR can safely be ignored. NOR comes into place when someone, (anyone acting in good faith), reads a statement in a Wikipedia article, then reads the source or sources, and isn't *convinced* that the statement is true.
To answer your questions... The main source of original research in the four-way-stop case would be direct observation.
See I agree, but I take that to mean that looking at a website is also original research.
Sourcing from public archives wouldn't be original research as far as I'm concerned.
However, there is a line of argument that me going to the public records office to look up someone's date of birth is original research, since I can't verify that the certificate I get is for the person I claim it to be for. SO sourcing from public archives is a contentious area.
Steve block
My beef is this ... What counts as a reliable source? Does a mention of a POV-pushing political phrase in heresy-hunting leftist rag count as a reliable source, such that said phrase could be used to label people and parties that may go 10 or 20% in the general direction claimed, but not the 100% claimed by the label applied to them? Lately I've had such run-ins. POV-pushing publications (even if respected by otherwise respectable people) do not count as verifiability. <probably a rabbit trail for your conversation> -- Chris (aka Gudsthegn)
On 4/23/06, Steve Block steve.block@myrealbox.com wrote:
I had a bash at creating a proposal which would define notability on wikipedia as meaning that an article or topic is mentioned in a third party reliable source. I figure it should be impossible to write an article without a third party reference, as per [[WP:V]], [[WP:NOR}] and [[WP:NPOV]], and so I hope that people will consider using that as the level for notability in areas where no other guidance exists.
Thoughts welcomed at [[Wikipedia:Notability/Proposals]].
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.5/322 - Release Date: 22/04/06
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On Mon, 24 Apr 2006 22:05:11 -0500, you wrote:
My beef is this ... What counts as a reliable source? Does a mention of a POV-pushing political phrase in heresy-hunting leftist rag count as a reliable source
Not that your POV is showing or anything...
Guy (JzG)
My point regards ANY POV-pushing source. Rightest rags don't work either.
-- Chris (Gudsthegn)
On 4/25/06, Guy Chapman aka JzG guy.chapman@spamcop.net wrote:
On Mon, 24 Apr 2006 22:05:11 -0500, you wrote:
My beef is this ... What counts as a reliable source? Does a mention of
a
POV-pushing political phrase in heresy-hunting leftist rag count as a reliable source
Not that your POV is showing or anything...
Guy (JzG)
http://www.chapmancentral.co.uk http://en.wikipedia.org/wiki/User:JzG
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
or rightist either. :-)
On 4/25/06, Christopher Erickson cerickson@gmail.com wrote:
My point regards ANY POV-pushing source. Rightest rags don't work either.
-- Chris (Gudsthegn)
On 4/25/06, Guy Chapman aka JzG guy.chapman@spamcop.net wrote:
On Mon, 24 Apr 2006 22:05:11 -0500, you wrote:
My beef is this ... What counts as a reliable source? Does a mention
of a
POV-pushing political phrase in heresy-hunting leftist rag count as a reliable source
Not that your POV is showing or anything...
Guy (JzG)
http://www.chapmancentral.co.uk http://en.wikipedia.org/wiki/User:JzG
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On Tue, 25 Apr 2006 16:28:01 -0500, you wrote:
My point regards ANY POV-pushing source. Rightest rags don't work either. -- Chris (Gudsthegn)
Sure. But if you're making strong statements about the kinds of sources which should be excluded per NPOV, it's best not to do it in pejorative partisan terms. As far as I'm concerned anything on Faux News is considered false until proven correct :-) Guy (JzG)
Christopher Erickson wrote:
My beef is this ... What counts as a reliable source? Does a mention of a POV-pushing political phrase in heresy-hunting leftist rag count as a reliable source, such that said phrase could be used to label people and parties that may go 10 or 20% in the general direction claimed, but not the 100% claimed by the label applied to them? Lately I've had such run-ins. POV-pushing publications (even if respected by otherwise respectable people) do not count as verifiability.
Rewrite the above substituting only "rightist" for "leftist" and the results come to the same thing. If you get away from political philosophies we'll have the same problem with other word pairs.
If in striving for NPOV we need to depend on a POV that determines a "reliable source" we haven't got NPOV at all. The best we can do is link to an article about the publication in question where hopefully there will be enough objective criteria to allow the reader to decide for himself. If we quote some article titles from the publication itself it will be evident that the articles, "Economic Gains of the Socialist Revolution," and "Human Rights Violation of the Socialist Revolution," will represent magazines with conflicting perspectives. How can we possibly come to the conclusion that any publication is POV-pushing without engaging in Original Research about that publication?
Ec
On 4/22/06, Philip Welch wikipedia@philwelch.net wrote:
Here's an interesting question: assuming those statistics are the same each month, is it the same 29 admins each month, or does it turn over?
It obviously does vary from month to month, but there are some people who are consistently in the top 25. I'm supposedly working on some stuff to report this more nicely, but as my toolserver account expires on May 1 and has not been reviewed, I probably won't actually do it.
Kelly
Oskar Sigvardsson wrote:
Simply disagreeing with someone, or thinking that they break some
policies are not enough for desysopping. Such an action is never punitive, which means that an admin can (and should) only lose their status for misuse of their priviliges. Can you name anyone lately? I mean, other than Eloquence. If you can't then stop writing these inflammatory messages, that serve no point whatsoever. If you can, then do something about it, and stop writing these inflammatory messages that serve no point whatsoever.
As a rule of thumb suspensions of privileges that exceed 24-hours should be considered punitive. When there are dangerous uncertainties about things that are happening 24 hours will be enough time to investigate. If after a best effort this still isn't enough one extend the time 24 hours at a time.
Ec
Ray Saintonge wrote:
As a rule of thumb suspensions of privileges that exceed 24-hours should be considered punitive. When there are dangerous uncertainties about things that are happening 24 hours will be enough time to investigate. If after a best effort this still isn't enough one extend the time 24 hours at a time.
I'd say that depends. An indefinite block of a vandalism-only account, made on the basis that "nothing good has ever come from this user, and most likely nothing ever will", is not punitive but preventative.
Ilmari Karonen wrote:
Ray Saintonge wrote:
As a rule of thumb suspensions of privileges that exceed 24-hours should be considered punitive. When there are dangerous uncertainties about things that are happening 24 hours will be enough time to investigate. If after a best effort this still isn't enough one extend the time 24 hours at a time.
I'd say that depends. An indefinite block of a vandalism-only account, made on the basis that "nothing good has ever come from this user, and most likely nothing ever will", is not punitive but preventative.
I suppose it's a bit of both. In most cases this is not the type of block to be reverted except in cases of insanity. There could be cases of shared IPs. There could be a reasonable explanation of newbie error. There could be a lack of adequate warning.
Where the blocker may have needed to act quickly in the middle of multiple vandal attacks, the reverter may have taken the time to investigate a single case more thoroughly. The reverter at least owes an explantion when he acts, but the presumption should be that he is acting in good faith. Reverters who make a habit of seriously unsound reverts will soon be known by the entire community.
Ec
On 4/20/06, jkelly@fas.harvard.edu jkelly@fas.harvard.edu wrote:
While we're engaging in this critique of Danny's response, it might make sense to ask whether or not Danny, and the other office people, are aware that there exists some large segment of the admin population who regard it as routine to undo other admin actions without discussion because they were "out of process", or "obviously wrong", or whatever. Can we imagine the possibility that some people might interpret that as inexplicable, or even hostile, interference, if they aren't used to this?
I just posted this to another thread, but it's more appropriate here. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war, meaning the admin who's only trying to return to the status quo ante gets the blame.
This is nonsense and it lies at the heart of all this trouble. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening (except where the original admin can't be contacted and it has to be done quickly). But as a rule, we shouldn't be undoing each other's admin actions at all.
Sarah
On 4/20/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
But as a rule, we shouldn't be undoing each other's admin actions at all.
And certainly not without talking with the other admin and bringing it to a wider forum in the hopes of getting some second, third, etc. opinions.
There are always emergency cases (e.g. a range block that accidentally blocked a whole ISP, etc) but in most cases a bit more deliberation won't be the end of the world.
-Matt
The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening (except where the original admin can't be contacted and it has to be done quickly). But as a rule, we shouldn't be undoing each other's admin actions at all.
I think "wheel war" is a great term that overly bold admins can throw at people who disagree with them, making it seem like it is the fault of the reverter, that the one returning things to the status quo is the rouge, when in fact it could simply be that the original admin's edits were unwarranted. Or stupid. I still haven't heard a reason why admins shouldn't revert admin actions "at all" except that it's wheel-warring, which is a rather circular answer (fitting, I suppose for a wheel). So I suppose my response to "We shouldn't be undoing each other's admin actions at all" is that we also shouldn't be making any mistakes at all. But it happens, and so should be able to unhappen.
Ben
On 4/20/06, Ben Lowe ben.lowe@gmail.com wrote:
I still haven't heard a reason why admins shouldn't revert admin actions "at all" except that it's wheel-warring, which is a rather circular answer (fitting, I suppose for a wheel). So I suppose my response to "We shouldn't be undoing each other's admin actions at all" is that we also shouldn't be making any mistakes at all. But it happens, and so should be able to unhappen.
My preferred policy change would not be 'we shouldn't ever undo admin actions' but rather 'we shouldn't undo admin actions instantly and without discussion'.
Very few things are so, so critical that there isn't time to discuss.
Yes, admins make mistakes - we all do. It's not undoing admin actions that's bad, it's the culture of instant, jump-to-conclusions reverting that is.
-Matt
Matt Brown wrote:
On 4/20/06, Ben Lowe ben.lowe@gmail.com wrote:
I still haven't heard a reason why admins shouldn't revert admin actions "at all" except that it's wheel-warring, which is a rather circular answer (fitting, I suppose for a wheel). So I suppose my response to "We shouldn't be undoing each other's admin actions at all" is that we also shouldn't be making any mistakes at all. But it happens, and so should be able to unhappen.
My preferred policy change would not be 'we shouldn't ever undo admin actions' but rather 'we shouldn't undo admin actions instantly and without discussion'.
Very few things are so, so critical that there isn't time to discuss.
A correlary ought to be: We shouldn't *do* admin actions instantly and without discussion, for the same reason.
-Mark
Delirium wrote:
Matt Brown wrote:
On 4/20/06, Ben Lowe ben.lowe@gmail.com wrote:
I still haven't heard a reason why admins shouldn't revert admin actions "at all" except that it's wheel-warring, which is a rather circular answer (fitting, I suppose for a wheel). So I suppose my response to "We shouldn't be undoing each other's admin actions at all" is that we also shouldn't be making any mistakes at all. But it happens, and so should be able to unhappen.
My preferred policy change would not be 'we shouldn't ever undo admin actions' but rather 'we shouldn't undo admin actions instantly and without discussion'.
Very few things are so, so critical that there isn't time to discuss.
A correlary ought to be: We shouldn't *do* admin actions instantly and without discussion, for the same reason.
In many cases that's just not practical. There's always a lot of uncontroversial routine cleanup jobs that need doing. Full discussion of these is tantamount to needing written permission from your wife each and every time you want to wash the dishes.
Ec
On 4/20/06, Ben Lowe ben.lowe@gmail.com wrote:
I still haven't heard a reason why admins shouldn't revert admin actions "at all" except that it's wheel-warring, which is a rather circular answer (fitting, I suppose for a wheel).
Because we elect admins we feel we can trust to use good judgment and be responsible. When someone's been an active admin for a while, they develop instincts about how to act in certain situations, and they tend to be very familar with policy and how it works de jure and de facto, and the admin community should trust and respect that experience. That doesn't mean don't question it. It means don't undo it, unless an unambiguous error has been made.
Sarah
Ben Lowe wrote:
The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening (except where the original admin can't be contacted and it has to be done quickly). But as a rule, we shouldn't be undoing each other's admin actions at all.
I think "wheel war" is a great term that overly bold admins can throw at people who disagree with them, making it seem like it is the fault of the reverter, that the one returning things to the status quo is the rouge, when in fact it could simply be that the original admin's edits were unwarranted. Or stupid. I still haven't heard a reason why admins shouldn't revert admin actions "at all" except that it's wheel-warring, which is a rather circular answer (fitting, I suppose for a wheel). So I suppose my response to "We shouldn't be undoing each other's admin actions at all" is that we also shouldn't be making any mistakes at all. But it happens, and so should be able to unhappen.
Sometimes it takes a little friction to stop the wheel from spinning ... Just like the wheels on your car.
Ec
On 4/20/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
This is nonsense and it lies at the heart of all this trouble. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening (except where the original admin can't be contacted and it has to be done quickly). But as a rule, we shouldn't be undoing each other's admin actions at all.
This sounds like a fine and productive suggestion.
It is not *completely* obvious that this is the right way to behave, however -- one of the arguments for IAR as applied to admins, for instance, has long been that other admins can rv your actions right back -- and it is not currently understood as policy. So it is not surprising that many admins don't operate under this understanding.
++SJ
On 4/20/06, Delirium delirium@hackish.org wrote:
It is quite acceptable and even encouraged to unprotect pages that have been inappropriately protected.
I think this is (a part of, at least) the core of the problem. Is it quite acceptable? Is it encouraged? Should it be?
Is it the right of every administrator to second-guess the administrative actions of any other administrator, and instantly revert them if they feel justified?
I feel that the immediatist attitude of the vandal-fighter has infected many of the decision-making processes of en-wikipedia way too much. Everything must be fixed NOW. We must act as if we have the attention span of a mayfly, because later is as good as never.
Whereas in my belief most administrator actions do NOT need to be fixed *right now*, even if they are wrong. Bans and blocks - in most cases, the world will not end if an individual can't edit Wikipedia for a day. Frustrating though it might be. Page protection: everyone can live with not editing an article for a little bit. Deletion: undeletion can be done at any time, and unless an article is a very high-traffic one, our readers are unlikely to even notice.
The culture of feeling entitled to instantly revert, though, is quite damaging. It escalates arguments, builds up pressure, makes everyone tense, encourages revert wars. Nothing on Wikipedia should be settled by a fight. I feel that instant, no-discussion reverts of anything other than *obvious vandalism* - whether edits or administrative actions - encourages a quite unpleasant pattern of behaviour.
If we feel we have to do things instantly because it's too hard to keep track of things otherwise, then we need tools - procedure or software - to help with that.
-Matt
Matt Brown wrote:
I feel that the immediatist attitude of the vandal-fighter has infected many of the decision-making processes of en-wikipedia way too much. Everything must be fixed NOW. We must act as if we have the attention span of a mayfly, because later is as good as never.
With the absolute deepest respect for the vandal fighters, whose immediatist attitude saves us from untold volumes of unspeakable horrors, I will say that I agree totally with Matt here.
Some things require immediate action. Even some things having to do with WP:OFFICE, although my view is that if it comes to that, what we really really should do is look at what failure of process led us to that impasse in the first place.
But mostly, no. Mostly, if we (any of us! for any reason!) stub a controversial article and demand careful sourcing for rebuilding it, that's fine, EVEN IF THE ARTICLE SUCKS FOR A FEW DAYS.
Whereas in my belief most administrator actions do NOT need to be fixed *right now*, even if they are wrong. Bans and blocks - in most cases, the world will not end if an individual can't edit Wikipedia for a day. Frustrating though it might be. Page protection: everyone can live with not editing an article for a little bit. Deletion: undeletion can be done at any time, and unless an article is a very high-traffic one, our readers are unlikely to even notice.
Totally. Some of the silliest fights we have gotten into about alleged 'censorship by admins' was over the most trivial of topics.
The culture of feeling entitled to instantly revert, though, is quite damaging. It escalates arguments, builds up pressure, makes everyone tense, encourages revert wars. Nothing on Wikipedia should be settled by a fight. I feel that instant, no-discussion reverts of anything other than *obvious vandalism* - whether edits or administrative actions - encourages a quite unpleasant pattern of behaviour.
If we feel we have to do things instantly because it's too hard to keep track of things otherwise, then we need tools - procedure or software - to help with that.
Absolutely!
On 4/20/06, Matt Brown morven@gmail.com wrote:
Is it the right of every administrator to second-guess the administrative actions of any other administrator, and instantly revert them if they feel justified?
The culture of feeling entitled to instantly revert, though, is quite damaging.
Exactly right. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war. This is nonsense. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule.
Sarah
On 4/20/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
On 4/20/06, Matt Brown morven@gmail.com wrote:
Is it the right of every administrator to second-guess the administrative actions of any other administrator, and instantly revert them if they feel justified?
The culture of feeling entitled to instantly revert, though, is quite damaging.
Exactly right. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war. This is nonsense. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule.
Sarah
So if I say delete [[Template:NPOV]] (T1) you wouldn't revert that action?
-- geni
On 4/20/06, geni geniice@gmail.com wrote:
So if I say delete [[Template:NPOV]] (T1) you wouldn't revert that action?
Sometimes it will be annoying following a culture of 'no instant admin reverts', but I think the overall effect will be positive.
In such a case, I'd leave a message on YOUR talk page to the effect of 'Are you crazy?', and post to a few noticeboard pages to the effect of 'Geni has deleted [[Template:NPOV]], anyone agree with me that he shouldn't have?' and wait for either your response or a few other opinions before acting. Wikipedia will not end for want of [[Template:NPOV]].
However, deleting a commonly-accessed page upon which policies and guidelines depend could be construed as vandalism, too.
-Matt
On 4/20/06, Matt Brown morven@gmail.com wrote:
On 4/20/06, geni geniice@gmail.com wrote:
So if I say delete [[Template:NPOV]] (T1) you wouldn't revert that action?
Sometimes it will be annoying following a culture of 'no instant admin reverts', but I think the overall effect will be positive.
In such a case, I'd leave a message on YOUR talk page to the effect of 'Are you crazy?', and post to a few noticeboard pages to the effect of 'Geni has deleted [[Template:NPOV]], anyone agree with me that he shouldn't have?' and wait for either your response or a few other opinions before acting. Wikipedia will not end for want of [[Template:NPOV]].
No but it would probably have some rather negative effects. The fallout from restoring it would probably be less serious than the fallout from waiting around
To chose a more extream example. How long would you hang around discusing this:
http://en.wikipedia.org/w/index.php?title=Special%3ALog&type=move&us...
However, deleting a commonly-accessed page upon which policies and guidelines depend could be construed as vandalism, too.
-Matt
The template is "divisive and inflammatory" a clear T1 candidate.
-- geni
He could always delete WP:AFD :)
On 4/20/06, Matt Brown morven@gmail.com wrote:
On 4/20/06, geni geniice@gmail.com wrote:
So if I say delete [[Template:NPOV]] (T1) you wouldn't revert that
action?
Sometimes it will be annoying following a culture of 'no instant admin reverts', but I think the overall effect will be positive.
In such a case, I'd leave a message on YOUR talk page to the effect of 'Are you crazy?', and post to a few noticeboard pages to the effect of 'Geni has deleted [[Template:NPOV]], anyone agree with me that he shouldn't have?' and wait for either your response or a few other opinions before acting. Wikipedia will not end for want of [[Template:NPOV]].
However, deleting a commonly-accessed page upon which policies and guidelines depend could be construed as vandalism, too.
-Matt _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On Thu, 20 Apr 2006 22:32:39 +0100, you wrote:
So if I say delete [[Template:NPOV]] (T1) you wouldn't revert that action?
Not without asking you why you did it, no. After all, nobody would do something with such far-reaching consequences unless they had a really compelling reason.
I seriously don't see what the problem is in having a default zero-revert policy for admin actions. Anything else is tantamount to suggesting that admins are not open to reason if asked to reconsider. Guy (JzG)
On 4/20/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
On 4/20/06, Matt Brown morven@gmail.com wrote:
Is it the right of every administrator to second-guess the administrative actions of any other administrator, and instantly revert them if they feel justified?
The culture of feeling entitled to instantly revert, though, is quite damaging.
Exactly right. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war. This is nonsense. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule.
I concur entirely with Sarah's definition of when a wheel war begins. This culture of "free whacks at the post" has to go. NOBODY is entitled to revert without discussion. 3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]].
Kelly
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
I concur entirely with Sarah's definition of when a wheel war begins. This culture of "free whacks at the post" has to go. NOBODY is entitled to revert without discussion.
Can I watch what happens when you tell the CVU this?
3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]].
Thanks for the invite but I've been there already. I play by the rules as written in policy. You have no right to ask anything more than that.
-- geni
Kelly said:
"NOBODY is entitled to revert without discussion. 3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]]."
Slimvirgin said:
"The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule."
True story: Last month, I restored [[Static grass]] after another admin mistook the AfD template for the PROD template I had replaced a few hours previously. The toolserver was lagging and as a result the PROD list was outdated, and because the two templates look similar, it was an easy mistake to make. The discussion on AfD was ongoing. More than 20 hours later, the deleting admin left a message on the AfD page apologizing for the mistake. Are you suggesting that I should I have just left the article deleted until he logged on again to undo the deletion, thus bringing the AfD discussion to a halt?
What if he had left on vacation immediately after deleting the article? Does the AfD just sit there?
Alternatively, what if I talked with 4-5 other admins and they all agreed that I should undelete the article? Under the definition above, I would still be starting a wheel war by undeleting the article.
Obviously wheel warring is bad news, but surely common sense must be applied in some situations. If you think I'm off track, please tell me what I should have done instead.
Nathaniel
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
On 4/20/06, Matt Brown morven@gmail.com wrote:
Is it the right of every administrator to second-guess the administrative actions of any other administrator, and instantly revert them if they feel justified?
The culture of feeling entitled to instantly revert, though, is quite damaging.
Exactly right. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war. This is nonsense. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule.
I concur entirely with Sarah's definition of when a wheel war begins. This culture of "free whacks at the post" has to go. NOBODY is entitled to revert without discussion. 3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]].
Kelly _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-- Nathaniel C. Sheetz http://www.personal.psu.edu/ncs124
On 21/04/06, Nathaniel Sheetz spangineer@gmail.com wrote:
What if he had left on vacation immediately after deleting the article? Does the AfD just sit there?
Under the amended definition I gave somewhere (if the revertee would not argue with you, it's not a wheel war), you could safely delete it.
Alternatively, what if I talked with 4-5 other admins and they all agreed that I should undelete the article? Under the definition above, I would still be starting a wheel war by undeleting the article.
Under the amended definition Kelly gave, this would not be wheel warring.
Obviously wheel warring is bad news, but surely common sense must be applied in some situations. If you think I'm off track, please tell me what I should have done instead.
The original definition was unnecessarily strict. The two amendments proposed introduce "common sense". Hopefully. :)
Steve
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
I concur entirely with Sarah's definition of when a wheel war begins. This culture of "free whacks at the post" has to go. NOBODY is entitled to revert without discussion. 3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]].
Slightly OT, I think it makes a lot of sense to clearly tell prospective admins what *obligations* they are subjecting themselves to, as well as what special 'powers' they are gaining, by becoming administrators.
Obligations to: * Learn relevant policy and keep up with policy changes * Restrict what they repost on other sites * Respond to inquiries about their admin actions by other admins? * Obey a 1RR?
--SJ
On 4/21/06, SJ 2.718281828@gmail.com wrote:
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
I concur entirely with Sarah's definition of when a wheel war begins. This culture of "free whacks at the post" has to go. NOBODY is entitled to revert without discussion. 3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]].
Slightly OT, I think it makes a lot of sense to clearly tell prospective admins what *obligations* they are subjecting themselves to, as well as what special 'powers' they are gaining, by becoming administrators.
Obligations to:
- Learn relevant policy and keep up with policy changes
WP:CSD is edited more than once a day. I mean seriously that page needs an RSS feed or something. Keeping up with it is no trivial task.
- Obey a 1RR?
Revert warriours would just love that.
-- geni
On 4/20/06, geni geniice@gmail.com wrote:
On 4/21/06, SJ 2.718281828@gmail.com wrote:
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
I concur entirely with Sarah's definition of when a wheel war begins. This culture of "free whacks at the post" has to go. NOBODY is entitled to revert without discussion. 3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]].
Slightly OT, I think it makes a lot of sense to clearly tell prospective admins what *obligations* they are subjecting themselves to, as well as what special 'powers' they are gaining, by becoming administrators.
Obligations to:
- Learn relevant policy and keep up with policy changes
WP:CSD is edited more than once a day. I mean seriously that page needs an RSS feed or something. Keeping up with it is no trivial task.
Yes. It's a good thing these aren't already obligations :-) But I can imagine someone creating a weekly 'policy update' newsletter, and writing a bot that spams admin talk pages with a link to the latest edition once a week. You wouldn't be able to opt out of this spam as an admin, and would be expected to catch up on the newsletter regularly.
- Obey a 1RR?
Revert warriours would just love that.
I meant "Obey a 1RR with regards to other admins?"... but the question mark is still there for a reason.
SJ
On Apr 20, 2006, at 2:37 PM, Kelly Martin wrote:
I concur entirely with Sarah's definition of when a wheel war begins. This culture of "free whacks at the post" has to go. NOBODY is entitled to revert without discussion. 3RR says we're willing to tolerate it for regular editors. Admins are expected to be above this. Any admin who doesn't want to play by this rule is invited to visit [[m:Requests for permissions]].
Kelly, I'm glad to see you come around to this position, but I hope you are aware that Wikipedia doesn't set policy by your say-so :)
On 4/22/06, Philip Welch wikipedia@philwelch.net wrote:
Kelly, I'm glad to see you come around to this position, but I hope you are aware that Wikipedia doesn't set policy by your say-so :)
I realize that some people refuse to see wisdom when confronted with it. :)
Kelly
On 20/04/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
Exactly right. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war. This is nonsense. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule.
How's this for a definition: X blocks Y unblocks
If X disagrees with Y's unblock, then Y has wheel warred. If X reinstates the block, then X has wheel warred too.
This covers the situation where X makes a mistake and Y fixes it - X agrees with the mistake, and no damage is caused. If Y fears that X may accuse him of wheel warring, he shouldn't be undoing X's actions. (or should be prepared for the consequences)
Steve
Steve Bennett wrote:
On 20/04/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
Exactly right. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war. This is nonsense. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule.
How's this for a definition: X blocks Y unblocks
If X disagrees with Y's unblock, then Y has wheel warred. If X reinstates the block, then X has wheel warred too.
This covers the situation where X makes a mistake and Y fixes it - X agrees with the mistake, and no damage is caused. If Y fears that X may accuse him of wheel warring, he shouldn't be undoing X's actions. (or should be prepared for the consequences)
Anything but a one free revert policy makes no sense at all. There are just too many reasons why one admin might revert the actions of another. Some are good reasons; others are very bad.
Not allowing one free revert sets up the presumption that the original admin was right to do what he did, whether or not he included an explanation. The first revert, which should at least have an edit summary lets it be known that there is a difference of opinion. The one point where I disagree with Steve it that Y could be retroactively declared a wheel warrior for an honest expression of opinion.
If X disagrees with Y's initial revert, he too owes us an explanation.
Ec
* Ray Saintonge wrote:
Anything but a one free revert policy makes no sense at all. There are just too many reasons why one admin might revert the actions of another. Some are good reasons; others are very bad.
Actually, I think this focus on 'sequence of reverts' misses the point. Even the FIRST admin action could be the start of what I would call a 'wheel war'... yet the third might not. How does that make sense? It's all about 'good faith'.
If someone takes an admin action that they KNOW one or more other admins are going to object to and almost certainly revert then that person is responsible for 'starting' the wheel war... it doesn't matter that they didn't reverse the action of another admin. They took an admin action which they knew was not supported by general consensus. Now usually that doesn't happen because we don't know how other admins are going to react, but sometimes we obviously do and we shouldn't give the instigator a pass just because they got out there with a non-consensus action FIRST. If anything that makes them 'the troublemaker'.
In contrast, the reversion of an admin action is NOT always the start of a 'wheel war'. There are various templates which were 'protected indefinitely' because of high use. When I have found that some of these have been deprecated into near non-existence I have unprotected them... without tracking down the admin who protected them in the first place to 'discuss' it. Admins do things like this every day... and they SHOULD. That's not 'wheel warring'... that's simply the reasonable assumption that the original admin would agree that protection is no longer needed. If some other admin sees my unprotect and says 'Ack! That's the most heavily used template in the world - it needs to be protected!' they aren't 'wheel-warring' either... just mistakenly acting on out of date information in good faith.
So far as I'm concerned admin actions become a problem when the admin taking them KNOWS that the action is going to be objected to by other admins, but goes ahead anyway without gathering consensus. It doesn't matter if that's the first admin action or the fifth. Obviously it is not always easy to determine whether someone is being deliberately confrontational vs making a good faith change that they assume will be ok - and that's where the sequence starts to play a part as it becomes more difficult to NOT realize that an action is controversial after it has been reverted. However, any hard and fast rules on 'first revert' or 'second revert' seem to me a bad idea. Any admin taking an admin action (without consensus after discussion) that they know other admins will find objectionable is acting in bad faith regardless of the 'sequence'.
Conrad Dunkerson wrote:
- Ray Saintonge wrote:
Anything but a one free revert policy makes no sense at all. There are just too many reasons why one admin might revert the actions of another. Some are good reasons; others are very bad.
Actually, I think this focus on 'sequence of reverts' misses the point. Even the FIRST admin action could be the start of what I would call a 'wheel war'... yet the third might not. How does that make sense? It's all about 'good faith'.
If someone takes an admin action that they KNOW one or more other admins are going to object to and almost certainly revert then that person is responsible for 'starting' the wheel war... it doesn't matter that they didn't reverse the action of another admin. They took an admin action which they knew was not supported by general consensus. Now usually that doesn't happen because we don't know how other admins are going to react, but sometimes we obviously do and we shouldn't give the instigator a pass just because they got out there with a non-consensus action FIRST. If anything that makes them 'the troublemaker'.
In contrast, the reversion of an admin action is NOT always the start of a 'wheel war'. There are various templates which were 'protected indefinitely' because of high use. When I have found that some of these have been deprecated into near non-existence I have unprotected them... without tracking down the admin who protected them in the first place to 'discuss' it. Admins do things like this every day... and they SHOULD. That's not 'wheel warring'... that's simply the reasonable assumption that the original admin would agree that protection is no longer needed. If some other admin sees my unprotect and says 'Ack! That's the most heavily used template in the world - it needs to be protected!' they aren't 'wheel-warring' either... just mistakenly acting on out of date information in good faith.
So far as I'm concerned admin actions become a problem when the admin taking them KNOWS that the action is going to be objected to by other admins, but goes ahead anyway without gathering consensus. It doesn't matter if that's the first admin action or the fifth. Obviously it is not always easy to determine whether someone is being deliberately confrontational vs making a good faith change that they assume will be ok
- and that's where the sequence starts to play a part as it becomes more
difficult to NOT realize that an action is controversial after it has been reverted. However, any hard and fast rules on 'first revert' or 'second revert' seem to me a bad idea. Any admin taking an admin action (without consensus after discussion) that they know other admins will find objectionable is acting in bad faith regardless of the 'sequence'.
In all that it's still better to assume good faith for the original action, and the first revert. It goes without question that some admins will act in bad faith, but we can't fairly make that assumption about any specific individual. Whether consensus is there for some action is not always evident; it's not rare to make a proposal that gets no response at all until after you have applied your consensus of one
Ec
On Apr 20, 2006, at 3:01 PM, Steve Bennett wrote:
How's this for a definition: X blocks Y unblocks
If X disagrees with Y's unblock, then Y has wheel warred. If X reinstates the block, then X has wheel warred too.
This covers the situation where X makes a mistake and Y fixes it - X agrees with the mistake, and no damage is caused. If Y fears that X may accuse him of wheel warring, he shouldn't be undoing X's actions. (or should be prepared for the consequences)
I would argue that X has the prerogative to reblock here, since Y wheel-warred (something that should not have happened) and after something that should not have happened, it's generally acceptable to reinstate the status quo ante.
On 4/22/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 20, 2006, at 3:01 PM, Steve Bennett wrote:
How's this for a definition: X blocks Y unblocks
If X disagrees with Y's unblock, then Y has wheel warred. If X reinstates the block, then X has wheel warred too.
This covers the situation where X makes a mistake and Y fixes it - X agrees with the mistake, and no damage is caused. If Y fears that X may accuse him of wheel warring, he shouldn't be undoing X's actions. (or should be prepared for the consequences)
I would argue that X has the prerogative to reblock here, since Y wheel-warred (something that should not have happened) and after something that should not have happened, it's generally acceptable to reinstate the status quo ante.
But X's block is clearly dissputed. Thus the status quo is no block. Wikipedia defults to doing nothing.
-- geni
On 22/04/06, geni geniice@gmail.com wrote:
But X's block is clearly dissputed. Thus the status quo is no block. Wikipedia defults to doing nothing.
We should probably keep this discussion general, about admin actions in general. What if X's action was an unblock, for example? Or a page unprotect...
Steve
On Apr 22, 2006, at 12:54 PM, Steve Bennett wrote:
But X's block is clearly dissputed. Thus the status quo is no block. Wikipedia defults to doing nothing.
We should probably keep this discussion general, about admin actions in general. What if X's action was an unblock, for example? Or a page unprotect...
An unblock or unprotect cannot exist without a block or protect. Unblocks and unprotects are by definition reversions.
On 22/04/06, Philip Welch wikipedia@philwelch.net wrote:
An unblock or unprotect cannot exist without a block or protect. Unblocks and unprotects are by definition reversions.
Hmm. Admin A protects a page then forgets about it. Two weeks later, Admin B notices the error and unprotects it. Admin C quickly jumps on him, and reprotects it. You're not going to argue that B is at fault, while C is simply restoring order in the force, are you...
(again my definition works: A would not object to B's action, hence B is not WWing. But B would object to C's action, so C is WWing).
Steve
On Apr 22, 2006, at 1:35 PM, Steve Bennett wrote:
An unblock or unprotect cannot exist without a block or protect. Unblocks and unprotects are by definition reversions.
Hmm. Admin A protects a page then forgets about it. Two weeks later, Admin B notices the error and unprotects it. Admin C quickly jumps on him, and reprotects it. You're not going to argue that B is at fault, while C is simply restoring order in the force, are you...
I'm only arguing that Admin B is, in fact, reverting an administrative action.
Philip Welch wrote:
On Apr 22, 2006, at 1:35 PM, Steve Bennett wrote:
An unblock or unprotect cannot exist without a block or protect. Unblocks and unprotects are by definition reversions.
Hmm. Admin A protects a page then forgets about it. Two weeks later, Admin B notices the error and unprotects it. Admin C quickly jumps on him, and reprotects it. You're not going to argue that B is at fault, while C is simply restoring order in the force, are you...
I'm only arguing that Admin B is, in fact, reverting an administrative action.
So, clearly a definition of "reverting any administrative action counts as wheel-warring" doesn't work.
On 4/23/06, Alphax (Wikipedia email) alphasigmax@gmail.com wrote:
So, clearly a definition of "reverting any administrative action counts as wheel-warring" doesn't work.
It's because it focuses on the "what" - it needs to look at the "why".
Take the example above of A blocking and B unblocking. Why did B unblock? Was it because the block was some sort of mistake (blocking the wrong range, or blocking an AOL proxy for too long, etc) or was it because B disagreed with A's interpretation of the user's edits? If there was such a disagreement, then why did B not discuss the block with A? It's that part which most people find problematic, the attack on someone's judgement, not the actual action of unblocking.
-- Stephen Bain stephen.bain@gmail.com
Ugh, when do we get to the part where I have to figure out whether a car loaded with apples going north can beat a train loaded with figs going in the same direction?
The basic problem is one of ego. For a place that prides itself on collegiality among editors, and particularly among administrators, we simply step on one another's toes too often. I don't see why we need to have all this parsing and ABC'ing when what we really need is to tug on a few ears and remind each other that it's rarely polite to undermine someone without so much as a word.
k
On 4/23/06, Stephen Bain stephen.bain@gmail.com wrote:
On 4/23/06, Alphax (Wikipedia email) alphasigmax@gmail.com wrote:
So, clearly a definition of "reverting any administrative action counts as wheel-warring" doesn't work.
It's because it focuses on the "what" - it needs to look at the "why".
Take the example above of A blocking and B unblocking. Why did B unblock? Was it because the block was some sort of mistake (blocking the wrong range, or blocking an AOL proxy for too long, etc) or was it because B disagreed with A's interpretation of the user's edits? If there was such a disagreement, then why did B not discuss the block with A? It's that part which most people find problematic, the attack on someone's judgement, not the actual action of unblocking.
-- Stephen Bain stephen.bain@gmail.com _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
Katefan0 wrote:
Ugh, when do we get to the part where I have to figure out whether a car loaded with apples going north can beat a train loaded with figs going in the same direction?
Elementary! Since apples have smoother skins than figs there will be less friction and that train will go faster. :-) The problem where there are pears instead of figs is more difficult because the skins are similar. We would need to study the relative aerodynamics of the two forms.
The basic problem is one of ego. For a place that prides itself on collegiality among editors, and particularly among administrators, we simply step on one another's toes too often. I don't see why we need to have all this parsing and ABC'ing when what we really need is to tug on a few ears and remind each other that it's rarely polite to undermine someone without so much as a word.
Sure. If the original administrator to take action feels undermined by a single reversal it is a matter of putting his ego ahead of the good of the community. The reverter should explain what he is doing, but at this stage an explanatory note with the revert will suffice.
Ec
In terms of egregious violations, sure, it's fine to act swiftly and doesn't necessarily require consultation. But people do this even with garden variety actions, which just isn't necessary.
I always make it a point to express my reservations and give the original administrator the courtesy of reversing his or her decision as a result, rather than me doing it for them. Obviously everybody thinks they're doing the right thing, but in this instance I think more administrators would do well to adopt this model. Having an article protected an extra 5 hours while the protecting administrator, for instance, evaluates your objections, isn't going to bring Wikipedia crashing down. It is, however, a much better way to treat our peers.
k
On 4/23/06, Ray Saintonge saintonge@telus.net wrote:
Katefan0 wrote:
Ugh, when do we get to the part where I have to figure out whether a car loaded with apples going north can beat a train loaded with figs going in the same direction?
Elementary! Since apples have smoother skins than figs there will be less friction and that train will go faster. :-) The problem where there are pears instead of figs is more difficult because the skins are similar. We would need to study the relative aerodynamics of the two forms.
The basic problem is one of ego. For a place that prides itself on collegiality among editors, and particularly among administrators, we
simply
step on one another's toes too often. I don't see why we need to have all this parsing and ABC'ing when what we really need is to tug on a few ears and remind each other that it's rarely polite to undermine someone
without
so much as a word.
Sure. If the original administrator to take action feels undermined by a single reversal it is a matter of putting his ego ahead of the good of the community. The reverter should explain what he is doing, but at this stage an explanatory note with the revert will suffice.
Ec
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On 4/23/06, Katefan0 katefan0wiki@gmail.com wrote:
The basic problem is one of ego. For a place that prides itself on collegiality among editors, and particularly among administrators, we simply step on one another's toes too often. I don't see why we need to have all this parsing and ABC'ing when what we really need is to tug on a few ears and remind each other that it's rarely polite to undermine someone without so much as a word.
Exactly right. We need to introduce a culture of respect for each other's admin actions, and when we disagree with something, try to argue and persuade, instead of rushing in to undo. That has to be accompanied by voting for users who will make responsible, committed, and active admins so that our trust and respect isn't misplaced.
Sarah
On 23/04/06, Stephen Bain stephen.bain@gmail.com wrote:
Take the example above of A blocking and B unblocking. Why did B unblock? Was it because the block was some sort of mistake (blocking the wrong range, or blocking an AOL proxy for too long, etc) or was it because B disagreed with A's interpretation of the user's edits? If there was such a disagreement, then why did B not discuss the block with A? It's that part which most people find problematic, the attack on someone's judgement, not the actual action of unblocking.
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
Steve
* Steve Bennett wrote:
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
I almost agree, but in some cases that person might still be operating under mistaken assumptions. Say they found some evidence which suggested that a particular user was a sockpuppet of a blocked user and placed a block on the 'sockpuppet' as a result. However, the second admin then uncovered proof that the person wasn't a sockpuppet and unblocked. The first admin might well accuse the second of 'wheel warring' and reblock, but only because of a failure of communication. The second admin wasn't 'opposing the judgement' of the first, they were just working off a different set of facts. The second admin shouldn't have to discuss the matter before taking an action they know to be correct... though it would be a good idea to send the first admin a note to fill them in on the details.
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- Steve Bennett wrote:
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
I almost agree, but in some cases that person might still be operating under mistaken assumptions. Say they found some evidence which suggested that a particular user was a sockpuppet of a blocked user and placed a block on the 'sockpuppet' as a result. However, the second admin then uncovered proof that the person wasn't a sockpuppet and unblocked. The first admin might well accuse the second of 'wheel warring' and reblock, but only because of a failure of communication. The second admin wasn't 'opposing the judgement' of the first, they were just working off a different set of facts. The second admin shouldn't have to discuss the matter before taking an action they know to be correct... though it would be a good idea to send the first admin a note to fill them in on the details.
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
Jay.
On 4/23/06, jayjg jayjg99@gmail.com wrote:
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- Steve Bennett wrote:
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
I almost agree, but in some cases that person might still be operating under mistaken assumptions. Say they found some evidence which suggested that a particular user was a sockpuppet of a blocked user and placed a block on the 'sockpuppet' as a result. However, the second admin then uncovered proof that the person wasn't a sockpuppet and unblocked. The first admin might well accuse the second of 'wheel warring' and reblock, but only because of a failure of communication. The second admin wasn't 'opposing the judgement' of the first, they were just working off a different set of facts. The second admin shouldn't have to discuss the matter before taking an action they know to be correct... though it would be a good idea to send the first admin a note to fill them in on the details.
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
Jay.
In the mean time an inocent user may stay blocked. Not good. Remeber the first admin was also sure enough that they knew best in order to block. -- geni
On 4/23/06, geni geniice@gmail.com wrote:
On 4/23/06, jayjg jayjg99@gmail.com wrote:
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- Steve Bennett wrote:
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
I almost agree, but in some cases that person might still be operating under mistaken assumptions. Say they found some evidence which suggested that a particular user was a sockpuppet of a blocked user and placed a block on the 'sockpuppet' as a result. However, the second admin then uncovered proof that the person wasn't a sockpuppet and unblocked. The first admin might well accuse the second of 'wheel warring' and reblock, but only because of a failure of communication. The second admin wasn't 'opposing the judgement' of the first, they were just working off a different set of facts. The second admin shouldn't have to discuss the matter before taking an action they know to be correct... though it would be a good idea to send the first admin a note to fill them in on the details.
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
Jay.
In the mean time an inocent user may stay blocked. Not good. Remeber the first admin was also sure enough that they knew best in order to block.
A brief block is not the end of the world. If it drags on for a lengthy period then it's something else. And yes, the first admin executed their best judgement when making the block; that's what admins are supposed to do. If a second admin disagrees with that judgement, then they need to take it up with the first admin, rather than initiate a wheel war with them.
Jay.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jayjg stated for the record:
A brief block is not the end of the world. If it drags on for a lengthy period then it's something else. And yes, the first admin executed their best judgement when making the block; that's what admins are supposed to do. If a second admin disagrees with that judgement, then they need to take it up with the first admin, rather than initiate a wheel war with them.
Jay.
Danny's judgement was that Eloquence should be desysopped and blocked for life. His /best/ judgement.
- -- Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil.
On 4/23/06, jayjg jayjg99@gmail.com wrote:
A brief block is not the end of the world. If it drags on for a lengthy period then it's something else. And yes, the first admin executed their best judgement when making the block; that's what admins are supposed to do. If a second admin disagrees with that judgement, then they need to take it up with the first admin, rather than initiate a wheel war with them.
Jay.
Pulling a block is not initiateing a wheel war. If I initiated a wheel war every time someone pulled one of my blocks we wouldn't be haveing this conversation now.
Allowing the revsal of admin actions is just a logical extension of [[WP:OWN]]. Most revsals of admin actions don't result in any problems thus it requires less rescources to do whatever and then deal with any screaming afterwards.~~~~
-- geni
On 4/23/06, geni geniice@gmail.com wrote:
On 4/23/06, jayjg jayjg99@gmail.com wrote:
A brief block is not the end of the world. If it drags on for a lengthy period then it's something else. And yes, the first admin executed their best judgement when making the block; that's what admins are supposed to do. If a second admin disagrees with that judgement, then they need to take it up with the first admin, rather than initiate a wheel war with them.
Jay.
Pulling a block is not initiateing a wheel war.
Actually, it is, by definition.
If I initiated a wheel war every time someone pulled one of my blocks we wouldn't be haveing this conversation now.
If someone pulled one of your blocks, then the wheel war has already started. How you respond, of course, is up to you.
Allowing the revsal of admin actions is just a logical extension of [[WP:OWN]].
WP:OWN is about articles, not actions. This is not a "logical extension". A more logical extension would have to do with not reverting.
Most revsals of admin actions don't result in any problems thus it requires less rescources to do whatever and then deal with any screaming afterwards.
Yes, and reverting someone using the admin revert button also requires less resources, and you can deal with any screaming afterwards.
Jay.
* jayjg wrote:
On 4/23/06, geni geniice@gmail.com wrote:
Pulling a block is not initiateing a wheel war.
Actually, it is, by definition.
"By definition" a wheel war is something which happens on TENEX or UNIX and has nothing to do with 'single revert' or 'double revert'.
Usage of the term has obviously been expanded, but no... you can't reasonably say, 'my definition of what is a wheel war is better than your definition'. Neither is written in stone, or even on paper, anywhere.
Better to say, 'pulling a block is not always a bad thing'.
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- jayjg wrote:
On 4/23/06, geni geniice@gmail.com wrote:
Pulling a block is not initiateing a wheel war.
Actually, it is, by definition.
"By definition" a wheel war is something which happens on TENEX or UNIX and has nothing to do with 'single revert' or 'double revert'.
The original definition had to do with undoing an admin action.
* jayjg wrote:
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- jayjg wrote:
On 4/23/06, geni geniice@gmail.com wrote:
Pulling a block is not initiateing a wheel war.
Actually, it is, by definition.
"By definition" a wheel war is something which happens on TENEX or UNIX and has nothing to do with 'single revert' or 'double revert'.
The original definition had to do with undoing an admin action.
Actually, the 'original definition' as I remember it was an attempt to lock out other admins entirely rather than simply undoing some action of there's. Sort of an electronic 'king of the mountain'. But then I wasn't involved in the TENEX days and I left USL when they were bought out.
On 4/24/06, jayjg jayjg99@gmail.com wrote:
On 4/23/06, geni geniice@gmail.com wrote:
On 4/23/06, jayjg jayjg99@gmail.com wrote:
A brief block is not the end of the world. If it drags on for a lengthy period then it's something else. And yes, the first admin executed their best judgement when making the block; that's what admins are supposed to do. If a second admin disagrees with that judgement, then they need to take it up with the first admin, rather than initiate a wheel war with them.
Jay.
Pulling a block is not initiateing a wheel war.
Actually, it is, by definition.
No. I have done something to try and fix something. They have decided to take responcibilty for the problem and try an different fix
If I initiated a wheel war every time someone pulled one of my blocks we wouldn't be haveing this conversation now.
If someone pulled one of your blocks, then the wheel war has already started. How you respond, of course, is up to you.
No. The first "wheel war" to recive wide attention would be the one involeing trying to inforce a 3RR block on an admin. There is a world of difference between that and someone pulling a 3RR block because someone contacted them by email. In any case you have just accused some fairly widely respect members of the old school admins of "wheel waring".
Allowing the revsal of admin actions is just a logical extension of [[WP:OWN]].
WP:OWN is about articles, not actions. This is not a "logical extension". A more logical extension would have to do with not reverting.
No. You do not own articles. You do not own blocks . You do not own page protections. You do not own deletions. You do not own your f****** Mediawiki namespace edits. You're a wikipedia admin. Your ego can go hang and it is about time you started wearing toecaps.
Most revsals of admin actions don't result in any problems thus it requires less rescources to do whatever and then deal with any screaming afterwards.
Yes, and reverting someone using the admin revert button also requires less resources, and you can deal with any screaming afterwards.
Jay.
Rollback does not give you a comment box. Unprotection and unblock does. -- geni
On 4/23/06, geni geniice@gmail.com wrote:
No. You do not own articles. You do not own blocks . You do not own page protections. You do not own deletions. You do not own your f****** Mediawiki namespace edits. You're a wikipedia admin. Your ego can go hang and it is about time you started wearing toecaps.
I don't know who this was directed at, but it's exactly the attitude that's causing a problem. Respecting someone else's judgment is not the same as them "owning" the block or protection or edit.
Sarah
On 4/24/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
I don't know who this was directed at, but it's exactly the attitude that's causing a problem.
Really? Most historical problems with "wheel wars" have been due to the problem that it is tricky to block an admin who doesn't want to be blocked.
Respecting someone else's judgment is not the same as them "owning"
the block or >protection or edit.
Sarah
Functionaly the difference is?
-- geni
On 4/23/06, geni geniice@gmail.com wrote:
On 4/24/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
I don't know who this was directed at, but it's exactly the attitude that's causing a problem.
Really? Most historical problems with "wheel wars" have been due to the problem that it is tricky to block an admin who doesn't want to be blocked.
I don't know what that means. The wheel war problem is caused by people taking it upon themselves to undo other people's admin actions, simply because they disagree with them. As Kate said, it often boils down to an ego problem, the presumption of knowing better.
Respecting someone else's judgment is not the same as them "owning"
the block or >protection or edit.
Functionaly the difference is?
You can strongly disagree with an admin action, but at the same time realize that perhaps the original admin knows more about the situation than you do; or perhaps knows just as much but has better judgment in this case; or perhaps neither of these, and you'll just have to agree to differ. Just as we can't always have our own way when editing, we also can't always have our own way when adminning.
Sarah
On 4/24/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
On 4/23/06, geni geniice@gmail.com wrote:
On 4/24/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
I don't know who this was directed at, but it's exactly the attitude that's causing a problem.
Really? Most historical problems with "wheel wars" have been due to the problem that it is tricky to block an admin who doesn't want to be blocked.
I don't know what that means.
http://en.wikipedia.org/w/index.php?title=Special:Log&type=block&use...
That is a real wheel war.
The wheel war problem is caused by people taking it upon themselves
to undo other >people's admin actions, simply because they disagree with them.
I can't offhand think of any other reason to undo them. However that doesn't cause wheel wars. The wheel war only gets going when the person who has had their admin action undone tries to get it redone by brute force.
As Kate said, it often boils down to an ego problem, the presumption of knowing better.
Of course. And yet you object to my point where I show what rejecting all that ego stuff means.
You can strongly disagree with an admin action, but at the same time realize that perhaps the original admin knows more about the situation than you do; or perhaps knows just as much but has better judgment in this case; or perhaps neither of these, and you'll just have to agree to differ.
Either the action is pulled or it is not. Agreeing to differ makes no sense in this context.
Just as we can't always have our own way when editing, we also can't always have our own way when adminning.
And yet you blame the person who is preventing someone from haveing their own way.
-- geni
On 4/23/06, geni geniice@gmail.com wrote:
No if danny hadn't taken his action in the first place all this could be avoided.
That's true of all admin actions. You're implying that the best way to stop wheel wars is to have no admins.
Sarah
On Apr 23, 2006, at 11:25 AM, geni wrote:
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
In the mean time an inocent user may stay blocked. Not good. Remeber the first admin was also sure enough that they knew best in order to block.
This discussion shouldn't take longer than 24 hours at absolute maximum, and oftentimes it'll take less than 1 hour. An innocent user can stay blocked for that period of time.
jayjg wrote:
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- Steve Bennett wrote:
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
I almost agree, but in some cases that person might still be operating under mistaken assumptions. Say they found some evidence which suggested that a particular user was a sockpuppet of a blocked user and placed a block on the 'sockpuppet' as a result. However, the second admin then uncovered proof that the person wasn't a sockpuppet and unblocked. The first admin might well accuse the second of 'wheel warring' and reblock, but only because of a failure of communication. The second admin wasn't 'opposing the judgement' of the first, they were just working off a different set of facts. The second admin shouldn't have to discuss the matter before taking an action they know to be correct... though it would be a good idea to send the first admin a note to fill them in on the details.
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
Maybe the second admin has evidence that the first admin is unaware of. Maybe the first admin was just acting in the heat of RC battle. It folows that it is perfectly valid to act under a good faith supposition.
It would not be appropriate to say that all these reversions are done in bad faith That would in itself be assuming bad faith.
Ec
On 4/23/06, Ray Saintonge saintonge@telus.net wrote:
jayjg wrote:
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- Steve Bennett wrote:
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
I almost agree, but in some cases that person might still be operating under mistaken assumptions. Say they found some evidence which suggested that a particular user was a sockpuppet of a blocked user and placed a block on the 'sockpuppet' as a result. However, the second admin then uncovered proof that the person wasn't a sockpuppet and unblocked. The first admin might well accuse the second of 'wheel warring' and reblock, but only because of a failure of communication. The second admin wasn't 'opposing the judgement' of the first, they were just working off a different set of facts. The second admin shouldn't have to discuss the matter before taking an action they know to be correct... though it would be a good idea to send the first admin a note to fill them in on the details.
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
Maybe the second admin has evidence that the first admin is unaware of. Maybe the first admin was just acting in the heat of RC battle. It folows that it is perfectly valid to act under a good faith supposition.
It would not be appropriate to say that all these reversions are done in bad faith That would in itself be assuming bad faith.
One can posit all sorts of "maybes", but the fact remains that reverting the first admin assumes the first admin is incorrect. Instead of assuming, contact them first, and find out for sure. It's quite simple, and it astonishes me that anyone would defend summarily reverting an admin action over communicating with them first and building a consensus. This is not an emergency, and almost never is.
Jay.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jayjg stated for the record:
One can posit all sorts of "maybes", but the fact remains that reverting the first admin assumes the first admin is incorrect. Instead of assuming, contact them first, and find out for sure. It's quite simple, and it astonishes me that anyone would defend summarily reverting an admin action over communicating with them first and building a consensus. This is not an emergency, and almost never is.
Jay.
And when the first admin explicitly refuses to communicate?
- -- Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil.
On 4/23/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jayjg stated for the record:
One can posit all sorts of "maybes", but the fact remains that reverting the first admin assumes the first admin is incorrect. Instead of assuming, contact them first, and find out for sure. It's quite simple, and it astonishes me that anyone would defend summarily reverting an admin action over communicating with them first and building a consensus. This is not an emergency, and almost never is.
Jay.
And when the first admin explicitly refuses to communicate?
That, in fact, is an unusual case. Communicate with them, and if they don't respond after a *reasonable* length of time, then drop them a note stating what you are doing and why. What is reasonable? In a case of blocking, I would say at least a half day if you don't see them editing, less time if you do see them editing.
Jay.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jayjg stated for the record:
And when the first admin explicitly refuses to communicate?
That, in fact, is an unusual case. Communicate with them, and if they don't respond after a *reasonable* length of time, then drop them a note stating what you are doing and why. What is reasonable? In a case of blocking, I would say at least a half day if you don't see them editing, less time if you do see them editing.
Jay.
By telephone. Danny /explicitly/ refused to discuss his multi-project indefinite block of a Wikipedian who's been around since 2001.
- -- Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil.
I hate to personalize this as I think Erik's gone through enough, but really I can't let this go by.
This phone call could've been avoided if he had simply made an attempt to communicate -- in any fashion -- before he reversed Danny.
k
On 4/23/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jayjg stated for the record:
And when the first admin explicitly refuses to communicate?
That, in fact, is an unusual case. Communicate with them, and if they don't respond after a *reasonable* length of time, then drop them a note stating what you are doing and why. What is reasonable? In a case of blocking, I would say at least a half day if you don't see them editing, less time if you do see them editing.
Jay.
By telephone. Danny /explicitly/ refused to discuss his multi-project indefinite block of a Wikipedian who's been around since 2001.
Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFES+KcMAt1wyd9d+URAvfCAJ9cRq7jLqX40+X0zTeIfhn1ew4p1wCeKTQ1 t5bFXKIieIh1QwwfhvSmhsE= =PkHs -----END PGP SIGNATURE----- _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Katefan0 stated for the record:
I hate to personalize this as I think Erik's gone through enough, but really I can't let this go by.
This phone call could've been avoided if he had simply made an attempt to communicate -- in any fashion -- before he reversed Danny.
Nice try. If you were paying attention, you would recall that the refusal came /before/ I attempted to correct the error. Eloquence called Danny to ask why he was blocked, and Danny refused to explain.
- -- Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil.
I wasn't talking about anything you did -- perhaps it was you not paying attention? I'm talking about the *very first* point at which someone could have reached out and did not. This whole thing got botched up when Erik reversed Danny's action without a word to him. If he'd tried to contact Danny *before* he decided to reverse his action, all this could've been avoided.
I'm not saying I agree with everything that happened later. But that indeed was the first place this all broke down, and is at the root of the lack of respect and courtesy I've been pressing since this started. (Speaking in general terms -- again, I'd really prefer not to be personalizing this and don't doubt Erik's dedication.)
k
On 4/23/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Katefan0 stated for the record:
I hate to personalize this as I think Erik's gone through enough, but
really
I can't let this go by.
This phone call could've been avoided if he had simply made an attempt
to
communicate -- in any fashion -- before he reversed Danny.
Nice try. If you were paying attention, you would recall that the refusal came /before/ I attempted to correct the error. Eloquence called Danny to ask why he was blocked, and Danny refused to explain.
Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFES/F/MAt1wyd9d+URAhOfAJ90im9FWITn5C6CXQ0Q/r2fEG/93ACfT/F+ yYztSW4PaHn2jRLrpaY6y6Q= =MCiD -----END PGP SIGNATURE----- _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
No, it's okay. Nothing personal. If we all didn't care so much about Wikipeida, this topic wouldn't engender such strong feelings.
k
On 4/23/06, Katefan0 katefan0wiki@gmail.com wrote:
I wasn't talking about anything you did -- perhaps it was you not paying attention? I'm talking about the *very first* point at which someone could have reached out and did not. This whole thing got botched up when Erik reversed Danny's action without a word to him. If he'd tried to contact Danny *before* he decided to reverse his action, all this could've been avoided.
I'm not saying I agree with everything that happened later. But that indeed was the first place this all broke down, and is at the root of the lack of respect and courtesy I've been pressing since this started. (Speaking in general terms -- again, I'd really prefer not to be personalizing this and don't doubt Erik's dedication.)
k
On 4/23/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Katefan0 stated for the record:
I hate to personalize this as I think Erik's gone through enough, but
really
I can't let this go by.
This phone call could've been avoided if he had simply made an attempt
to
communicate -- in any fashion -- before he reversed Danny.
Nice try. If you were paying attention, you would recall that the refusal came /before/ I attempted to correct the error. Eloquence called Danny to ask why he was blocked, and Danny refused to explain.
Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFES/F/MAt1wyd9d+URAhOfAJ90im9FWITn5C6CXQ0Q/r2fEG/93ACfT/F+ yYztSW4PaHn2jRLrpaY6y6Q= =MCiD -----END PGP SIGNATURE----- _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On 4/23/06, Katefan0 katefan0wiki@gmail.com wrote:
I wasn't talking about anything you did -- perhaps it was you not paying attention? I'm talking about the *very first* point at which someone could have reached out and did not. This whole thing got botched up when Erik reversed Danny's action without a word to him. If he'd tried to contact Danny *before* he decided to reverse his action, all this could've been avoided.
No if danny hadn't taken his action in the first place all this could be avoided.
-- geni
On 4/23/06, geni geniice@gmail.com wrote:
No if danny hadn't taken his action in the first place all this could be avoided.
That's true of all admin actions. You're implying that the best way to stop wheel wars is to have no admins.
Sarah
On 4/24/06, slimvirgin@gmail.com slimvirgin@gmail.com wrote:
On 4/23/06, geni geniice@gmail.com wrote:
No if danny hadn't taken his action in the first place all this could be avoided.
That's true of all admin actions. You're implying that the best way to stop wheel wars is to have no admins.
Sarah
Well it would be one logical aproach.
There is no more reason to as a default attribute blame to person who undid the action than there is to attribute it to the person who did it.
In reality it is quite posible to have no fault "wheel "wars"". -- geni
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Katefan0 stated for the record:
I hate to personalize this as I think Erik's gone through enough, but really I can't let this go by.
This phone call could've been avoided if he had simply made an attempt to communicate -- in any fashion -- before he reversed Danny.
k
I apologize for my previous reply.
After rereading your message, I realize I misunderstood you -- I was confused about which "he" you meant.
- -- Sean Barrett | Knowledge is power. Power sean@epoptic.org | corrupts. Study hard, be evil.
* jayjg wrote:
One can posit all sorts of "maybes", but the fact remains that reverting the first admin assumes the first admin is incorrect. Instead of assuming, contact them first, and find out for sure. It's quite simple, and it astonishes me that anyone would defend summarily reverting an admin action over communicating with them first and building a consensus. This is not an emergency, and almost never is.
I find your position equally illogical. Tracking down the admin who originally protected a page to get their 'buy in' on unprotecting it after the issue has been resolved would be a pointless waste of time. MAYBE one time in a hundred they are going to have some non-apparent reason for wanting the page to remain protected, but usually not.
Admins contravene the actions of others every day without anyone saying a word about it. When situations change or new facts are uncovered admins SHOULD take the initiative to do what makes sense in the current circumstances. Putting that on hold to get the original admin's near certain agreement would be a pointless drag on getting things done. Ergo, this 'never ever undo the action of another admin without discussing it' seems to me untenable.
The only time you should need to 'discuss first' is if you think the other admin might disagree with your decision. People who's judgement of what another admin might object to is consistently off aren't likely to become admins in the first place or to remain that way. Wheel warring is almost never due to such mistaken assumptions as to what is ok, but rather due to deliberate actions which the person KNOWS the other admin will object to... often while 'discussion' is going on.
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- jayjg wrote:
One can posit all sorts of "maybes", but the fact remains that reverting the first admin assumes the first admin is incorrect. Instead of assuming, contact them first, and find out for sure. It's quite simple, and it astonishes me that anyone would defend summarily reverting an admin action over communicating with them first and building a consensus. This is not an emergency, and almost never is.
I find your position equally illogical. Tracking down the admin who originally protected a page to get their 'buy in' on unprotecting it after the issue has been resolved would be a pointless waste of time. MAYBE one time in a hundred they are going to have some non-apparent reason for wanting the page to remain protected, but usually not.
You keep forgetting the element of time here. The key is that it need not be done immediately; unprotecting a page after 20 minutes is wheel warring. Unprotecting a page after 20 days is probably fine.
Admins contravene the actions of others every day without anyone saying a word about it.
Sometimes for good, often for bad.
When situations change or new facts are uncovered admins SHOULD take the initiative to do what makes sense in the current circumstances. Putting that on hold to get the original admin's near certain agreement would be a pointless drag on getting things done. Ergo, this 'never ever undo the action of another admin without discussing it' seems to me untenable.
Sort of like reverting. Oh wait, but we should always discuss reversions, shouldn't we?
The only time you should need to 'discuss first' is if you think the other admin might disagree with your decision. People who's judgement of what another admin might object to is consistently off aren't likely to become admins in the first place or to remain that way. Wheel warring is almost never due to such mistaken assumptions as to what is ok, but rather due to deliberate actions which the person KNOWS the other admin will object to... often while 'discussion' is going on.
You can bet that if an admin has blocked someone, he'll object to the block being lifted a few minutes later, unless he has it explained first. I've never seen a case where that wasn't true.
Jay.
On 4/24/06, jayjg jayjg99@gmail.com wrote:
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- jayjg wrote:
One can posit all sorts of "maybes", but the fact remains that reverting the first admin assumes the first admin is incorrect. Instead of assuming, contact them first, and find out for sure. It's quite simple, and it astonishes me that anyone would defend summarily reverting an admin action over communicating with them first and building a consensus. This is not an emergency, and almost never is.
I find your position equally illogical. Tracking down the admin who originally protected a page to get their 'buy in' on unprotecting it after the issue has been resolved would be a pointless waste of time. MAYBE one time in a hundred they are going to have some non-apparent reason for wanting the page to remain protected, but usually not.
You keep forgetting the element of time here. The key is that it need not be done immediately; unprotecting a page after 20 minutes is wheel warring. Unprotecting a page after 20 days is probably fine.
Probably?
Sometimes for good, often for bad.
Evidences?
Sort of like reverting. Oh wait, but we should always discuss reversions, shouldn't we?
Not always beyond the edit summery.
You can bet that if an admin has blocked someone, he'll object to the block being lifted a few minutes later, unless he has it explained first. I've never seen a case where that wasn't true.
Me. Three revert rule way back when I was dealing with most of the blocks resulting from it. Why should I care if anonther admin wishes to take responsibilty for a users behaviour?
-- geni
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jayjg stated for the record:
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
Jay.
The statement "if the second admin has conclusive evidence, then the first admin will undoubtedly unblock" has been recently demonstrated to be untrue -- the conclusive evidence that Eloquence is not a danger to the project is patent, yet Danny (first admin) reverted my (second admin's) unblocking.
- -- Sean Barrett | Power corrupts. Atomic power corrupts atomically. sean@epoptic.org |
On 4/23/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jayjg stated for the record:
No, what the second admin should do is discuss the case with the first admin, rather than unblocking. Maybe the first admin has evidence that the second admin is unaware of. If the second admin has conclusive evidence, then the first admin will undoubtedly unblock. If not, then there is a dispute, and the second admin should not wheel war. In any event, admins should not act under the bad faith supposition that *they know better*; that is what starts the wheel war.
Jay.
The statement "if the second admin has conclusive evidence, then the first admin will undoubtedly unblock" has been recently demonstrated to be untrue -- the conclusive evidence that Eloquence is not a danger to the project is patent, yet Danny (first admin) reverted my (second admin's) unblocking.
Did you communicate first? The first reversion is wrong, regardless of who does it, unless they've communicated.
Jay.
* jayjg wrote:
Did you communicate first? The first reversion is wrong, regardless of who does it, unless they've communicated.
I disagree. Entirely.
Example 1: Admin A protects a 'high use' template to prevent possible vandalism. Months pass and the template is deprecated and is now barely used. Admin B unprotects the template without 'discussion'. Admin B has done nothing wrong whatsoever.
Example 2: Admin A is in discussion with other admins and states that they are going to take a course of action. The other admins all strongly object and state their reasons. Admin A goes ahead with their plan anyway. No reversion has taken place but in my view Admin A is clearly 'wrong' and any Admin B would be justified in reversing it based on the existing consensus.
The 'first reverter' is NOT always the problem and 'discussion' does not cure all ills. I don't think I've ever seen a serious wheel war where discussion WASN'T going on.
On 4/23/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
- jayjg wrote:
Did you communicate first? The first reversion is wrong, regardless of who does it, unless they've communicated.
I disagree. Entirely.
Example 1: Admin A protects a 'high use' template to prevent possible vandalism. Months pass and the template is deprecated and is now barely used. Admin B unprotects the template without 'discussion'. Admin B has done nothing wrong whatsoever.
"Months pass". That's the key, of course. We're not talking about actions taken months later.
Example 2: Admin A is in discussion with other admins and states that they are going to take a course of action. The other admins all strongly object and state their reasons. Admin A goes ahead with their plan anyway. No reversion has taken place but in my view Admin A is clearly 'wrong' and any Admin B would be justified in reversing it based on the existing consensus.
Ah, but then we're already in discussion, aren't we? And if "other admins" object, then there is a clear consensus against the action.
We need to deal with the real issues here, not strawman scenarios.
Jay.
On Apr 23, 2006, at 9:35 AM, Conrad Dunkerson wrote:
I almost agree, but in some cases that person might still be operating under mistaken assumptions. Say they found some evidence which suggested that a particular user was a sockpuppet of a blocked user and placed a block on the 'sockpuppet' as a result. However, the second admin then uncovered proof that the person wasn't a sockpuppet and unblocked. The first admin might well accuse the second of 'wheel warring' and reblock, but only because of a failure of communication. The second admin wasn't 'opposing the judgement' of the first, they were just working off a different set of facts. The second admin shouldn't have to discuss the matter before taking an action they know to be correct... though it would be a good idea to send the first admin a note to fill them in on the details.
I tend to think that even in this case, Wikipedia is unique in that it's better to ask permission than forgiveness.
Steve Bennett wrote:
On 23/04/06, Stephen Bain stephen.bain@gmail.com wrote:
Take the example above of A blocking and B unblocking. Why did B unblock? Was it because the block was some sort of mistake (blocking the wrong range, or blocking an AOL proxy for too long, etc) or was it because B disagreed with A's interpretation of the user's edits? If there was such a disagreement, then why did B not discuss the block with A? It's that part which most people find problematic, the attack on someone's judgement, not the actual action of unblocking.
Funnily enough, my definition works here as well. Someone whose judgment is being questioned will accuse their reverter of wheel warring. Someone who made a mistake won't.
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
So someone whose poor judgement has been questioned is perfectly justified to impute bad faith! Seems that you're arguing that his two wrongs would make things right.
Ec
On Apr 23, 2006, at 12:33 AM, Steve Bennett wrote:
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
And the only way of knowing that for sure before you revert is to contact the other admin before you do anything.
In both cases, there's the admin absentee problem. Solution? Silence + external consensus = consent to go-ahead. We're enough of a community that you can seek out another admin for a third opinion if the admin you're reverting isn't around.
On 4/23/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 23, 2006, at 12:33 AM, Steve Bennett wrote:
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
And the only way of knowing that for sure before you revert is to contact the other admin before you do anything.
In both cases, there's the admin absentee problem. Solution? Silence
- external consensus = consent to go-ahead. We're enough of a
community that you can seek out another admin for a third opinion if the admin you're reverting isn't around.
Exactly so; we're not working in a vacuum here. There's WP:AN/I, for example.
Jay.
Philip Welch wrote:
On Apr 23, 2006, at 12:33 AM, Steve Bennett wrote:
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
And the only way of knowing that for sure before you revert is to contact the other admin before you do anything.
In both cases, there's the admin absentee problem. Solution? Silence
- external consensus = consent to go-ahead. We're enough of a
community that you can seek out another admin for a third opinion if the admin you're reverting isn't around.
It should be easy to look through the list of thosoe who voted for you when you became a sysop for one who shares your Point of View, and can help to guarantee the objectivity that you want. ;-)
Ec
On 23/04/06, Philip Welch wikipedia@philwelch.net wrote:
On Apr 23, 2006, at 12:33 AM, Steve Bennett wrote:
In other words: If the person you reverted accuses you of wheel warring, then you wheel warred.
And the only way of knowing that for sure before you revert is to contact the other admin before you do anything.
In both cases, there's the admin absentee problem. Solution? Silence
- external consensus = consent to go-ahead. We're enough of a
community that you can seek out another admin for a third opinion if the admin you're reverting isn't around.
Actually in my definition, admin absenteeism isn't a major problem. If you do something that the admin would have approved of (like lifting a block at the right time), then you didn't wheel war. If you take advantage of his absence to do something sneaky, then you're wheel warring...
Steve
Stephen Bain wrote:
On 4/23/06, Alphax (Wikipedia email) alphasigmax@gmail.com wrote:
So, clearly a definition of "reverting any administrative action counts as wheel-warring" doesn't work.
It's because it focuses on the "what" - it needs to look at the "why".
Take the example above of A blocking and B unblocking. Why did B unblock? Was it because the block was some sort of mistake (blocking the wrong range, or blocking an AOL proxy for too long, etc) or was it because B disagreed with A's interpretation of the user's edits? If there was such a disagreement, then why did B not discuss the block with A? It's that part which most people find problematic, the attack on someone's judgement, not the actual action of unblocking.
I would expect B to give a brief explanation of why he unblocked. But nuance the issue a bit more: A blocks for 1 week; B reduces the block to 24 hours. Do you consider that to be a revert?
Ec
On 22/04/06, Philip Welch wikipedia@philwelch.net wrote:
I would argue that X has the prerogative to reblock here, since Y wheel-warred (something that should not have happened) and after something that should not have happened, it's generally acceptable to reinstate the status quo ante.
At first glance that seems reasonable, if you accept my definition of a wheel war being reverting an action in a way that the originating admin wouldn't agree with. But really, once that's happened, it would be better for some third/neutral/senior admin to step in.
Steve
Steve Bennett wrote:
On 22/04/06, Philip Welch wikipedia@philwelch.net wrote:
I would argue that X has the prerogative to reblock here, since Y wheel-warred (something that should not have happened) and after something that should not have happened, it's generally acceptable to reinstate the status quo ante.
At first glance that seems reasonable, if you accept my definition of a wheel war being reverting an action in a way that the originating admin wouldn't agree with. But really, once that's happened, it would be better for some third/neutral/senior admin to step in.
Better still for the two parties to start a dialogue. Both have established opening positions; they might still find common ground. If that doesn't work, then bring in the third person.
Ec
I believe Ray's assesment identifies the crux of the problem. Both parties on opposing sides of said debate need to engage in discussion regarding the matter. Hopefully through dispute resolution or the introduction of a third party, the conflict will be satisfied.
Ray Saintonge saintonge@telus.net wrote: Steve Bennett wrote:
On 22/04/06, Philip Welch wrote:
I would argue that X has the prerogative to reblock here, since Y wheel-warred (something that should not have happened) and after something that should not have happened, it's generally acceptable to reinstate the status quo ante.
At first glance that seems reasonable, if you accept my definition of a wheel war being reverting an action in a way that the originating admin wouldn't agree with. But really, once that's happened, it would be better for some third/neutral/senior admin to step in.
Better still for the two parties to start a dialogue. Both have established opening positions; they might still find common ground. If that doesn't work, then bring in the third person.
Ec
_______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
--------------------------------- Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
slimvirgin@gmail.com stated for the record:
Exactly right. Some admins have adopted a definition of "wheel warring" that excludes the first revert of an admin action -- so that if X blocks, and Y unblocks, Y is not wheel warring. But if X restores the block, X has started the wheel war. This is nonsense. The first person to undo the original admin action has started the wheel war, and it's that first undoing that shouldn't be happening as a rule.
Sarah
Under this definition, Eloquence's block truly would be a death sentence, since no one could ever revert Danny's stupid initial indefinite block -- even Jimbo.
Is that the effect you want to have?
- -- Sean Barrett | I've had a perfectly wonderful evening. sean@epoptic.org | But this wasn't it. --Groucho Marx
On 4/20/06, Sean Barrett sean@epoptic.org wrote:
Under this definition, Eloquence's block truly would be a death sentence, since no one could ever revert Danny's stupid initial indefinite block -- even Jimbo.
Don't be silly. All you have to do is have a discussion and reach consensus. A reversal based on consensus is not wheel warring.
Kelly
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Kelly Martin stated for the record:
On 4/20/06, Sean Barrett sean@epoptic.org wrote:
Under this definition, Eloquence's block truly would be a death sentence, since no one could ever revert Danny's stupid initial indefinite block -- even Jimbo.
Don't be silly. All you have to do is have a discussion and reach consensus. A reversal based on consensus is not wheel warring.
Kelly
That's not what you said, and when I consider how extreme some of your other contributions to this discussion have been, I didn't know what to assume.
- -- Sean Barrett | Bad: all life stopping instantaneously, sean@epoptic.org | and every molecule in your body | exploding at the speed of light.
Someone please define wheel-warring, and not simply by example. If "wheel-warring" is when one admin reverts another, the word "wheel" seems irrelevant and the word "war" is blatant hyperbole.
Ben
On 4/20/06, Ben Lowe ben.lowe@gmail.com wrote:
Someone please define wheel-warring, and not simply by example. If "wheel-warring" is when one admin reverts another, the word "wheel" seems irrelevant and the word "war" is blatant hyperbole.
We have an article on it:
http://en.wikipedia.org/wiki/Wheel_war
Which doesn't quite lay out the exact definition of one in Wikipedia terms, but the gist of it is there.
Kirill Lokshin
On 21/04/06, Ben Lowe ben.lowe@gmail.com wrote:
Someone please define wheel-warring, and not simply by example. If "wheel-warring" is when one admin reverts another, the word "wheel" seems irrelevant and the word "war" is blatant hyperbole.
Wheel war: Two or more admins (wheels) repeatedly undermining each other (warring). This discussion has mostly been trying to determine the threshold for the smallest occurrence that could be called a "wheel war". Everyone agrees that 2 admins repeatedly reverting each others' admin actions for days on end is a "wheel war". We're less sure whether the first revert counts.
Note that we're only talking about reverting admin actions - hence the "wheel" is relevant.
Steve
Delirium wrote:
Kelly Martin wrote:
On 4/20/06, Delirium delirium@hackish.org wrote:
But Danny has explicitly said (on this list) that he is also a normal editor, and only his actions that are accompanied with a statement that they are WP:OFFICE actions should be treated as such. So if he does something and does not tag it WP:OFFICE, we should all operate on the presumption that he is doing it in his capacity as a normal Wikipedian.
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard. WP:OFFICE has nothing to do with that; wheel warring is still wheel warring.
He didn't revert Danny's edits or wheel war. Danny stubbed and protected the page; Erik noted that he was willing to give Danny the benefit of the doubt on stubbing, but that the protection was contrary to the protection policy (a correct observation), so unprotected the page but left it stubbed. It is quite acceptable and even encouraged to unprotect pages that have been inappropriately protected.
If the original protection was not clearly explained one cannot really blame Erik for the steps that he took in making a single reversion. Going further than that should have required more discussion than a simple edit summary. Kelly justifies her stand with the words "could easily have been". It is improper to conclude that what could be is what is. Yes, wheel warring is still wheel warring, but what could be a wheel war is not a wheel war; it's speculation. Assume good faith ... even from Erik. ;-)
Ec
Kelly Martin kelly.lynn.martin@gmail.com:
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard.
Yet, equally, that does not excuse the indefinite blocking of a Wikipedian in good-standing. Reverting another admin, while undesireable, should not result in immediate excommunication. I'm sure Danny is a fine fellow who does a great job for us, but I'm afraid to say that his punitive actions here were Not Good. If that's also the general view of the community, then Danny should take that on board.
-- Matt
[[User:Matt Crypto]]
On 4/20/06, Matt R matt_crypto@yahoo.co.uk wrote:
Kelly Martin kelly.lynn.martin@gmail.com:
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard.
Yet, equally, that does not excuse the indefinite blocking of a Wikipedian in good-standing.
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
Kelly
G'day Kelly,
On 4/20/06, Matt R matt_crypto@yahoo.co.uk wrote:
Yet, equally, that does not excuse the indefinite blocking of a Wikipedian in good-standing.
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
A little while back someone on IRC told me that if an admin did something outside policy, they should no longer be considered a Wikipedian in good standing, but rather a vandal, and that an admin should be able to revert them 'til doomsday without feeling any guilt.
I think he was commenting on the rash of userbox deletions in December/January, but I could be wrong.
We shouldn't twist our definitions until good admins become bad Wikipedians ... there's no telling what we might be saying to one another without knowing. A Wikipedia in which my mate on IRC isn't talking crap would be a grim Wikipedia indeed.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Kelly Martin stated for the record:
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
Kelly
Untrue and inflammatory. In a word, trolling.
- -- Sean Barrett | Bad: all life stopping instantaneously, sean@epoptic.org | and every molecule in your body | exploding at the speed of light.
On Apr 20, 2006, at 11:41 PM, Sean Barrett wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Kelly Martin stated for the record:
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
Kelly
Untrue and inflammatory. In a word, trolling.
The courtesy and sense train have really left the station on this one, haven't they?
-Phil
On 4/21/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Matt R matt_crypto@yahoo.co.uk wrote:
Kelly Martin kelly.lynn.martin@gmail.com:
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard.
Yet, equally, that does not excuse the indefinite blocking of a Wikipedian in good-standing.
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
Kelly
Doubtful. Certianly you have no evidence of that claim and if we look at hostoric wheel wars they were rarely planned.
-- geni
Kelly Martin kelly.lynn.martin@gmail.com:
On 4/20/06, Matt R matt_crypto@yahoo.co.uk wrote:
Kelly Martin kelly.lynn.martin@gmail.com:
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard.
Yet, equally, that does not excuse the indefinite blocking of a Wikipedian in good-standing.
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
What you are arguing is untenable. Even if we agree with your interpretation that Erik was starting a wheel-war, an indefinite block was not an appropriate reaction by any reasonable standard (to use your phrase). We kick people off the project in a limited set of circumstances: when it's clear that they are hindering us more than they are helping us. Danny, for all the good work that he no doubt does, did the wrong thing here. For him to acknowledge this in a public forum would be reassuring.
-- Matt [[User:Matt Crypto]]
On 21/04/06, Matt R matt_crypto@yahoo.co.uk wrote:
What you are arguing is untenable. Even if we agree with your interpretation that Erik was starting a wheel-war, an indefinite block was not an appropriate reaction by any reasonable standard (to use your phrase). We kick people off the project in a limited set of circumstances: when it's clear that they are hindering us more than they are helping us. Danny, for all the good work that he no doubt does, did the wrong thing here. For him to acknowledge this in a public forum would be reassuring.
I'm sticking with my interpretation that the "indefinite" bit of the block was most likely not intended to be a life ban, but was simply Danny making a quick decision, and leaving the question of how long to block for later reflection. I could be wrong, but that seems quite reasonable. Sort of like how when a parent sends a kid to his room "Until I say so", they're not really sentencing the kid to death by starvation...
However, it would probably be better, for everyone's sake, to ban for some conventional period like 1 week in future cases.
Steve
Matt R wrote:
Kelly Martin kelly.lynn.martin@gmail.com:
On 4/20/06, Matt R matt_crypto@yahoo.co.uk wrote:
Kelly Martin kelly.lynn.martin@gmail.com:
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard.
Yet, equally, that does not excuse the indefinite blocking of a Wikipedian in good-standing.
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
What you are arguing is untenable. Even if we agree with your interpretation that Erik was starting a wheel-war, an indefinite block was not an appropriate reaction by any reasonable standard (to use your phrase). We kick people off the project in a limited set of circumstances: when it's clear that they are hindering us more than they are helping us. Danny, for all the good work that he no doubt does, did the wrong thing here. For him to acknowledge this in a public forum would be reassuring.
Danny's silence in this series of threads has been very loud. He, more than anyone else, is in a position to quell the flames with one short post.
Ec
On Apr 22, 2006, at 12:17 AM, Ray Saintonge wrote:
Danny's silence in this series of threads has been very loud. He, more than anyone else, is in a position to quell the flames with one short post.
I have trouble implicating anyone for the frankly wise decision to not follow the fecal matter that populates this listserv.
-Phil
On Fri, Apr 21, 2006 at 09:17:13PM -0700, Ray Saintonge wrote:
Matt R wrote:
Kelly Martin kelly.lynn.martin@gmail.com:
On 4/20/06, Matt R matt_crypto@yahoo.co.uk wrote:
Kelly Martin kelly.lynn.martin@gmail.com:
That does not excuse reversion without discussion. Even taking as an assumption that Danny had been acting on his own behalf, Erik's actions could easily have been the start of a wheel war, and were inappropriate by any reasonable standard.
Yet, equally, that does not excuse the indefinite blocking of a Wikipedian in good-standing.
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
What you are arguing is untenable. Even if we agree with your interpretation that Erik was starting a wheel-war, an indefinite block was not an appropriate reaction by any reasonable standard (to use your phrase). We kick people off the project in a limited set of circumstances: when it's clear that they are hindering us more than they are helping us. Danny, for all the good work that he no doubt does, did the wrong thing here. For him to acknowledge this in a public forum would be reassuring.
Danny's silence in this series of threads has been very loud. He, more than anyone else, is in a position to quell the flames with one short post.
Ec
I am not an administrator and have only been around since the last day of October last year. I have been on this list for a few months because I like to understand what is going on in some detail. Naturally I have wondered about whether I should at some point aim to become an administrator. What is going on here makes me think that I would need very strong persuasion indeed to even consider it. Basically one should not have to put up with what Erik has had inflicted on him. Now of course I have no problem with the OFFICE block and I do not disagree one little bit with what Jimbo has said recently, but neither he or Danny have given even a hint about why Erik's block was justified or apologised if it was not. We do not want or need the full story, but we do want a hint. Administrators are volunteers. The mushroom principle should not apply here (keep people in the dark and throw shit over them).
[[Bduke]]
On 22/04/06, Brian Salter-Duke b_duke@octa4.net.au wrote:
I like to understand what is going on in some detail. Naturally I have wondered about whether I should at some point aim to become an administrator. What is going on here makes me think that I would need very strong persuasion indeed to even consider it. Basically one should not have to put up with what Erik has had inflicted on him. Now of course I have no problem with the
There are lots of good reasons not to put your hand up to become an administrator. But to be fair, this was a really exceptional example, and far from "par for the course".
HTH.
Steve
Steve Bennett wrote:
On 22/04/06, Brian Salter-Duke b_duke@octa4.net.au wrote:
I like to understand what is going on in some detail. Naturally I have wondered about whether I should at some point aim to become an administrator. What is going on here makes me think that I would need very strong persuasion indeed to even consider it. Basically one should not have to put up with what Erik has had inflicted on him. Now of course I have no problem with the
There are lots of good reasons not to put your hand up to become an administrator. But to be fair, this was a really exceptional example, and far from "par for the course".
True, but it's a pretty scary example. It seems to me that if it can happen to someone like Eloquence, it can happen to anyone (except _maybe_ Jimbo, I guess). And most of us don't have Eloquence's reputation to back us up.
On 4/22/06, Ilmari Karonen nospam@vyznev.net wrote:
Steve Bennett wrote:
There are lots of good reasons not to put your hand up to become an administrator. But to be fair, this was a really exceptional example, and far from "par for the course".
True, but it's a pretty scary example. It seems to me that if it can happen to someone like Eloquence, it can happen to anyone (except _maybe_ Jimbo, I guess). And most of us don't have Eloquence's reputation to back us up.
-- Ilmari Karonen
It can, of course, happen to anyone, with "it" being a desysopping and block of a user. Presumably if it happened to Jimbo the board would act quickly to correct it (his business partners make up at least 4/5 of the board, with a majority holding lifetime positions, after all). And in the case of Erik, Jimbo stepped in rather quickly to correct it.
Anthony
His status as a reputable long timer counts against him rather then for him in such circumstances. Anyone who has witnessed the wheel wars ought to know better.
Fred
On Apr 20, 2006, at 8:44 PM, Kelly Martin wrote:
Except he wasn't an Wikipedian in good standing; he had attempted to start a wheel war.
Kelly
On 4/21/06, Fred Bauder fredbaud@ctelco.net wrote:
His status as a reputable long timer counts against him rather then for him in such circumstances. Anyone who has witnessed the wheel wars ought to know better.
Fred
I don't necessarily agree with that. He has proven beyond any reasonable doubt that he wants nothing but the best for the project. We can trust him completely, just as we can trust that Jimbo, Danny, Angela, David Gerard, you, etc only want the best for the project. He got banned and desysopped from both wp and meta, an unprecedented crossproject banishment.
If you made a single mistake similar to this (and it was a mistake, but I blame Danny more than Eloquence), would you deserve similar treatment?
It was a removal of a protection. Nothing more. Eloquence deserves an apology.
--Oskar
On 4/20/06, Delirium delirium@hackish.org wrote:
Stephen Bain wrote:
On 4/20/06, Katefan0 katefan0wiki@gmail.com wrote:
Everybody who's an administrator knows -- or ought to know -- that any
of
Danny's actions could be undertaken on behalf of the foundation. To me,
this
suggests -- in fact, demands -- a lot more caution with undoing his
admin
actions than otherwise, and at the very least warrants a discreet
"what's
this about?" before taking action.
I agree, and I think this is really the point to take out of this. We should all operate on the presumption that when Danny does something, he's doing it for a Good Reason, and that one shouldn't undo it unless one has checked the reason behind it with Danny first (that's if it should even be undone at all). A little communication solves alot of problems.
But Danny has explicitly said (on this list) that he is also a normal editor, and only his actions that are accompanied with a statement that they are WP:OFFICE actions should be treated as such. So if he does something and does not tag it WP:OFFICE, we should all operate on the presumption that he is doing it in his capacity as a normal Wikipedian.
Silly, you didn't read the Ultraviolet memo that states that sometimes Danny makes WP:OFFICE actions under double-super-secret background, which are tagged only by the Ultraviolet WP:OFFICE tag. If you do not have Ultraviolet clearance, any reversions or contestations of Ultraviolet Double-Super-Secret Background actions will be grounds for immediate termination. Of course, if you do not have Ultraviolet clearance, you cannot see the Ultraviolet WP:OFFICE tag.
Finally, only those with Ultraviolet clearance are allowed knowledge of the Ultraviolet authorization level. So far as you are concerned Ultraviolet clearance does not exist, the above statements notwithstanding.
--The Management
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Cunctator stated for the record:
Silly, you didn't read the Ultraviolet memo that states that sometimes Danny makes WP:OFFICE actions under double-super-secret background, which are tagged only by the Ultraviolet WP:OFFICE tag. If you do not have Ultraviolet clearance, any reversions or contestations of Ultraviolet Double-Super-Secret Background actions will be grounds for immediate termination. Of course, if you do not have Ultraviolet clearance, you cannot see the Ultraviolet WP:OFFICE tag.
Finally, only those with Ultraviolet clearance are allowed knowledge of the Ultraviolet authorization level. So far as you are concerned Ultraviolet clearance does not exist, the above statements notwithstanding.
--The Management
/me reports for duty as reactor shielding.
- -- Sean Barrett | You'll never find a more wretched hive sean@epoptic.org | of scum and villainy. --Obi-Wan Kenobi
On 4/27/06, Sean Barrett sean@epoptic.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Cunctator stated for the record:
Silly, you didn't read the Ultraviolet memo that states that sometimes
Danny
makes WP:OFFICE actions under double-super-secret background, which are tagged only by the Ultraviolet WP:OFFICE tag. If you do not have
Ultraviolet
clearance, any reversions or contestations of Ultraviolet Double-Super-Secret Background actions will be grounds for immediate termination. Of course, if you do not have Ultraviolet clearance, you
cannot
see the Ultraviolet WP:OFFICE tag.
Finally, only those with Ultraviolet clearance are allowed knowledge of
the
Ultraviolet authorization level. So far as you are concerned Ultraviolet clearance does not exist, the above statements notwithstanding.
--The Management
/me reports for duty as reactor shielding.
That's one reference! For full points, do you note the other two?
The Cunctator wrote:
On 4/27/06, Sean Barrett sean@epoptic.org wrote:
The Cunctator stated for the record:
Silly, you didn't read the Ultraviolet memo that states that sometimes Danny
makes WP:OFFICE actions under double-super-secret background, which are tagged only by the Ultraviolet WP:OFFICE tag. If you do not have Ultraviolet
clearance, any reversions or contestations of Ultraviolet Double-Super-Secret Background actions will be grounds for immediate termination. Of course, if you do not have Ultraviolet clearance, you cannot
see the Ultraviolet WP:OFFICE tag.
Finally, only those with Ultraviolet clearance are allowed knowledge of the
Ultraviolet authorization level. So far as you are concerned Ultraviolet clearance does not exist, the above statements notwithstanding.
--The Management
/me reports for duty as reactor shielding.
That's one reference! For full points, do you note the other two?
Reactor shielding is ineffective against extrasensory perception or Superman's x-ray vision. ;-)
Ec
On 4/19/06, Matt R matt_crypto@yahoo.co.uk wrote:
Katefan0 katefan0wiki@gmail.com:
I think that lately Danny has not been using the OFFICE tag because people tend to raise a fuss over things protected under this specific policy, and more publicity to/furor over an issue that's already very sensitive is a thorny thing to deal with. My guess, anyway.
Forgive me if I haven't understood this correctly, but: OFFICE actions are unreversible on pain of dire consequences (e.g. desysopping and indefinite banning), yet anything that Danny does could be an OFFICE action even though not identified as such? This seems very problematic; is there now a class of editor (Danny) whose actions noone can now dare risk undoing in case the action turns out to be an OFFICE action? Surely not.
-- Matt
Danny has a talk page, he has email, and he has a phone number, all well published. USE THEM.
Kelly
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Kelly Martin stated for the record:
Danny has a talk page, he has email, and he has a phone number, all well published. USE THEM.
Kelly
- From Eloquence's original message: "I have called Danny on the phone, but he said that he was not willing to discuss the issue, and that I should instead talk to the Foundation attorney instead."
"'Shut up,' he explained" should be the punchline of a joke, not standard operating procedure.
- -- Sean Barrett | I've had a perfectly wonderful evening. sean@epoptic.org | But this wasn't it. --Groucho Marx
On Apr 19, 2006, at 1:47 PM, Katefan0 wrote:
I think that lately Danny has not been using the OFFICE tag because people tend to raise a fuss over things protected under this specific policy, and more publicity to/furor over an issue that's already very sensitive is a thorny thing to deal with. My guess, anyway.
Something that needs to be clarified. *Editing an article*, even removing most of it, is something that any editor can do, and certainly something that Danny, if he gets a phone call that requires it, should feel free to do without involving WP:OFFICE. *Protecting an article* is *NOT*. We have a specific set of reasons why an article can be protected, and NPOV issues *are not one of them*. If responding to a phone call requires that an article be protected for NPOV issues - Danny or whoever does it needs to cite a policy, for example, WP:OFFICE.
Protection is listed on a central log for a reason. It's *not* a quiet, insignificant action to take - it should be assumed that protecting a page will generate some amount of publicity/furror - that's the nature of it.
Unless Jimbo or the Board wish to amend the Office Actions policy to state that anytime Danny protects a page it is an OFFICE action, protection without citing the OFFICE policy is simply wrong, "sensitive" situations or not. Fix the policy.
Jesse Weinstein
On 4/19/06, Katefan0 <katefan0wiki@gmail.com > wrote:
I think that lately Danny has not been using the OFFICE tag because people tend to raise a fuss over things protected under this specific policy, and
more publicity to/furor over an issue that's already very sensitive is a thorny thing to deal with. My guess, anyway.
Is this really a surprise? I remember always hearing the best way to make a book popular is to get it banned; why should this be any different on Wikipedia? For people looking for controversy and scandal on the encyclopedia that anyone can edit, the two or three articles that *no one -- NO ONE -- can edit for fear of eternal exile *are way more interesting than the more-than-a-million other articles. I suspect more Wikipedians (and slashdotters) know about [[Brian Peppers]] than [[Jordanhill railway station]]. Is OFFICE necessary? Sure, probably. Wikipedia definitely needs to be responsible, both in terms of its own liability. But if Danny wants to use WP:OFFICE without controversy, he needs it to be normalized, not hidden. People need to simply get used to it. The only way that WP:OFFICE is going to become non-controversial is if it's openly used.
Now of course, I'm reading into this a bit. Perhaps there's some other reason, besides trying to avoid outcry, that Danny didn't mention it was an OFFICE action and removed the OFFICE tag from the page. Regardless, if we're to change the policy to say "Danny edits Wikipedia with Sharpieshttp://en.wikipedia.org/wiki/Sharpie_%2528marker%2529" (which I don't think is a good idea), if [[WP:OFFICE]] should redirect to [[WP:DANNY]], it needs to actually say that somewhere. (And, of course, so everyone is clear about the difference, Danny shouldn't edit the encyclopedia anymore, except as Office Danny.)
Ben
P.S. -- If Jimbo is referred to as "God-King" I can only imagine the nicknames this will create for Danny.
On 19/04/06, Ben Lowe ben.lowe@gmail.com wrote:
Is this really a surprise? I remember always hearing the best way to make a book popular is to get it banned; why should this be any different on Wikipedia? For people looking for controversy and scandal on the encyclopedia that anyone can edit, the two or three articles that *no one -- NO ONE -- can edit for fear of eternal exile *are way more interesting than the more-than-a-million other articles. I suspect more Wikipedians (and slashdotters) know about [[Brian Peppers]] than [[Jordanhill railway station]]. Is OFFICE necessary? Sure, probably. Wikipedia definitely needs to be responsible, both in terms of its own liability. But if Danny wants to use WP:OFFICE without controversy, he needs it to be normalized, not hidden. People need to simply get used to it. The only way that WP:OFFICE is going to become non-controversial is if it's openly used.
Here's another solution. Make it possible for Danny to silently protect a page without it being unprotectable. Communicate a policy to all admins that if an admin discovers that a page has been protected in such a way, that he should keep it to himself, or risk desysopping.
The ordinary user will simply see a protected page. Admins, unless they actually try and unprotect it, will be none the wiser. And if they do try, perhaps a message should alert them to keep it confidential.
But that's just breeding conspiracy theories, I know.
Steve
On 4/19/06, Steve Bennett stevage@gmail.com wrote:
Here's another solution. Make it possible for Danny to silently protect a page without it being unprotectable. Communicate a policy to all admins that if an admin discovers that a page has been protected in such a way, that he should keep it to himself, or risk desysopping.
The ordinary user will simply see a protected page. Admins, unless they actually try and unprotect it, will be none the wiser. And if they do try, perhaps a message should alert them to keep it confidential.
Recent office actions involve more than just protection. They tend to involve a serious cut down of the article as well. As wikitruth has shown tracing admins who are leaking information is tricky.
-- geni
On 4/19/06, geni geniice@gmail.com wrote:
Recent office actions involve more than just protection. They tend to involve a serious cut down of the article as well. As wikitruth has shown tracing admins who are leaking information is tricky.
-- geni
Actually, I've been wondering about this. Do we really know that an admin is behind Wikitruth? I haven't seen anything to prove that they haven't simply scraped Wikipedia at the right time or an outdated mirror later, and simply claimed to be an admin.
~maru
On 4/19/06, maru dubshinki marudubshinki@gmail.com wrote:
On 4/19/06, geni geniice@gmail.com wrote:
Recent office actions involve more than just protection. They tend to involve a serious cut down of the article as well. As wikitruth has shown tracing admins who are leaking information is tricky.
-- geni
Actually, I've been wondering about this. Do we really know that an admin is behind Wikitruth? I haven't seen anything to prove that they haven't simply scraped Wikipedia at the right time or an outdated mirror later, and simply claimed to be an admin.
~maru
http://en.wikipedia.org/wiki/Image:Restore_Wikitruth_info.png
Ad nothing in the metadata suggests photoshop.
-- geni
On 4/19/06, geni geniice@gmail.com wrote:
http://en.wikipedia.org/wiki/Image:Restore_Wikitruth_info.png
Ad nothing in the metadata suggests photoshop.
-- geni
Point taken. All the other possibilities (an admin innocently taking a screencap, exporting his desktop to another computer who did take a screencap etc) seem less likely than a disgruntled admin. Albeit, the shot is a bit odd- do logged in accounts really look like that in monobook? It's been so long I've forgotten.
~maru
On 4/20/06, maru dubshinki marudubshinki@gmail.com wrote:
On 4/19/06, geni geniice@gmail.com wrote:
http://en.wikipedia.org/wiki/Image:Restore_Wikitruth_info.png
Ad nothing in the metadata suggests photoshop.
-- geni
Point taken. All the other possibilities (an admin innocently taking a screencap, exporting his desktop to another computer who did take a screencap etc) seem less likely than a disgruntled admin. Albeit, the shot is a bit odd- do logged in accounts really look like that in monobook? It's been so long I've forgotten.
~maru
Yes they do. I cheacked because I was wounding if they were using a custom .JS or.CSS which would have made them traceable.
-- geni
On Apr 19, 2006, at 4:55 PM, maru dubshinki wrote:
On 4/19/06, geni geniice@gmail.com wrote:
http://en.wikipedia.org/wiki/Image:Restore_Wikitruth_info.png
Ad nothing in the metadata suggests photoshop.
Point taken. All the other possibilities (an admin innocently taking a screencap, exporting his desktop to another computer who did take a screencap etc) seem less likely than a disgruntled admin. Albeit, the shot is a bit odd- do logged in accounts really look like that in monobook? It's been so long I've forgotten.
Well, the photo has obviously been carefully cropped, as the personal toolbar (which begins with the account name) has been erased. Also, I've only checked on Firefox on Mac OS X, but the font picked might be able to identify what browser and OS it was taken from. Furthermore, as it contains the toolbox links for Lupin's anti-vandal tool, a combination of http://en.wikipedia.org/w/index.php?title=Special:Whatlinkshere/User: Lupin/recent2.js&limit=500&from=0 and http://en.wikipedia.org/w/index.php? title=Special%3AListusers&group=sysop&limit=2000 results in the following list of 60 admins(a much smaller list than 800+...) who have installed Lupin's tool into their monobook.js file and have not taken the easy step of removing the link-back to recent.js.
Aaron Brenneman Acetic Acid Adashiel Arwel Parry Banes Bbatsell Bkonrad BorgHunter BorgQueen BrokenSegue Brookie Can't sleep, clown will eat me Canderson7 Cdc Celestianpower Chris 73 Commander Keane DaGizza Dan100 Dante Alighieri Docu Drini Dustimagic EdwinHJ Flcelloguy Fuzheado Gflores Hall Monitor Icairns Jacoplane Jareth Johnleemk Jpgordon Kbh3rd Kmccoy Marudubshinki Master Jay Mathwiz2020 NSLE No Guru Petros471 Pschemp Quadell Ral315 Raven4x4x Redvers Rhobite RoyBoy Shanel Sj Ta bu shi da yu Tawker TexasAndroid Tom harrison Trevor macinnis Ugen64 Vary Who Woohookitty Zippy
On 4/19/06, Jesse W jessw@netwood.net wrote:
Well, the photo has obviously been carefully cropped, as the personal toolbar (which begins with the account name) has been erased. Also, I've only checked on Firefox on Mac OS X, but the font picked might be able to identify what browser and OS it was taken from. Furthermore, as it contains the toolbox links for Lupin's anti-vandal tool, a combination of http://en.wikipedia.org/w/index.php?title=Special:Whatlinkshere/User: Lupin/recent2.js&limit=500&from=0 and http://en.wikipedia.org/w/index.php? title=Special%3AListusers&group=sysop&limit=2000 results in the following list of 60 admins(a much smaller list than 800+...) who have installed Lupin's tool into their monobook.js file and have not taken the easy step of removing the link-back to recent.js.
I don't know when that image was first posted (anyone have a link to it on the wikitruth.info site, rather than our screenshot?), but that date would further reduce the list by removing admins who were promoted after the screenshot was taken.
On 4/19/06, Blackcap snoutwood@gmail.com wrote:
On 4/19/06, Jesse W jessw@netwood.net wrote:
Well, the photo has obviously been carefully cropped, as the personal toolbar (which begins with the account name) has been erased. Also, I've only checked on Firefox on Mac OS X, but the font picked might be able to identify what browser and OS it was taken from. Furthermore, as it contains the toolbox links for Lupin's anti-vandal tool, a combination of http://en.wikipedia.org/w/index.php?title=Special:Whatlinkshere/User: Lupin/recent2.js&limit=500&from=0 and http://en.wikipedia.org/w/index.php? title=Special%3AListusers&group=sysop&limit=2000 results in the following list of 60 admins(a much smaller list than 800+...) who have installed Lupin's tool into their monobook.js file and have not taken the easy step of removing the link-back to recent.js.
I don't know when that image was first posted (anyone have a link to it on the wikitruth.info site, rather than our screenshot?), but that date would further reduce the list by removing admins who were promoted after the screenshot was taken.
The article's only a few days old; and the screenshot reflects the very recent deletions. I don't believe, offhand, that any of the admins on that list were promoted that recently.
Kirill Lokshin
Jesse W wrote:
Also,
I've only checked on Firefox on Mac OS X, but the font picked might be able to identify what browser and OS it was taken from.
That looks very much like Windows to me, judging by the font and the general shape of the "Go" and "Search" buttons. However, if we want to muck around in the server logs...how many people have Lupin's tool installed...AND have visited all those pages that are purple in color recently, not to mention that Undelete page? It's a long shot, but if we're serious about finding the mole, it would seem a logical place to look.
Jesse W wrote:
On Apr 19, 2006, at 4:55 PM, maru dubshinki wrote:
On 4/19/06, geni geniice@gmail.com wrote:
http://en.wikipedia.org/wiki/Image:Restore_Wikitruth_info.png
Point taken. All the other possibilities (an admin innocently taking a screencap, exporting his desktop to another computer who did take a screencap etc) seem less likely than a disgruntled admin. Albeit, the shot is a bit odd- do logged in accounts really look like that in monobook? It's been so long I've forgotten.
Well, the photo has obviously been carefully cropped, as the personal toolbar (which begins with the account name) has been erased. Also, I've only checked on Firefox on Mac OS X, but the font picked might be able to identify what browser and OS it was taken from.
It's Internet Explorer on Windows XP. That narrows it down a bit, but not much.
Jesse W wrote:
On Apr 19, 2006, at 4:55 PM, maru dubshinki wrote:
On 4/19/06, geni geniice@gmail.com wrote:
http://en.wikipedia.org/wiki/Image:Restore_Wikitruth_info.png
Ad nothing in the metadata suggests photoshop.
Point taken. All the other possibilities (an admin innocently taking a screencap, exporting his desktop to another computer who did take a screencap etc) seem less likely than a disgruntled admin. Albeit, the shot is a bit odd- do logged in accounts really look like that in monobook? It's been so long I've forgotten.
Well, the photo has obviously been carefully cropped, as the personal toolbar (which begins with the account name) has been erased. Also, I've only checked on Firefox on Mac OS X, but the font picked might be able to identify what browser and OS it was taken from.
It's either Firefox or Mozilla Suite on Windows XP.
On 4/19/06, geni geniice@gmail.com wrote:
As wikitruth has shown tracing admins who are leaking information is tricky.
What is there to be leaked? I thought we pretty much kept everything out in the open. Unless there's some super sekrit admin meeting that I haven't been invited to.
What is to be "leaked" is the contents of deleted articles.
Fred
On Apr 19, 2006, at 4:46 PM, Rob wrote:
On 4/19/06, geni geniice@gmail.com wrote:
As wikitruth has shown tracing admins who are leaking information is tricky.
What is there to be leaked? I thought we pretty much kept everything out in the open. Unless there's some super sekrit admin meeting that I haven't been invited to. _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
... which, if you think back to the not-so-distant incident with Gator1, can contain deleted material of a personal nature one would rather not be made public.
k
On 4/19/06, Fred Bauder fredbaud@ctelco.net wrote:
What is to be "leaked" is the contents of deleted articles.
Fred
On Apr 19, 2006, at 4:46 PM, Rob wrote:
On 4/19/06, geni geniice@gmail.com wrote:
As wikitruth has shown tracing admins who are leaking information is tricky.
What is there to be leaked? I thought we pretty much kept everything out in the open. Unless there's some super sekrit admin meeting that I haven't been invited to. _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On 4/19/06, geni geniice@gmail.com wrote:
Recent office actions involve more than just protection. They tend to involve a serious cut down of the article as well. As wikitruth has shown tracing admins who are leaking information is tricky.
Can't we look in the server logs to see who's looked at, for example, [[Special:Undelete/Wikitruth.info]] (due to [[Image:Restore Wikitruth info.png]])? From what I've read at [[m:Privacy policy#Security of information]], such logs do exist and could at least narrow down the possible suspects.
On 4/19/06, Blackcap snoutwood@gmail.com wrote:
On 4/19/06, geni geniice@gmail.com wrote:
Recent office actions involve more than just protection. They tend to involve a serious cut down of the article as well. As wikitruth has shown tracing admins who are leaking information is tricky.
Can't we look in the server logs to see who's looked at, for example, [[Special:Undelete/Wikitruth.info]] (due to [[Image:Restore Wikitruth info.png]])? From what I've read at [[m:Privacy policy#Security of information]], such logs do exist and could at least narrow down the possible suspects.
It would narrow it down a bit, but not all that much, because no doubt a bunch of admins have looked- from curiosity, if nothing else. However, combined with the popups evidence, it might narrow it down from 800 to around maybe only 20. We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
~maru
maru dubshinki wrote:
We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
But should critics of Wikipedia be admins of Wikipedia? I don't believe so. However, I suppose it's up to Jimbo and the Board if they want to expend the energy to look into it. As for privacy...it's not against the privacy policy, and besides which, I'm not sure that's an invasion of privacy anyway. You're sending data to the Wikimedia servers every time you visit a page, and that info is logged, and you (should) know that. I have no problems with the devs looking through page access logs, myself.
On 4/19/06, BorgHunter borghunter.wiki@gmail.com wrote:
maru dubshinki wrote:
We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
But should critics of Wikipedia be admins of Wikipedia? I don't believe so. However, I suppose it's up to Jimbo and the Board if they want to expend the energy to look into it. As for privacy...it's not against the privacy policy, and besides which, I'm not sure that's an invasion of privacy anyway. You're sending data to the Wikimedia servers every time you visit a page, and that info is logged, and you (should) know that. I have no problems with the devs looking through page access logs, myself.
We should be the critics of Wikipedia! I mean, admins make up by far the majority of the group of the most qualified-to-criticize-Wikipedia. Your average admin knows far more about Wikipedia than just about everyone except the rare various Wales, Sanger, Foundation member/employees, and developers, and certainly more than your average current critic like Brandt or the various reporters we keep reading.
As for the privacy bit, I think we basically fought this issue a while ago with CheckUser; I don't see why we can't work on an analogous basis. My personal reading of the CheckUser policies would suggest against checking, but that's me...
~maru
On 21/04/06, maru dubshinki marudubshinki@gmail.com wrote:
On 4/19/06, BorgHunter borghunter.wiki@gmail.com wrote:
maru dubshinki wrote:
We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
But should critics of Wikipedia be admins of Wikipedia? I don't believe so. However, I suppose it's up to Jimbo and the Board if they want to expend the energy to look into it. As for privacy...it's not against the privacy policy, and besides which, I'm not sure that's an invasion of privacy anyway. You're sending data to the Wikimedia servers every time you visit a page, and that info is logged, and you (should) know that. I have no problems with the devs looking through page access logs, myself.
We should be the critics of Wikipedia! I mean, admins make up by far the majority of the group of the most qualified-to-criticize-Wikipedia. Your average admin knows far more about Wikipedia than just about everyone except the rare various Wales, Sanger, Foundation member/employees, and developers, and certainly more than your average current critic like Brandt or the various reporters we keep reading.
A sample conversation a little while ago at work:
Boss: "Wikipedia scares me." AG: "It scares the *hell* out of me"
This seems to be a broadly held opinion among admins...
-- - Andrew Gray andrew.gray@dunelm.org.uk
On 4/20/06, maru dubshinki marudubshinki@gmail.com wrote:
We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
If the circumstantial evidence provided is valid, this is far worse than vandalism. This is people in a position of trust abusing it and possibly exposing Wikipedia to liability for copyright infringement or defamation by causing such material to be published.
On 4/19/06, Tony Sidaway f.crdfa@gmail.com wrote:
On 4/20/06, maru dubshinki marudubshinki@gmail.com wrote:
We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
If the circumstantial evidence provided is valid, this is far worse than vandalism. This is people in a position of trust abusing it and possibly exposing Wikipedia to liability for copyright infringement or defamation by causing such material to be published.
I disagree. Vandalism is direct actual damage to our content and our reputation, as opposed to possible theoretical damages caused by those iages. The abuse of trust is sad, and possibly a moral lapse (do we expect admins to never take screenshots of deleted pages, and to hold close to their chest any information declared verboten?), but the legal argument I'm not sure I buy- the guilty one is the one retrieving it and publishing it. We removed it, in good faith. While I am not a lawyer, our responsibility seems minimal.
~maru
On 4/19/06, maru dubshinki marudubshinki@gmail.com wrote:
On 4/19/06, Tony Sidaway f.crdfa@gmail.com wrote:
On 4/20/06, maru dubshinki marudubshinki@gmail.com wrote:
We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
If the circumstantial evidence provided is valid, this is far worse than vandalism. This is people in a position of trust abusing it and possibly exposing Wikipedia to liability for copyright infringement or defamation by causing such material to be published.
I disagree. Vandalism is direct actual damage to our content and our reputation, as opposed to possible theoretical damages caused by those iages. The abuse of trust is sad, and possibly a moral lapse (do we expect admins to never take screenshots of deleted pages, and to hold close to their chest any information declared verboten?), but the legal argument I'm not sure I buy- the guilty one is the one retrieving it and publishing it. We removed it, in good faith. While I am not a lawyer, our responsibility seems minimal.
Vandalism is also much easier to fix, of course.
But the question is not one of admins innocently taking screenshots of deleted pages. It's one thing to fail to properly safeguard information that shouldn't be getting distributed; it's quite another to use admin abilities within Wikipedia in order to pass sensitive information to an openly anti-Wikipedia site.
Kirill Lokshin
On 4/19/06, Kirill Lokshin kirill.lokshin@gmail.com wrote:
On 4/19/06, maru dubshinki marudubshinki@gmail.com wrote:
I disagree. Vandalism is direct actual damage to our content and our reputation, as opposed to possible theoretical damages caused by those iages. The abuse of trust is sad, and possibly a moral lapse (do we expect admins to never take screenshots of deleted pages, and to hold close to their chest any information declared verboten?), but the legal argument I'm not sure I buy- the guilty one is the one retrieving it and publishing it. We removed it, in good faith. While I am not a lawyer, our responsibility seems minimal.
Vandalism is also much easier to fix, of course.
But the question is not one of admins innocently taking screenshots of deleted pages. It's one thing to fail to properly safeguard information that shouldn't be getting distributed; it's quite another to use admin abilities within Wikipedia in order to pass sensitive information to an openly anti-Wikipedia site.
Kirill Lokshin
Don't get fixated on the admin power abuse thing. It is merely a convenient method and sign of who they have on their side. They could do it just as easily through database dumps, or spidering CFD/AFD, or scaping mirrors, or... You see what I'm getting at? Frankly, the CC GFDL issue aside, I find it kinda amusing we're all so horrified at seeing some of our content (for better or worse) on other websites. They're the one hosting it; no moral blame descends on us for at one time making a mistake, rectifying it, and then keeping records in case our rectification was a mistake. But I think I've posted enough in this thread, so good night.
~maru
On 4/19/06, maru dubshinki marudubshinki@gmail.com wrote:
Don't get fixated on the admin power abuse thing. It is merely a convenient method and sign of who they have on their side. They could do it just as easily through database dumps, or spidering CFD/AFD, or scaping mirrors, or... You see what I'm getting at? Frankly, the CC GFDL issue aside, I find it kinda amusing we're all so horrified at seeing some of our content (for better or worse) on other websites. They're the one hosting it; no moral blame descends on us for at one time making a mistake, rectifying it, and then keeping records in case our rectification was a mistake. But I think I've posted enough in this thread, so good night.
It's not the fact that they've obtained the deleted material per se. As you point out, they could have gotten it by other means; and the material itself, in this case, isn't particularly impressive.
My concern is more to the "sign of who they have on their side" aspect. The Wikipedia admin model works to a great extent because admins can be trusted not to harm the project. Here we have evidence -- circumstantial and not very specific, but nevertheless quite damning -- that one or more admins _are_ clearly attempting to harm Wikipedia. I would argue that this is a bad thing regardless of whether they've actually damaged anything yet.
Kirill Lokshin
Kirill Lokshin wrote:
On 4/19/06, maru dubshinki marudubshinki@gmail.com wrote:
Don't get fixated on the admin power abuse thing. It is merely a convenient method and sign of who they have on their side. They could do it just as easily through database dumps, or spidering CFD/AFD, or scaping mirrors, or... You see what I'm getting at? Frankly, the CC GFDL issue aside, I find it kinda amusing we're all so horrified at seeing some of our content (for better or worse) on other websites. They're the one hosting it; no moral blame descends on us for at one time making a mistake, rectifying it, and then keeping records in case our rectification was a mistake. But I think I've posted enough in this thread, so good night.
It's not the fact that they've obtained the deleted material per se. As you point out, they could have gotten it by other means; and the material itself, in this case, isn't particularly impressive.
My concern is more to the "sign of who they have on their side" aspect. The Wikipedia admin model works to a great extent because admins can be trusted not to harm the project. Here we have evidence -- circumstantial and not very specific, but nevertheless quite damning -- that one or more admins _are_ clearly attempting to harm Wikipedia. I would argue that this is a bad thing regardless of whether they've actually damaged anything yet.
The most disturbing aspect of this view is the classic paranoia. Of course we are in no position to go so far as to put a bullet in somebody's head for disloyalty, but the underlying aura of suspicion is similar. The fear that the people you might be working with are not as loyal as you, that they do not worship the words of the great leader as much as you are very scary. In a totalitarian regime there is no need for the leadership to issue repressive orders, or to hire high-price hitmen. A few handshakes, a smile or a bit of casual praise to a roomful of sycophants and paranoids will be far more cost effective.
As long as these rogue admins are taking ludicrous positions can they really harm Wikipedia with their rants? And how do we distinguish between the kooks and the honest whistleblowers who are exposing legitimate problems?
Ray Saintonge wrote:
Kirill Lokshin wrote:
On 4/19/06, maru dubshinki marudubshinki@gmail.com wrote:
Don't get fixated on the admin power abuse thing. It is merely a convenient method and sign of who they have on their side. They could do it just as easily through database dumps, or spidering CFD/AFD, or scaping mirrors, or... You see what I'm getting at? Frankly, the CC GFDL issue aside, I find it kinda amusing we're all so horrified at seeing some of our content (for better or worse) on other websites. They're the one hosting it; no moral blame descends on us for at one time making a mistake, rectifying it, and then keeping records in case our rectification was a mistake. But I think I've posted enough in this thread, so good night.
It's not the fact that they've obtained the deleted material per se. As you point out, they could have gotten it by other means; and the material itself, in this case, isn't particularly impressive.
My concern is more to the "sign of who they have on their side" aspect. The Wikipedia admin model works to a great extent because admins can be trusted not to harm the project. Here we have evidence -- circumstantial and not very specific, but nevertheless quite damning -- that one or more admins _are_ clearly attempting to harm Wikipedia. I would argue that this is a bad thing regardless of whether they've actually damaged anything yet.
The most disturbing aspect of this view is the classic paranoia. Of course we are in no position to go so far as to put a bullet in somebody's head for disloyalty, but the underlying aura of suspicion is similar. The fear that the people you might be working with are not as loyal as you, that they do not worship the words of the great leader as much as you are very scary. In a totalitarian regime there is no need for the leadership to issue repressive orders, or to hire high-price hitmen. A few handshakes, a smile or a bit of casual praise to a roomful of sycophants and paranoids will be far more cost effective.
As long as these rogue admins are taking ludicrous positions can they really harm Wikipedia with their rants? And how do we distinguish between the kooks and the honest whistleblowers who are exposing legitimate problems?
Honest whistleblowers don't post defamatory information about people or their children.
I don't mean to be rude or anything, but if you are going to discuss wikitruth, can you please change the subject and start a new thread. My gmail inbox is hard to navigate enough :P
--Oskar
Most of us who see problems complain to Jimbo directly and at great length on the mailing lists. We may even create a fork. What we don't do is make up a bunch of scurrilous accusations, for example, bogus accusations that we are friendly to pedophiles, and promote them in the external media.
Results vary when you complain, some problems are dealt with, some work themselves out, some are ignored, but I have never seen a vengeful or paranoid attitude from our central leadership.
Fred
On Apr 20, 2006, at 12:25 AM, Ray Saintonge wrote:
The most disturbing aspect of this view is the classic paranoia. Of course we are in no position to go so far as to put a bullet in somebody's head for disloyalty, but the underlying aura of suspicion is similar. The fear that the people you might be working with are not as loyal as you, that they do not worship the words of the great leader as much as you are very scary. In a totalitarian regime there is no need for the leadership to issue repressive orders, or to hire high-price hitmen. A few handshakes, a smile or a bit of casual praise to a roomful of sycophants and paranoids will be far more cost effective.
As long as these rogue admins are taking ludicrous positions can they really harm Wikipedia with their rants? And how do we distinguish between the kooks and the honest whistleblowers who are exposing legitimate problems?
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
Fred Bauder wrote:
Results vary when you complain, some problems are dealt with, some work themselves out, some are ignored, but I have never seen a vengeful or paranoid attitude from our central leadership.
Depends on who you count among the "central leadership", I suppose. I'm not trying to single her out here, but I was struct by the juxtaposition of your comment above and a message just left by Kelly Martin (who seems to be "in the know" on this current issue) at [[WP:1WW]:
"... Eloquence deciding that he's entitled to unilaterally reverse without discussion a protection imposed by Danny, one of most trusted administrators. That was wheel warring. He deserves to be desysoped (and was desysoped, although that punishment, while originally imposed by Jimbo, was subsequently reversed by Jimbo for reasons that frankly make no sense to me) for that."
So, let's see:
* That nice hot-button word "unilaterally". It wasn't more than a few months ago when the unwashed hordes were screaming it at Kelly herself.
* Desysoping (and prosumably blocking) are apparently now punitive, not preventative.
* "I am sure Erik will not do anything bad" frankly makes no sense to her.
I'm sorry to say this, but, all in all, that comment sounds pretty nasty. Maybe not "vengeful or paranoid", but certainly very stressed out and high-handed, with a good amount of zero tolerance and "assume bad faith" thrown in. Maybe I'm reading too much into this paragraph, but it sure sounds as if someone is in urgent need of a vacation here.
Mind you, when the smoke clears, I'd really like to know what caused all this panic at the office in the first place -- did someone hold Jimbo at gunpoint while demanding that the articles be removed, or what?
Just another admin without all the pieces of the puzzle,
On 4/20/06, Ilmari Karonen nospam@vyznev.net wrote:
- That nice hot-button word "unilaterally". It wasn't more than a few
months ago when the unwashed hordes were screaming it at Kelly herself.
There is a big difference between my unilaterally deleting a bunch of rather unimportant userboxes and Erik reverting the protection of a hot article implemented by Danny. You will also note that I did not wheel war with respect to any of the userboxes I deleted; I did not redelete any of the ones that were speedily restored by various admins, and the small handful which I did delete twice I redeleted after discussion with the objectors to the original deletion. I may not have much respect for some of enwiki's arbitrary processes, for the vast quantities of cruft that float around in enwiki, or for the community that seems to exist more much for its own perpetuation than for its purported purpose of writing an encyclopedia, but I have a great deal of respect for the need of the Foundation to take appropriate measures to protect its very real legal interests in the face of potential litigation. I tend to believe that the Foundation is, at its core, more interested in being "an encyclopedia being written by a community" than a "community which is writing an encyclopedia". I'm not so convinced that the same is true of the Wikipedia community as a whole.
And, yes, I am somewhat more in the know on this issue than you are, but that doesn't mean I have all of the pieces of the puzzle either. All rhetoric aside, not all admins on Wikipedia are equal; some of us are clearly more bothered about this than others.
Kelly
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
There is a big difference between my unilaterally deleting a bunch of rather unimportant userboxes and Erik reverting the protection of a hot article implemented by Danny. You will also note that I did not wheel war with respect to any of the userboxes I deleted; I did not redelete any of the ones that were speedily restored by various admins, and the small handful which I did delete twice I redeleted after discussion with the objectors to the original deletion.
Just to make sure all of the facts are on the table: 1) I did not "wheel war". I reverted the protection once, and left a comment on the talk page. I did not revert the stubbification in respect of Danny's editorial judgment on the matter. 2) The Office Protection was not labeled as such. It was instead labeled as a normal protection. 3) When another user added an Office Protection label, Danny reverted him. This is only visible in the list of deleted revisions of [[NewsMax.com]]. 4) He did this using [[User:Danny]], at a point when he had already created his separate [[User:Dannyisme]] account for foundation tasks.
I'll shut up again now.
Erik
On 4/20/06, Erik Moeller eloquence@gmail.com wrote:
- When another user added an Office Protection label, Danny reverted
him. This is only visible in the list of deleted revisions of [[NewsMax.com]].
Actually, no, he didn't. I did.
Kelly
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Erik Moeller eloquence@gmail.com wrote:
- When another user added an Office Protection label, Danny reverted
him. This is only visible in the list of deleted revisions of [[NewsMax.com]].
Actually, no, he didn't. I did.
http://en.wikipedia.org/wiki/Special:Undelete/NewsMax.com # 00:46, April 19, 2006 . . Danny (Reverted edits by ContiE (talk) to last version by Danny) # 22:31, April 18, 2006 . . ContiE (using the office template. (http://en.wikipedia.org/w/index.php?title=User_talk:Splash&diff=prev&...))
Erik
On 4/20/06, Erik Moeller eloquence@gmail.com wrote:
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Erik Moeller eloquence@gmail.com wrote:
- When another user added an Office Protection label, Danny reverted
him. This is only visible in the list of deleted revisions of [[NewsMax.com]].
Actually, no, he didn't. I did.
http://en.wikipedia.org/wiki/Special:Undelete/NewsMax.com # 00:46, April 19, 2006 . . Danny (Reverted edits by ContiE (talk) to last version by Danny) # 22:31, April 18, 2006 . . ContiE (using the office template. (http://en.wikipedia.org/w/index.php?title=User_talk:Splash&diff=prev&...))
Erik
Ah, yes. Danny did revert, and THEN I deleted both the edit and the reversion. My mistake.
Kelly
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Erik Moeller eloquence@gmail.com wrote:
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
On 4/20/06, Erik Moeller eloquence@gmail.com wrote:
- When another user added an Office Protection label, Danny
reverted
him. This is only visible in the list of deleted revisions of [[NewsMax.com]].
Actually, no, he didn't. I did.
http://en.wikipedia.org/wiki/Special:Undelete/NewsMax.com # 00:46, April 19, 2006 . . Danny (Reverted edits by ContiE (talk) to last version by Danny) # 22:31, April 18, 2006 . . ContiE (using the office template. (
http://en.wikipedia.org/w/index.php?title=User_talk:Splash&diff=prev&...) )
Erik
Ah, yes. Danny did revert, and THEN I deleted both the edit and the reversion. My mistake.
Kelly
Why did you get involved?
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote: <snip>
...but I have a great deal of respect for the need of the Foundation to take appropriate measures to protect its very real legal interests in the face of potential litigation.
This has been repeated ad nauseum in this thread, but it appears that this point hasn't gotten through: I'm positive that 99% of the community (and this thread) has NO problem WHATSOEVER with WP:OFFICE. We get it, it's a necessary evil. It's not fun, but it is something that has to be there. We don't want wikipedia sued, and if that's what it takes, so be it. WP:OFFICE is not the point in this case.
The point is that Eloquence, one of the oldest and most trusted users on wikipedia, one of the people that have really helped shape the way we see and use wikipedia today, was indefinitly blocked and desysopped for undoing what he thought was a random admin action, one that he thought was out of policy. Danny, who is the only one who can invoke WP:OFFICE, simply ignored to tell us, the rest of the community, that he was doing just that.
When it comes to WP:OFFICE, we don't demand much. You can lock down the article for as long as it is an issue, you don't have to tell us anything about the case, you don't even have to inform us how long it will be locked. We're fine with all that. But please, show us enough respect to actually, properly, inform us what we are doing, and don't perma-ban one of the most trusted editors out there for a simple misunderstanding.
That is really not ok, not in any way, shape or form.
Oskar Sigvardsson wrote:
The point is that Eloquence, one of the oldest and most trusted users on wikipedia, one of the people that have really helped shape the way we see and use wikipedia today, was indefinitly blocked and desysopped for undoing what he thought was a random admin action, one that he thought was out of policy. Danny, who is the only one who can invoke WP:OFFICE, simply ignored to tell us, the rest of the community, that he was doing just that.
I agree wholeheartedly.
-Mark
Oskar Sigvardsson wrote:
On 4/20/06, Kelly Martin kelly.lynn.martin@gmail.com wrote:
<snip>
...but I have a great deal of respect for the need of the Foundation to take appropriate measures to protect its very real legal interests in the face of potential litigation.
This has been repeated ad nauseum in this thread, but it appears that this point hasn't gotten through: I'm positive that 99% of the community (and this thread) has NO problem WHATSOEVER with WP:OFFICE. We get it, it's a necessary evil. It's not fun, but it is something that has to be there. We don't want wikipedia sued, and if that's what it takes, so be it. WP:OFFICE is not the point in this case.
The point is that Eloquence, one of the oldest and most trusted users on wikipedia, one of the people that have really helped shape the way we see and use wikipedia today, was indefinitly blocked and desysopped for undoing what he thought was a random admin action, one that he thought was out of policy. Danny, who is the only one who can invoke WP:OFFICE, simply ignored to tell us, the rest of the community, that he was doing just that.
If Danny is the only one who can invoke WP:OFFICE why is it that the category tag is there under the name of user:David Newton, and the protection tag under the name of User:Lbmixpro? Surely if the effects of this tag are going to be so severe it's addition by anyone else should not be permitted.
If the intention of imposing a block is to initiate discussion of a problem, 24 hours will be long enough to have that effect. Indefinite blocks only encourage acrimony.
When it comes to WP:OFFICE, we don't demand much. You can lock down the article for as long as it is an issue, you don't have to tell us anything about the case, you don't even have to inform us how long it will be locked. We're fine with all that. But please, show us enough respect to actually, properly, inform us what we are doing, and don't perma-ban one of the most trusted editors out there for a simple misunderstanding.
Yes, the point is that if harsh measures are needed there needs to be a stricter adherence to process by those who would impose such measures.
Ec
Kelly Martin wrote:
I have a great deal of respect for the need of the Foundation to take appropriate measures to protect its very real legal interests in the face of potential litigation. I tend to believe that the Foundation is, at its core, more interested in being "an encyclopedia being written by a community" than a "community which is writing an encyclopedia". I'm not so convinced that the same is true of the Wikipedia community as a whole.
And, yes, I am somewhat more in the know on this issue than you are, but that doesn't mean I have all of the pieces of the puzzle either. All rhetoric aside, not all admins on Wikipedia are equal; some of us are clearly more bothered about this than others.
Welcome to Animal Farm.
At this point we have nothing more than a guess that there is potential litigation. That's a great foundation for sand castles. Has anyone ever heard of verifiability?
Ec
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ilmari Karonen wrote:
Fred Bauder wrote:
Results vary when you complain, some problems are dealt with, some work themselves out, some are ignored, but I have never seen a vengeful or paranoid attitude from our central leadership.
Depends on who you count among the "central leadership", I suppose. I'm not trying to single her out here, but I was struct by the juxtaposition of your comment above and a message just left by Kelly Martin (who seems to be "in the know" on this current issue) at [[WP:1WW]:
| "... Eloquence deciding that he's entitled to unilaterally reverse | without discussion a protection imposed by Danny, one of most trusted | administrators. That was wheel warring. He deserves to be desysoped (and | was desysoped, although that punishment, while originally imposed by | Jimbo, was subsequently reversed by Jimbo for reasons that frankly make | no sense to me) for that."
So, let's see:
- That nice hot-button word "unilaterally". It wasn't more than a few
months ago when the unwashed hordes were screaming it at Kelly herself.
Ah, yes, but they were wrong. :-)
- Desysoping (and prosumably blocking) are apparently now punitive, not
preventative.
It is a preventative measure against further actions which are to the serious detriment of the Foundation.
- "I am sure Erik will not do anything bad" frankly makes no sense to her.
The point is, I believe, that the term used in the statement is "do", not "continue to do".
I'm sorry to say this, but, all in all, that comment sounds pretty nasty. Maybe not "vengeful or paranoid", but certainly very stressed out and high-handed, with a good amount of zero tolerance and "assume bad faith" thrown in. Maybe I'm reading too much into this paragraph, but it sure sounds as if someone is in urgent need of a vacation here.
That's an intriguing line to take.
I'd really like to know what caused all this
Evidently this isn't getting through. The reasons for such actions normally cannot and certainly should not be revealed. I'd love to know everything, too, but the answer is: "tough".
Just another admin without all the pieces of the puzzle,
Indeed. Which is the exact point.
Yours sincerely, - -- James D. Forrester Wikimedia : [[W:en:User:Jdforrester|James F.]] E-Mail : james@jdforrester.org IM (MSN) : jamesdforrester@hotmail.com
I don't know the details either, but apparently someone made a complaint about the article which had considerable merit. I only glanced at the article, but it seemed to be a hatchet job.
Fred
On Apr 20, 2006, at 8:46 AM, Ilmari Karonen wrote:
Mind you, when the smoke clears, I'd really like to know what caused all this panic at the office in the first place -- did someone hold Jimbo at gunpoint while demanding that the articles be removed, or what?
Kelly Martin is not in "our central leadership" (that would be Jimbo, Angela, Anthere, Daniel Mayer, and a few others) and has no future as a diplomat. Kelly is correct about our difficulties with establishing that wheel warring is absolutely unacceptable. I have have had a few invitations to wheel warring when someone felt they could simply revert what I had done, but so far I haven't gotten in a real mess by taking the bait. It is just not good practice to reverse another administrator's actions. That needs to be part of our culture, not some wishy-washy notion that it is OK to wheel war when the other administrator is "wrong". If they are wrong, especially repeatedly, it needs to be dealt with by talking, that is negotiation, and if that is unsuccessful, with the remaining steps in the dispute resolution process.
Fred
On Apr 20, 2006, at 8:46 AM, Ilmari Karonen wrote:
Fred Bauder wrote:
Results vary when you complain, some problems are dealt with, some work themselves out, some are ignored, but I have never seen a vengeful or paranoid attitude from our central leadership.
Depends on who you count among the "central leadership", I suppose. I'm not trying to single her out here, but I was struct by the juxtaposition of your comment above and a message just left by Kelly Martin (who seems to be "in the know" on this current issue) at [[WP:1WW]:
"... Eloquence deciding that he's entitled to unilaterally reverse without discussion a protection imposed by Danny, one of most trusted administrators. That was wheel warring. He deserves to be desysoped (and was desysoped, although that punishment, while originally imposed by Jimbo, was subsequently reversed by Jimbo for reasons that frankly make no sense to me) for that."
So, let's see:
- That nice hot-button word "unilaterally". It wasn't more than a few
months ago when the unwashed hordes were screaming it at Kelly herself.
- Desysoping (and prosumably blocking) are apparently now punitive,
not preventative.
- "I am sure Erik will not do anything bad" frankly makes no sense
to her.
I'm sorry to say this, but, all in all, that comment sounds pretty nasty. Maybe not "vengeful or paranoid", but certainly very stressed out and high-handed, with a good amount of zero tolerance and "assume bad faith" thrown in. Maybe I'm reading too much into this paragraph, but it sure sounds as if someone is in urgent need of a vacation here.
Mind you, when the smoke clears, I'd really like to know what caused all this panic at the office in the first place -- did someone hold Jimbo at gunpoint while demanding that the articles be removed, or what?
Just another admin without all the pieces of the puzzle,
Ilmari Karonen _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
* Fred Bauder wrote:
taking the bait. It is just not good practice to reverse another administrator's actions. That needs to be part of our culture, not some wishy-washy notion that it is OK to wheel war when the other administrator is "wrong".
Umm... where do you suppose the "wishy washy notion that it is OK to wheel war when the other administrator is 'wrong'" COMES from?
There was an arbitration case on wheel warring not so long ago where the set of administrators who were adjudged 'wrong' were reprimanded or de-sysoped while the set of administrators who were adjudged 'right' were not... regardless of the degree to which each individual had engaged in 'wheel warring'. One admin was even PRAISED for 'wheel warring'.
If you really want to make the case that wheel-warring is ALWAYS wrong then it needs to be treated that way. Not as a cudgel for use only against 'those with whom we disagree'.
Quite right. I want to move that way.
Fred
On Apr 20, 2006, at 2:40 PM, Conrad Dunkerson wrote:
- Fred Bauder wrote:
taking the bait. It is just not good practice to reverse another administrator's actions. That needs to be part of our culture, not some wishy-washy notion that it is OK to wheel war when the other administrator is "wrong".
Umm... where do you suppose the "wishy washy notion that it is OK to wheel war when the other administrator is 'wrong'" COMES from?
There was an arbitration case on wheel warring not so long ago where the set of administrators who were adjudged 'wrong' were reprimanded or de-sysoped while the set of administrators who were adjudged 'right' were not... regardless of the degree to which each individual had engaged in 'wheel warring'. One admin was even PRAISED for 'wheel warring'.
If you really want to make the case that wheel-warring is ALWAYS wrong then it needs to be treated that way. Not as a cudgel for use only against 'those with whom we disagree'. _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
On 4/20/06, Conrad Dunkerson conrad.dunkerson@worldnet.att.net wrote:
There was an arbitration case on wheel warring not so long ago where the set of administrators who were adjudged 'wrong' were reprimanded or de-sysoped while the set of administrators who were adjudged 'right' were not... regardless of the degree to which each individual had engaged in 'wheel warring'. One admin was even PRAISED for 'wheel warring'.
The AC is not supposed to be setting policy, but interpreting it; while this does, de facto, set policy to some degree, there was and AFAIK still is no agreed-upon policy forbidding "wheel warring" (a term I dislike because of its lack of real definition). I personally could not countenance punishing all admins who had reverted all other admins' actions simply to make an example of them, when what they did was not defined as "wrong" anywhere.
I do not think that the just way to get rid of the problem is for the AC to decide on what the policy should be and then make examples of admins until everyone 'gets the message'.
-Matt
Fred Bauder wrote:
Kelly Martin is not in "our central leadership" (that would be Jimbo, Angela, Anthere, Daniel Mayer, and a few others) and has no future as a diplomat. <snip>
Fred
I think we all know that. However, the way she has been behaving as of late seems to indicate she has more pieces of the puzzle than the rest of us, which would certainly imply some (un?)official role in the "central leadership".
John
On Apr 20, 2006, at 8:28 AM, Fred Bauder wrote:
It is just not good practice to reverse another administrator's actions. That needs to be part of our culture, not some wishy-washy notion that it is OK to wheel war when the other administrator is "wrong".
Amen to that. Sadly (and to name names), a certain administrator whose name begins with "T" and ends with "ony Sidaway" has, in the past, been allowed to (and even congratulated for) reverting other administrators' actions multiple times while the ruling culture derides any criticism of this as "lynching".
My point? Any prohibition against wheel warring must be *objective* and *applied across the board*. Unless every case, without exception, of violating any wheel-warring policy is met with immediate desysopping (pending further review) then the wheel-warring policy will be selectively enforced to enable certain administrators to "win" wheel wars against unfavored administrators.
On Apr 22, 2006, at 3:11 PM, Philip Welch wrote:
Amen to that. Sadly (and to name names), a certain administrator whose name begins with "T" and ends with "ony Sidaway" has, in the past, been allowed to (and even congratulated for) reverting other administrators' actions multiple times while the ruling culture derides any criticism of this as "lynching".
Congratulations! Your skill at trolling has increased! Congratulations! Your skill at thread derailment has increased! Congratulations! Your skill at cliched personal attacks has increased! Congratulations! You are now a level 2 Wiki-EN user!
-Phil
On Apr 22, 2006, at 12:17 PM, Phil Sandifer wrote:
Amen to that. Sadly (and to name names), a certain administrator whose name begins with "T" and ends with "ony Sidaway" has, in the past, been allowed to (and even congratulated for) reverting other administrators' actions multiple times while the ruling culture derides any criticism of this as "lynching".
Congratulations! Your skill at trolling has increased! Congratulations! Your skill at thread derailment has increased! Congratulations! Your skill at cliched personal attacks has increased! Congratulations! You are now a level 2 Wiki-EN user!
Thanks for your most instructive reply. I see you conveniently snipped out the entire point that this post was leading to, which I will repeat thrice for emphasis, since you didn't seem to get it the first time:
My point? Any prohibition against wheel warring must be *objective* and *applied across the board*. Unless every case, without exception, of violating any wheel-warring policy is met with immediate desysopping (pending further review) then the wheel-warring policy will be selectively enforced to enable certain administrators to "win" wheel wars against unfavored administrators.
My point? Any prohibition against wheel warring must be *objective* and *applied across the board*. Unless every case, without exception, of violating any wheel-warring policy is met with immediate desysopping (pending further review) then the wheel-warring policy will be selectively enforced to enable certain administrators to "win" wheel wars against unfavored administrators.
My point? Any prohibition against wheel warring must be *objective* and *applied across the board*. Unless every case, without exception, of violating any wheel-warring policy is met with immediate desysopping (pending further review) then the wheel-warring policy will be selectively enforced to enable certain administrators to "win" wheel wars against unfavored administrators.
Phil Sandifer wrote:
On Apr 22, 2006, at 3:11 PM, Philip Welch wrote:
Amen to that. Sadly (and to name names), a certain administrator whose name begins with "T" and ends with "ony Sidaway" has, in the past, been allowed to (and even congratulated for) reverting other administrators' actions multiple times while the ruling culture derides any criticism of this as "lynching".
Congratulations! Your skill at trolling has increased! Congratulations! Your skill at thread derailment has increased! Congratulations! Your skill at cliched personal attacks has increased! Congratulations! You are now a level 2 Wiki-EN user!
You get backstab at level 7. </obligatory [[m:bash]] reference>
On Apr 19, 2006, at 8:17 PM, maru dubshinki wrote:
I disagree. Vandalism is direct actual damage to our content and our reputation, as opposed to possible theoretical damages caused by those iages. The abuse of trust is sad, and possibly a moral lapse (do we expect admins to never take screenshots of deleted pages, and to hold close to their chest any information declared verboten?), but the legal argument I'm not sure I buy- the guilty one is the one retrieving it and publishing it. We removed it, in good faith. While I am not a lawyer, our responsibility seems minimal.
We could keep the contact information of people who make legal complaints to the office, and then if/when Wikitruth.info republishes the material inform the complaining party so they go after wikitruth.info.
Would that constitute disrupting their lives to make a point? Yes. Should we do it? Absolutely.
Tony Sidaway wrote:
On 4/20/06, maru dubshinki marudubshinki@gmail.com wrote:
We shouldn't examine that data, however. Very bad precedent, and poor for privacy, especially since we aren't dealing with out-and-out vandals here, but merely critics.
If the circumstantial evidence provided is valid, this is far worse than vandalism. This is people in a position of trust abusing it and possibly exposing Wikipedia to liability for copyright infringement or defamation by causing such material to be published.
If the premise that the material is such that would expose its publisher to that kind of liability there would be no liability to Wikipedia if the material was removed shortly after the problem was discovered. If a person subsequently abuses the material any liability would be on his shoulders.
Ec
Steve Bennett wrote:
On 19/04/06, Ben Lowe ben.lowe@gmail.com wrote:
Is this really a surprise? I remember always hearing the best way to make a book popular is to get it banned; why should this be any different on Wikipedia? For people looking for controversy and scandal on the encyclopedia that anyone can edit, the two or three articles that *no one -- NO ONE -- can edit for fear of eternal exile *are way more interesting than the more-than-a-million other articles. I suspect more Wikipedians (and slashdotters) know about [[Brian Peppers]] than [[Jordanhill railway station]]. Is OFFICE necessary? Sure, probably. Wikipedia definitely needs to be responsible, both in terms of its own liability. But if Danny wants to use WP:OFFICE without controversy, he needs it to be normalized, not hidden. People need to simply get used to it. The only way that WP:OFFICE is going to become non-controversial is if it's openly used.
Here's another solution. Make it possible for Danny to silently protect a page without it being unprotectable. Communicate a policy to all admins that if an admin discovers that a page has been protected in such a way, that he should keep it to himself, or risk desysopping.
The ordinary user will simply see a protected page. Admins, unless they actually try and unprotect it, will be none the wiser. And if they do try, perhaps a message should alert them to keep it confidential.
But that's just breeding conspiracy theories, I know.
Steve
What about adding another protection "level". Instead protecting under a edit=sysop, move=sysop, have Danny protect the pages under edit=board, move=board, so admins can't "accidentally" unprotect a WP:OFFICE protected article?
--Ruud
Sean Barrett wrote:
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I have unblocked Erik and hope that everyone will relax so we can talk about these issues slowly and carefully. I am sure Erik will not do anything bad.
I have not had time to really study anything yet, and I am about to go have dinner with some wikipedians.
--Jimbo
Aha, the inner circle I assume? :)
On 4/20/06, Jimmy Wales jwales@wikia.com wrote:
Sean Barrett wrote:
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I have unblocked Erik and hope that everyone will relax so we can talk about these issues slowly and carefully. I am sure Erik will not do anything bad.
I have not had time to really study anything yet, and I am about to go have dinner with some wikipedians.
--Jimbo
WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
I wrote:
I have not had time to really study anything yet, and I am about to go have dinner with some wikipedians.
Carl Fûrstenberg wrote:
Aha, the inner circle I assume? :)
Mindspillage and GMaxwell. So, yeah. 2 of them. :)
On 4/20/06, Jimmy Wales jwales@wikia.com wrote:
I have unblocked Erik and hope that everyone will relax so we can talk about these issues slowly and carefully. I am sure Erik will not do anything bad.
Not more than usually ;-). Thank you, Jimmy. I appreciate it. Thanks also to Angela for restoring my access on Meta. From what I can tell, I am now fully reinstated. Given this, I have no further comments on this matter. I will only say that I hope the discussion will move on from this particular conflict to the underlying policy issues. But that's for others to work out - I've had my share of "Office Action" for now. ;-)
Thanks again,
Erik
On 4/19/06, Jimmy Wales jwales@wikia.com wrote:
Sean Barrett wrote:
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I have unblocked Erik and hope that everyone will relax so we can talk about these issues slowly and carefully. I am sure Erik will not do anything bad.
I have not had time to really study anything yet, and I am about to go have dinner with some wikipedians.
You might consider getting a different lawyer.
On 4/20/06, The Cunctator cunctator@gmail.com wrote:
On 4/19/06, Jimmy Wales jwales@wikia.com wrote:
Sean Barrett wrote:
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I have unblocked Erik and hope that everyone will relax so we can talk about these issues slowly and carefully. I am sure Erik will not do anything bad.
I have not had time to really study anything yet, and I am about to go have dinner with some wikipedians.
You might consider getting a different lawyer.
Dear lord, why? Brad is one of the few people in this entire incident who is behaving sensibly.
Kelly
I know something about this, for someone who is an "outsider", not deeply involved in day to day Wikipedia rough and tumble, he's doing OK. No practicing lawyer could spend hours and hours editing or dealing with policy issues in the trenches and we will always face some lack of insight, but Brad is OK, actually does have a sense of humor, and, I think, serves us well.
Fred
On Apr 20, 2006, at 7:33 AM, The Cunctator wrote:
On 4/19/06, Jimmy Wales jwales@wikia.com wrote:
Sean Barrett wrote:
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I have unblocked Erik and hope that everyone will relax so we can talk about these issues slowly and carefully. I am sure Erik will not do anything bad.
I have not had time to really study anything yet, and I am about to go have dinner with some wikipedians.
You might consider getting a different lawyer. _______________________________________________ WikiEN-l mailing list WikiEN-l@Wikipedia.org To unsubscribe from this mailing list, visit: http://mail.wikipedia.org/mailman/listinfo/wikien-l
Sean Barrett wrote:
John Lee stated for the record:
Sean Barrett wrote:
I have unblocked Eloquence on the English Wikipedia. Blocking him was clearly inappropriate. Blocking him indefinitely was astoundingly stupid. Desysopping is equally insane, but resysopping him can wait for the wheels to grind.
Danny reverted the block, but didn't use the OFFICE account (Dannyisme). This is getting interesting...
John
I will not wheel-war, so I will not re-un-block Eloquence, but I firmly stand by my characterizations of this action. Regardless of any WP:OFFICE issues involved, Eloquence is not a danger to the project; blocking him and refusing to communicate is a stupid thing to do.
I eagerly wait an explanation of why Eloquence was indefinitely blocked.
I too think that an informed explanation is required, not just a lawyer's lame mumbo-jumbo to justify secrecy.
I often disagree with Eloquence, but I have no reason to doubt his good faith in what he does. It seems that the accusation of recklessness was excessive.
I did look at the material, and it seemed like just another routine dispute about an obscure right-winger. I looked at the article history and note that Danny was not the one to add the WP:OFFICE tag. This opens up the big question of who is authorized to use it. If just anybody can add the tag it doesn't mean very much. Perhaps the explanation page should also list those who are authorized to add it. When it is added by anyone else it should be safe to ignore it.
Ec
* Sean Barrett wrote:
I have unblocked Eloquence on the English Wikipedia. Blocking him was clearly inappropriate. Blocking him indefinitely was astoundingly stupid. Desysopping is equally insane, but resysopping him can wait for the wheels to grind.
Oi!
Before this gets any uglier could everyone agree to stop making nasty comments and pointing fingers?
One 'bad action' (if it was such) should not merit an indefinite block and de-sysoping without discussion.
One 'unwarranted de-sysoping and block' (if it was such) should not merit insults about "stupid" and "insane".
Somewhere along the line tempers frayed and questionable action or actions were taken. Making more snap judgements and nasty comments can only cause the situation to get worse.
I'd like to hear from 'the office' / 'board' / 'Jimbo' / 'Danny' / whoever what the rationale behind the initial block / de-sysoping was.
----- Original Message ---- From: Erik Moeller eloquence@gmail.com wrote:
I have just been indefinitely blocked from the English Wikipedia, and desysopped, by user Danny, under the new nickname "Dannyisme", as an "Office Action" for alleged "reckless endangerment" which was not specified further. I have called Danny on the phone, but he said that he was not willing to discuss the issue, and that I should instead talk to the Foundation attorney instead.
This is astonishing. It would be good to hear Danny's version of events. Even so, it's difficult to imagine any adequate justification for an indefinite block in this situation.
-- Matt [[User:Matt Crypto]]