The owners of http://www.celebritythegame.com claim ownership of the name "Celebrity" as a game, and are publishers of a packaged version. In as much as I can find any sources provably about the game they mainly discuss the rules (as if it were a long-standing parlour game) and do not mention this publisher. I don't mind linking to the publisher, but I can't see how the claim of ownership holds up. More importantly, I am having real trouble finding non-trivial sources about it, I can't prove or disprove the claim of ownership, and the article clearly violates WP:NOT a howto or game guide - it is a set of rules for a game, not a discussion of the game. I can't find any significant discussion of the game, only rules. The OTRS complainant will, I think, be unhappy about the rules being on Wikipedia (hard to sell what's free for download) but that may be irrelevant. I honestly have no idea what to do for the best here. Guy (Help!) 22:09, 9 May 2007 (UTC)
All (Free/GFDL) Images Need to Be Transferred to Commons
How do I start a vote/movement in order to move all images to Commons? This requires that any images uploaded must have the person sign up for an account at commons. Any support/criticism is well respected. Real9622:15, 9 May 2007 (UTC)
Commons does not accept fair use imagery. Also, why would we want to push our users to upload their free imagery to a failed project? Matthew22:16, 9 May 2007 (UTC)
Matt, 1.) Reduce server overloads on Wikipedia 2.) Reduce image backlogs on Wikipedia 3.) Have images easily to search with Tango's Mayflower, etc.Real9622:19, 9 May 2007 (UTC)
I just can't consider it feasible. I truly consider commons a failed project, primarily because I believe it's run badly and secondly because the foundation is incapable of making a clear statement on copyright, so we could end up having a ton of images deleted from commons.... that would end up having to be uploaded back here. Matthew22:24, 9 May 2007 (UTC)
Commons has way over 1M images. I wasn't aware that was a typical failure criterion. But then I'm biased, I think Commons is swell. On the other hand I don't think we want to push ALL images there, only the ones that have free licenses and clear provenance information. ++Lar: t/c22:27, 9 May 2007 (UTC)
Commons will not, under any circumstances, accept fair-use images. That's Foundation-level policy, so you'd have to talk to them about changing that. In terms of free images, well, if you see one that needs moving, move it! SeraphimbladeTalk to me22:22, 9 May 2007 (UTC)
(1) You realise it's the same set of servers? (2) Moving the backlogs elsewhere doesn't actually fix them. --pgk06:14, 10 May 2007 (UTC)
(EC) The Wikimedia Commons is what its name suggests; a commons for media to be shared among all Wikimedia Foundation websites. They also only accept images under Creative Commons or GFDL copyrights or items that exist in the public domain. There should be no reason to prevent users from uploading media to the English Wikipedia htat will never be used on any other project. Also, I do not see how the Commons is a failed project. I have something that I would not upload to the commons because I fear it may be abused by other projects, despite my attempts at trying to get the content released under the GFDL.—Ryūlóng (竜龍) 22:22, 9 May 2007 (UTC)
(ECx3)Good idea, in theory does not always equal good idea in reality. One huge problem: fewer admins on commons means fewer people to work on problem pages (e.g., pure vandalism - a page with some random guy's dick, falsely claimed licenses, etc.) If you think point 2 (remove image backlogs on en) is bad, imagine what it will be on commons. However, if there could be some mass policy change allowing all en admins to become commons admins (which I don't think they now can), it might be possible, though there would certainly be some growing pains. The Evil Spartan22:25, 9 May 2007 (UTC)
While I appreciate what your trying to do with this idea, I'd oppose it b/c of what it would mean for fair use images and b/c it will require people to use two accounts to do anything with images. --Alabamaboy 22:38, 9 May 2007 (UTC)
I have heard from some people on other projects that images from their projects (i.e. wikipedia-es - see this) derive their free images/GFDL images on commons. In theory, I am talking about free images, not fair use. Real9622:44, 9 May 2007 (UTC)
Exactly what i was talking about in vandalism images: Image:KhaliSUCKS.JPG. tough backlog (BTW, AIV could use some help, and I can't access the other user's images because I'm in a public library and have children nearby). The Evil Spartan22:52, 9 May 2007 (UTC)
Instead of all the work involved in moving and deleting files, why not make commons into a database of files that exist on other projects, and at the same time, allow every project to access media files from any other project. So if I'm looking for a picture of a Japanese bridge, I'd go to commons, find a link to the picture on Japanese Wikipedia, confirm that the rights apply to my own project, and add a link to my page like this [[ja:Image:Great Soto Bridge.jpg]]. Of course, this would be more work for the developers to set up, but once established, it would be easier for everyone else. -- Samuel Wantman 23:34, 9 May 2007 (UTC)
Because that would be infinately more work then telling people to move their free images to commons. Its alwaqys been policy that GFDL/free images need to go to commons, people were just being stupid and ignoring it. -Mask?23:47, 9 May 2007 (UTC)
It wouldn't be more work, it would be less. People would just upload files in the project they are in, and it would automatically be transcluded to commons if it is tagged as a GFDL/free image. When you went to commons, you'd see a complete set of images. They would just have to be categorized (this is much less work than copying them over). When you find the image you want you just transclude it into your own article from whichever wikiproject it resides. This is the same amount of effort as it currently takes to use a commons image. So the only change in the amount of work would be removing all the copying and deleting. -- Samuel Wantman 23:58, 9 May 2007 (UTC)
the big stumbeling blocks for moveing all free content to commons are 1) inertia 2)lack of SUL 3)need for screening to make sure things are not copyvios 4)slightly different policies with regards to images 4)different objectives 5) the need to be able to protect images to prevent vandalism.Geni00:53, 10 May 2007 (UTC)
Real96, you really don't understand this whole thing (no offense). Images that are free or acceptable for Commons are usually re-uploaded there by another user (who either wishes to use it on another project or just thinks it would be of use on Commons). It's an option as it will always be. Forcing a user to get a new account or upload off the project will just get us less imges and be more annoying for all of us. Don't think that I don't like Commons (I actually think it is great!) but what you are proposing is too crazy in my opinion. You, however, are more than welcome, to upload some images to commons and put {{NowCommons}} on their local page as long as you keep all the information the same. That would be more helpful than stopping all non-fair use En-wiki uploads. Cbrown1023talk01:01, 10 May 2007 (UTC)
We aren't forcing them to get an account. We are just technically moving all of the free/GFDL images (with the user's consent) to Commons so that other wikipedia users on various other projects can use them accordingly. How is this too crazy? Admins are always complaining about the image backlog needing to be reduced. Real9601:09, 10 May 2007 (UTC)
So, I've uploaded lots of unused images to commons, and a fewer still some that are used. But I've got older images I'd move if there was an easy way to do it. Is there a simple move button? Why not? I imagine it's not a lot of dev time. SchmuckyTheCat02:15, 10 May 2007 (UTC)
Asking everyone to assume good faith with compromised admins
As we deal with this fallout from the hacking of admin accounts, I hope everyone will remember to assume good faith with the admins whose accounts were compromised. Some of these compromised admins have been around for years and have a long track record here. Remember: Times change. Until recently, Wikipedia didn't have a secure log-in function (and when I tried to use it a few minutes ago, that function had again disappeared for some reason). We also failed to require strong passwords.
Yes, we must take action to fix this situation. Yes, they can't get their admin powers back until their identities are confirmed and we're sure the hackers no longer have access to their accounts. But too many editors here seem to have the attitude that b/c an admin used a weak password, they now can't be trusted. My understanding of Wikipedia is that we assume good faith and, once someone admits a mistake, let the issue go. Don't let these hackers win by driving off some of our best people. Instead, let's fix this problem and get back to creating the best free encyclopedia in the world. --Alabamaboy 02:14, 8 May 2007 (UTC)
Well put. I strongly agree with this.
How many of you reading this, when you first opened your Wikipedia account (remember that day, long ago?), thought that it was one that required a strong password? How many have retained that first password until the present day? We should not be punishing people who failed to choose a strong password when they first tried out their hand at editing the encyclopedia. How many of you, when you started, thought your involvement here would be a serious endeavor?
I see a lot of overreaction to this incident -- to be expected, because it was a serious one -- but react strongly in the right way. React to the security hole: make your passwords strong now; implement better security; guard your account. But please do not beat up people who have made tens of thousands of good contributions to our encyclopedia, and spent, in a couple cases, thousands of hours of their personal time building this fine project, just because they were the victims of a hacker attack. Antandrus (talk)02:21, 8 May 2007 (UTC)
I endorse the two above comments completely. It is quite disappointing to see how other users are kicking the compromised admins while they're down. We all make mistakes. Titoxd(?!? - cool stuff)03:01, 8 May 2007 (UTC)
They may be very nice people, but this isn't about how nice they are. They're either too stupid or too lazy to take the most basic precautions to protect their sysop bits from abuse. --Tony Sidaway03:22, 8 May 2007 (UTC)
Someone whose password was hacked isn't "stupid" or "lazy". S/he was the victim of hacking, although precautions can be taken to help prevent futher hacks. Firsfron of Ronchester03:28, 8 May 2007 (UTC)
No, they chose passwords like "password" and "fuckyou". That's just stupid, and wouldn't require any 'hacking' to break into. —Centrx→talk • 04:05, 8 May 2007 (UTC)
Wikipedia makes it extremely easy to execute a brute force or a dictionary attack. I can begin cracking passwords with a single shell line. Yes, a few unfortunate passwords. But don't forget that this could have been prevented from a software point of view, which is usually easier to do. -- ReyBrujo04:13, 8 May 2007 (UTC)
These passwords are so weak that that it is the first password anyone would try. You don't even need to use one incorrect password to get the captcha; you don't even need to be trying to crack these accounts at all. Anyone even accidentally could log into these accounts. If you go to a secret doorway in an alley, and the person guarding the door says "What is the password?" and you say "Uh, password?" that should not then get you access. If the person guarding the door says "What is the password?" and you say "Fuck you!" that should not then get you access. The situation is primitive; no software is needed, no one need even attempt to be breaking in. —Centrx→talk • 15:03, 8 May 2007 (UTC)
So, if your account gets compromised, it would be fair game to call you an idiot? That is essentially what you are saying. You do have to consider that people may have registered here when Wikipedia was just one more site on the Internet, and did not bother to change their passwords with time. Then, there's the whole issue of people making mistakes. So, they fucked up and they don't get second chances? Is that the message you want to send in a volunteer-driven project? Titoxd(?!? - cool stuff)03:29, 8 May 2007 (UTC)
I've seen it suggested elsewhere that compromised admin accounts would have to reapply for adminship. Is there any basis in policy for this assertion? My impression is that the burden should be on those users who feel they automatically cannot trust someone whose account is hacked to request the removal of admin status. Savidan03:31, 8 May 2007 (UTC)
Seeing his reaction, I guess Tony wants them to follow the same path he must follow to regain adminship access. I don't have a real opinion (yet) about whether they should recover their sysop access or reapply, but down here, if you lose your credit card and someone uses it to buy something, you call the company and have not only the operation canceled, but a new credit card. They don't even ask you why you were carrying the card inside your cigarette package when you threw it away. -- ReyBrujo03:39, 8 May 2007 (UTC)
It is not a question of good faith or bad faith, it is a question of judgment. These are not just bad password, but really really bad passwords. "password" and "fuckyou" are passwords that are downright negligent. HighInBC(Need help? Ask me)03:41, 8 May 2007 (UTC)
I'm more in agreement with Tony here. I may not go as far as to say "stupid", but the use of excessively weak passwords is irresponsible, especially for an admin. I'm sorry, but I didn't need a huge banner on the login page telling me I needed a good password. The lack of such a banner elicits no sympathy from me toward the afflicted admins. It's basic knowledge that when choosing a debit card PIN, password, or access code, one should choose something difficult to guess. If accounts with good passwords were being hacked, that'd be a different story. However, that does not seem to be the case here. -- tariqabjotu03:43, 8 May 2007 (UTC)
[edit-conflict]Given enough time, any password can be cracked. If someone spent weeks cracking yours, would you be "negligent"? Should we resysop you? Prodegotalk03:46, 8 May 2007 (UTC)
(edit conflicted) They made a mistake, they've been embarrassed, and Wikipedia has come out better. If we can confirm who they are, I think it would be best to have them as admins again. Remember, there was never any advice not to have "password" as a password. Not all admins are 20something computer geeks -- and that's a good thing. alphachimp03:45, 8 May 2007 (UTC)
It has nothing to do with being a computer geek. The entire concept of a password---and the concept far preceded the invention of computers, you can find it in Ali Baba, the Bible, and the Republic---is that it is in some way secret or non-obvious. This is not some technical concept. This is not about choosing passwords that are secure against brute-force dictionary attacks, this is about choosing passwords that are so fundamentally simple that anyone whatsoever could have accessed the accounts just by playing around and typing in obvious things like "password". Choosing "password" as a password is simply idiotic, and someone born in 1800 can recognize that. —Centrx→talk • 04:12, 8 May 2007 (UTC)
(double edit conflict) And again, the judgment of the admin in question does not quantize to a different energy level all of a sudden because his account got hacked. These admins made a mistake, and the said admins are probably the most embarrassed users on Wikipedia right now. They realize their mistake, and I'm pretty darn sure that they will not do it again... in fact, I'm actually quite confident that these users will never have these problems again, because of the public embarrassment it carries. So what is the point of these insanely punitive reactions? Pardon me, but I don't get it. Titoxd(?!? - cool stuff)03:46, 8 May 2007 (UTC)
I don't get it either, it seems like some folks want to punish these editors. RxS03:51, 8 May 2007 (UTC)
We're talking about someone stupid enough to have a password like "password" or "fuckyou". Understandable in 1988, but this is 2007. How can we trust someone so stupid with a sysop bit? --Tony Sidaway03:49, 8 May 2007 (UTC)
And can we stop with the "too stupid or too lazy" comments? Being civil is still a value here..RxS03:51, 8 May 2007 (UTC)
I have to agree with Tony on this one. If they had a very good password, and the hijacking was done because the software didn't react, then I might be OK with restoring sysop access... but if you're dumb enough to use the word "password" as your password, then I'm sorry... how can we trust you to make good judgment elsewhere? Having a weak password as an editor is one thing... so someone adds "poop" to a few pages and you get blocked, not as much of a big deal. As an admin, they were given that right for being trustworthy. Yet they couldn't have even been bothered to change their passwords to something that would've protected them. I'm sorry if it seems harsh, but they can always re-apply. Review MeCASCADIAHowl/Trail03:58, 8 May 2007 (UTC)
Can I ask who you are calling dumb here? Those admins already affected or any that might have the same thing happen going forward? You'd have a point if you're talking about it happening in the future, but there's no evidence that those involved here are either stupid, dumb or lazy. RxS04:04, 8 May 2007 (UTC)
Per my comment above, what is the 'line of stupidity'? Is 'rover' stupid? 'Hairc1ip'? 'pinkhouse#1'? When do we declare a password "stupid". Prodegotalk03:53, 8 May 2007 (UTC)
I'm speaking in general terms here. The use of the word "password" is just plain stupid, lazy, and dumb, and has no excuse... not even living under a rock since 1970. The fact that everything these days has passwords, like bank accounts, email, chat rooms, even your employer's network... a strong password is encouraged or required at all of these places, to get people in the habit of choosing secure passwords. Review MeCASCADIAHowl/Trail04:07, 8 May 2007 (UTC)
As with anyone who works in a company who uses computers, or a bank account they check online, typically the password requirements are 8+ characters alphanumeric. I cannot for one moment believe that someone does not understand the concept of password security in our day and age, especially people who are considered intelligent in nearly every other aspect. Review MeCASCADIAHowl/Trail04:02, 8 May 2007 (UTC)
(edit conflict) Users so remarkably stupid that no one had any complaints of their behaviour before these incidents. What are you trying to accomplish, Tony? Drive off good users? Titoxd(?!? - cool stuff)03:54, 8 May 2007 (UTC)
Because they, as far as I know, have a clear background, and everyone makes mistakes. With that kind of thought, unless you are a computer geek who reads Slashdot everyday, you should go work with Britannica. If they do repeat the mistake, I would consider them stupid. But until then, assume good faith, dang. -- ReyBrujo03:59, 8 May 2007 (UTC)
Also, I would like to see the current death toll. By the tone some users use, it appears as if someone cracked the password of an atomic plant root account and blew it up. -- ReyBrujo04:01, 8 May 2007 (UTC)
Non sequiturs, red herrings, and hyperbole are not welcome here. I do not think you are accurately representing the view of people like me who believe that using heinously insecure passwords makes someone untrustworthy to the point that adminship may be in question. Really, are you trying to solve anything, or just trying to win empty rhetorical points by batting at straw men that are warped beyond recognition from any views actually held by anyone present? --Cyde Weys04:06, 8 May 2007 (UTC)
Following your point of view, we should also block those admins who use WEP encryption in their wireless setting, who are not logged through the secure website, and who don't lock the computer when taking a break. -- ReyBrujo04:10, 8 May 2007 (UTC)
Again with the hyperbole. Having your password being "password" or "fuckyou" is not equivalent in the slightest to your example. --Cyde Weys04:13, 8 May 2007 (UTC)
I'm sorry, but as far as system community goes, it makes them dumber than rock. We don't need administrators that much that we shouldn't be asking these people, politely, to reapply for their sysop bits, with the knowledge that they failed a very basic test of trustworthiness. --Tony Sidaway13:33, 8 May 2007 (UTC)
This could have been prevented via software. It was not. It is MediaWiki fault as much as the users' fault. Of course, you won't accept it because, in your world, having passwords of 16 characters with alphanumerics and strange symbols is common knowledge. Open your eyes, not everyone is a geek. -- ReyBrujo04:22, 8 May 2007 (UTC)
(ec) Bottom line of this whole discussion: Admins are chosen based on their trust to use their powers for good, and this includes trust on preventing those powers from getting in to the wrong hands. The use of a ridiculously simple password shows absolutely no understanding of security, the ability to put the need to have a simple and really easy to remember password over the well being of the community, and the audacity to think that a simple "I'm sorry" will suffice. Admins are chosen based on trust, and in this case all trust has been lost. Assume Good Faith does not mean getting duped. It means where good faith is due, it is given, where it is not... you're on your own. Review MeCASCADIAHowl/Trail04:23, 8 May 2007 (UTC)
That is certainly not the bottom line. Being a trustworthy admin did not mean having an understanding about computer security. It does now, admins should always be aware of issues that have come up in the past. But they were not picked because of their computer expertise, but were picked because they were trusted not to abuse the tools. Abuse of tools may now include password security, but it didn't when these editors were selected. And you can bet they won't allow it to happen to them again. RxS04:33, 8 May 2007 (UTC)
So, computer security is suddenly something that admins have to have an understanding about? This is 2007. How many times have there been stories in the news about personal data being stolen, records being accessed... more often than I care to count. It does not take a computer scientist to know that "password" is not a good password. Like I stated before, the use of secure passwords is everywhere these days. College records can only be accessed by the student on most college websites, and they require secure passwords. Bank account information, again, is the same way. To stand here and say that it requires a computer expert to know that using a very simple password is dangerous is insulting to every non-computer expert that understands this fact. This is not a debate over the merits of the admins edits, its on the fact they put the speed of logging in, and the ability to not have to remember a password over protecting their admin tools. Everyone is ultimately responsible for their own password security, but if you're willing to ignore the fact that people have even offered money to have an admin turn over their account for a day and use a simple password that doesn't require such a person to give money, then why should we trust that person? It's like calling a parent a bad parent only after the first baby dies of starvation, because they didn't know to feed it. It's not a direct comparison, but it illustrates the fact that password security should be as common knowledge as the idea that you have to feed your children. Review MeCASCADIAHowl/Trail04:50, 8 May 2007 (UTC)
"...password security should be as common knowledge as the idea that you have to feed your children"? That says all there needs to be said about how unrealistic you're being. You don't understand that all people don't happen to live like you....RxS14:29, 8 May 2007 (UTC)
Yes, how dare people have "the audacity" to think they'd be forgiven when they've said "I'm sorry". There's hyperbole going both ways here: since when were passwords required at all' in 1970? Firsfron of Ronchester04:30, 8 May 2007 (UTC)
Be my guest: search every RFA to see if there is a single one before all these incident happened in which the nominator is asked which measures he would take to prevent his account from being compromised. Common knowledge? Come on, not even us recognized MediaWiki was so easy to crack until this happened. -- ReyBrujo04:28, 8 May 2007 (UTC)
Is this supposed to be a constructive discussion, or is everyone just bitching at each other? I sense that the latter premise is manifesting itself at the expense of the former. —210physicq (c) 04:25, 8 May 2007 (UTC)
Good point, but I always bristle a little when people toss the words lazy and stupid around...RxS04:35, 8 May 2007 (UTC)
Sorry if I went that way. At school, I always solved math problems by reductio ad absurdum, something I tend to use everywhere. Basically, if using a weak password demonstrates the user's unsuitability of being an administrator, so would using WEP encryption, not using a secure connection, not logging out before going to sleep, etc. -- ReyBrujo04:40, 8 May 2007 (UTC)
I hate to burst your bubble but you're not using reductio ad absurdum, you're using slippery slope and straw man, both of which are extremely well-known logical fallacies. Please knock it off. --Cyde Weys04:54, 8 May 2007 (UTC)
(ec)Indeed. It is common sense that if you can type in a password, someone else can type in a password, and if your password happens to be as weak as 'password', then someone with the a few minutes to spare and an angry will can probably guess it. No l33t hax0rz needed. WEP's weakenesses, on the other hand, are not common sense at all, but require specific knowledge'. Though that said, I don't have an opinion either way on the resysopping. -- Consumed Crustacean (talk) 04:58, 8 May 2007 (UTC)
Well, I have left this discussion, can't argue against the knowledge of the mass. However, if strong passwords are being cracked like KOS's one, there is a possibility that, somehow, this attack has been going on for months, or that communications are being intercepted (or, that someone, somehow, managed to get the password hashes). -- ReyBrujo17:41, 8 May 2007 (UTC)
(ec) Rey, by your logic though, we shouldn't have admins... because there is no way to even check if an admin is using WEP encryption, not using a secure connection, and not logging out before going to sleep. See where Cyde is going with this? Review MeCASCADIAHowl/Trail04:57, 8 May 2007 (UTC)
Bitch? Not at all. Tony Sidaway and I are actually here to belittle and deliver harsh punishments to the compromised admins. — Rebelguys2talk05:33, 8 May 2007 (UTC)
Can Check-user users check for failed attempts to login? If so, then we can tell the difference between a brute-force attempt to try every password and someone who used an easy-to-guess password. In the second case, I think the following should apply:
After the first time it's been compromised, re-sysop without any process once it's clear the account is no longer compromised and the user claims to have a secure password.
The second time it's compromised (again, due to an obvious password), no re-sysopping. If the user didn't learn after the first time, then he/she isn't responsible enough to be an admin. As the saying goes, "Fool me once, shame on you. Fool me twice, shame on me!".
Choosing really bad password may be irresponsible but the conversation that developed here is well over the top IMO. As long as WP:CIVIL is a policy here nobody (and his/her actions) should be called stupid, dumb, etc. Did anybody bother to check the work those people did here? I would not expect to find such a violation of WP policy on Admin' noticeboard. Lots of people got warnings for a lot less. Thank you, stay calm and consider finding a way of resysoping those users as a gesture of good faith.--Pethr05:01, 8 May 2007 (UTC)
Agree. Please don't call longstanding contributors and administrators here lazy, stupid or dumb. This is a volunteer project. There are more civil ways of raising your arguments -- Samir05:37, 8 May 2007 (UTC)
Another agree. I've been editing here for over 3 years. Since I've been using firefox's password manager, I had to stop and think about what password I started my account with over 3 years ago when this site was just a curiosity to me and I didn't even know there were admins. I'm glad I picked a secure password and I wasn't a victim. I can easily imagine how someone could overlook creating a more secure password as they up their involvement here. Lack of civility is probably the biggest threat we have. It is a bigger threat than cracking passwords. Civility is one of the qualities of this community that inspired me to contribute. If it disintegrates, we will loose much more than the front page, we will loose many valuable contributors and perhaps destroy the project entirely. -- Samuel Wantman 09:17, 8 May 2007 (UTC)
You have a point here, but the truth is that the concept of civility is being abused in the project much more often than cracked passwords are. "Incivility" has become a mantra for those willing to persecute their opponents under any convenient pretext. --Ghirla-трёп-09:32, 8 May 2007 (UTC)
Section break
A couple of questions:
(1) Will those calling for going back through RfA for compromised accounts even after it is satisfactorily verified that the account is no longer compromised) apply these standards to themselves if their accounts are ever compromised, in any way what-so-ever? Do they realise that they might be making themselves targets for ambitious crackers if they continue along this line of reasoning?
(2)Will those calling for going back through RfA for compromised accounts be calling for those who deal with Wikimedia security to resign over this? Or will they say that such people are too valuable to lose? If so, why aren't admins with demonstrable long-term committment to the project as valuable?
(3) Is this issue about password security, or about who has to go back through RfA? Please make the connection between these issues clear before conflating them. Expanding the criteria concerning which desysopped admins have to back through RfA shouldn't be a knee-jerk reaction.
And I agree with the need for civility here. Tossing words like 'lazy' and 'stupid' around is not going to help. Carcharoth10:05, 8 May 2007 (UTC)
If being lazy was grounds for deopping someone, there's quite a bunch of admins that have been inactive lately, or haven't used their admin tools much. Given our extensive backlogs, it's easy to make a case for those people being lazy. Is that helpful? No. Are we going to deop all those people? Of course not. We're all volunteers here, and a lazy volunteer is still a welcome volunteer. >Radiant<10:36, 8 May 2007 (UTC)
I strongly agree with the coment by Alabamaboy that started this thread, and the comment by Radient just above. I strongly disagree with both the tone and the substance of the comments by Tony Sidaway. I have seem editors, and indeed admins, make errors that are far more clearly culpable than having a weak PW, and thsoe errors are routinely forgiven on an apology and a promise not to offend again. Indeed, we routienly forgive things that are not "errors" but intentional actions, such as the making of legal threats, on the promise that the editor will not ofend again. I strongly suspect that if these editors resume activity, no one will be more fanatic about security than they will ("once burned..."). I see no reason why one error, even though it had potentially serious consequences (and lets remeber that the actual damage was fixed quite quickly) should make us less willign totrust an individual. at the very least, lets wait until there is some confirmation that the proper editors are in control of thsoe accounts, and then see what they have to say about the matter, before rushing to judgement, or should I say pre-judgement. DES(talk)12:14, 8 May 2007 (UTC)
Well obviously the only solution is to have 128-character one-time elliptic entropic passwords, otherwise there's a possibility they might get cracked! And no staying logged in! And no admining from a non-SSL server! You never know who might be looking, and Jebus help you if your password gets cracked, obviously you're far too stupid to be doing anything here! Luigi30 (Taλk) 12:46, 8 May 2007 (UTC)
I'm still trying to process DESiegel's statement that he has seen "admins, make errors that are far more clearly culpable than having a weak PW, and thsoe errors are routinely forgiven on an apology and a promise not to offend again." Short of actually deleting the main page yourself, what action by a Wikipedia admin could possibly be more culpable than having a stupid password like "password"? That's just flatly incorrect. The problem here, in any case, is not punishment or forgiveness or anything like that, it's that fact that Wikipedia cannot afford to routinely continue to trust people who have proven so feckless or negligent. I only ask, as I have from the beginning, that these editors not be routinely resysopped as has apparently happened here, but that they should be required to test whether they retain the community's trust as administrators. --Tony Sidaway13:22, 8 May 2007 (UTC)
So who was negligent enough to allow the Mediawiki software to accept simple passwords like 'password' or even (since fixed) blank passwords? Would you continue to trust people that allowed a security loophole like this to go unfixed (for the record, I would). Carcharoth13:47, 8 May 2007 (UTC)
Let me get this straight, someone leaves the door unlocked, and you blame the lock designer for not autolocking? HighInBC(Need help? Ask me)13:49, 8 May 2007 (UTC)
As you've said below that you were replying to me I've indented to show this and, then yes, the lock designer should bear some of the blame, as the final design of this sort of lock (choosing the password) is done by the 'owner' of the lock, and not the designer. A good design would place limits on that part of the process. Carcharoth14:13, 8 May 2007 (UTC)
Speaking as someone whose PIN for banking, intruder alarm, and office are all the first digits of my phone number I am probably am one of those Tony would think very stupid, but I'm not so stupid I can't see when Tony is deliberately making provocative statements. The simple truth is those admins (whoever they are) have learnt the hard way that many of us need to be more security conscious. They have learned, we have all learned, we are all better and wiser for it. They can still be admins - now let us move on. Giano13:49, 8 May 2007 (UTC)
HighInBC, I'm finding it difficult to work out who you are replying to. Could you possibly indent to the correct level when replying? Carcharoth13:52, 8 May 2007 (UTC)
I did not know there is a correct way to indent(please point me to a page describing it), my response dated 13:49, 8 May 2007 is to you. If the community asked for a blacklist of passwords the devs would have added them. HighInBC(Need help? Ask me)13:54, 8 May 2007 (UTC)
Probably no page describing it. One of those unwritten rules. The general rule is to indent one more level than the person you are replying to, and to try and keep replies in chronological order, so if someone else replies first, your reply goes below their's (unless there is a good reason to jump the queue, when you can double indent to indicate you have done that). I wonder what happened to LiquidThreads? I've taken the liberty of correcting the indentation above, though I took care to take the courtesy to ask you to clarify who you were replying to before doing that. Now, tongue-in-cheek I wonder if this sort of "common knowledge" about threading of conversations (more familiar to those who use bulletin boards or Usenet) is on a level with the 'obviousness' of password security? :-) Carcharoth14:13, 8 May 2007 (UTC)
(resetting indent) My two cents' worth is this: the Wikipedia community was the prey to a grievous attack, which hurt us. This attack was in part due to the negligence of some admins who used passwords that were too simple. Those admins were chosen in the first place for their general good judgment in most matters. However, I don't see that never making an error in judgment was a prerequisite for being an admin. Last time I checked, it wasn't. These admins, in not choosing a strong enouhg password, did, IMHO commit an error in judgment, the grievousness of which is debatable (as all the damage was rather quickly and painlessly reverted). Unless we start asking for all admins to reapply any time they make any error of judgment, I don't see how we can ask them to go through the same process now. I believe we should just ask them to prove their identity and demonstrate they are using a stronger password ("strong enough" is subjective). If, however, their password were to get cracked a second time, that would be recurring negligence, which might be rightfully sanctionable. If we want to move forward from this, I would welcome us putting way more effort in making sure it doesn't happen again (and I don't think we should rely that everyone should fully understand what a strong password is) than assigning blame. These admins didn't suddenly prove themselves untrusworthy, they made an error in judgment, certainly, they were negligent, probably, but in the end, erring is human. Let's please let it go at that.--Ramdrake14:09, 8 May 2007 (UTC)
It's not really on to equivocate like this. It isn't merely "an error of judgement", it's such a basic failure of the norms we require of any editor on Wikipedia, that if an administrator fails surely his trustworthiness is called into question. Let me be clear here, because often we seem to be losing sight of it: deliberately choosing a password like "password" or "fuckyou" can only happen for two reasons: stupidity or negligence. The effect is to expose Wikipedia potentially to damage that for reasons that must be obvious I will not describe here. This is fundamental: can we place Wikipedia's integrity in the hands of someone who would guard it with passwords like this? --Tony Sidaway14:49, 8 May 2007 (UTC)
It's certainly a very foollish thing to do, given the damage we know can be done with an admin account. Guy (Help!) 14:53, 8 May 2007 (UTC)
Tony, in future, no the community shouldn't let this happen. I agree with the changes being made, and I would urge you to suggest (over there) that this question be asked of all RFA candidates. Forcing people to go back through the RfA process in matters like this is counter-productive though. To be fair you should have all admins go back through RfA and let the community judge whether their judgement in cases like this (password security) is suspect. Also, for reasons of natural justice, singling out those who (for whatever reason) were compromised in this case, would be unfair. Several people changed their passwords to stronger ones in the wake of this, many more probably did so and said nothing. Did those people have weak passwords? Should they be castigated and desysopped as well? Concentrate on putting safeguards in place now, be more vigilent, and let the past become history while learning from it. Carcharoth14:59, 8 May 2007 (UTC)
I agree with your interpretation of my view as "you should have all admins go back through RfA and let the community judge whether their judgement in cases like this (password security) is suspect." That absolutely encapsulates my view. I have openly promulgated, before the attacks yesterday, at around 1100 GMT, that we run a sweep of admin account and summarily desysop all those who have weak passwords [11][12]. Actually Brion did perform the sweep but has locked out the accounts by changing the passwords, so those who had no email address have lost their accounts--this isn't a bad solution.
I don't think asking questions of RFA candidates along the lines of "have you got a strong password?" is productive. Actively testing their passwords, and rejecting any candidate with an easily hackable password, would be much more effective. It's easy enough to write a "yes/no" hackability test that can be run by a bureaucrat. --Tony Sidaway15:20, 8 May 2007 (UTC)
Actually, by "all admins" I meant all 1000+ admins should be questioned in depth about their knowledge of password security issues. I mean, you can run password crackers over accounts all you like, but educating the weak links is best (yes, I'm being slightly sarcastic here). Carcharoth16:55, 8 May 2007 (UTC)
So Brion desysopped a bunch of admins yesterday? Huh, I would think there would be a little more discussion about that then a unilateral action...unless he has some way of letting them into their accounts when asked to. RxS15:34, 8 May 2007 (UTC)
Well locked out for those foolish enough not to have an email set. What alternative did we have? The site was under attack because of some people's poor password choices. Secretlondon15:44, 8 May 2007 (UTC)
Dunno, unless there was a way to record what the old password was (not always possible) then it's a hard lesson learned I guess. RxS15:51, 8 May 2007 (UTC)
So did Brion actually desysop them, or just lock them out of the accounts? If the latter, we're going to haev a hard time telling what our actual admin totals are now. -- nae'blis16:06, 8 May 2007 (UTC)
I agree. Can we have a link somewhere to something stating what exactly was the outcome of Brion's sweep? Do those locked out by changed passwords get the same sort of message as those blocked? If not, there may be some puzzled people out there wondering if they've suddenly developed amnesia or something... (sure, as admins, they should eventually work out what is going on, but still). Carcharoth16:50, 8 May 2007 (UTC)
Well, Tony, the question then is, if this was so important, how come you didn't test their account for security? Or anybody else for that matter? I mean, if their password is as terrible as you're implying, and if your trust of them is contingent on their establishment of this minimum level of security, why weren't you out there trying, in the simplest possible ways, to crack the accounts during RfA? The reasoning here is essentially the same as that forbidding ex post facto laws in many nations - it cannot be a crime to do something if nobody knows that it's a crime. This isn't just a failure of those admins - it's a failure of the community for not making it an issue, the developers for not building in all manner of security tools, and every person that didn't think to ask about it. I work in IT. I certainly know that "password" is a weak password (and I haven't personally seen confirmation of that specific case, which isn't to say it's not there), but, if you can believe it, I've worked with people IN THIS LINE OF BUSINESS that don't realize that sort of thing. If you haven't tried to teach a child, you can't blame him for not knowing long division.Cool moe dee 34515:48, 8 May 2007 (UTC)
See my earlier comments in which I suggested a scan of weak accounts and automatic desysopping. This was at 1100 GMT yesterday. I agree that the community had failed, but for understandable reasons--it may be obvious to you that many people are too stupid to set a proper password, but it was not obvious to me and I'm sure not to most other editors. This does not excuse those negligent editors their responsibilities. In short, it looks like you're having a good go at deflecting attention from the cause of the problem. --Tony Sidaway17:56, 8 May 2007 (UTC)
Tony, you have a good point. But I think asking all these admins to go through RFA again when we don't even know the extent of the problem is rushing things a bit. Surely, if (1) we can re-identify a user definitively, (2) they agree to choose a stronger password, (3) we check that they have done so, then the only remaining question is whether the community can still trust them given the weakness of their password, right? I see the point, but we rely on admins to do a lot of work around here, and RFA is very contentious, and the last thing we want is to drive such dedicated volunteers away over what is probably a single lapse of judgement, that as others mention, probably was made well before they came to prominence as admins. Mangojuicetalk15:53, 8 May 2007 (UTC)
Agreed. Blanket requirements for re-RFA (with its concommittant tendency to magnify 'problems') may only net us a total reduction in admins, something the vandal may have wanted. Although I hate to quote GWB, "if we desysop people because of old passwords, the vandals have already won". -- nae'blis16:06, 8 May 2007 (UTC)
Please, Tony - can you stop throwing hyperbolic insults about how "lazy" and "stupid" (even - ! - "mendacious") the poor people who have been caught up in this sorry mess have been. I have lost count of the number of times I have seen variations on this theme from you over the past few days.
Admittedly, passwords like "password" are at the far end of the spectrum as far as security (or lack thereof) go, but it is unfortunately a fact of life that some people are less aware of or less concerned about computer security issues than others. Does that make them "stupid" or "lazy", or even untrustworthy?
At the end of the day, Wikipedia is just a project to build an online encyclopedia, not a repository of medical or banking records, so it is understandable that some participants may choose passwords that are not as secure as you or others with more familiarity of such issues might like or expect. Perhaps it is second nature for some people to choose different lengthy random strings every time they are asked for a new password, and to change them regularly too, but most people don't, particularly article-orientated editors: that is, people that are actually writing the encyclopedia. Being an admin is not (or not solely) about knowledge about geeky computer-administration issues: admins are people that the community is confident will not abuse the admin buttons. No more, no less.
I agree pretty much with Alabamaboy and Antandrus. Let this be a lesson to us all to choose our passwords more wisely. It is also comforting that technical solutions - like the captcha - are being implemented to help to stop this sort of thing happening again. -- ALoan(Talk)15:58, 8 May 2007 (UTC)
Yes these people were ignorant, and yes that has consequences. Fortunately, on wikipedia, ignorance is a viable defence. :-)
So I'm just going to say good luck to those who lost their accounts yesterday. If they can prove who they are, they can get their accounts back, and will have learned a valuable lesson. One which they will likely not soon forget.
If they can't identify themselves, well, yeah, that's kind of tough, because we really won't know if they are actually themselves. :-/
--Kim Bruning16:04, 8 May 2007 (UTC) (said the manager of the man who just lost the company $1 000 000 : "What? Fire him? Never! It just cost me a million bucks to educate him!")
I don't think it makes sense to punish the admins in question for this incident (and it certainly wouldn't be a preventative response since this mistake is unlikely to repeat itself). This is better dealt with by the path that we have already begun -- checking password strength and requesting admins with weak passwords to improve them. It is better to focus on our response to the malicious parties, not the punishment of the honestly negligent in our own camp. Christopher Parham(talk)16:17, 8 May 2007 (UTC)
Part of the issue is judgement, for example: Could they be duped into giving out their passwords? Are they going to leave their admin account logged in at an Internet cafe? Are they running Windows with no updates? Those are just some of the security issues, and they are serious security issues; we are lucky the vandal only deleted the main page and blocked a few users, though that should still never happen. —Centrx→talk • 16:23, 8 May 2007 (UTC)
Again I'm surprised to find a respected Wikipedia (in this case, Kim Bruning) questioning the obvious:
Admittedly, passwords like "password" are at the far end of the spectrum as far as security (or lack thereof) go, but it is unfortunately a fact of life that some people are less aware of or less concerned about computer security issues than others. Does that make them "stupid" or "lazy", or even untrustworthy?
Um, yes, I think the presumption should be that they have been trusted and found wanting. This is obvious. Automatically resysopping should not be done. Unless there are extensive mitigating factors, they should be required to go to the community and ask if they're still trusted. --Tony Sidaway17:49, 8 May 2007 (UTC)
That was me. It is not at all obvious to me that someone who knows little or nothing about computer security is lazy, stupid, mendacious or untrustworthy. They are just vulnerable, and in need of guidance and assistance. -- ALoan(Talk)22:28, 8 May 2007 (UTC)
Yes, we know you think that. You have said so quite a few times in this thread. You haven't said anythign new about the matter for the past few times. Othjer people have read and understood what you have said, and at least some of them disagree with you. I do, for one. DES(talk)18:11, 8 May 2007 (UTC)
You seem to have acquired a royal plural. Yes, I have no problem repeating the facts in appropriate permutations until they permeate the consciousness and are established beyond dispute. This can take some time but I've never regarded that as a problem. --Tony Sidaway20:41, 8 May 2007 (UTC)
(reset) Oh good grief! I can assume good faith and deplore bad security habits on the same line. Be glad that you have a system that allows rolling destructive changes back. I'd urge you to set up a system to actively test or challange administrator's passwords, and to timeout an administrator's login after a couple of minutes of inactivity. I suspect that most of the problems are from human factors other than password choice. Not that that can't be a problem, too. (forgot to sign, sigh!) htom18:21, 8 May 2007 (UTC)
That is a horrible idea, that won't accomplish anything. Considering that Wikipedia does not transmit passwords encrypted during login (and this has been public for a while, so no risk of WP:BEANS here), you want admins to have to log in more? Titoxd(?!? - cool stuff)19:07, 8 May 2007 (UTC)
That the passwords are not encrypted is not good. That an administrator might be distracted and leave their account accessable to someone walking by -- whether their cat or a shoulder surfer -- should also be avoided. If you don't like the five minute timeout, how about fifteen? htom19:13, 8 May 2007 (UTC)
Neither. I'm not concerned about my cat editing. This solution doesn't accomplish anything, besides allowing more interception attack vectors. Titoxd(?!? - cool stuff)19:18, 8 May 2007 (UTC)
Question: For about a day or so, we had a secure log-in option on the site. I used it and it seemed to work ok. Last night that option disappeared. What's up with that? Will the option return or were there major bugs with it?--Alabamaboy 19:32, 8 May 2007 (UTC)
That has been there for a long time, not just a day. It was where we recommended AOL users to log in. I would guess that when all these editors found out about it, the load got too high to support it. Prodegotalk20:23, 8 May 2007 (UTC)
No, we were advised by the devs not to so publicly advertise it. We have, I believe, only one server that supports HTTPS for all Wikimedia wikis; it can't handle the load of every single user. Nonetheless, it is still available at https://secure.wikimedia.org and you're welcome to use it; just don't advertise it (as I just did :D). AmiDaniel (talk) 23:26, 8 May 2007 (UTC)
(In response to the original post): Hear, hear! Lets pay no mind to the cruel histrionics of the geeklitists. ˉˉanetode╦╩23:17, 8 May 2007 (UTC)
The above thread about admins with compromised accounts got me thinking: if my account was compromised, would there be a way I could convince someone unfamiliar with me that it was the same me operating in a different account? I suppose we could use Checkuser, but I came up with a different solution: use a cryptographic commitment scheme to specify my real-life identity on my user page, in case I'd ever need it. I created a template, Template:User committed identity, so others could do the same thing. I encourage my fellow admins to use this, just in case (if they haven't already specified their real-life identity publically). I do have a strong password, but nothing makes you immune from a dedicated attacker who could try every ascii string until they get your password. Mangojuicetalk17:13, 8 May 2007 (UTC)
I'll have to check this out. One thought, though: Could you change this to something other than "Committed Identities." That makes these people sound like they were committed to a mental institution or something. Of course, excessive WP editing might be a deciding factor in getting one committed. :-)--Alabamaboy 17:31, 8 May 2007 (UTC)
Hehe! From a crypto standpoint, it's the right term... but if you can think of a better name, that would be good. Mangojuicetalk20:48, 8 May 2007 (UTC)
Assuming that it's not feasible to reverse the algorithm, couldn't they try every ASCII string until they get your real name? No thanks to that. —freak(talk) 13:34, May. 9, 2007 (UTC)
It's best to put more info in there - for instance, I put my phone number, my username, and an email address. The string is much too long to brute force. But I'll add that to the instructions, people should be careful about this. Mangojuicetalk14:16, 9 May 2007 (UTC)
I have two static IPs so if I log a comment from both of those then it's definitely me. I don't mind giving those to a trusted party for justin. Guy (Help!) 21:06, 8 May 2007 (UTC)
Looks to me like it is not mandatory to use it for a real-life identity, it could be any phrase. As long as you can state what the magic word is, it confirms that you are the person who placed that hash in your use page. One could have several strings for several future uses. (SEWilco05:27, 9 May 2007 (UTC))
That's true, you can commit to anything. However, I felt like using a real-life identity would be best, because then the re-verification of your identity is two-pronged: not only do you know the secret, but the identity in the secret is the one who knows it. So, if someone managed to figure out my real-life identity, they could maybe figure out my secret string, but they probably couldn't convince someone else that they really are me. Mangojuicetalk14:14, 9 May 2007 (UTC)
Brilliant idea for confirmation of identities, Mangojuice. I've set one up myself. —The preceding unsigned comment was added by Premeditated Chaos (talk • contribs) 10:05, 9 May 2007 (UTC). Damnations, that's a fast bot. I literally just hit "save page". ♠PMC♠10:06, 9 May 2007 (UTC)
Yes, one of your confirmations can be your real identity. You could have other confirmations, such as a long phrase which mentions an action you did on Wikipedia, in case all that is needed is confirmation that someone is a certain Wikipedia editor and not necessarily who the editor is. (SEWilco04:04, 11 May 2007 (UTC))
There should be some WP Categories on the template so people have a chance to find the template. (SEWilco17:28, 9 May 2007 (UTC))
I signed up. I also moved the template docs to a subpage and tweaked the category includes so the template isn't in the user category. CMummert · talk 18:55, 9 May 2007 (UTC)
Table: namespace
Um... frankly wtf! See this. Is there some reason this was done with no visible discussion at all (other then on the bug report that I've dug up). Am I missing something? —— Eagle101Need help?03:52, 9 May 2007 (UTC)
I've emailed wikitech-l asking for this namespace to be removed. There is no consensus at all for it, and that bug report came from a suggestion made in 2005 that we should have a complete WYSIWYG table editing system that would incidentally use its own namespace. There was little discussion on the subject even back then, and there certainly isn't anything near a consensus now that this namespace is wanted or needed, or what we should do with it. This sort of thing needs a complete proposal to be written (and generally agreed upon) beforehand, and that just hasn't happened – Gurch03:54, 9 May 2007 (UTC)
(double edit conflict)I recall a rather lengthy discussion about it on the village pump a while ago (no concrete timeframe, sorry) that was quite positive towards the idea, so that's not completely true. The use seems rather straightforward as well: containing data tables which are better suited for transclusion than direct insertation into pages or existence as stand-alone articles.
Is there any particular reason you guys have to be against this? Do you think it will hurt Wikipedia somehow? Or is this just a general reaction against change? --tjstrftalk04:03, 9 May 2007 (UTC)
That this functionality is essentially the same as templates; that the reason behind the idea (that it will provide the background work for a table editor) is baseless, as they're completely unrelated; that there is no clear definition of what the distinction between a template and a table will be; that wikisyntax to link to tables will not be modified any time soon; that tables can be part of the article mainspace, and don't need to be relegated to a back corner of the wiki... I could go on and on... Titoxd(?!? - cool stuff)04:06, 9 May 2007 (UTC)
The only short term benefit I see is reusing tables. The bad thing is that we already do that with templates, offering no advantage at all. I have no opinion about this, though, although it has no real advantages. Personally, I find a Draft namespace (so that we stop using subpages in talk pages to create drafts) is more useful. -- ReyBrujo04:09, 9 May 2007 (UTC)
A Draft namespace may well be a good idea. Hardly matters, though, as you could request it today, nothing will happen and then in 2009 when everyone has forgotten all about your idea it gets added without warning – Gurch04:20, 9 May 2007 (UTC)
Ok, may I ask... whats the point of this? What makes this different from Template namespace? Most of our infoboxes are in there anyway. —— Eagle101Need help?04:09, 9 May 2007 (UTC)
It's not just that, though – it's more the fact that the namespace was added just like that... with no warning, at all... when it had been requested two years before. We need guidelines on how to a new namespace, what it's for and what belongs there, before we create the namespace and start moving stuff into it. That hasn't happened – Gurch04:10, 9 May 2007 (UTC)
I'm neutral towards it myself, since it was just implemented and we haven't seen what its effects will be. We can work out the rules for which stuff should go where as we go. --tjstrftalk04:16, 9 May 2007 (UTC)
Gurch are you upset that the devs forgot to fill in form WEF-32F-C3? I admit that it would have been nice to have some notification, and more importantly some explaination as to how it is actually useful, but its not the end of the world. I'm still personally asking for why is it different then template space? Whats the deal :P —— Eagle101Need help?04:20, 9 May 2007 (UTC)
No, I'm upset that they didn't tell anyone, at all that they were about to add a new namespace for which there was no active and advertised proposal – or even anything close. If they add something that everyone has obviously wanted for ages, then that's not so much of a problem, but that is not the case here – Gurch04:23, 9 May 2007 (UTC)
Search through archived discussion and obscure forgotten project pages and you'll find dozens of new namespace proposals. I remember making one myself. That doesn't mean it's OK for them all to suddenly show up in MediaWiki tomorrow – Gurch04:25, 9 May 2007 (UTC)
Mmm yeah that part could have been done better, but really if the use of the namespace is made clear, then we are better off for having it. —— Eagle101Need help?04:32, 9 May 2007 (UTC)
WP Tables:Table of tables for deletion. Obviously the namespace Wikipedia Tables: is needed. (SEWilco04:05, 11 May 2007 (UTC))
Could somebody please explain a meaningful difference between the table namespace and what we use templates for? >Radiant<08:34, 9 May 2007 (UTC)
The new namespace was discussed at VPR, and is still in the archives (current linkpermlink, due to the VP's strange archiving system). So I suppose the question is, what should be considered to be sufficient consensus/advertising to add a new namespace? --ais523 09:06, 9 May 2007 (UTC)
By the way, I found out about it from the announcement on wikibugs-l, where all software and language configuration changes are announced (except for ones that didn't use the bug tracker); however, this is a somewhat obscure mailing list with much traffic the average user wouldn't care about (it's a sort of 'recent changes' for bugzilla:, and its messages are automatically generated). --ais523 09:08, 9 May 2007 (UTC)
I also announced the change at #New namespace above on AN, and also at WP:VPN, shortly after it had been made, because I realised that it hadn't been announced anywhere people were likely to notice. --ais523 09:24, 9 May 2007 (UTC)
Hey, it's no big deal. If you prefer to do your tables with templates, fine. If you prefer to put your tables inline into an article, fine. If you prefer to put your tables into this new namespace and include them via the new [[Table:... syntax, fine.
There is, to me, a fine semantic distinction:
templates are (general-purpose) building blocks intended to be included in many pages, and useful for many purposes, whereas
any single table is typically intended to be included in very few pages only, in most cases even only on one single page, and is not general-purpose at all but very context specific.
That might be an argument for doing tables inline within articles, but apparently some people feel this unnecessarily intimidating to novice editors, a concern I can understand.
Just some anecdotal evidence: in Shrimp farm, I originally had the table in a subpage (which turned out not to be a subpage, as these are disabled on the main namespace, but let's ignore that). I didn't want to have the table in the article for size considerations and also because the article was going to be on the main page, and I feared it might be a magnet for subtle vandalism. (Someone changing only a few digits...) I did not want to pollute the Template namespace with this single-purpose table, so I chose a "subpage" and transcluded that. Sometime later, someone else put the table directly into the article, removing the transclusion, because the "subpage" wasn't a real subpage. I'm now seriously considering to move this table to this new Table namespace. Lupo09:30, 9 May 2007 (UTC)
Many pages that are currently templates are intended only to be included in one page, to simplify that page's formatting. So by your logic, they'd go in table namespace. Thing is, many of them aren't "tables" at all – some of them are tables in the sense that they use tables for markup purposes, but that has nothing to do with tables in the sense of a table of data, which is what people seem to think this namespace is for. Either we have single-transclusion/multi-transclusion namespaces, or we use Template namespace for both... but either way, I don't see that having a "table" namespace will help. Especially not with our current lack of guidelines, which will lead to administrators who want things done "their" way deleting any table namespace pages they don't like with pithy explanations like "it's not a table" (it happens, when you don't have agreed-upon policies and guidelines specifiying what is allowed) – Gurch10:35, 9 May 2007 (UTC)
I believe that the original purpose of the namespace was so that tables would be treated like images, hoping that eventually a separate table editor would be created. --ais523 12:36, 9 May 2007 (UTC)
Which is purely a proposal, as that page doesn't mean that a developer will look at it. All the active MediaWiki developers have their projects to work on, and unless you convince one, a table editor is not one of them. Titoxd(?!? - cool stuff)19:49, 9 May 2007 (UTC)
I don't understand a) the hue and cry, and b) why this is a AN issue. Is it harming, or were you just not sent an invitation to the discussion? Not many people complained about the idea, several thought it was positive, and the namespace is easily removed if it becomes a problem. -- nae'blis19:05, 9 May 2007 (UTC)
Not easily. All the pages in the namespace become inaccessible the moment the namespace is removed, and have to be retrieved by a developer with shell access. Titoxd(?!? - cool stuff)19:50, 9 May 2007 (UTC)
Well, "easily" in the sense that we can move all the Table: pages into other namespaces before deletion, considering it should be a well-considered and consensus decision to remove it upon evidence that the experiment has failed. :) -- nae'blis20:30, 9 May 2007 (UTC)
Eagle101's link at the top doesn't work, so try this one. :-) 13 pages in the Table: namespace so far. One has even been marked on its talk page as "Table Class" and a category created for table class pages! Also, has anyone noticed that the talk page syntax is inconsistent? It goes Talk:Table:... rather than Table talk:... Carcharoth12:25, 10 May 2007 (UTC)
That's because the namespace was just removed again, and all the pages in it were moved into articlespace by the developers using Table: or Talk:Table: prefixes. (It was Table talk: while the namespace existed, and will be if the namespace is created again.) --ais523 12:33, 10 May 2007 (UTC)
I started out defending the two people accused of sockpuppetry, but requests for explanations have largely been ignored by Gaimhreadhan, and after initial protests, by W. Frank. See also User_talk:W._Frank. At the very best, the two are very close friends, have been editing with a similar viewpoint on some articles, and are unable to understand Wikipedia's processes or are unwilling to cooperate in resolving the matter. The "smoking gun" appears to be an email W. Frank said he sent to User:Tyrenius, but which arrived from Gaimhreadhan's email address.-gadfium09:18, 9 May 2007 (UTC)
Thank you for your fairness, gadfium. G and I have known each other for more than 20 years and I do not consider friendship to be grounds for accusing people of being meatpuppets. Please do not take this the wrong way but I am happy to discuss these matters by phone or in person with anyone that does not require the shelter of anonymity. Because of security concerns (related to the industry we both work in and the subject matter of the articles that `caused' the blocks) I am completely unwilling to discuss our personal details with anyone that does require the shelter of anonymity. W. Frank00:58, 11 May 2007 (UTC)
I was involved in a disagreement with Gaimhreadhan, which was then carried on by W. Frank. Gaimhreadhan did seem to have taken a far more measured approach since his initial unblocking, and although he didn't discuss the sockpuppetry despite requests I don't see much merit in this block, it doesn't seem to be preventative. Even as a party who was involved in a mild dispute with him prior to the initial blocking, I'd support unblocking. One Night In Hackney30309:21, 9 May 2007 (UTC)
Thank you for your fairness, One Night In Hackney. Please do not take this the wrong way but I am happy to discuss these matters by phone or in person with anyone that does not require the shelter of anonymity. Because of security concerns (related to the industry we both work in and the subject matter of the articles that `caused' the blocks) I am completely unwilling to discuss our personal details with anyone that does require the shelter of anonymity. W. Frank00:58, 11 May 2007 (UTC)
I don't think the block still serves any purpose and would be happy for it to be lifted. I have notified Tyrenius of this discussion, as he's the blocking admin.-gadfium20:26, 9 May 2007 (UTC)
I have unblocked per the wish of this discussion. There is more talk related to this on User:W. Frank. Please note that the recent reinstatement of the sockpuppet block occurred only after I had requested an explanation and waited 4 days, but none was forthcoming. User:Gaimhreadhan ignored the request and carried on editing regardless. The question was how come User:W. Frank said he had emailed me, when the email was from Gaimhreadhan's email address and signed Gaimhreadhan. I am not aware this has been explained yet. There is other material relating to these two users, which I have not made public because of WP:BEANS. Tyrenius23:05, 10 May 2007 (UTC)
I am not a process wonk, God knows, but it does irritate me when a deletion is overturned without any comment whatsoever. I speedied corporate censorship as patent nonsense (which it is, in my view), and only found out it was back by looking in my deletion log. I have no problem at all with people reviewing, challenging or even undoing my deletions, but please, friends, at least let other admins know when you do it, otherwise we look like clowns, repeatedly deleting and undeleting stuff. Freely acknowledging past faults on my own part, restoring without notifying, especially where the content is blatant POV-pushing and likely to be reposted by the original POV-pushers, as in this case, is a great way to accidentally start a wheel war. I think we have enough low drama already without that. I promise to try to remember this, too, although as an arch-deletionist I don't often undo deletions. Guy (Help!) 12:14, 9 May 2007 (UTC)
Did you see the article as it was on 3 May 2007 (which mentioned Wikipedia) but overlook the shorter, more neutrally-worded stub that has been there since 27 December 2005 and doesn't? I think it's safe to say that speedying an article that has existed for so long is more or less always inadvisable, whatever the content. Reverting to the older version (and then using {{prod}} if it is still unsatisfactory) may have been a better course of action – Gurch12:27, 9 May 2007 (UTC)
Yes, and yes. The older article has only about half a dozen non-vandalism edits, links to a speech which does not mention the term (corporatism was not a widely-discussed concept in 1644) and was referenced solely to an anti-corporate tract, so the original article was almost certainly serving to advance an agenda as well. But this misses the point. I'm happy to accept I may be wrong, the problem is undeleting stuff without leaving any kind of note - even to say don't be silly. Guy (Help!) 12:43, 9 May 2007 (UTC)
Your deletion in the first place wasn't a good idea, so I'm not sure what the problem is. --badlydrawnjeff talk 12:47, 9 May 2007 (UTC)
That he would have liked a note about it, I think. Sounds reasonable to me. Perhaps Guy shouldn't have deleted the article in the first place (I haven't read it), but if that were the case a note pointing this out might actually be helpful in addition to being polite. --kingboyk12:52, 9 May 2007 (UTC)
There is never/rarely a rush to undelete anything. Unless it is obvious rouge, you ask the deleting admin to reconsider and wait. If you don't a response, or you can't agree, then off to DRV. Simple.--Docg12:55, 9 May 2007 (UTC)
Yes, at least talk to the admin, and if you cannot come to an agreement seek a larger consensus(with the exception of honest mistakes that are objectively obvious). HighInBC(Need help? Ask me)12:57, 9 May 2007 (UTC)
Those of us who were around when the speedy deletion criteria were first drawn up will remember that its purpose was to specify a a very limited set of circumstances within which an administrator may presume that the will of the community is to delete, without bothering to ask them. You should therefore never speedily delete an article unless you are certain that the community will wish it so. If in doubt, ask. A corollary of this is that if a good faith editor overturns or challenges your speedy deletion, you are automatically in the wrong for having deleted it in the first place. Hesperian12:59, 9 May 2007 (UTC)
Not in doubt - but not relevant. Highly POV articles are frequently re-created by the POV-pushers, and that is not good-faith. The vast majority of links in my deletion log that go blue, are either gross POV or spam, reposted by the original editor. Sometimes I make a bad call, which is fine, and I don't mind that being undone, but it is annoying not to be told about it. Guy (Help!) 16:22, 9 May 2007 (UTC)
And would not discussing it first increase the likelihood that both adimins will understand what is going on? Challenging a delete is fine, but talk about it. HighInBC(Need help? Ask me)13:02, 9 May 2007 (UTC)
Not sure what you disagree with. Even if we accept you are entirely right (which I don't, really, but that's tangential), a note to Guy telling him he was "wrong" might help. The best of us you learn from mistakes, after all. --kingboyk13:04, 9 May 2007 (UTC) (e/c)
(after numerous edit conflicts) Yes, I certainly agree that overturning an administrative (or indeed editorial) action without prior discussion is discourteous, and not even informing them after the fact is highly so. I was making a slightly different point. Hesperian13:08, 9 May 2007 (UTC)
... that point being that if I were to challenge one of Guy's deletions, Guy's next step must be to undelete, and then take it to AfD if he so wishes. The situation where he declines to undelete and we have to go off to DRV, as canvassed by Doc Glasgow and HighInBC, should never arise, as the mere fact that I have challenged Guy's speedy automatically renders it improper. (I'm just using Guy as a convenient example here - no offense or challenge to Guy is intended by it). Hesperian13:15, 9 May 2007 (UTC)
Not neccessarily disagreeing with that. But, someone times when a deletion is challenged as seemly poor, the deleting admin is able to say either 'oh, your right' or 'no, you've not notices that...'. In many cases the two can reach an agreement or if they can't they can agree that there's a discussion to be had which then goes to afd or drv depending. Discussion always comes first, and the CSD are not exhaustive.--Docg13:38, 9 May 2007 (UTC)
Must? I'd say it depends on the article. I'd be more likely to accept some people's word on that than others. Sometimes DRV is a better venue, when having the article during the debate may cause harm (thinking here of actions in response to OTRS complaints, in particular). Guy (Help!) 16:24, 9 May 2007 (UTC)
The point of seeking a larger consensus is that there is a possibility you are wrong, not saying that is the case here, but a sanity check is always nice. You may be right on technical grounds, but seeking consensus is beneficial, even if not mandatory. HighInBC(Need help? Ask me)13:44, 9 May 2007 (UTC)
Was that to me? I completely agree. The problem is not being challenged, it's being reverted without anyone bothering to say anything. Maybe it's irrational to be pissed off by that, who knows. Guy (Help!) 20:21, 9 May 2007 (UTC)
<sigh> No need to prejudice the discussion in this way. The absence of bizarreness is adequately covered at the AfD. You could have just linked to the new discussion, instead of characterising the first closure as bizarre, but hey, in a thread titled "Gaaaah!" that is par for the course. Carcharoth10:57, 10 May 2007 (UTC)
Identifying repeat noticeboard reportees
I've just created {{userlinks-an}}, a {{userlinks}} variant, for use on the admins' noticeboards (here and ANI, etc.) It contains a link to use the ~eagle AN/ANI/CN/3RR archive search on the toolserver (thanks, Eagle 101 and GeorgeMoney, for creating it) to search for mentions of a username on those pages (it's designed to try to avoid the sig of the user themself, although it probably isn't perfect in this regard, with both false negatives and false positives likely). For instance, Ais523 (talk·contribs·logs·block user·block log·search noticeboard archives) will show all the times I've been mentioned at AN and AN/I. What do people think of this? --ais523 10:43, 10 May 2007 (UTC)
I think I haven't been mentioned nearly often enough. Clearly I need to create some kind of major drama. I'll get back to you – Gurch11:52, 10 May 2007 (UTC)
Most of the credit should go to Eagle 101 and GeorgeMoney for creating the search tool in the first place; I just worked out the template coding and the regexp required. ais52316:00, 10 May 2007 (UTC)
How do I deal with this? [13]. He was previously blocked for this [14]. I've been checking his images because he has a habit of uploading from Flickr with the wrong licensing tags... Not a dog11:01, 10 May 2007 (UTC)
Looks like you've already responded ([15]) and I think you handled it pretty well. My advice is to stay cool, report any further breaches of WP:CIVIL/WP:NPA and don't be put off. You're doing nothing wrong by keeping an eye on a user who makes frequent mistakes (assuming good faith). If he continues to breach the rules having been warned, that's verging on vandalism and should be reported as such. Waggers14:25, 10 May 2007 (UTC)
We have an OTRS complaint re Celebrity (game). The complainant asserts that he owns the name "Celebrity" as applied to games. The game appears, as far as I can tell from a Google search, to be generic, a parlour game. The article is a how-to, which the complainant does not appear to like (impacts on ability to sell for profit). Google search is not especially helpful, due to the generic nature of any searches; I cannot verify whether the game is ripped off from the published game, a generic parlour game which was incidentally published, or somewhere between the two. I also can't find sources for the history of the game, which is what the article needs to avoid deletion as a game guide / how-to. I do not know what to do for the best here. I thought I'd already posted this, but can't find it, so apologies if this is a duplicate. Guy (Help!) 13:47, 10 May 2007 (UTC)
Now now, that's not true. But hopefully this helps answer the questions - it's worth noting that the corporate site suggests that they produced this game in 2000, the second link predates it by at least six years. A rename may be in order. --badlydrawnjeff talk 14:04, 10 May 2007 (UTC)
Yes, you did post before but iirc you didn't link to the article :P I'll take a look. --kingboyk14:06, 10 May 2007 (UTC) (e/c *2)
Well, I for one have definitely played this game, and it wasn't any kind of "official published version". Not that this helps, but thought I'd say so. --Ali'i14:08, 10 May 2007 (UTC)
I'm not sure I understand this complaint. Is the person claiming we have infringed copyright? If that's the case, we could figure it out if they would show us where the text is allegedly copied from. I would like to see the article have a source backing up the name, though (which Jeff's sources don't show), because if someone else has used the name to refer to the game, we're just commenting on that. Mangojuicetalk14:12, 10 May 2007 (UTC)
I believe this is similar to the drinking game AfDs from last year - they're known by a variety of names, but are created under the name whichever person got around to creating the article. We may very well have this article on Wikipedia already under a separate name. --badlydrawnjeff talk 14:16, 10 May 2007 (UTC)
Possible breach of WP:NOT#INDISCRIMINATE. Besides that, if he owns a trademark the article can say so, it doesn't stop us covering it. Sounds spurious to me. If, OTOH, he's claiming a copyvio I think we need to see some proof. --kingboyk14:14, 10 May 2007 (UTC)
Why are all the blue-links turning red? The articles are still there, but the links are red. Maybe some CSS glitch? (I'm using monobook). Some are still blue, others are red. It varies as you refresh it. Surreal. Oh, and not really red, as Pastor David says. Maroon is a good description. Carcharoth15:21, 10 May 2007 (UTC)
It looks to me like articles are red (or maroon), and some wikipedia space things, while everything else is still blue. hmmm Pastor David†15:23, 10 May 2007 (UTC)
Please don't post if you have nothing productive to say; it just causes repeated edit conflicts. —Centrx→talk • 15:31, 10 May 2007 (UTC)
It's a bug. Article links are being tagged with class="stub" which is generally a feature you can find in Preferences->Misc->Threshhold for stub display to change the link color for short articles. —Centrx→talk • 15:30, 10 May 2007 (UTC)
Fix. Go to Preferences -> Misc -> Threshold for stub display and change the 0 to a larger number, like 8000. That should fix the problem for you. CMummert · talk 15:37, 10 May 2007 (UTC)
Without changing anythin in my settings, this appears to have been fixed. Thanks for all the hardwork. It was quite unnerving (the sky is falling, the sky is falling ...) Pastor David†15:41, 10 May 2007 (UTC)
Now that it's fixed, and I understand it, it is kind of a neat feature. Setting the threshold to 0 leaves the display the same. Setting it at a certain number colors the links for all articles shorter than that number as maroon - so that you know that they are stubs. I found that 6000 is about right. Pastor David†15:47, 10 May 2007 (UTC)
But, but, nearly everything is stubs. Oh no. If we want them to turn blue again, we will have to write some content. Oh. Hang on. You can't fool us that easily!! :-) (off to turn a maroon link blue.) Carcharoth16:00, 10 May 2007 (UTC)
Styling stub links with css
You can style stub links with CSS so that they are the same color but distinguished in some other way. I am trying the following code to see if I like it: a little superscript s after a stub link, but with the usual colors. It works in Firefox but maybe not in IE. CMummert · talk 17:53, 10 May 2007 (UTC)
Previous posting here at ANI went completely ignored, and as the problem is a long term issue it probably needs to be in AN anyway. User has a consistent history dating back to September of last year of making up his own arbitrary names for wrestling moves and adding them to articles. Way back when he was warned about this, repeatedly, and constantly ignored the warnings. He was blocked for disruption due to these edits and stopped for a bit but returned later and since then has been continuing his effort of changing wrestling articles to his own made up names. The only edits he makes outside of adding his own names to wrestling moves are vandalism to other articles, and he has received a total of four test4 warnings for what is pretty much vandalism. Any effort to talk to him is ignored and every warning is ignored. This requires admin intervention. –– Lid(Talk)19:17, 10 May 2007 (UTC)
A quick scan through this user's recent edits shows no obvious vandalism nor edits of the type you are complaining about. His talk page warnigns are all weeks or months old. Can you provide diffs to any recent edits you think are problems? Several of this user's recent edits do not seem to match your descriptions. DES(talk)19:45, 10 May 2007 (UTC)
I could keep finding more but I think that's enough for now. To someone looking in from the outside the edits don't look like vandalism but they are completely made up names, randomly added prefixes or suffixes, or applying a move that isn't the move the name applies to. –– Lid(Talk)20:03, 10 May 2007 (UTC)
The user is obviously doing what he's doing in good faith. He's been adding {{GFDL-presumed}} to many images that were uploaded long after the cutoff date of January 1, 2006. In addition, he's been adding {{pd-self}} and probably other templates to different images as well. There's no problem with his conduct as he seems to have been mislead, I'm just posting here as I need help reverting all inappropriate additions of license tags by him. Yonatantalk20:15, 10 May 2007 (UTC)
Somebody please delete or BJAODN the template that appears here and in other edits by the same IP. He may have just made it up for one-time use, but he may also have "subst"ed it, and I can't track it down. Thanks. 129.98.212.73 01:26, 11 May 2007 (UTC)
User:Chloride was blocked a few days ago for being a vandalism account. However, though he did vandalize and confessed to being a sock-puppet of User:Elspeth Monro, he created many articles about battery companies. I deleted a few of them that seemed to be particularly non-notable or hoaxes, but some appear to be legitimate articles, though they often contain many typo corrections. But because of the vandalism by this user, can somoene help go through this user's contributions to make sure that the rest of these articles are really legitimate and written correctly? I tried to sort some of this out, but it's getting confusing and I have to go offline for the evening. Does anyone have any other comments about what should be done? Thanks. Academic Challenger04:12, 11 May 2007 (UTC)
A previous section of this page makes it clear that DennisGay shouldn't have been blocked. Can some admin please unblock the autoblock he caused, #496143? OdMishehu05:40, 11 May 2007 (UTC)
I am in a dispute with user:Momento about two highly diverging versions of the article. We are both completely unwilling to use the other sides' version as a basis for further improvement. Basically, I think the old, long version was reasonable good and intense efforts has been done to sourcing over a period of 3 to 4 years. User:Momento has made a new shortened re-write that I believe is significantly flawed and has many, many issues to be resolved. I estimate that it would cost me one year to bring the quality of the new, shortened version to the standard of the old, long version. I think this is a near-complete waste of time. I am willing to shorten the old, long version but only when using the old version as a basis. No compromise seems in sight. What to do? Andries05:02, 10 May 2007 (UTC)
Contrary to Andries claim the old version is the basis of the new version. The major difference is that the old version was severely criticised by two independent GA reviewers for being "bloated" and "too long" and in need of "merciless editing". I initiated a rewrite and with the help of other editor's, an independent reviewer and two month's hard work, a shorter version has been created. It was reviewed several times by one of the original GA reviewers and pronounced "very good". Andries' objection to the new version stems from several editor's desire to see it attain GA status. Andries' is a regular poster on an anti- Prem Rawat website and seeks only to contribute negatively to the Rawat article. Andries was banned indefinitely from editing Sathya Sai Baba and related articles or their talk pages for similar behaviour.Momento00:02, 11 May 2007 (UTC)
I admit that the old version is too long, but your re-write only improves the length issue and introduces many serious flaws. Andries18:03, 11 May 2007 (UTC)
I gave several examples where your re-write is seriously flawed, but I am unwilling to give an exhaustive list of mistakes and flaws, because a reasonable version is available at our fingertips that has far fewer and less serious flaws. Andries18:08, 11 May 2007 (UTC)
Momento, please first make sure that the new re-write is better than the old long version and only then replace the old version. That is the write (right) order. Andries18:09, 11 May 2007 (UTC)
List of people by name
This set of lists has been nominated for deletion about 6 times now, but people keep !voting to retain them basically because they like it.
There are 370,000 biographies known to WikiProject Biography on Wikipedia; the true number is probably far north of that. Having any sort of catch all list when this number of articles is involved just ridiculous. Having an incomplete list seems pretty useless too, and is to an extent original research. The lists are redundant to the category scheme too.
So, after 6 nominations that didn't succeed you want this deleted by going here? Why didn't you take this to deletion review if you believe the closer didn't properly discard the WP:ILIKEIT !votes? This is not the way to delete articles unless you believe that it could be speedy deleted. MartinDK14:44, 10 May 2007 (UTC)
I'm an admin and here's where we discuss issues which might be of interest to the community and admins in particular. Problem? I'm asking for suggestions: perhaps it is speediable, perhaps it should go to AFD again, perhaps I should let it lie. Hence the question. --kingboyk15:09, 10 May 2007 (UTC)
I quite simply wondered why you didn't take this to deletion review since that is how this kind of thing is normally handled. Especially after 6 nominations. Also, I'm quite familiar with what this page is and it says at the top of it that non-admins are free to leave comments. But I will just buzz off then. MartinDK15:16, 10 May 2007 (UTC)
No, you're quite welcome to comment, I thought I made that clear. I don't know why you're telling me to take it to DRV, I'm not appealing any closure. I'm merely stating my opinion that this is utter crap that needs to be deleted! --kingboyk15:32, 10 May 2007 (UTC)
Haha, I thought you were joking, then I clicked through the list .. and wow ... we actually do have huge lists of people by name. Totally unexpected to me. --Cyde Weys14:57, 10 May 2007 (UTC)
Oh and "a bit unwieldy" is something of an understatement. It's scope covers approximately 25% of all the articles on Wikipedia, and what use is it if it's not complete? --kingboyk21:59, 10 May 2007 (UTC)
Why?, and no. I doubt I can be convinced that an area of interest which has maybe 400,000 articles on Wikipedia can be listified, nor that a selected list is not useless. --kingboyk15:30, 10 May 2007 (UTC)
My opinion is that it contains useful red-links. Someone would need to strip out the red-links, or at least devise a way to generate a similar set of lists from categories, before quietly putting it to rest. I'd wait until the technology makes the list obsolete. The technology is not quite there yet. Carcharoth15:39, 10 May 2007 (UTC)
Red links are a maintenance issue. Maintenance should happen in project space. It would be quite possible to have a bot create such a list and place it on a WikiProject Biography page. --kingboyk15:42, 10 May 2007 (UTC)
The red links are in any case of no use whatsoever in a list like this. Far more likely to be filled in a project-specific or subject-specific list. Guy (Help!) 16:02, 10 May 2007 (UTC)
You might not like it, but surely this is exactly the kind of case where WP:IAR applies, particularly as consensus has shown time and time again that this shouldn't be deleted? Doesn't WP:CONSENSUSgenerally overrule policy? That said, I'd be in favour of categorising it if at all possible... -Halo21:50, 10 May 2007 (UTC)
I don't mean "ignoring all rules and delete it" - deleting things citing WP:IAR, in my view, is plain abuse of administrator privileges. I'm saying that if enough people vote "keep" because of WP:ILIKEIT, and one of existing [[WP:PILLARS] doesn't cover it, consensus has spoke and as such WP:IAR comes into play where the policies don't actually matter for that individual case. Of course, there's one or two exceptions (which I'm not 100% convinced of myself), but still... That said, you are right about the category, but it doesn't actually tell you who the people were, which gives me the feeling that List of people by name isn't quite as absurd as it first sounds, even if I find it a bit overly kludgey with sub-sub-sub-categories to be useful to myself personally. The theory behind a giant reference list of names with an overview of each person is something I could quite get behind myself, and I actually quite like the idea if not the implementation of it... -Halo22:08, 10 May 2007 (UTC)
Could another admin review my block of User:Reachouttrust, I blocked it as a username violation because it was promotional for Reachout Trust, if you check their contribs, you will also notice that they were editing Reachout Trust. Now I quote WP:U#PROMOTIONAL (under innappropriate usernames), Promotional usernames that attempt to promote a group or company on Wikipedia, including but not limited to: Usernames that match the name of a company or group, especially if the user promotes it.User:Doc glasgow contacted me about the block and although I have stated the reason it is against policy, he has overturned my block with a reason, "no reason to block this. ID confirmed by OTRS anyway)" - Firstly, I can see a very good reason per WP:U to block this, secondally, since when was a user allowed to promote their group using their username as long as they confirmed they were the company? Ryan Postlethwaite15:53, 10 May 2007 (UTC)
I overturned this in response to an OTRS contact. I can confirm that the user represents the association in question - and I've asked him to contribute to the article by constructively commenting on the userpage. He was blocked without warning and was a little confused. My reasons for doing this were 1) WP:AGF and see if he can indeed make useful contributions to the article. If not, then we block him for revert waring, pov pushing or whatever - but he's not done any of these things yet. 2) Yes, he's got a conflict of interest - but it is better than this is out in the open, rather than he logs in under a different name and pretends to be neutral. I say again, there has been no disruption here. Yes, he posted an article about his organisation - but others have worked on it and it now looks OK. Anyway, there's no hard and fast rule about not posting article about yourself - we just discourage it. A n00b doesn't know our rules, or the intricacies of our username policy, which even I don't understand. Seems to me too many people are far too fast with username blocks these days.--Docg16:08, 10 May 2007 (UTC)
The original block seems reasonable to me, and Doc's reasons for unblocking do too. Sounds like the situation is fine as it is right now. Friday(talk)16:20, 10 May 2007 (UTC)
The blocking policy does suggest to seek a greater consensus if you cannot come to agreement with the blocking admin before unblocking. HighInBC(Need help? Ask me)16:44, 10 May 2007 (UTC)
I think the policy page needs changed. It seems that to block people, without warning, who use their organisation's name and thus are upfront about their conflic of interests, breaches WP:BITEWP:AGF and the long-held idea that everyone but vicious vandals merit discussion before people jump in with the tools. I am greatly afraid that zealous admins who like blocking things will use that crazy policy to justify more of this. This is bad, bad, bad. I don't recall any major discussion about this - when did we depart from WP:AGF? Where did this new policy come from?--Docg17:27, 10 May 2007 (UTC)
I think the intent of that particular part of the username policy has two facets, one is the passing off as representing the company/person/whatever, the other is in line with not being a vehicle for advertising or self promotion. Having your companies name appear littered throughout talk pages and page histories can be pretty spammy. Like most it's a case of considering each instance on its own merits. --pgk17:34, 10 May 2007 (UTC)
This is why I brought it here, the fact is it is in policy, a username which is the name of a group or company aren't allowed, if they are actively editing their own article, it shows that they certainly are using their name for promotion (whether they mean to or not) - as I said to you, it was a blatant infringement of the policy (I'm not saying that it was offensive or anything, it was just blatant) so I blocked. I left the {{UsernameBlocked}} template on their userpage giving a full reason that the name was against policy and it gave them details of how they could request a name change or simply change their name. The point is, I did things by the book, I don't agree a quick sharp username block is biting, it's a lot better to get the block in quicker rather than subjecting a new user to a massive disccusion about their name. Ryan Postlethwaite17:35, 10 May 2007 (UTC)
It is always better to use your head, rather than follow policy to the letter. This use was only editing his own article. If the article was spam - fine - delete it and tell him not to do that. But in this case, the article is/was salvageable and a bit of discussion with the use wouldn't go a miss. Sure, if someone is passing themselves off as microsoft, or using 'user:shop at Joe's' hit them with a block - but a bit of investigation here would have shown every likelyhood that the user wasn't really spamming or disrupting. When User:Bill Smith - creates Bill Smith (musician) we don't hit him with a block. Policies are fine if commons sense is used too - following policy to the letter is what ends up in trouble.--Docg17:44, 10 May 2007 (UTC)
I do agree with you to some extent, but the problem is this username is spam (not just the article), you probably don't realise the number of usernames which are blocked on sight, no discussion (I'm not just meaning me) for promoting a group or company, it happens all the time. It's not simply the article being spam, it's the fact that every time they edit, they will have free advertising for their company/group in the histories, watchilists. They are more than welcome to request an unblock to change their name, as I said, the point is it's in policy, if people disagree with it, WT:U may be the place to start. Ryan Postlethwaite17:49, 10 May 2007 (UTC)
I agree that User:Ryan Postlethwaite followed existing policy and procedure. i further believe that he was right to do so, and that this policy is a good one, and that this user name in particular, and such usernames in general, are spammy. Moreover, we generally ban "role accounts" and i don't think we normally want soemone being presented as an "official representative" of a company or institution. If an editor is an official or employee of a firm or org, that fact should be disclosed on that editor's user page, but the editor should still be, and be treated as, an individual, not a firm. I would favor asking this user to change username, and blocking if a change is not started reasonably promptly. DES(talk)18:01, 10 May 2007 (UTC)
Accounts are supposed to be for individuals, not multiple people. With accounts named after organizations, it is unclear if one person is using it or it's a role account. While preventing accounts names after organizations doesn't prevent people from sharing the same account, I do think it tends to make it less likely. There is also the issue that we have no way of knowing in many cases whether the person with the account is authorized by the organization to publicly represent it. -- JLaTondre12:21, 11 May 2007 (UTC)