This is an old revision of this page, as edited by 81.5.140.5 (talk) at 21:48, 12 December 2005. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 21:48, 12 December 2005 by 81.5.140.5 (talk)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Noticeboards | |
---|---|
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes. | |
General | |
Articles, content | |
Page handling | |
User conduct | |
Other | |
Category:Misplaced Pages noticeboards |
This page is for urgent incidents or chronic, intractable behavioral problems.
- Before posting:
- Consider other means of dispute resolution first
- Read these tips for dealing with incivility
- If the issue concerns a specific user, try discussing it with them on their talk page
- If the issue concerns use of admin tools or other advanced permissions, request an administrative action review
- Just want an admin? Contact a recently active admin directly.
- Be brief and include diffs demonstrating the problem
- Do not report breaches of personal information on this highly visible page – instead go to Requests for oversight.
When starting a discussion about an editor, you must leave a notice on their talk page; pinging is not enough.
You may use {{subst:ANI-notice}} ~~~~
to do so.
Closed discussions are usually not archived for at least 24 hours. Routine matters might be archived more quickly; complex or controversial matters should remain longer. Sections inactive for 72 hours are archived automatically by Lowercase sigmabot III. Editors unable to edit here are sent to the /Non-autoconfirmed posts subpage. (archives, search)
Start a new discussion Centralized discussion- Refining the administrator elections process
- Blocks for promotional activity outside of mainspace
- Voluntary RfAs after resignation
- Proposed rewrite of WP:BITE
- LLM/chatbot comments in discussions
Administrators' (archives, search) | |||||||||
---|---|---|---|---|---|---|---|---|---|
349 | 350 | 351 | 352 | 353 | 354 | 355 | 356 | 357 | 358 |
359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 |
Incidents (archives, search) | |||||||||
1156 | 1157 | 1158 | 1159 | 1160 | 1161 | 1162 | 1163 | 1164 | 1165 |
1166 | 1167 | 1168 | 1169 | 1170 | 1171 | 1172 | 1173 | 1174 | 1175 |
Edit-warring/3RR (archives, search) | |||||||||
472 | 473 | 474 | 475 | 476 | 477 | 478 | 479 | 480 | 481 |
482 | 483 | 484 | 485 | 486 | 487 | 488 | 489 | 490 | 491 |
Arbitration enforcement (archives) | |||||||||
328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 |
338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 |
Other links | |||||||||
Inexhaustible vandalism from the UK Internet for Learning: range block warranted?
These IPs (and surely others that I haven't come across, and indeed the whole range) are registered to the UK Internet for Learning, according to notes on several of the talkpages:
- 62.171.194.4 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.6 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.12 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.40 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.41 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.42 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.43 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.44 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
- 62.171.194.45 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)
From them flows a steady, deep, inexhaustible river of childish vandalism into the encyclopedia. After quite some time spent sampling, I haven't found one single good edit from any of them, though I can't swear that one isn't hiding out somewhere, obviously. All the warnings posted on all the talkpages by all the ambitious Wikipedians have an air of pathos, if you read them all together. Don't we have enough to do? If the range is indeed static, and the sole purview of enthusiastically scrawling children, can it be blocked wholesale, by someone who understands the art of range blocking? Or can somebody who's better than me at navigating the intarweb find their way to someone in a position of responsibility at the UK Internet for Learning? Or, does anybody have any other suggestions? Please? --Bishonen | talk 17:03, 25 November 2005 (UTC)
- My thought is to block all of these and then wait for some feedback from any legitimate users. It seems to be a network which would go to all primary schools in the UK when it is built out. Fred Bauder 17:14, 25 November 2005 (UTC)
- From whois "All abuse reports should be sent to abuse at ifl.net Fred Bauder 17:17, 25 November 2005 (UTC)
- There may be a handful of good edits in there - see the recent by User:62.171.194.12. Which is not to say that I object to massive blockage. FreplySpang (talk) 17:21, 25 November 2005 (UTC)
- Further to Fred Bauder, the whois indicates that Research Machines have sub-allocated 62.171.194.0/23 to ifl.net. --GraemeL 17:32, 25 November 2005 (UTC)
- Ahh... I ... see. (Not.) Could somebody get on it, please? Bishonen | talk 18:01, 25 November 2005 (UTC)
- Further to Fred Bauder, the whois indicates that Research Machines have sub-allocated 62.171.194.0/23 to ifl.net. --GraemeL 17:32, 25 November 2005 (UTC)
- See Classless Inter-Domain Routing. 62.171.194.0/23 is a range of 512 IP addresses from 62.171.194.0 to 62.171.195.255. It's also the format that you use for range blocking on the block page. Personally, I would like to see a greater consensus here before we take action to indef block such a large range. --GraemeL 18:09, 25 November 2005 (UTC)
- Do it. Just make sure the blocking admin has an email set and send a complaint at the same time.Geni 18:27, 25 November 2005 (UTC)
- See Classless Inter-Domain Routing. 62.171.194.0/23 is a range of 512 IP addresses from 62.171.194.0 to 62.171.195.255. It's also the format that you use for range blocking on the block page. Personally, I would like to see a greater consensus here before we take action to indef block such a large range. --GraemeL 18:09, 25 November 2005 (UTC)
- OK, I blocked 62.171.194.0/23 indefinitely. I sent an email to their abuse desk advising them of the block and the reasons that it was implemented. I also asked them if they subnet in any way that would enable us to reduce the size of the block and if they had any additional comments. --GraemeL 19:43, 25 November 2005 (UTC)
- :-) Outstanding. Thanks! Bishonen | talk 00:32, 26 November 2005 (UTC)
- Make sure that indefinitely means indefinitely and not infinitely! Redwolf24 (talk) Attention Washingtonians! 05:15, 26 November 2005 (UTC)
- :-) Outstanding. Thanks! Bishonen | talk 00:32, 26 November 2005 (UTC)
- OK, I blocked 62.171.194.0/23 indefinitely. I sent an email to their abuse desk advising them of the block and the reasons that it was implemented. I also asked them if they subnet in any way that would enable us to reduce the size of the block and if they had any additional comments. --GraemeL 19:43, 25 November 2005 (UTC)
Collateral damage
I received an email indicating that this block is also affecting some libraries in the UK. I still haven't heard back from the ISP and I asked the user that mailed me to try and get the IPs of the library computers to see if I can work round that range with the block. Is this worth maintaining if we're going to cause collateral damage? --GraemeL 19:02, 29 November 2005 (UTC)
- Sounds promising. They must divide that block of addresses up. Fred Bauder 20:15, 29 November 2005 (UTC)
- If we can get the library range (i.e. if the vandal fonts are, indeed, static), we can except them, but we need to be aware of the fact that libraries may be one of the sites of vandalism, and the only thing denied them now is the ability to edit. We're still good for researching on. The amount of spew the range was producing was truly staggering. Geogre 14:02, 30 November 2005 (UTC)
I'm taking a wikibreak, so I removed the block on this range. Feel free to re-block it. --GraemeL 23:10, 30 November 2005 (UTC)
Recent activity
In order to try to get a handle on what these folks have been up to, I've documented the contributions from all the IP addresses in this range (addresses with no contributions are not shown):
Address | Vandalisms | Other |
---|---|---|
62.171.194.6 | ||
62.171.194.7 | ||
62.171.194.8 | ||
62.171.194.9 | ||
62.171.194.4 | (revert) (revert) (revert) (revert) (revert) (revert) | |
62.171.194.10 | ||
62.171.194.11 | ||
62.171.194.12 | (questionable) | |
62.171.194.13 | ||
62.171.194.37 | (revert) | |
62.171.194.38 | (new) (revert) | |
62.171.194.40 | ||
62.171.194.42 | (revert) (revert) | |
62.171.194.43 | ||
62.171.194.44 |
The "other" edits are good-faith attempts to create content, or at least, aren't clear vandalism (some of them have been reverted, some have not). Many of them are reversions of other edits from this range. The overall pattern seems to me that of schoolkids teasing each other using Misplaced Pages, and some other people (older students?) reverting them and sometimes adding content. The vandalism seems to come in short spates, and I'm guessing the IPs might correspond to workstations in a computer lab or school library. My gut feeling is not to re-block the IP range, but since the vandalism doesn't come very fast, to block the individual IPs as needed for short periods (but without separate warning). Demi /C 08:50, 6 December 2005 (UTC)
Why not hold an election?
Can someone official, e.g. ArbCom or Jimbo or related, please indicate the reasoning behind not having an election for the next arbitration committee? I find it worrying that neither has so far been willing to comment on this. At present, the impression is that without having the proper connections, one cannot become an arb. There has been considerable opposition to appointing an ArbCom rather than electing one, and ignoring this without bothering to comment on it will likely decrease community support for the ArbCom as a whole. Radiant_>|< 19:51, 26 November 2005 (UTC)
- For those unfamiliar with ArbCom, answers to the following questions would also be helpful:
- Has ArbCom been elected or appointed in the past?
- Has ArbCom been doing a good or a bad job in the past, and how this is related to the change of election/appointment procedure?
- How long are ArbCom cadencies?
- Is it possible to remove somebody from ArbCom? If so, how?
A possible solution might be to have ArbCom appointed one year and elected another. After several years we should be able to judge which method is better.--Piotr Konieczny aka Prokonsul Piotrus 20:53, 26 November 2005 (UTC)
- 1.a mixture of apointements and elections at various times.
- 2.Imposible to objectively judge. Only one descission has been rejected by the community
- 3. in thoery 1 to 3 years. In practice untill they quit which tends to be a lot shorter
- 4.It could probably be done through getting the other arbcom memebers to vote them off or a descission by the board. It would not be easy. It hasn't come up yet though.Geni 21:35, 26 November 2005 (UTC)
- I should point out in relation to (2), that criticism of Arbs and the ArbCom has increased significantly since Jimbo's recent appointements. But the situation is more complex than that, it's certainly not a straight "post hoc ergo propter hoc". The answer to (4) is almost certainly "no", given that it's already next-to-impossible to get deadminned. Radiant_>|< 23:27, 26 November 2005 (UTC)
- I think 4 would just about be posible. Apointments would make it harder bit still doable. It would be likely to involve a fair bit of damage to wikipedia in the process though.Geni 23:54, 26 November 2005 (UTC)
- The AC cannot comment on this with any authority because we don't know what the procedure will be. All I can say without wild speculation is that if you'd like to be considered, you should probably put a statement on the candidate statements page. Mindspillage (spill yours?) 22:23, 26 November 2005 (UTC)
- Once again, that is more information than was previously known, so thanks. So who does know? Only Jimbo? The board? Some hidden discussion someplace? Since this affects the entire community, I think it's patently unreasonable to keep the entire community in the dark on this. I've seen several candidates withdrawing because of the uncertainty; it gives the appearance that most people putting up candidate statements will not actually be considered at all, with no reasons given. Radiant_>|< 23:27, 26 November 2005 (UTC)
- A very slight clarification of geni's comment, which I think bears explaining - the Committee has never been directly elected. There have been two times (out of five total) when Jimbo was appointing people to it where he asked the community to use the "voting" software to suggest who he should appoint; both times, he happened to appoint along the same lines as the "vote" suggested, but it wasn't an election per se.
- James F. (talk) 23:02, 26 November 2005 (UTC)
- And has this system produced any undesirable results, apart from the infamous "disendorsements" page that everybody agrees should not be started this year? Radiant_>|< 23:27, 26 November 2005 (UTC)
- Well, out of all the arbitrators elected last time, only three served out the full first year of their terms. That's a bit of a botch there. Phil Sandifer 23:29, 26 November 2005 (UTC)
- I am aware of that. Do you believe that arbiters appointed by Jimbo would be less subject to burnout? If so, why? Radiant_>|< 23:51, 26 November 2005 (UTC)
- Radiant - Please check out User talk:Simon Chartres (... not everyone agrees to your common sense point) Raul654 23:31, 26 November 2005 (UTC)
- Okay, but I think we can ignore that sock, and anyway that wasn't my point. I ask again, "has this system produced any undesirable results"? Radiant_>|< 23:51, 26 November 2005 (UTC)
- Hello to you all. I think we can assume good faith for Jimbo :) Besides that I 'd like to point out, a part of his statement "with the appointments made in consultation with the existing and former ArbCom members and the community at large, followed by confirmation votes from the community requiring some supermajority". +MATIA ☎ 23:41, 26 November 2005 (UTC)
- assumeing good faith is one thing. Assumeing correct judgement is another.Geni 23:50, 26 November 2005 (UTC)
- Current suggestion is 50%, which is not really a supermajority. To my best knowledge, no consultation of the community at large has occured. Radiant_>|< 23:51, 26 November 2005 (UTC)
- If this wasn't clear - the steps I described above (where I mentioned the 50% number) is only my best guess. Jimbo has described the process informally several times, and if memory serves, he used supermajority in one description and majority in another. Raul654 23:59, 26 November 2005 (UTC)
- So even Jimbo hasn't decided what's being done, then? A little keeping-the-community-in-the-loop would be really, genuinely helpful. I wonder where he is planning to conduct the consultation with the community before announcing his choices, for example? Can the ArbCom tell us what discussions they have so far had (the message from MATIA implies some), and who they are recommending? -Splash 02:52, 27 November 2005 (UTC)
- If this wasn't clear - the steps I described above (where I mentioned the 50% number) is only my best guess. Jimbo has described the process informally several times, and if memory serves, he used supermajority in one description and majority in another. Raul654 23:59, 26 November 2005 (UTC)
- Well, out of all the arbitrators elected last time, only three served out the full first year of their terms. That's a bit of a botch there. Phil Sandifer 23:29, 26 November 2005 (UTC)
- I second Splash's request. I should also point out that most of the questions in this section and the previous have not in fact been answered by the Powers That Be. Radiant_>|< 16:29, 27 November 2005 (UTC)
- I agree with Splash too (and I must note that the message I've cited was given in the previous section by Raul654). Reading that message (and unless or until something else is announced) I think that Jimbo will select some candidates (from the volunteers that would go for an election), and then a second selection will be done by JW, ArbCom and the community in general (that's what I understand, perhaps I'm wrong). I also think that within the next days some announcement will be made that will clarify the things better (WP is not a crystal ball, am I? ) +MATIA ☎ 18:20, 27 November 2005 (UTC)
- the statement was made on the 20th of october. we've been waiting for some form of clarification for some time.Geni 18:26, 27 November 2005 (UTC)
- Well, at least here, we 've shown that there are good reasons for the clarifications to be given and there's a consensus (or something like it) among many editors asking for them. +MATIA ☎ 18:37, 27 November 2005 (UTC)
- I we had managed to establish that about two weeks ago.Geni 19:06, 27 November 2005 (UTC)
- Now if only a consensus on the part of the community that Jimbo should say something had particular meaning. Phil Sandifer 19:26, 27 November 2005 (UTC)
- the statement was made on the 20th of october. we've been waiting for some form of clarification for some time.Geni 18:26, 27 November 2005 (UTC)
I think we should probably avoid elections for arbitrators altogether. They're just a bunch of people who make commonsense decisions when the normal dispute resolution process has failed. There aren't that many people both capable of and willing to do the job. Jimbo should just name some names of people that he would be happy with acting on his behalf, and we can forget about it for the next few months. The elections have been unnecessary and, in my opinion, probably only made things worse within the community. --Tony Sidaway|Talk 09:12, 28 November 2005 (UTC)
- They're just a bunch of people who make what they may claim and even believe are commonsense decisions. But their idea of common sense may not be the same as mine or yours. Why should you or I or anyone submit to arbitrarily selected arbiters of what's "common sense"? I know that WP is not a democracy, but I hope decisions aren't made by a self-perpetuating oligarchy. -- Hoary 09:42, 28 November 2005 (UTC)
- Have you read Misplaced Pages:Arbitration Committee Elections December 2005/Straw poll? There's a large (and growing) consensus for direct elections; it'd be a disaster to carry forward with Jimbo only giving us his choices (and what happens if his choices don't get the majority vote needed; will he renominate them again or reconsider those he passed over, or will he leave that seat unfilled?). The worst part is that the details of how this election will proceed are virtually unknown to anyone except Jimbo. And the election is next month! —Locke Cole 09:59, 28 November 2005 (UTC)
I think some people are forgetting that we are all here because Jimbo lets us be here. Electing arbitrators is not a right conferred to us by our citizenry in Misplaced Pages land. It's times like this that we should be thanking him for creating and maintaining Misplaced Pages, not making bold demands about how he should exercise his rightful authority over it. That said, I would like to echo Tony Sidaway's point. Given the trainwreck that was the last elections, I don't see the need for a repeat. Let Jimbo appoint some trustworthy folks so we can all move past the Wiki-politics and write an encyclopedia. :-) --Ryan Delaney 10:39, 28 November 2005 (UTC)
we are here because Jimbo lets us and because readers and community members donate money for the servers. I would definitely prefer some transparency here. If I began to feel WP was becoming a "self-perpetuating oligarchy" I would be less enthusiastic about investing time and content. If enough people felt like that, the project would be damaged (WP is, after all, about content). dab (ᛏ) 10:55, 28 November 2005 (UTC)
- I'm another who feels just like that. As noted
aboveelsewhere, I've withdrawn from the process because I refuse to be part of something that has not been explained, never mind justified. Filiocht | The kettle's on 11:02, 28 November 2005 (UTC)- I thought we were here as volunteers (and I don't overlook neither Jimbo's contributions - including that he is the founder, nor donations - most of them are perhaps by volunteers). +MATIA ☎ 11:23, 28 November 2005 (UTC)
Put another way, I think Misplaced Pages editors should not feel that their contributions to Misplaced Pages (monetary or otherwise) entitle them to a "Republican form of government" or anything else. Like MATIA said, we are volunteers, and donations are donations; they aren't payment for services. When someone donates to the foundation, she does not think she is purchasing a vote in a bureaucracy. If public elections for arbitrators are manifestly harmful, because they waste time and are highly contentious for no beneficial reason but that people tend to feel strongly about the Wikipolitics, then I would greatly appreciate it if Jimbo would "cut through the bullshit" as it were and just make appointments. I think these are the real questions in this disagreement:
- Are we "owed" anything by the WikiMedia foundation, in particular a vote in elections of officers? Why?
- Given the high cost, what would be gained by public elections of arbitrators, anyway?
--Ryan Delaney 17:11, 28 November 2005 (UTC)
- Well said. We're not owed particapation in selecting Arbcom membership and I still maintain that the projectable level of debate (where ever it occurs) will do more harm than good. Rx StrangeLove 06:54, 29 November 2005 (UTC)
- Indeed. First and foremost I'm here to help write an encyclopedia. Regardless of what I've contributed, this isn't my website and I'm not owed anything. If Jimbo wants to make appointments, so be it. --Kbdank71 18:28, 29 November 2005 (UTC)
- Well said. We're not owed particapation in selecting Arbcom membership and I still maintain that the projectable level of debate (where ever it occurs) will do more harm than good. Rx StrangeLove 06:54, 29 November 2005 (UTC)
I think this thread is getting off topic a bit, the only real point of the election IMO is to select people who will make the arbcom into something into something users feel will be authoritative enough to trust regarding enforcing/interpreting policy in disputes, much like a court(if people didn't respect the authority of courts, they'd be ignored, as some users do regarding the arbcom). If this happens via election or appointment, i'm happy, but I think the outcry here is it'll only happen through election and Jimbo stays on the sidelines as an advisor rather than any kind of participant. karmafist 22:56, 5 December 2005 (UTC)
Permanent protection of George W. Bush
At present, there are a set of admins who are effectively seeking to permanently protect George W. Bush. Should it be permanently protected? Yes, or no? No daydreaming about semiprotection or other non-existent MediaWiki features. The article has been protected for most of the last 24 hours and is reprotected every few edits. If you can't edit pages in a Wiki, it's not a Wiki is my personal feeling. Should I just be leaving this page protected until 2009? It's a yes or a no. -Splash 21:20, 1 December 2005 (UTC)
- Are you suggesting we unprotect Template:In the News? If you can't edit pages in a wiki...? Even if someone slaps a penis on there a few times a day? I say we leave it protected til the Devs give us a better option. It's not a daydream, it's a requirement. --Golbez 21:24, 1 December 2005 (UTC)
- That's the main page of a high-profile website. There is no analogy. But I read your answer as a yes to 2009. Semiprotection is a requirement that is firmly in daydream territory, and I'm trying to deal with right now. The Devs have never implemented a major new software feature overnight just because some people wanted them to. -Splash 21:28, 1 December 2005 (UTC)
- The proper analogy would be to one of the articles on the main page, linked from the FA, ITN, or DYK. They are never protected, precisely because they are so high traffic. And with good reason. (There is no reason anyone viditing the main page would ever really end up at the ITN template page, btw.) Dmcdevit·t 21:42, 1 December 2005 (UTC)
- A particularly good example of that analogy would be a few weeks back when Cheese was our main-page article. That gets silly amounts of vandalism as it is, and it was more than a little ridiculous that day. But we lived to tell the tale, without protection I think. -Splash 21:45, 1 December 2005 (UTC)
- Splash, almost everyone agreed that George W. Bush should not be fully protected until 2009. However, that isn't what is being proposed on that talk page. Titoxd 22:01, 1 December 2005 (UTC)
- The import of the talk page is that it will be protected whenever vandals hit it. Which will be until sometime in 2009. The good-edit-per-24-hours idea was discarded very quickly by Jtdirl in reprotecting it, and there's no other offer. -Splash 22:16, 1 December 2005 (UTC)
- No other offer? We're trying to draft something to show the devs there. It will never be implemented if nothing is agreed on to implement. Titoxd 22:29, 1 December 2005 (UTC)
- That emphatically doesn't deal with what to do with the article today. Or until the devs implement something they aren't to our knowledge working on. Can you point out to me the last time that a comletely new mediawiki feature was added and how long it took between request and provision? This is why I deliberately asked for "no daydreaming". -Splash 22:50, 1 December 2005 (UTC)
- No other offer? We're trying to draft something to show the devs there. It will never be implemented if nothing is agreed on to implement. Titoxd 22:29, 1 December 2005 (UTC)
- The import of the talk page is that it will be protected whenever vandals hit it. Which will be until sometime in 2009. The good-edit-per-24-hours idea was discarded very quickly by Jtdirl in reprotecting it, and there's no other offer. -Splash 22:16, 1 December 2005 (UTC)
- Splash, almost everyone agreed that George W. Bush should not be fully protected until 2009. However, that isn't what is being proposed on that talk page. Titoxd 22:01, 1 December 2005 (UTC)
- A particularly good example of that analogy would be a few weeks back when Cheese was our main-page article. That gets silly amounts of vandalism as it is, and it was more than a little ridiculous that day. But we lived to tell the tale, without protection I think. -Splash 21:45, 1 December 2005 (UTC)
- The proper analogy would be to one of the articles on the main page, linked from the FA, ITN, or DYK. They are never protected, precisely because they are so high traffic. And with good reason. (There is no reason anyone viditing the main page would ever really end up at the ITN template page, btw.) Dmcdevit·t 21:42, 1 December 2005 (UTC)
- That's the main page of a high-profile website. There is no analogy. But I read your answer as a yes to 2009. Semiprotection is a requirement that is firmly in daydream territory, and I'm trying to deal with right now. The Devs have never implemented a major new software feature overnight just because some people wanted them to. -Splash 21:28, 1 December 2005 (UTC)
- What admins are advocating a permanant protection? Phil Sandifer 21:33, 1 December 2005 (UTC)
- A group acting together, but the protection log show frequent protection by Hall Monitor in particular, Golbez more recently and at least several editors on Misplaced Pages talk:Semi-protection policy. All this suggests I should see the numbers in favour and let it slide, but I dont think they are right. I deliberately said effectively, since whenever I point out 2009, someone says "well then until the devs invent something", which is basically indefinitely far in the future, and certainly not within any sensible timescale. -Splash 21:37, 1 December 2005 (UTC)
- Although semi-protection seems to me useful (Though misplaced - don't we have a place for feature requests?), permanant protection seems to me an express violation of policy. Phil Sandifer 21:51, 1 December 2005 (UTC)
- A group acting together, but the protection log show frequent protection by Hall Monitor in particular, Golbez more recently and at least several editors on Misplaced Pages talk:Semi-protection policy. All this suggests I should see the numbers in favour and let it slide, but I dont think they are right. I deliberately said effectively, since whenever I point out 2009, someone says "well then until the devs invent something", which is basically indefinitely far in the future, and certainly not within any sensible timescale. -Splash 21:37, 1 December 2005 (UTC)
- Until this becomes "the encyclopedia that only admins can edit", then no, it shouldn't be permanently protected. --Kbdank71 21:51, 1 December 2005 (UTC)
- Seconded. --LV 21:56, 1 December 2005 (UTC)
- I believe it should remain unprotected (except for page moves). For one thing, it's an article that needs regular updates since the topic itself is dynamic, and we can't reasonably restrict editing ability only to admins. Yes, the vandalism there is a nuisance, but one we can live with. Antandrus (talk) 21:57, 1 December 2005 (UTC)
- I don't think permanent protection is necessary, I agree with Antandrus here. But I'd encourage anybody who took a minute to think about this particular request to head to Misplaced Pages:Semi-protection policy with an open mind and take a look at the proposal. · Katefan0/my ridiculous poll 21:59, 1 December 2005 (UTC)
- Agree with those who oppose protection: vandalism is just bothersome, protecting the page would undermine a crucial goal. One represents temporary damage to the encyclopdia, the other represents useful contributions permanently lost. Christopher Parham (talk) 22:02, 1 December 2005 (UTC)
- As before, I think we should leave this page unprotected and continue reverting vandalism. It's so high-profile that lots and lots of admins and editors have it on their watchlist, and no vandalism is going to stay there for long. —Cleared as filed. 22:13, 1 December 2005 (UTC)
- In a sick sort of way, the vandalism is actually good for us. The very reason (most) people write crap in there is because they don't believe the "anyone can edit" thing. The vandalism is annoying, but it will lead to more good contributions in the long run.--Sean|Black 22:23, 1 December 2005 (UTC)
- As before, I think we should leave this page unprotected and continue reverting vandalism. It's so high-profile that lots and lots of admins and editors have it on their watchlist, and no vandalism is going to stay there for long. —Cleared as filed. 22:13, 1 December 2005 (UTC)
I am going to float an idea, which may just be crazy (and don't be afraid to say so), but how about some form of psuedo-protection. For example, protect the GWB page, but create a GWB/temp page that is an open copy of the page and have admins frequently incorporate the useful changes into the real GWB page. This wouldn't accomplish very much (since vandals might just as well attack the temp page), but it would ensure that the main GWB page consistently presents a good face to the world. Thoughts? Dragons flight 22:24, 1 December 2005 (UTC)
- The problem with such an idea is that it already was tried, and it was quickly shot down. Also, there is a similar proposal, Requests for publication, that wants to do that. Titoxd 22:29, 1 December 2005 (UTC)
- Specifically, the idea was to have a protected "good version" that admins would routinely add the useful changes to. That created the eqivalent of a copy-and-paste move, thus violating the GFDL.--Sean|Black 22:32, 1 December 2005 (UTC)
- No permanent protection. Just absolutely, HELL NO. --Phroziac . o º 22:34, 1 December 2005 (UTC)
- Offer an alternate solution then. Just saying no to the offered one isn't good enough anymore. --Golbez 22:37, 1 December 2005 (UTC)
- Why isn't it good enough anymore? I know it's bad to have vandalism on such a highly visible article, but permanent protection would be worse. If you are tired of reverting, drop the page from your watchlist and let us revert it. No one is forcing you to revert it. There are plenty of others waiting in the wings. --LV 22:47, 1 December 2005 (UTC)
- We don't have an alternative, adn we've to decide what to do or not with the tools that are available to us, as well as pestering for new ones. -Splash 22:50, 1 December 2005 (UTC)
- LV, all this talk about permanent protection, with all due respect to Splash, is a little diversionary. The real proposal is at Misplaced Pages:Semi-protection policy. I doubt anyone is seriously advocating permanently protecting the article, or if they are are they're a serious minority. Unfortunately, this is distracting from more discussions on a policy that has more support. · Katefan0/my ridiculous poll 22:52, 1 December 2005 (UTC)
- No, it's no distraction. The article is spending an increasing proportion of the time protected, and I think the majority of the last 24. It has been protected numerously many times over the same period. Deciding how to handle the problem, here and now with what we've got is as important and more important than thinking of new MediaWiki features to do the job better. -Splash 23:00, 1 December 2005 (UTC)
- It is a distraction to frame this issue in the alarmist way it's being framed. Nobody, that I know of at least, has proposed permanently protecting this article. You're suggesting that it's being protected for longer periods, but that's not the same thing. · Katefan0/my ridiculous poll 23:03, 1 December 2005 (UTC)
- As I understand the options, they are
- Protect until the vandals go away
- Protect until the devs invent semi-protection
- That sounds pretty
permanentindefinite to me. -Splash 23:08, 1 December 2005 (UTC)- I realize you're suggesting that certain folks' actions on the page in effect mean they are pushing for permanent protection. (I'm not sure they'd agree with that, but that's for them to say.) My point is that the way this thread is being framed is so alarmist as to be distracting. Nobody has said the article should be permanently protected, at least not that I've seen (I'm willing to be proven wrong), yet this thread rattles on, while discussion on a real policy proposal gets lost in the hubbub. · Katefan0/my ridiculous poll 23:12, 1 December 2005 (UTC)
- As I understand the options, they are
- It is a distraction to frame this issue in the alarmist way it's being framed. Nobody, that I know of at least, has proposed permanently protecting this article. You're suggesting that it's being protected for longer periods, but that's not the same thing. · Katefan0/my ridiculous poll 23:03, 1 December 2005 (UTC)
- No, it's no distraction. The article is spending an increasing proportion of the time protected, and I think the majority of the last 24. It has been protected numerously many times over the same period. Deciding how to handle the problem, here and now with what we've got is as important and more important than thinking of new MediaWiki features to do the job better. -Splash 23:00, 1 December 2005 (UTC)
- LV, all this talk about permanent protection, with all due respect to Splash, is a little diversionary. The real proposal is at Misplaced Pages:Semi-protection policy. I doubt anyone is seriously advocating permanently protecting the article, or if they are are they're a serious minority. Unfortunately, this is distracting from more discussions on a policy that has more support. · Katefan0/my ridiculous poll 22:52, 1 December 2005 (UTC)
- Semi-protection as suggested above, is quite a good idea as it opens up editing to pages in more of a wiki-manner to pages that were fully closed before. There's a few things to iron out, though.
- A certain type of protection could give someone an advantage in an edit war. One person can be locked out with the other continuing their editing. You can punish an admin for editing a protected article during an edit war they are involved in, but it's harder to block someone for editing an article someone else protected while you were unaware.
- The tabs still doesn't show whether an article is fully protected or just protected from moves. If we were to make more levels of protection, one need to be easily able to see how an article was protected without slugging through logs and stuff.
- Mgm| 23:35, 1 December 2005 (UTC)
- I think that it's obvious that permanent protection is fundamentally un-wiki. That is all that needs be said against the idea. James F. (talk) 00:26, 2 December 2005 (UTC)
- I don't believe anyone here is lobbying for permanent protection. What has been said is that the current protection model is broken, and that some sort of "semi-protection" is needed. Hall Monitor 00:33, 2 December 2005 (UTC)
- More specifically, what has been said is that this article should remain protected until that happens. — this is a call for permanent (indefinite, if you like) protection of the article. -Splash 00:37, 2 December 2005 (UTC)
- Well, then let's end the confusion. No. George W. Bush should not be protected indefinitely, we should keep doing what we're doing (which is leaving it move-protected with temporary full protection during vandal attack waves), until we decide on the semi-protection policy. Titoxd 01:40, 2 December 2005 (UTC)
- That said, semi-protection is a completely separate issue that should be discussed post-haste, since the current situation isn't pretty. Titoxd 01:42, 2 December 2005 (UTC)
- More specifically, what has been said is that this article should remain protected until that happens. — this is a call for permanent (indefinite, if you like) protection of the article. -Splash 00:37, 2 December 2005 (UTC)
- I don't believe anyone here is lobbying for permanent protection. What has been said is that the current protection model is broken, and that some sort of "semi-protection" is needed. Hall Monitor 00:33, 2 December 2005 (UTC)
- I think that it's obvious that permanent protection is fundamentally un-wiki. That is all that needs be said against the idea. James F. (talk) 00:26, 2 December 2005 (UTC)
I'm adding another "Hell no" vote to permanent protection. Permanent protection is worse than vandalism. The current situation isn't great, but permanent protection cures the disease by killing the patient. --Ryan Delaney 22:58, 1 December 2005 (UTC)
At this point, the article is protected without as much as a "protected" template. This is not acceptable. If you protect it, say it is "temporarily proctected due to vandalism". If the vandals persist, "temorarily" may mean "for a longish time", but that's still temporary. It's just Misplaced Pages as usual. I agree with permanent protection of the Main Page, since that's a special case, but there is no reason to extend this to individual articles. so, "hell, no", from me too. Semi-protection may be useful, but articles will also be semi-protected temporarily, at least in principle. dab (ᛏ) 11:09, 2 December 2005 (UTC)
- At that particualr moment in time, it was only protected against moves, for which we have no template. -Splash 13:55, 2 December 2005 (UTC)
- Oh dear, I shouldn't have interferred if I didn't know what I was doing, then. my apologies :( I don't suppose there will be a need to move the article anytime soon. dab (ᛏ) 14:08, 2 December 2005 (UTC)
Just to chip in my two cents here, I am adamently against any type of protection at all. Flcelloguy (A note?) 22:40, 2 December 2005 (UTC)
What about implementing a fairly simple technical solution in mediawiki: protection from anon edits? Just as we had eventually introduced protection from moves, this would be another useful solution. Technical note: make sure the page can be protected in several different ways at the same time.--Piotr Konieczny aka Prokonsul Piotrus 15:30, 3 December 2005 (UTC)
- I think almost everyone agrees that having such tools would be useful. The main disagreement is over what to do until the developers give us this option, which is likely some time away. - SimonP 15:56, 3 December 2005 (UTC)
I strongly oppose permanent protection. --Ixfd64 03:26, 6 December 2005 (UTC)
That page absolutely does not need permanent protection, indeed it should almost never be protected and then only for a short period. This is a wiki, and that is a popular article. That's why it gets vandalised more. It's on nearly everybody's watchlist, so just revert vandalism and carry on editing. --Tony Sidaway|Talk 12:16, 9 December 2005 (UTC)
User:Chooserr and date eras
Chooserr (talk · contribs) has started an anti-BCE/CE drive, and has started removing this era on a number of pages. In some places, the user's statement that the article started out with BC/AD is true. However, I found this user trying the same argument on articles for which it isn't true — Al-Hirah (edit | talk | history | protect | delete | links | watch | logs | views). Keep an eye on this account's edits so that we don't have another jguk to deal with. --Gareth Hughes 18:45, 3 December 2005 (UTC)
- See also Misplaced Pages:Administrators' noticeboard/3RR#User:Chooserr. --Gareth Hughes 21:34, 3 December 2005 (UTC)
- And there are just as many (if not more) article which originally used BCE/CE, yet now use BC/AD. It is far better to leave article as they currently stand, and if a change is desired, obtain consensus on the talk page. Sortan 21:38, 3 December 2005 (UTC)
Keep an eye also on 212.134.22.141, who just went on a short anti-BCE/CE drive. —Bunchofgrapes (talk) 22:03, 3 December 2005 (UTC)
For the record, I paroled Chooserr from his 24-hour 3RR block on the condition that he not make any changes to date system for those 24 hours. If, before that period expires, he breaks his promise, the 24-hour 3RR block should be immediately reinstated. -- SCZenz 22:33, 3 December 2005 (UTC)
I also think it might be an oversight that policy does not explicitly state articles should be left as they currently are. If it did say this, we could treat all such problems as simple vandalism after a warning. -- SCZenz 22:33, 3 December 2005 (UTC)
- It does already (well, the style guide does say they should be left as started) and actually, you still can't per blocking policy - David Gerard 19:01, 4 December 2005 (UTC)
- The style guide doesn't seem to say that about dates, that I've found—if it does, can you tell me where? Anyway, the problem with Chooserr is that he's changing pages that originally used AD and BC, which he feels is justified by the "left as started" clause. I think "status quo" would be a more sensible thing. Finally, you're absolutely right about blocking policy—saying that was a newbie admin error, and I should have realized that was a mistake. -- SCZenz 19:13, 4 December 2005 (UTC)
- Then, until the policy is changed (and given it's a hot issue it's unlikely just changing the page will pass unnoticed) he's actually acting according to