User talk:Jamesday
If you want to contact me I recommend using the email option. Unless I'm changing something I usually read without being logged in and there may be a long delay before I see your comment. Thanks! :)
All New: 5 10 15 20 25 30 35 40 Orphaned: 500 1001 1501
West publishing is not a wiki
[edit]I do not agree with the statement that the situation with Wikipedia is equivalent to the decisions in West Publishing cases. Wikipedia can clearly be distinguished on the facts. How? it is two way, not one way and West just adds trivial stuff as a corporate entity, here you have a voluntary association with thousands of members (unless you confuse Wikimedia with Wikipedia, they are not the same thing at all). Moreover, there is the issue of a group copyright owned jointly, when you say you are working for Wikipedia this means you are representing all contributors, therefore the rights owned by the conglomerate of Wikipedians taken together is an exclusive right, no matter how you look at it as no one else collectively owns the rights. This is what makes wiki software a true innovation vis-a-vis copyright law. Copyright is owned collectively by a group on the wiki (no where else) and anyone on the wiki who decides to represent themselves as the spokesperson for the group can do so, as is often done and tolerated here as a matter of custom. I would not make pronouncements about law that are untested, just argue for all of the options that could be put forward, unless you want to sue Wikipedia to find out I doubt that we will have any clear cut answer, but my position is that Wikipedia does have a copyright as it is not the same as the software developed by the Free Software Foundation. Cheers. — Alex756 [http://www.wikipedia.org/wiki/User_talk:Alex756 talk] 04:51, 2 Feb 2004 (UTC)
I distinguish between the Wikipedia, a business unit of the Wikimedia Foundation, with a trademark I think is owned by that Foundation (if its ownership is clear at all), and Wikipedians. If the Wikipedia/Wikimedia Foundation owns the copyright it can assign it (perhaps accidentally as part of a print deal) or otherwise limit its freedom. That's a strongly negative result for a work intending to be free, so avoiding any possibility of the Wikipedia/Wikimedia Foundation owning the work is necessary to keep the work free. Avoiding the whole Wikipedia work being a collective work owned by all who have contributed any article is necessary to avoid any potentially infringing party contributing something to a few articles and then being protected from infringement claims as a co-author. Viewing each article as an individual work, owned only by those who have made a copyright-significant contribution seems like a safer course. Not as easy for taking infringement action becuase it's necesssary to find a useful subset of Wikipedians (those who have contributed article work) to be a sufficiently substantive part of a work that prevailing will harm the infringing work substantially. That is doable, provided he Wikipedia/Wikimedia Foundation is behaving properly. If it ever seeks to abuse its position, via soe future board we can't know about, the required support for infringement actions will dry up and it'll find itself powerless to take infringement action against forks seeking to behave properly. It's a very useful strategy to help to keep the work free. The usual indemnification clauses for a publication contract seems to me to be best provided for by insurance, not by discouraging contributors by trying to get them to indemnify for things happening in jurisdictions they don't contemplate, in forms they may never have contemplated - more a business argument than a legal one. Jamesday 01:02, 2 Mar 2004 (UTC)
Your advice on an image sought
[edit]Hello Jamesday, could you please take a quick look at Image:mjf_1983.png and tell we whether or not using this picture on Montreux Jazz Festival this is indeed fair use. Thanks, Lupo 12:13, 4 Feb 2004 (UTC)
- Wow, that was fast! Muchas graçias! Lupo 12:19, 4 Feb 2004 (UTC)
You wrote: Please refrain from engaging in the revert war over the redirect at Terrorism against Israelis. The matter is in discussion at the talk page of Violence against Israelis and that's the place to sort out what the article should be called. If you revert again prior to the matter being resolved by discussion I'll protect the page so resolution can happen through consensus rather than a revert war. Jamesday 16:35, 10 Feb 2004 (UTC)
- Yes indeed, the matter is under discussion when User:Viajero started editting that page and others it refers to...I have been reverting his edits. his edits are based upon the assumption that his view will prevail...it very well might, but the edits should wait for the discussion to resolve the matter, I would think. As can be seen from the edit which began the matter:
(cur) (last) . . 11:06, 10 Feb 2004 . . Viajero (#REDIRECT Violence_against_Israelis) OneVoice 18:28, 10 Feb 2004 (UTC)
JamesDay, please take a look at the text at the end of Talk:EdPoor it seems that the non-stop deletion of material and revision of articles is being persued by Viajero and Zero0000 on a number of other pages with the two acting in concert. OneVoice 19:26, 10 Feb 2004 (UTC)
Copyright
[edit]Sorry. I didn't think that was fair use. --Ed Senft! 13:07, 11 Feb 2004 (UTC)
The page where I got it doesn't said something of a permission. There are other pics with the advice to ask for a permission, but not at this one, so it think that no permission is needed. Sp4z 16:17, 11 Feb 2004 (UTC)
Yes I realize that I made that mistake. I don't know if that image is fair use. Personally, I think it is ugly and might not belong in wikipedia (some ugly things belong in wikipedia though). Is this image fair use in your opinion? --Ed Senft! 17:35, 11 Feb 2004 (UTC)
Swapping articles
[edit]Please don't do anything to the articles Bogosort, Stupid sort and Stupid sort swap temp or variations of them for the next hour. I'm swapping a new version of Bogosort which was written at Stupid sort with bogosort and someone renaming back part way through the move causes a random version to be deleted. In this case, it was the new one. I'll let you know when the swap and is complete so you can see why preserving the history rather than doing a copy and paste move was the course agreed in IRC discussion. Jamesday 17:54, 11 Feb 2004 (UTC)
- I am sorry about this matter. I had no idea. I saw swap in the title but the algorithm seems not quite related to swapping, though it is involved. So I just changed the name. Please regard this as an accident, careless. -- Taku 18:14, Feb 11, 2004 (UTC)
Copyright question
[edit]A new user asked me if it was acceptable to download images from Wikipedia, alter them, and repost them to Wikipedia. I told him it was, as I'm fairly sure, but I'd like some confirmation. This is OK, right? And is it in any way affected by the source of the image (e.g. fair use etc.)? Thanks very much, Meelar 22:24, 14 Feb 2004 (UTC)
Request for Comments on Plautus satire
[edit]Your comments are requested on Wikipedia:Requests for comment/Plautus satire. →Raul654 05:14, Feb 19, 2004 (UTC)
I don't work for NASA. After receiving your message, I updated my user page to make that clear. NASA 22:26, 19 Feb 2004 (UTC)
Is that possible? How do I change my name? I looked for it in the preferences. I want to change the name to FBI or CIA. NASA 22:59, 19 Feb 2004 (UTC)
Plautus satire (again)
[edit]James - it appears that Plautus has decided to ignore what you have told him (to move to less conspiracy-theory suseptible articles), and has instead decided to take to expand his tin-foil hattery vandalism to include several other articles. A glance at his talk page shows that talking with him in an excercise in frustration. I think you might want to reconsider your vote at Wikipedia:Requests for comment/Plautus satire. →Raul654 02:17, Feb 21, 2004 (UTC)
USAF Museum images
[edit]I agree with you that the USAF Museum's conditions of use are probably over-reaching, in terms of copyright -- merely scanning, cropping, resizing, levels adjustment don't rise to the level of artistic output. The only legal leg they have to stand on is that SOME material in the USAF Museum's archives is not public domain, but donated from corporations or individuals and under different conditions of use, and the museum doesn't want the responsibility of keeping track of which images on their web site are from PD sources and which aren't.
It seems mostly, though, to do with a bad attitude. Firstly, a resentment of their scanning work being used by other websites. Secondly, that they want people to have to come to their website to get the info so that they get website hits to boast of (justifying their mission, I guess).
They offer the justification of 'well, you always had to come to our archives in person before to get USAF images, so it's not like we're taking anything away'. Well, they say on the same site that their archives are (post Sep 11 2001) closed to the public!
My considered opinion about the images being used on Wikipedia: we most likely have the legal right to do so. However, given the Museum's stated opposition to such use, we are probably better off using images whose source doesn't disapprove of the use; and sources where we can verify that the images are indeed public domain, which the USAF Museum won't do.
- What is really stupid about the USAF site is that they say "Information presented on the USAF Museum web site is considered public information and may be distributed or copied", but then try and impose conditions. Now, I'm not sure what the precise legal definition of public information is, but on all other US Government websites that I have seen, "public information" is synonymous with public domain.
- Their mealy-mouthed excuse about the Research division archives being indexed differently than the website is, in my opinion, a bunch of crap. THEY should have done the cross-referencing before putting the photographs on the website. Others, like the Naval Historical Center can do it, and the NHC is not exactly a huge organisation. The rules may "always have been this way", but that is no excuse for not changing things to reflect the internet. It also doesn't reflect post-9/11. Perhaps they should think about cataloguing their holdings properly? If they have volunteers who are willing to run a website, perhaps they could get volunteers who are willing to catalogue things. Also, perhaps they should not be running the website on a .mil domain if it is a private website.
- All in all, I agree it is a completely ridiculous situation. I will email them to try and cajole them into changing the wording of their site. They certainly need to. David Newton 19:40, 21 Feb 2004 (UTC)
On the online law section, I've put in the relevant bits of current British copyright law to define what constitutes a work eligible for copyright in the UK. I've also found a definition on the UK Patent Office site that defines what exactly originality is for a work in the UK. David Newton 03:28, 22 Feb 2004 (UTC)
Linkback
[edit]It appears that v2.0 of cc-by will have a linkback requirement: see http://creativecommons.org/drafts/license2.0 , section 4(d). CC summarised it as "Licensees will only be required to link back to licensors if (1) it's reasonably practical to do so; (2) the licensor actually specifies a URI; (3) that URI actually points to license information about the work". So, that's nice. Martin 20:02, 22 Feb 2004 (UTC)
ISS
[edit]I looked but could no longer find the article I read which claimed 75% completion of spacewalk tasks. Probably means they were wrong and pulled the article (or edited it beyond recognition) Rmhermen 22:49, Mar 1, 2004 (UTC)
Look, of course the editor was not a new user. It's obvious that it's Lance/Hector. But LanceMurdoch and HectorRodriguez weren't banned. This user has a problem with POV, but he's being singled-out because his ideology isn't popular. On the Stalin article, for instance, most of his changes were long needed. Please don't make a sweeping change back to the 2/28 version. 172 01:41, 4 Mar 2004 (UTC)
Best Wishes
[edit]Hi, just received your wishes on my talk. I would like to give you my Best Wishes for Happiness, Good Luck and Peace Profound. Optim 19:11, 6 Mar 2004 (UTC)
Deleted Userpages
[edit]- Yes, you can undelete my userpage/talkpage, and list them on speedy deletions. Optim 19:53, 6 Mar 2004 (UTC)
- As you can see, this has the effect of redlinking everything Optim's ever signed. I agree the history should go at his request, but there ought to be a placeholder I think. - Hephaestos|§ 20:14, 6 Mar 2004 (UTC)
revert wars
[edit]I opened your talk page to thank you for illustrating how to interject in a numbered list without screwing up the numbering (I didn't realise it was possible)... then I notice you've made a great suggestion for refinement too. :) Do you think it would be more useful to change the voting headings to say "I support the propsal with this amendment", "I am opposed to the proposal including this amendment" or something like that, so that people who were in favor of my idea can still vote to say that they prefer/like yours also? Otherwise none of the yes votes to my proposal can be considered to be backing your amendment, and perhaps some of them would prefer that? fabiform | talk 14:44, 11 Mar 2004 (UTC)
- Done! And I just realised that I had appeared to vote in a html comment in every section. Whoops, they were supposed to show as <!--- #~~~~ ---> for quick voting, not make me look terminally undecided. :) fabiform | talk 15:42, 11 Mar 2004 (UTC)
Dastar Corp. v. Twentieth Century Fox Film Corp.
[edit]The page you created, Dastar Corp. v. Twentieth Century Fox Film Corp., is on VfD right now. Just thought you might want to know, in case you were planning to use it. Yours, Meelar 15:45, 11 Mar 2004 (UTC)
Copyright question
[edit]Hi, Mikkalai has asked my advice on the issues raised at Talk:The Red Book of the Peoples of the Russian Empire. I think you would be able to better help that I can, so I hope you don't mind me redirecting this question to you. Angela. 20:11, Mar 14, 2004 (UTC)
24 hour bans for edit wars
[edit]Hi Jamesday,
I've amended the proposal on 24 hour bans for edit wars. In short, the amendment calls for a quickpoll to take place before any such ban can be implemented. If you support this, I'd like you to add your vote in favor to the 24 hour ban vote, with the comment "with quickpolls".
Please also participate in the discussion on Wikipedia talk:Quickpolls.—Eloquence 22:16, Mar 14, 2004 (UTC)
- Heh. Thanks for catching that sysop editing thing. I guess we've got a lot of repeat violators ... —Eloquence 22:47, Mar 14, 2004 (UTC)
Re: Freedom Tower
[edit]Hi Jamesday, this topic has already been discussed and resolved. It is true that these images are copyrighted and I clearly put it is copyrighted and the source which it was released to the public by the LMDC. If you have any more questions you can reply back on my Talk Page or the Freedom Tower Talk Page. -ZackDude
- Again, the specification image of the Freedom Tower has already been discussed. It's actually still on my talk page. The image was re-released by me into the Public Domain and that is all to it. - ZackDude 01:31, 23 Mar 2004 (UTC)
message
[edit]I intially agreed with your view apprently it depends on the time zone as to whether it is one day or not. GrazingshipIV 03:58, Mar 31, 2004 (UTC)
"Republican" Clarke
[edit]I think I understand your point, but I think we have a problem with the description of Clarke as a Republican. He served both Republican and Democratic administrations (all eight years of Clinton). To tag him "Republican" suggests a Republican critic of a Republican president, but his role is this dispute is more professional and perhaps personal than political, per se.
IOW, he is an advisor rather than a politician, which is suggested by mentioning his party identification, and should be viewed in a different light than if a well-known but maverick Republican like John McCain (for example) were to oppose Bush. Cecropia 06:40, 4 Apr 2004 (UTC)
Polish
[edit]I don't suppose you want to take on yourself to standardize Krakow/Kraków or Gdansk/Gdańsk in the St Mary article and the relevant article titles. :) --Dante Alighieri | Talk 22:44, Apr 5, 2004 (UTC)
Meta sysop
[edit]Congratulations! You are now a Meta administrator. Please read the Meta:Deletion policy before deleting anything, and make sure you understand how to edit pages such as the fundraising page before doing so. Angela. 21:39, Apr 12, 2004 (UTC)
Fair use of music
[edit]Excellent! This means I'll go back to providing samples for a couple of artists. Thanks for the information. Fredrik 23:18, 18 Apr 2004 (UTC)
Since I'm from Sweden, would that mean any infringements will be subject to Swedish law? Hmm. Anyway, the one clip I've uploaded before is media:NonFreeImageRemoved.svg, which is less than 30 seconds long and tagged with copyright information... Fredrik 23:44, 18 Apr 2004 (UTC)
eh James. Thanks for the m:Steward matter :-) It meant a lot to me :-) 'cause these were hard times. Feel free to criticize if I wander SweetLittleFluffyThing 20:06, 20 Apr 2004 (UTC)
I'm sure it'll happen eventually.:)
- Knowing myself, I am sure it will happen ;-)
Perhaps mediation?
[edit]Given the disputes you're involved in, have you considered the use of mediation between you and those you're disagreeing with as a possible way to resolve the disputes? Jamesday 21:28, 21 Apr 2004 (UTC)
"Mediation" will not likely resolve the disputes, as there is a cabal of "lying hypocrites" within Wikipedia that will not listen to reason nor act in "good faith", and will do and say "anything", including "bald-faced" lies, in their slanderous campaign to have me banned and censored and mostly due to my "unpopular" religion of cosmotheism that requires me to uphold the WHOLE TRUTHS of REALITY, for their own sake, without regard to egotism or self-delusion.-PV
Adminship
[edit]I have nominated you for adminship at sep11:Wikipedia:Administrators. --"DICK" CHENEY 16:00, 3 May 2004 (UTC)
I just wanted to let you know that Maximus Rex now has 80% support at sep11:Wikipedia:Administrators --"DICK" CHENEY 01:57, 16 May 2004 (UTC)
Scatman John
[edit]I replied to your comment. Check out my comment page. ---Dagestan
Hello--Jimbo The troll Slayer 05:22, 13 May 2004 (UTC)
From Chris Mahan
[edit]Answered your questions on my talk page. Christopher Mahan 15:47, 13 May 2004 (UTC)
Thank you for your questions. I've replied at User talk:Angela/Questions. Angela. 21:02, May 13, 2004 (UTC)
Your question
[edit]Just to let you know, I have posted my response to your inquiry at User:Michael Snow/Candidate statement and discussion. --Michael Snow 00:40, 14 May 2004 (UTC)
Opt-out
[edit]Hi. I'm active mostly at Japanese wikipedia, but interested in learning a bit more about how legal matters are handled here.
I saw your statement at Wikipedia:Submission_Standards/copyright_compliance_opt_out_application. I am wondering if I may ask you to tell me what that is about.
I understand that it is about enforcing potential GFDL violation. I also see that you are concerned about your licensee (esp. when they use your contents under different licenses such as, say, BSD or creative commons attribution).
But as I read the submission standards, the Wikimedia Foundation does not act as the exclusive compliance enforcement agent. More importantly, the standards seem to say that Wikimedia Foundation act only when certain conditions are met, and if you allow others to use your content elsewhere, then the Foundation does not enforce your right.
So, it seems you don't need to opt-out at all.
Thanks, Tomos 02:21, 14 May 2004 (UTC) (P.S. I check this page later, so you don't have to reply in my talk page or notify me.)
Please first look at the version as it existed at the time [1]. With the current versions the concerns include:
- The agency grant threatens the freedom (as in speech) of the work. The Wikimedia Foundation may eventually receive a legal judgment against it which transfers its rights to a third party or a board 5 or 50 or 80 years from now may want to "encourage" large reusers to get licenses, perhaps to help it charitably distribute print versions. The agency agreement gives such an inheritor a weapon to use against reusers which wouldn't be available otherwise. We've seen some large formerly free projects go private in is sort of way and it's important to prevent it from being possible for this work. It's an unpleasant future I hope won't happen but contracts need to provide for unpleasant futures as well as pleasant ones. If you don't think it can happen, look at the SCO case to see how thin an argument needs to be for it to become very expensive for those defending their lawful rights to use something. This sort of situation is also why I grant other parties an agency to take legal action to enforce my rights against the Wikipedia.
- The revised version helps to reduce the scope for this. In the earlier versions it was possible for the Wikipedia to stop distributing things needed to comply with the GFDL, then take legal action against people for not complying because it wasn't providing the information needed to comply. Note that I'm confident that the current board and Jimmy Wales wouldn't even remotely consider this - it's the legal judgment, Jimmy Wales hit by a bus and such cases I'm considering.
- The way Wikipedia works is generally that those most interested in a subject take care of it. In this case, that means that those with the greatest interest in a restrictive interpretation of the GFDL are likely to be the ones doing the enforcing. That's contrary to our objective of producing a widely reusable encyclopedia, in part because the GFDL terms are very unpleasant for most casual reusers - schoolchildren, for example, or bloggers who might want to use part of an article.
- It assumes that the community can't be trusted to decide whether something is worth signing up to stop. That also encourages excessive enforcement and makes reuse less likely. An explicit opt in for a specific case would tend to reserve legal action only for situations which are significant enough to matter, letting casual reusers do what we intend: use the work quite freely. I did volunteer to be one complainant in a case which was significant, using the DMCA/OCILLA article as the basis for a DMCA/OCILLA takedown notice.:) That case was resolved prior to that becoming necessary.
- It's not only the licenses I grant here which matter. I've written things elsewhere with licenses unrelated to those on my user page and then contributed them here. It's not fair for those other reusers to place them at risk of getting a takedown notice without asking me first so I can confirm that they don't have a license from me. It's also not unlikely that at some point I, writing under a pseudonym elsewhere, would receive a takedown notice for things I've contributed here and might then have unpleasant choices relating to compromising my own anonymity elsewhere. Those non-Wikipedia licensees have the right for the existence and terms of their licenses to remain private if they wish, without the Wikipedia sending a takedown notice forcing their disclosure.
- One requirement for sending a DMCA/OCILLA takedown notice is that the sender must be acting on behalf of an exclusive rights holder. That has the effect of preventing the sort of one licensee acting against another licensee situation I've described above, assuming only that the exclusive rights holder won't make baseless infringement claims. That's problematic here, because the agency grant is automatic - we don't ask whether there are any other licensees, we assume that there aren't. That undermines the effect of the exclusive rightsholder requirement and will result in us acting like the RIAA and sending invalid infringement notices. I don't want to be in that sort of company and I don't want the Wikipedia sending out invalid takedown notices in my name. The changes since I opted out reduce this possibility but it's still significant. An opt in system eliminates this problem, because opting in can require a declaration that the works haven't been licensed in any other way.
- I'm entirely happy to opt in to support action against people who I know aren't my licensees and who are doing something substantive in the way of infringement. Taking action against sites with a 10,000 Alexa ranking or individuals using articles just serves to harm our reputation, IMO, and gets in the way of the possibility of us becoming THE free (bear and freedom) encyclopedia of the internet.
- So, if you license your works elsewhere, or if you want to ensure that the work stays free even if bad futures happen, I think it's still best to opt out. Jamesday 17:06, 23 May 2004 (UTC)
Thank you very much for your informative explanation, Jamesday. Would you mind if I rephrase and confirm some of your points (some implicit) I find significant?
- Your action is not out of suspicion to the current Foundation or Jimmy. But it is a preparation to some of the worst-case senarios.
- The right to act as an agent could be transferred by a court decision to another party.
- Because the Foundation receives such a right from massive amount of contributors through opt-out system, it is indeed a powerful "weapon". Virtually only the Foundation can obtain such a collection of rights.
- The current opt-out system make it possible for the Foundation to wrongly assume that contents are not licensed elsewhere. (Or I should perhaps say that by not opting-out, users let the Foundation make wrong assumption?)
- Aggressive enforcement efforts based on that assumption could result in unreasonable legal and financial burdens on the side of the reusers. That has the effect of discouraging reuse.
- You think that the current version of the submission standards has small but still significant chance of allowing that possiblity.
Tomos 01:36, 25 May 2004 (UTC)
Yes, that's a good summary. You might want to look at the past GFDL infringement actions to decide whether you are comfortable with the significance of the cases where action has been taken. I'm comfortable with some and uncomfortable with others. Jamesday 15:30, 25 May 2004 (UTC)
Question regarding license compatibility issues
[edit]I have responded to your question at User:Anthony_DiPierro/questions. anthony (see warning) 11:46, 23 May 2004 (UTC)
And again to your followup question. anthony (see warning) 10:29, 27 May 2004 (UTC)
The White Nationalist FAQ was, apart from a POV piece by a banned user, also a copyright violation. Danny 01:38, 26 May 2004 (UTC)
Star of the County Down
[edit]I listed it on VfD again. There is nothing in the article to indicate why it needs its own article. RickK 02:43, 26 May 2004 (UTC)
Queick deletion of blatant nonsense is totally appropriate. RickK
- I see that your talk page is protected because of that vandal so I'll at least temporarily reply here. The article in the version you deleted said at the end "This song shares its melody with the church hymn Led By the Spirit" and at the start contained the standard VfD notice. You gave in the deletion log the reason "03:26, 14 May 2004 RickK deleted "Star of County Down" (lyrics are copyrighted)". A quick Google search showed me its significance as an old Irish ballad. The notice told everyone that it was listed on VfD, the text gave some idea of its significance and you gave copyvio as the reason for the deletion. Again, please follow the copyvio, deletion and quick deletion policies. Jamesday 03:30, 26 May 2004 (UTC)
PD
[edit]Hi, could you comment here as I am not sure what you were saying yesterday, but I think it contradicts this: MediaWiki talk:PD-USGov. Thanks, Dori | Talk 00:34, Jun 2, 2004 (UTC)
Please Help Me
[edit]Thank you for your support. To make a long story short (or perhaps not so short), when I wrote the majority of my articles, I was an anonymous user. I believe that the site had some number to track my movements, and at any rate that number became attached to me. Because I was new to the site, I did not know that I wasn't allowed to put my name at the end of articles. In fact, I only began doing so after my mother (I am 19 years old) said that my articles were high quality and that I should take credit for them. Then Moriori sent me a message asking me if my articles were copyright infringements. I did not know how to use the user talk feature at the time, but I tried to reach him at his e-mail address. I am not very experienced with e-mail, and whether it was my ignorance of virtual communication, a malfunction of my computer or Internet service or a malfunction of his e-mail site I don't know, but at any rate I was unable to reach him. Later on my father suggested that I register using my own name so that it would be clearer that I was the author of the articles I'd taken credit for. This was when Moriori became convinced that I'd changed my user name (even though to my knowledge I never had one), and began spreading reckless reports that I was committing copyright infringement. It was around this time that I learn how to respond with user talk, and when Moriori repeatedly called me a "troll" (which I gather is a slang term for someone who commits copyright infringement) and with his propaganda won over some of the more powerful users of this site, he and I exchanged angry "user talks" in which he demanded that I remove my articles from the site and I threatened to sue him for libel for his false accusations. Although I repeatedly attempted to explain the situation to him, he simply continued to respond sarcastically and spread rumors about my "copyvio" as he calls it. A user who calls himself Raul654 also accused me of being a "PC Pusher", which, ignorant though I am of Internet slang, I would guess means someone who illegally posts copyrighted material. Moriori and his friends, being far more experienced in working on Wikipedia than I am, have gotten the upper hand in convincing nearly everyone on the site that I have violated copyrights. Although I sincerely want to take him to court, I realize that this may be impossible or extremely difficult since I believe he lives in New Zealand and I am sitting at a computer in Oregon in the United States. I have not copied any articles. In fact, I never so much as copied a full sentence from any of my research sources, but no matter how many times I tell Moriori this he simply continues to accuse me both directly and behind my back. I am convinced that he has become particularly determined to ruin me since the censorship controversy, but of course I cannot prove his motives. As for the articles that I censored, I was under the impression that I had every right to edit them, since another user had exercized a kind of political censorship by removing a line I wrote about Newt Allen, who is not in the National Baseball Hall of Fame, being kept out of the Hall "in spite of being far superior to a number of white inductees", a deletion that could be interpreted as racist. I care little about censoring indecent articles now, however, for I am at my wits ends about this dishonest persecution of me. I understand that you are something of an expert in law, and I am desperately in need of some kind of support or advice, since, as I said, Moriori and company are far more powerful on Wikipedia than I am. Thank you, and please help me. PS- Sorry, I just found out that PC in this case probably stands for "political correctness" and not "personal computer" as I had originally thought. At any rate this seems to indicate that the people trying to run me off this site have political motives. Thank you.User: Felix F. Bruyns
Note to Jamesday
[edit]I am sorry to say that I am leaving Wikipedia and will be unable to answer any response you may give me to my e-mail. I cannot convince the majority of users of my innocence, and Moriori and friends continue to persecute me incessantly. I am very grateful, however, for your attempt to help me, as you are one of the very few people on this site who has not bought into Moriori's lies. For your legal curiosity, I will tell you that he specifically stated to another user that I copied my article on Turkey Stearnes from the "African American Registry". If you go to that website you will see that their article on Stearnes is not even similar to mine, and it was not even one of the sources I used to do my research about him. This proves, of course, that Moriori isn't merely reckless and irresponsible-he is dishonest. Although I myself will be unable to respond to any messages, I would greatly appreciate it if you would spread the facts across the message boards on this site, since I registered under my own name and the majority of users on this site now believe that "Felix F. Bruyns" is a copyright violator. Thank you very much. User: Felix F. Bruyns
AFK
[edit]I'm on a trip and will be back in a few days. You may see my ghost computer on IRC without me. Jamesday 02:07, 13 Jun 2004 (UTC)
Back - or will be on Friday daytime. Jamesday 04:57, 18 Jun 2004 (UTC)
Source?
[edit]Jamesday..do you have a source for your addition to Bombe: Another [US Bombe] is believed to exist, but at an unknown location in storage.? Thanks! — Matt 09:07, 18 Jun 2004 (UTC)
- Re: my bombe photograph - Yes, it was one of the bombe replicas created for the Enigma movie, and it's on display at Bletchley Park, where Alan Turing worked during the Second World War. They've got some great cryptography related stuff there - including an Enigma machine, and a complete working replica of the Colossus computer. - MykReeve 10:58, 18 Jun 2004 (UTC)
I am very jealous! I'd like to make a visit some day, but it's quite some distance from the UK (still, Bletchley Park isn't that far...). I've tweaked the addition about a second bombe, attributing it directly, because I think we have to be careful about including rumours concerning secretive government agencies (though I could well believe a second bombe is about somewhere...). — Matt 00:23, 21 Jun 2004 (UTC)
- I've been planning a trip to Bletchley for a while, if you wanted to meet up for a visit to the museum when you get to the UK; I've tried without success to convince my fiance that it'd be a fascinating day out... ;-) — Matt 02:32, 21 Jun 2004 (UTC)
Images
[edit]Hi, I wasn't sure if fair use would cover all the images uploaded by User:Ta bu shi da yu. For example, I had questions about the publicity shot of Holly Valance (see Image:Holly Valance.jpg). I was hoping you could resolve these for me, and perhaps discuss with him (?) on his talk page if they're not covered. He seems quite reasonable, I'm just not sure. Thanks very much for your effort and your courtesy. Best wishes, [[User:Meelar|Meelar (talk)]] 06:30, 26 Jun 2004 (UTC)
Copyright infringements?
[edit]It's not clear to me where I have ever listed a possible copyright infringment on the images for deletion page. I listed one image which did not seem to be a copyright infringment at all, but for which wikipedia specific permission was given, which Jimbo has declared unacceptable. You know I know about possible copyright infringements. Don't act like you're telling me something I don't know. anthony (see warning)
I still don't think you understand what I'm saying. It wasn't a copyright infringement. That's why I didn't list it on Copyright Problems. Copyright Problems is for copyright infringments. If you want to broaden its scope to images which are not copyright infringements but are merely non-free, feel free to propose such an expansion. anthony (see warning) 12:39, 7 Jul 2004 (UTC)
Adding attributes to pages demo
[edit]Hi, over on the Creative Commons "Get Content" planning wiki you suggested that you could demo how text substitution and category capabilities in MediaWiki 1.3 could work for CC's plans, and suggested asking here. Please do demonstrate. Thanks!
Houston Press
[edit]Glad to help! - I'm a bit intrigued to read that it is a 'solid neswpaper', presumably the converse in a Liquid Paper :-) MPF 19:37, 6 Jul 2004 (UTC)
Database Error
[edit]Hello, I just got another error while trying to check my Watchlist:
SELECT cur_namespace,cur_title,cur_comment, cur_id, cur_user,cur_user_text,cur_timestamp,cur_minor_edit,cur_is_new FROM watchlist,cur USE INDEX (name_title_timestamp) WHERE wl_user=44062 AND (wl_namespace=cur_namespace OR wl_namespace+1=cur_namespace) AND wl_title=cur_title AND cur_timestamp > '20040714103323' ORDER BY cur_timestamp DESC from within function "wfSpecialWatchlist". MySQL returned error "1104: The SELECT would examine more rows than MAX_JOIN_SIZE. Check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is ok".
older≠wiser 22:38, 14 Jul 2004 (UTC)
Hi, I just got an error checking my watchlist (days=0.5), which was working ok half a day ago:
SELECT cur_namespace,cur_title,cur_comment, cur_id, cur_user, cur_user_text,cur_timestamp,cur_minor_edit,cur_is_new FROM watchlist,cur USE INDEX (name_title_timestamp) WHERE wl_user=XXXXX AND (wl_namespace=cur_namespace OR wl_namespace+1=cur_namespace) AND wl_title=cur_title AND cur_timestamp > '20040714132602' ORDER BY cur_timestamp DESC
from within function "wfSpecialWatchlist". MySQL returned error "1104: The SELECT would examine more rows than MAX_JOIN_SIZE. Check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is ok".
(wl_user obscured by me)
Curiously, the page also showed that I had new messages, but there were none in the last week. Trying a second time did not show this, but still had the database error. --Zigger 02:06, 2004 Jul 15 (UTC)
- Thanks, it is working OK now. older≠wiser 11:53, 15 Jul 2004 (UTC)
- The error has gone again on my list too, thanks. --Zigger 16:18, 2004 Jul 15 (UTC)
Thanks re: Image list
[edit]Thanks for running the SQL query for my image uploads -- I really appreciate it! Catherine | talk 18:53, 15 Jul 2004 (UTC)
Request
[edit]James - please peruse Wikipedia:Copyright FAQ and fix anything you think needs fixing. In the fair use section, "The nature of the copyrighted work;" need an explination and I can't remember what that one means (I asked before and you told me, but I have since forgotten). I think the fair use section still needs a lot of work, but every other section is done, methinks. →Raul654 09:40, Jul 20, 2004 (UTC)
Substub support
[edit]Thanks a lot for your contribution to Wikipedia:substub. If you support the idea of having substubs (it's pretty controversial right now) then can you please list your name on Wikipedia talk:substub#Substub support? It'd be really great to have more support. Thanks! [[User:Mike Storm|Mike Storm (Talk)]] 22:31, 22 Jul 2004 (UTC)
- Thanks! [[User:Mike Storm|Mike Storm (Talk)]] 12:46, 23 Jul 2004 (UTC)
hi
[edit]Thanks for givin' me the news on ish. I'm going to beef it up some. If people still think it's inadequate after that, kill it. Kzzl
question
[edit]I found an article that's a little biased. It's good, long, comprehensive but some parts of it are not objective. Is a certain kind of tag appropriate here if I'm not confident making the needed changes myself?? {Clean up} doesn't seem quite right. Maybe I will try to do it myself. Kzzl
Vandalism
[edit]Do you mean a dynamic IP? And obviously the problem hax0r was working from a different location. Peace Profound! --Merovingian✍Talk 03:43, Jul 31, 2004 (UTC)
Developer poll
[edit]Hi. I'd like to have your opinion on m:Developer payment poll thanks :-) SweetLittleFluffyThing
Summaries
[edit]Here is a start: m:Wikisummaries. I think I will begin in my user space on en. +sj+ 23:56, 3 Aug 2004 (UTC)
James, can you speak to this guy please, he's going off on one, and since you supported his substub plan, he's more likely to converse with you. He has a lot of bark but no bite :) Dunc_Harris|☺ 23:02, 5 Aug 2004 (UTC)
Nothin' ain't simple 'bout copyright
[edit]On the mailing list, Ray Saintonge <saintonge@telus.net> mentioned http://onlinebooks.library.upenn.edu/okbooks.html#whatpd. That the site I had in mind when I was talking to you at the Boston meeting.
http://onlinebooks.library.upenn.edu/c-fineprint.html
It says thatpossibly a work published within the juridiction of the Ninth Circuit Court might still be under copyright if
- a) The work was first published on or after July 1, 1909, and
- b) The work was never published prior to 1923 with a copyright notice recognized by the US, and
- c) The work was never published prior to 1923 in the United States, but
- d) This might only apply to works that were not published in the English language.
Ain't that sumpin'? [[User:Dpbsmith|Dpbsmith (talk)]] 14:55, 7 Aug 2004 (UTC)
- Thanks for the followup - it's appreciated. Always more wrinkles in the weird and wonderful world of IP law.:) Jamesday 04:43, 8 Aug 2004 (UTC)
If you have a minute, could you please weigh in at Wikipedia:Votes for deletion/Image:TrangBang.jpg? マイケル ₪ wants to remove the image ASAP, I have no opinion, and you talked about the fair use aspects on Image_talk:TrangBang.jpg. Thanks! -- ke4roh 21:43, Aug 7, 2004 (UTC)
Thanks for calming this latest bout of copyright paranoia. 172 04:40, 8 Aug 2004 (UTC)
- Last time I was on wikipedia, which was several months ago if you look at my edit history (Sep 17, 2003), we ruled on the side of caution with regard to copyrighted content. Clearly things have changed. I can't say I feel right about putting copyrighted material on wikipedia, we shouldn't be dependent on non-free material. However, clearly I'm out numbered in my belief that it's not worth more freedom, or less legal risk, so I'll let it be. — マイケル ₪ 20:50, Aug 8, 2004 (UTC)
Another substub vote
[edit]I just wanted to let people know that there's another vote on substubs going on in Template talk:Substub#Survey. I know that this is a second vote, however, apparently it was originally intended to be only a vote about whether to keep the template message, but somehow evolved into a vote on the existence of substubs themselves. I know that you already voted in favor of substubs, so I wanted to get your support on this poll too. Thanks for your support! [[User:Mike Storm|Mike∞Storm]] 23:32, 9 Aug 2004 (UTC)
Hi. Do you when the VFD and copyright headings can be removed from the Trang Bang image. I'm not sure about the policy issues. Thanks. 172 04:58, 10 Aug 2004 (UTC)
Please see the recent changes to Template:Fairuse. You're better versed than I am on this, so I want to defer this matter to you. Thanks. 172 09:16, 12 Aug 2004 (UTC)
Copyright question re Beasts of England from Animal Farm
[edit]There's a discussion in progress at Wikipedia:Votes_for_deletion/Beasts_of_England regarding an article which consists—correction, formerly consisted—mostly of the complete seven stanzas of Beasts of England, from Animal Farm. I believe there is at least a question about the copyright status. And I believe that whomever inserted the line in the article saying:
- Note: Lyrics are public domain, under 50-year death expiration. see copyrights
is oversimplifying. I'd appreciate it if you could make some knowledgeable commentary about this in the VfD discussion, near the bottom (where I've put a longish comment). My guess is that maybe it's OK, but not because it's in the public domain. I don't believe it is in the public domain in the U.S. My reason for believing this is that the UPenn Online Books Page says it isn't. I don't say we can't use it. I say if we can we need a clear rationale, and "50-year death expiration" ain't it. [[User:Dpbsmith|Dpbsmith (talk)]] 20:19, 22 Aug 2004 (UTC)
Could you please provide an image copyright tag for this image? Thanks!--Diberri | Talk 22:51, Aug 26, 2004 (UTC)
Hi Jamesday,
you have made edits to the license template for works by the US government that are released into the public domain. As it seems now, this is not the case worldwide - I posted a comment about it on the talk page. Could you have a look at it, please? Maybe the template text should be updated.
Best regards, --zeno 11:35, 10 Sep 2004 (UTC)
Review?
[edit]Hey, as the original author, when you get a chance, could you take a look at the recent edits to Gulf of Sidra incident (1981). I'm just not sure about the overall picture... Thanks. jengod 20:51, Sep 14, 2004 (UTC)
Thank you for your contribution to one, or more, articles that are now organized under Data management.
Because of your previous intrest, you are recieving an invitation to become a founding member of the Data Management Wiki Committee.
The members, of course, will form and solidify the purpose, rules, officers, etc. but my idea (to kick things off) is to establish a group of us who will take responsiblity to see that the ideas of Data management are promoted and well represented in Wikipedia articles.
If you are willing to join the committee, please go to Category_talk:Data_management and indicate your acceptance of this invitation by placing your three tilde characters in the list.
KeyStroke 01:16, 2004 Sep 25 (UTC)
Thanks for the guidance
[edit]Thanks for the guidance about avoiding mass changes in favor of gradual changes so the community can gradually decide whether it's a good thing. I hadn't considered that approach, which makes good sense. • Benc • 06:36, 25 Sep 2004 (UTC)
Query
[edit]? CryptoDerk 06:46, Oct 11, 2004 (UTC)
make sure external links are valid
[edit]At meatball, you removed two working links to wikibooks, and replaced it with a link to an empty page. Please make sure external links you create, especially to our sister projects, are in fact valid links. Thank you. Gentgeen 20:32, 22 Oct 2004 (UTC)
- You're right, I created the page at the Cookbook but got the link to it wrong. Thanks for fixing it! Jamesday 11:08, 23 Oct 2004 (UTC)
Good to see you
[edit]I've been reading some of your well thought out comments on the VfU page. Its good to know there are folks such as your self in our company. [[User:Radman1|(talk)]] 00:03, 29 Oct 2004 (UTC)
Any idea where I can find the deletion debate on Moanalua High School?
[edit]The notice was added
16:44, 17 May 2004 UninvitedCompany (vfd)
but I can't find the archived deletion debate. [[User:Dpbsmith|Dpbsmith (talk)]] 18:04, 29 Oct 2004 (UTC)
Redrawing illustrations?
[edit]By the way, what do you know about redrawing copyrighted illustrations? It suddenly occurs to me that all those line drawings I used to see in biology books with captions like "after so-and-so," which were basically just hand-drawn copies of other illustrations, may have been a technique to avoid copyright issues? Any guidelines, hints, wisdom, pointers to old discussions? [[User:Dpbsmith|Dpbsmith (talk)]] 18:04, 29 Oct 2004 (UTC)
User: Train Spotter
[edit]Thanks for the note, but it makes no difference whether I control the account because similar ones are so easy to set up. Similar usernames aren't a problem. Redirects between user pages may be, but they're easy to find with "what links here". Anyway, I don't think it was a very serious attempt at impersonation. If someone really wanted to impersonate another user, the last thing they'd do is choose a user who edited the same article recently, and is therefore likely to be watching it.
By the way, my POV is anti-Bush. I'm amazed nobody's yet found the comments which I slipped into Data corruption ;-) ;-)
,,,Trainspotter,,, 11:39, 3 Nov 2004 (UTC)
Elblag, Poznan, ...
[edit]Haie Jamesday,
I wonder why you removed the " the incorrect technical limitations header" ... as the cities are not Elblag but Elbląg, not Poznan but Poznań .... i tried once to move one of these cities ... it didnt work as the lemma was looking quite strange? .. I'm not to much in the technical details and agreements of en so it would be nice to tell me! ...Sicherlich 22:17, 10 Nov 2004 (UTC)
{{Wrongtitle | title=article}}
[edit]I saw you removed several {{Wrongtitle}} tags on several pages named incorretly. What is the reason for that?[[User:Halibutt|Halibutt]] 01:45, Nov 11, 2004 (UTC)
I'm wondering about that too. For instance, on Akcja Wyborcza Solidarnosc the point of the {{wrongtitle}} tag was that the correct spelling of the last word is Solidarność, but it's not possible to include the characters ś and ć in the article title. I'm reverting your edit until I see an explanation. ←Hob 04:07, 2004 Nov 11 (UTC)
- BTW, I realize that you're a Wikimedia techie so you probably do know something I don't... but I haven't seen any indication that the non-ISO-Latin-characters issue has gone away yet, so please enlighten us... ←Hob 01:14, 2004 Nov 12 (UTC)
- See Wikipedia:Naming conventions (use English). Per the naming convention, the correct version of the article page name is without the accents, transliterated if required, or using whatever form is most commonly used in English (probably the English words of the same meaning in this case, though I didn't check). Jamesday 07:43, 17 Nov 2004 (UTC)
- Which creates only double standards - the nations that use ISO-Latin script are allowed to use their diacritics in wikipedia, while others should stick to incorrect names and stay quiet. Also, the convention you cited says explicitly that we should name our pages in English and place the native transliteration on the first line of the article unless the native form is more commonly used in English than the anglicized form. - which is exactly what this tag does. The {{Wrongtitle}} tag is but a workaround since the English wiki is AFAIK the only wiki out there not to upgrade to the Unicode, but it works pretty well as a temporary solution and could help in finding all the articles that will have to eventually be moved to where they belong - as soon as someone finally gets the Unicode job done instead of declaring that the thing is under control. [[User:Halibutt|Halibutt]] 02:06, Dec 20, 2004 (UTC)
- Finally, there's also a Wikipedia:Naming conventions (technical restrictions) page, which sets the matter straight. [[User:Halibutt|Halibutt]] 02:09, Dec 20, 2004 (UTC)
Undeletion
[edit]Hi, I was hoping you could take a look at John Ogonowski, Thomas F. McGuinness, Jr., and Jean Destrehan Roger. These three articles received a majority of votes for undeletion at VFU, but have not yet been undeleted. And now Texture is removing the listings from VFU saying that they are expired and no admin chose to honor the undeletion. anthony 警告 22:35, 12 Nov 2004 (UTC)
Creative Commons
[edit]I added some categories to your user page to reflect the your releasing of changes for the Creative Commons licenses so we can track them. If you'd like to, you can use the {{DualLicenseWithCC-BySA-Dual}} template instead. -- Ram-Man 02:58, Nov 17, 2004 (UTC)
Kate's Tools
[edit]Thanks! Proteus (Talk) 13:36, 22 Nov 2004 (UTC)
Protection of personal CSS and JS
[edit]Thanks for the info! I'll remove the protection right away. David Cannon 21:33, 5 Dec 2004 (UTC)
Protection of personal CSS and JS
[edit]Thanks for the info! I'll remove the protection right away. David Cannon 21:36, 5 Dec 2004 (UTC)
RFC pages on VfD
[edit]Should RFC pages be placed on VfD to be deleted? I'm considering removing Wikipedia:Requests for comment/Slrubenstein, Wikipedia:Requests for comment/Jwrosenzweig and Wikipedia:Requests for comment/John Kenney from WP:VFD. Each of them was listed by CheeseDreams. Your comments on whether I should do this would be appreciated. - Ta bu shi da yu 03:46, 10 Dec 2004 (UTC)
Speedy Bot Policy
[edit]Please have a look over my responses to the bots policy change and the proposals I've made, then get in touch so we can arrange a chat in IRC and/or phone, so I can answer all of your questions about those respnses and find some way to get done what you want to get done ( a proposal I probably like in content, if not necesarily in details of method). Thanks. Jamesday 05:23, 13 Dec 2004 (UTC)
- I'm sorry, but I can't agree with major policy discussion taking place on IRC, phone, or email. It only contributes to the few deciding the issues when it should be kept as open as possible. Besides, we need a record of what the discussion was, so keep it on Wikipedia. – Ram-Man (comment) (talk)[[]] 14:34, Dec 13, 2004 (UTC)
I didn't realise you guys existed, so I created Wikipedia:WikiProject computers. Sorry! As you kicked off the project, I was wondering what you thought of a merger? I have a little more structure, and it kind of looks like Wikipedia:WikiProject Computing has been abandoned (or fallen into disuse). I have some ideas and a vision of what I'd like to see happen with computing related articles... could I add vast amounts of my proposed structure into your project, or do you think that would just annoy everyone? - Ta bu shi da yu 14:25, 17 Dec 2004 (UTC)
Image tag
[edit]Hi! Thanks for uploading the following image:
I notice it currently doesn't have an image copyright tag. Could you add one to let us know its copyright status?
You can use {{gfdl}} if you wish to release your own work under the GNU Free Documentation License, {{PD-self}} if you wish to release your own work to the public domain, {{fairuse}} if you claim fair use of someone else's work, and so on. Click here for a list of the various tags.
If you don't know what any of this means, just let me know at my talk page where you got the image from, and I'll tag it for you. (And if you know exactly what this means and are really tired of the constant reminders, please excuse me. They will stop once the tagging project is complete.) Thanks so much. Denni☯ 03:47, 2004 Dec 16 (UTC)
P.S. You can help tag other images at Wikipedia:Untagged_Images. Thanks again.
Page-move vandalism
[edit]James: Due to confusion over the page-move vandalism of George W. Bush and U.S. presidential election, 2004, the pages' histories have been quadruplicated and duplicated, respectively. The problem, caused by User:Julie1984, was announced on IRC, and the result was that a lot of people tried to move the page back at the same time as other people were deleting the redirects. The result was that the actual pages were deleted, after which several people tried to undelete them at once. There were no developers on #mediawiki when the problem was occurring, so could you look into fixing the pages' histories? Thanks a bunch. Rdsmith4— Dan | Talk 03:08, 19 Dec 2004 (UTC)
- Never mind, it appears Tim Starling is taking care of the problem. Rdsmith4— Dan | Talk 04:59, 19 Dec 2004 (UTC)
Thanks for the comments on my personal copyright tag. I'm not that much of a copyright geek and I must say I don't have much knowledge on the topic. Could you help me with the exact wording of the template? I want it to stay compliant to GFDL, mostly due to ideological reasons (I like wikipedia :) ), but I have no idea how to make your proposals into text shown in the copyright tag... [[User:Halibutt|Halibutt]] 23:30, Dec 19, 2004 (UTC)
gl.wiktionary
[edit]Hi Jamesday,
as mentioned in IRC, i ask you about reseting my passwort at gl.wiktionary.org. I don't renember my IP, when i registered my nick. I normaly use the same password and the same e-Mailadresse when i register a nick (commons, wikiquote, wikipedia and so..)
Thanks for your help!
-- da didi 19:37, 20 Dec 2004 (UTC)
- Sorry, but i could get sent my password by mail. You don't have to do anymore! -- da didi 19:54, 20 Dec 2004 (UTC)
Just to let you know, it's leaking a href tags. - Ta bu shi da yu 03:32, 23 Dec 2004 (UTC)
Tucson, Arizona and more
[edit]Hi. I saw that you voted on the RFC regarding Tucson, Arizona, and I thought you might be interested in commenting on a broader application of the formatting to other city articles. The discussion (for now) is at Talk: Tucson, Arizona#Other Arizona and nearby cities. (It might get moved to WikiProject Cities, if there's interest in doing so.) Thanks! kmccoy (talk) 02:39, 27 Dec 2004 (UTC)
More Abdel Qadir socks?
[edit]User:JAYJG just emailed me saying you'd said Alberuni was another of the hydra. Alberuni, of course, has an arbitration case against him at the moment. Just wanted to confirm this one with you first - David Gerard 09:28, 29 Dec 2004 (UTC)
Loading data file for LinkBot
[edit]Hi Jamesday, You mentioned previously on the Wikipedia talk:Bots page that bots which want to load large amounts of data may be able to supply you with some kind of data file, which can then be loaded into the Wikipedia at a suitably non-peak time. Would I be able to take you up on that, for LinkBot? An example of the things that it is loading can be seen in the user contributions for this bot. I've tried to take things very slowly with this bot, and provide outlets for user feedback, and incorporate that feedback where it is feasible to do so. I think the LinkBot is now at the stage where the size of the data being uploaded can be increased (previously this was done in blocks on 100 pages). What do you think? Is this something that can be done by me supplying a data file to be loaded? If so how do we start? How many pages would you want to start with? e.g. 500 or 1000 pages? What format would the data need to be in? Also, if the data contains things like ~~~~, will those be converted into standard signatures if the data is loaded manually (which is what I'm hoping for)? Also the bot makes two types of edits (one where it adds a brief note to the talk page pointing to the suggestions, and one where it adds a new page with the actual suggestions on it) - is it possible to do both of these using a data file? Basically I'm more than happy to work with you to make this happen in an acceptable way, I'm just not sure how to get the ball rolling, or the exact mechanics of what I need to do, so any guidance would be most appreciated. -- All the best, Nickj (t) 02:05, 11 Jan 2005 (UTC)
Image:Sykes-Picot bilevel work in progress.png
[edit]Hi. You uploaded Image:Sykes-Picot bilevel work in progress.png in Oct 2003 stating it was a work in progress and not to be used. Perhaps you could update the status or delete it? Thanks. RedWolf 05:45, Jan 13, 2005 (UTC)
Old user page versions
[edit]Thankx for deleting the old versions of my user page! Dbach 13:38, 17 Jan 2005 (UTC)
Thanks
[edit]James, thank you so much for explaining about the problems and fixes on the Open Facts page. It helps to hear that you're working so hard to fix things, and I will also be starting to make regular financial donations. Thanks for all the work you're putting in to keep the project going. Best, SlimVirgin 11:15, Jan 19, 2005 (UTC)
Fair use question
[edit]Heya, you appear to be one of the knowledgeable people on fair use around, if you have the time could you have a look at Image:Mesa-thumb-lg-3.jpg (which I suspect comes from here) and give your opinion on whether its use in Mesa, Arizona is fair use? I suspect it may not be. --fvw* 09:01, 2005 Jan 21 (UTC)
- Even better, nice job, thanks! Just out of curiosity and for calibrating my fairuseometer, do you think it was defendable as being fair use? --fvw* 23:12, 2005 Jan 21 (UTC)
Hey Jamesday, that was exceptionally good work. I actually got it from Google images, and wasn't too sure of the source. Thanks. Ollieplatt 00:07, 22 Jan 2005 (UTC)
I have replied to your attacks on me at Wikipedia:Administrators' noticeboard. I would appreciate a response. And an explanation. RickK 00:10, Jan 22, 2005 (UTC)
- The comments you suggest are personal attacks are here. Replies to your responses in subsequent edits. Jamesday 00:50, 22 Jan 2005 (UTC)
Umlaut glitches
[edit]James, I've only just noticed this editing glitch. Whenever I preview or save an article that contains umlauts (two dots above letters) or acutes (forward slash above e), odd characters appear. This is even when I haven't edited the words in question. For example, at Helga Zepp-LaRouche the words Bürgerrechtsbewegung Solidarität party (BüSo) became BŸrgerrechtsbewegung SolidaritŠt party. (If it happens on this page too, then both sets will look the same; if you get the umlaut, then for some reason, it's working on this page). I use a Mac, OS 10.2.8, with Safari 1.0.3. Best, SlimVirgin 23:08, Jan 24, 2005 (UTC)
SQL Queries
[edit]I draw your attention, in your role as a developer, to Wikipedia:Village pump (technical)#SQL Queries. - Mark 09:46, 29 Jan 2005 (UTC)
- Thank you for your reply. There are issues there I would never have even considered, and I guess it's a good thing the developers are taking these steps to maintain privacy and security. Thanks also for the heads-up about my user page being screwed up. I knew when I made it that it would most likely be broken in one way or another; I was intending to make a more standard one in the next couple of weeks now that I have some time off. - Mark 02:08, 31 Jan 2005 (UTC)
database compression
[edit]I know you were involved with compressing many old histories, to preserve space in the database. Of course, that has a side effect of preventing some moves and deletions.
Would you consider uncompressing the histories of pages within the Template:, MediaWiki:, and Category: namespaces (and the related talk:'s)? This would greatly help us in performing many regular maintenance tasks, such as Wikipedia:Templates for deletion, which currently has a backlog of deletions due to the compression "bug". Because of their nature, pages in these spaces usually have fewer byte counts and revisions, so keeping them uncompressed wouldn't (correct me if I'm wrong) cause much of an impact overall. Please let me know on my talk page if this is possible. -- Netoholic @ 15:48, 2005 Jan 31 (UTC)
Thanks for the reply. If the histories can't be uncompressed, then what is the process for us to get these pages deleted? -- Netoholic @ 15:18, 2005 Feb 2 (UTC)
In addition to the Template, Category, and MediaWiki namespaces, can you also leave out Image (and respective talks) in future compression runs? Thanks. -- Netoholic @ 15:54, 2005 Feb 15 (UTC)
Checking for private bots
[edit]Hi, I thought you might know or know who to ask. Has anyone checked the logs for page scanning from problematic IP's? E.g. checked Gzornenplatz 's IP to see if he is using a private bot to scan pages that he wishes tightly monitor (edit war on).--Daeron 20:27, 31 Jan 2005 (UTC)
- Yes, it's called "Watchlist". Gzornenplatz 21:03, Jan 31, 2005 (UTC)
- Yes, it just occurred to me that while a page scanner is quick & easy, that updating the current list of desired targets would be much easier done via the "Watchlist" - and therefore if Gzornenplatz is Wik he could keep polling Wikipedia for any change in his "Watchlist".--Daeron 04:42, 1 Feb 2005 (UTC)
monobook.js
[edit]Hi James, since sometime this morning Wikipedia send me XHTML source that does no longer contain a reference to my private User:Lupo/monobook.js. A page load done at 08:39 (UTC) did include it, but later loads do not include it anymore. Pages served more recently are missing the "<script type="text/javascript" src="/w/index.php?title=User:Lupo/monobook.js&action=raw&ctype=text/javascript&dontcountme=s"></script>" at the end of the <head> </head>. Could that be fixed again, please? Lupo 13:51, 3 Feb 2005 (UTC)
- Since I haven't found an existing bug report for this, I filed a new one at bugzilla, like you said. Lupo 20:04, 3 Feb 2005 (UTC)
- And apparently fixed by Brion a few minutes later! Amazing! Lupo 20:14, 3 Feb 2005 (UTC)
meta-templates
[edit]We spoke briefly on IRC, about the impact of "meta-templates" (templates used to create other templates, like the Wikipedia:Stub categories ones). I realize the server impact for each one individually may not be large, but as a concept, I'm of the opinion they should be avoided where possible. I'm trying to make this case one one page, but need some input from someone like you, as the "database guy" :) Could you read over my comments at Template talk:Sisterproject#No meta-template, please. and give your input? -- Netoholic @
Thank you for providing such a nicely written description of the technical problems. I found it even more compelling than I had first assumed. As such, I've take some of our comments and drafted Wikipedia:Meta-templates considered harmful. I'd welcome your further input if there is anything I've missed. -- Netoholic @ 19:07, 2005 Feb 4 (UTC)
- I also want to thank you for patiently explaining in detail the consequences of using meta-templates. To be honest, I thought taht Netoholic's description was so overwrought in regards to the one area that I am familiar with (topic stubs) that I found it hard to trust anything he was saying. I do have two additional questions for you. 1) Are there any problems with using a meta-template as just a common format page and then creating all of the "daughter" templates using the "subst:" feature? 2) Is it time to revisit Wikipedia:Protection policy and protected pages are considered harmful and, as a matter of policy, protect any templates that are used on a large number of pages? BlankVerse ∅ 21:38, 19 Feb 2005 (UTC)
Security and stuff
[edit]You wrote on Wikipedia:Text editor support:
- See the release notes for more details of what you need to do to modify a bot or tool to deal with this.
So I wonder, where is the link to the details? Thanks. Oleg Alexandrov | talk 01:29, 5 Feb 2005 (UTC)
Usernames to be changed
[edit]Can you change contributor's username, since you are developer? If not, could you name someone who can? Because I have been waiting that someone would change my username for over half a year! And since last summer no developer has touched the requests on meta:Changing username. -Hapsiainen 02:39, Feb 5, 2005 (UTC)
- I have not posted this message to every developer's userpage. This message is currently only in your talk page to prevent people from doing overlapping work. I believe you read the messages in your talk page, so why don't you respond? -Hapsiainen 16:00, Feb 16, 2005 (UTC)
No Follow
[edit]Left some comments on your page at Meta, just so you know --BozMo|talk 09:29, 6 Feb 2005 (UTC)
Sisterproject metatemplate
[edit]Greetings. I left a question for you at Template talk:Sisterproject#Technical impact of templates like this. In brief, the question boils down to "Wouldn't this problem go away if the metatemplate were protected?" I look forward to your further input. Thanks, – Quadell (talk) (sleuth) 14:42, Feb 8, 2005 (UTC)
- Echo that. Isn't the problem only a problem when a template used in many places is altered? Each change of use is minimally expensive in itself. So using meta-templates is not in itself a bad thing, provided that the meta-template itself and the child-templates, once in place, are not fiddled with endlessly. --Phil | Talk 18:11, Feb 8, 2005 (UTC)
New user list
[edit]Is there a special page for a list of new users? Like, something in RC format where it shows the time and date that a new account was created? -- AllyUnion (talk) 04:07, 13 Feb 2005 (UTC)
- Not currently a list of new accounts. Producing one for all wikis as a batch job is currently on my to do list (batch job because it's much more efficient). Account age is also being considered as a possible ranking or highlighting factor in recent changes and watchlists. No ETA for any of this though. Jamesday 08:19, 13 Feb 2005 (UTC)
Weird editing glitch
[edit]James, can you help with this? Anon IP 67.173.227.156 made an anti-Semitic edit at 04:33, Feb 15, at Anti-Semitism (begins "I realize some racist bastard is gonna delete this right away"). Here's the edit history [2]
I deleted it at 04:42, Feb 15, but due to some editing glitch, the deleted post now shows up as having been added by User:Sfdan, who made an edit just before the anon IP [3] and by me, who made an edit (to delete) just after the anon IP [4] and [5] Is there any way of correcting this? One editor has already written to me wondering why I wrote it. Best, SlimVirgin 05:11, Feb 15, 2005 (UTC)
Special request for admin tool
[edit]James, Willy on Wheels is starting to become very annoying. When are we going to see a special sysop swap function be implemented? Deleting pages twice is getting very annoying. -- AllyUnion (talk) 12:56, 16 Feb 2005 (UTC)
Contribution count
[edit]You have written, "You have made 22732 undeleted edits. If it's you who is repeatedly abusing the databases servers by asking for a list of 25,000 edits by you in one chunk, please stop. We have that 500 at a time limit and paging in steps of 500 for a reason." If I might beg to inquire, have you any reason to believe that I, in particular, have asked for a list of all my edits (for as far as I am aware, I have not), or have you merely posted this message on the talk pages of all individuals with more than 20,000 edits? -- Emsworth 21:07, 17 Feb 2005 (UTC)
Vote on Talk:Gdansk/Vote
[edit]Hi. Since you have edited on pages with disputes about the names of Polish/German locations, I would invite you to vote on Talk:Gdansk/Vote to settle the multi-year dozens-of-pages dispute about the naming of Gdansk/Danzig and other locations. The vote has two parts, one with questions when to use Gdansk/Danzig, and a second part affecting articles related to locations with Polish/German history in general. An enforcement is also voted on. The vote has a total of 10 questions to vote on, and ends in two weeks on Friday, March 4 0:00. Thank you -- Chris 73 Talk 00:51, Feb 18, 2005 (UTC)
Sockpuppet check
[edit]With Tim and Brion on break, I'm not sure who to talk to about getting a sockpuppet check. You're a developer who's pretty active on the community side... can you run one, or tell me who can? A certain user I'd hoped would eventually go away is still here, and I strongly suspect he's using an sockpuppets again. Isomorphic 22:06, 21 Feb 2005 (UTC)
- See User:Isomorphic/Minions of the Church for a list that I and others have compiled of all the accounts we think are him. Most of those are old, so the IP logs wouldn't go back that far, but I'd like a check for password matches within that group. He's pretty sly, but I'm hoping he missed that trick. [[User:Mike Church|], 256, and EventHorizon were each his principle account at some point, so you might want to start there for password matches. It might also net some accounts I didn't know about.
- Accounts that have been used in the past few months are EventHorizon, Crocogator, 160, and Ludocrat. Those I'd like IP checks for, if you can. I'm especially interested in the events surrounding Wikipedia:Requests for adminship/EventHorizon, where I believe he used a sockpuppet to nominate himself for adminship, and Ambition (cards), whose existence is the fundamental purpose of all this nonsense.
- Thanks a lot, and sorry to dump all this on you. Mike has been doing this for well over a year now. It's becoming obvious that he won't stop until he's forced to, and getting some solid proof of his dishonesty would be a first step. Isomorphic 16:19, 5 Mar 2005 (UTC)
- If you're going to do this, I'd be interested in knowing if 137.22.3.153 is EventHorizon's IP. If so, they're most definately Church. ✏ OvenFresh² 01:58, 6 Mar 2005 (UTC)
- For legal reasons, definitely match (and not check) the passwords. I run a small message board that's had problems with sock puppets and trolling and they pretty much always use the same password. There's been a study that most Internet users can only remember 4 passwords, and almost always use a "main" one. It cuts down the ambiguity. Checking the IPs would be "security breach" under the law; your target probably wouldn't know you did it, but if you ever announced it, you'd struggle to back down from that one. Even checking the passwords, if not granted permission by the user, is illegal. There was a facebook clone that got busted in May 2004 for that. Matching the passwords, if there's a program available to do that, would be legit. (That is, it keeps the PWs internal, but returns a response if PW1 = PW2.) Anything more will get you in really hot water. Swatara 05:18, 6 Mar 2005 (UTC)
- Note that Swatara has two edits to Wikipedia, the first of which created his user page. I leave you to draw your own conclusions. Isomorphic 21:22, 7 Mar 2005 (UTC)
- Since joining these discussions seems a popular pastime, let me give it a try: Iso, are you sure you aren't being extremely paranoid? Anyone can jump in these things by watching RC (like yours truly) and anyone can edit under an IP for any amount of time before registering an account (like yours truly). Swatara's account is new and he "suspiciously" stumbles into this discussion, ergo he's Mike Church? (Oh, sorry, I mean "we can draw our own conclusions"?) Can't we at least evaluate his claims at face value instead of pre-emptively accusing him? I know you don't want to hear this, but I'm going to say it anyway: assume good faith. 82.92.119.11 21:44, 7 Mar 2005 (UTC)
- Re the legal issues (as you asked on my Talk page). I'm afraid I don't know specific details. Anyway, what I do know is that there was a thefacebook clone last spring that tried to harvest passwords from various colleges not yet on the real facebook. They got busted pretty hard. As for IPs, it's more shady, but there's an implicit trust when people create user names that their IPs will be hidden. The username is supposed to have two functions (1) cover IP information, which might compromise security or spin the information (particularly if the source is a governmental or corporate authority) and (2) to collect a person's contributions (which might be under multiple IPs) under a single identity. To blow cover on IPs would compromise that first purpose. I don't know how strongly that "implicit trust" would hold up in court, but it's definitely not something you want to find out... and precedent would not be on your side. A hypothetical scenario is that a developer (or other person with IP-spy privileges) finds out that the CEO of his company is writing to articles about an industry, then reports (in some other context, such as a blog) "CEO -X- thinks that". This spawns speculation and potentially trade secrets are blown. The likelihood of this is tiny, but protection against litigation is all about avoiding those low-probability pitfalls.
- I think the "sock puppet" issue on Wikipedia is not as severe as people make it. There are legitimate reasons for people to conceal their identities (most users don't reveal their offline identities, and aren't considered "sock puppets" for using a pseudonym.) To enumerate the illegitamite reasons for having sock puppets:
- 3RR violations. This issue is a result of bad policy, as much as problem users. A semivandal (not an explicit vandal, but overt POV soapboxer or other problem user) with multiple socks can paralyze legit users, and 3RR has no mechanism to encourage editing toward consensus. (Instead of encouraging positive behaviors, it merely punishes negative ones, delaying the problem for the time of the block but leaving the bitterness extant.) A better 3RR system would be that, whenever 3+ reverts per side (not person since it's impossible to tell) of an argument occur per article, the article is forked (e.g. Zionism => Zionism (1) and Zionism (2) for both sides, which will hopefully reconcile) with one talk page to settle the dispute. A more modest step in this direction is to eliminate tag-team reverting and sock puppetry by revising 3RR to 3-per-side.
- Multi-voting. This is dealt with socially, well enough, by the general attitude which discounts users with <50 edits on VfD and especially RfA. Most multi-voters are new users and don't have any sock puppets with serious history, so it's easy to call them out. Most long-going users with sock-puppets (and there are quite a few) exercise restraint.
- Ban-evading. This one's impossible to fix. Every society (Wikipedia included) has the problem of its persona non grata with no stake in it. Short of coercion, it's impossible to get them to follow the rules. Ban a user and you'll probably see socks, some never detected. If spotted, revert his or her contributions for content reasons, but that's realistically all you can do.
- Relative to the particular Mike Church/Ambition issue, though, the "sock puppet" question may be interesting from a psychological viewpoint, but is utterly irrelevant. This is a content question (and I believe there is more than enough case for sending Ambition to VfD on content/fame grounds); the "sock puppet" issue will only make Mike win by fueling the growing suspicion of many that he is under a politically-motivated personal attack. Forget the "sock" issue entirely, send Ambition to VfD, and prosecute it on content grounds alone.
- Finally, since User:Crocogator is a 7-month running sporadic user, I don't think he's a sock of User:EventHorizon, who was apparently completely absent from mid-2003 (he said "a year and a half" on his user page) to Dec. 2004. Even in the oddball chance that he was, EventHorizon declined the nom, so it wouldn't be a multivote nor a violation of policy. The deceptive element would be disturbing, and may be characteristic of Mr. Church (he left before I started editing) but not, on any basis I can construct, of EventHorizon. Swatara 07:59, 8 Mar 2005 (UTC)
- Since joining these discussions seems a popular pastime, let me give it a try: Iso, are you sure you aren't being extremely paranoid? Anyone can jump in these things by watching RC (like yours truly) and anyone can edit under an IP for any amount of time before registering an account (like yours truly). Swatara's account is new and he "suspiciously" stumbles into this discussion, ergo he's Mike Church? (Oh, sorry, I mean "we can draw our own conclusions"?) Can't we at least evaluate his claims at face value instead of pre-emptively accusing him? I know you don't want to hear this, but I'm going to say it anyway: assume good faith. 82.92.119.11 21:44, 7 Mar 2005 (UTC)
- Note that Swatara has two edits to Wikipedia, the first of which created his user page. I leave you to draw your own conclusions. Isomorphic 21:22, 7 Mar 2005 (UTC)
- For legal reasons, definitely match (and not check) the passwords. I run a small message board that's had problems with sock puppets and trolling and they pretty much always use the same password. There's been a study that most Internet users can only remember 4 passwords, and almost always use a "main" one. It cuts down the ambiguity. Checking the IPs would be "security breach" under the law; your target probably wouldn't know you did it, but if you ever announced it, you'd struggle to back down from that one. Even checking the passwords, if not granted permission by the user, is illegal. There was a facebook clone that got busted in May 2004 for that. Matching the passwords, if there's a program available to do that, would be legit. (That is, it keeps the PWs internal, but returns a response if PW1 = PW2.) Anything more will get you in really hot water. Swatara 05:18, 6 Mar 2005 (UTC)
- Apologies for the crap clogging your talk page. If such cases arise in the future, I will use email. Isomorphic 21:08, 8 Mar 2005 (UTC)
- If you're going to do this, I'd be interested in knowing if 137.22.3.153 is EventHorizon's IP. If so, they're most definately Church. ✏ OvenFresh² 01:58, 6 Mar 2005 (UTC)
Removing meta-templates
[edit]Following the issues raised with using meta-templates, I would like to change the stub templates to no longer use metapicstub or metastub. I'd like to know if this might cause a DoS-type attack or any other problems. At what article count does this become a problem? For instance, should I be worried about changing a template used in 200 articles? 500 articles? 1,000 articles? Or is this only a problem for 5,000/10,000 articles? Finally, when is the best time of day to do these changes? (Don't worry, I don't plan to do this until things are back to normal.) Thanks! --jag123 19:50, 23 Feb 2005 (UTC)
I've begun to change the stub templates but I receive an error on those that are used on many articles, such as Template:Africa-stub, Template:art-stub, Template:actor-stub, Template:christianity-stub. The error is "Sorry- we have a problem...The wikimedia web server didn't return any response to your request." I'll continue to change as many as I can, but is there something that can be done about the others? Thanks! --jag123 18:47, 28 Feb 2005 (UTC)
Interface glitch
[edit]James, I've lost your e-mail address. Please e-mail me privately about the interface glitch; you asked me a question which I hesitate to answer in public. -- Uncle Ed (talk) 22:14, Mar 1, 2005 (UTC)
- Er, never mind. Anthere has taken the lead and managed it all. Again, I thank you for your utmost courtesy and attention to detail. Clearly, the right people are all in place, and you are one of the best! -- Uncle Ed (talk) 14:22, Mar 2, 2005 (UTC)
Page move bugs
[edit]- Somehow, Mikkalai's move of List of English words of Russian origin to Words of Russian derivation caused all of the editing history to be lost except for the most recent edit, mine. Contrary to what the history now says, I am not the sole contributor to that article. Is there any way to fix this? Uncle G 14:34, 2005 Mar 2 (UTC)
Bring back quickpolls
[edit]I think it's time that quickpolls be re-evaluated as a solution to short term disputes between users. What say you? --Ryan! | Talk 05:13, Mar 11, 2005 (UTC)
Dev workflow
[edit]I'm trying to make sure i've got a good grasp on what development looks like as it relates to a remote /PHP/Mysql/wiki environment.
User a PHP/webserver (local) to develop and test code. Use SSH/SCP? to copy code up to server and test via browser? -- Dbroadwell 17:10, 11 Mar 2005 (UTC)
- Your copious reply was appreciated; it reflects the community at Wikipedia. I wholeheartedly agree that using a raw text link to communicate code to a live server would be, suicidal given the net today. On the code side of things, my real coding experience is about two years, so I fall into the highly procedural side of things. (Hopefully I'll grok it in the next year.) Your other suggestion of being able to copy articles is currently beyond me, though there is a place to implement it eventually. Loving the open source movement, I think I've found something I can do, for no more time than I would spend on the task anyway. There is a reasonable interface for Linkbot, that implies a tacit permission by the editor, with a very simple interface: Include a template like {{User:Linkbot/linkthis}} . Yielding and explicit parse able list of articles to do and something to remove from the article when done. The community was also exceedingly forthcoming with brainstorming ideas … it’s inspiring. -- Dbroadwell 04:37, 12 Mar 2005 (UTC)
This is the other account I wanted checked. Thanks for your response :) -- Grunt 🇪🇺 15:48, 2005 Mar 12 (UTC)
Proposed amendment revote - personal vs official capacity
[edit]Grunt said that I should talk to you, not him, about this.
I think you got "personal capacity" and "official capacity" confused in proposals A3.1 and A4.1 at Wikipedia:Arbitration_policy/Proposed_amendment_revote, so I have edited it. I feel confident that you and I agree on this, based on our similar remarks when casting "No" votes at Wikipedia:Arbitration policy/Proposed amendment ratification vote, but I wanted to let you know. (If you are not the author of proposals A3.1 and A4.1, do you know who I should talk to?) —AlanBarrett 16:22, 13 Mar 2005 (UTC)
- I did not write those proposed amendments to the policy. I strongly oppose them as they are written. If you are aware of anyone else who thinks I wrote them, please correct them and note to them that I strongly oppose them.
- I did note that there was merit in splitting personal and official capacity. However, I oppose all four of the proposals which make the arbcom follow the directions of and report to the Foundation instead of this community. It's a massive and, IMO, very unwise change. Jamesday 13:10, 14 Mar 2005 (UTC)
Hi James, can you peek at the above proposed policy? The part about replacing lists with categories is something you probably want to know about. --iMb~Mw 15:26, 16 Mar 2005 (UTC)
- I was going to ask you the same. As Meowbot pointed out, the current implementation of categories makes the proposal somewhat awkward. So could you please enlighten us if there are any plans to augment or modify categorization coding? See also User_talk:Brion_VIBBER#Categories and User_talk:Brion_VIBBER#Another category idea for some ideas on cross-category searches. Radiant_* 13:22, Mar 17, 2005 (UTC)
- Thanks. Commented over there. I'll have a word with brion and the others as well - we definitely need to do something about the assorted category issues, to make them behave more like the normal pages peoople seem to view them as. The perils of something becoming popular.:) Jamesday 19:25, 17 Mar 2005 (UTC)
- For what it's worth - I am a professional programmer, and while there probably are enough coders already, if there's a discussion on this I'd be happy to join it if people think that could be useful. Radiant_* 10:33, Mar 18, 2005 (UTC)
Hardware status update
[edit]Hi Jamesday, could you please take a look at http://openfacts.berlios.de/index-en.phtml?title=Wikipedia_Status . Thanks :-) --217.9.26.233 17:50, 17 Mar 2005 (UTC)
IP check
[edit]I think User:VonBluvens may be the same as User:Earl Turner who was blocked for using misleading edit summaries. Could check if this is the case? -- Mgm|(talk) 19:44, Mar 17, 2005 (UTC)
If you don't mind, please take a quick look at my latest bot proposal. I'd like your thoughts and opinion on the matter. Thanks. -- AllyUnion (talk) 09:12, 18 Mar 2005 (UTC)
Sockpuppet check
[edit]67.67.114.200 posted this to Fadix' talk page. Since Fadix is part of a dispute, could you please check if this IP can be traced to User:Coolcat, User:Stereotek, User:Torque or perhaps Fadix himself? -- Mgm|(talk) 08:35, Mar 22, 2005 (UTC)
suspected sockpuppets (same person, using multiple usernames)
[edit]THOTH, Davenbelle, Stereotek, Fadix Please advise me. I also posted this on Tim Starling's page Cat chi? 01:11, 31 Mar 2005 (UTC)
- Absurd; check if you like. I'm no one's sock and I have none. — Davenbelle 02:30, Mar 31, 2005 (UTC)
Results? Cat chi? 21:57, 31 Mar 2005 (UTC)
Limited availability
[edit]I'm not around much for the next month or so as I change country. Best to make requests of one of the other developers for now. Jamesday 08:29, 31 Mar 2005 (UTC)
deleting of old versions
[edit]haie Jamesday,
on de we wonder when it will be possible to delete older articles again? as we start to get first problems with people who copy from "so called deleted" versions of Copyvio-articles to create new articles .. thanks for your answer we could not find any informations somewhere...Sicherlich talk 20:43, 4 Apr 2005 (UTC)
- thanks for the quick answer! ...Sicherlich talk 09:00, 5 Apr 2005 (UTC)
possible improvement for meta-templates
[edit]Hi - I've recently discovered Wikipedia:Avoid using meta-templates and have suggested on the talk page some potential solutions. One, in particular, seems like it might be feasible. The basic idea is to convert references to (at least parameter-less) templates into a server-side include syntax that would be understood (and processed) by the squid servers. With this change, if a template changes the only cache invalidation that would be necessary would be the template itself (rather than all pages including the template, or including a template including the template, etc.). I found a paper on the web that describes "edge side includes" which looks (to me) like an implementation of this idea, see http://www.oscom.org/attachment/72c7a5e5939d06b8545b6a41cc703144/af0bc06820a06da52903300a570fe891/Living_on_the_Edge.pdf Is this something you've heard of or considered? Thanks. -- Rick Block 23:29, 5 Apr 2005 (UTC)
Zürich to Zurich
[edit]Zürich has been nominated on Wikipedia:Requested moves for a page move to Zurich. Perhapse you might like to express your opinion about this proposed move on talk:Zürich. Philip Baird Shearer 10:45, 8 Apr 2005 (UTC)
re: Legal status of m:transwiki
[edit]Good evening. I read your recent opinion on the m:transwiki#legal status process with great interest. You inspired me to read the statute itself and to re-read the text of GFDL. I come to softer conclusions than those you expressed and replied at m:Talk:Transwiki#Legal (not) status of some transwiki operations. I would like your opinion when you have a minute. Rossami (talk) 02:55, 11 Apr 2005 (UTC)
Hello James, I'm not sure what to do about this, so I'm leaving this note for you and one on WP:AN/I. The above IP keeps being blocked, I believe because of vandalism from User:Kracky. This is a Shaw proxy server and the block keeps catching legitimate editors too, even though this isn't their IP address. That is, it seems Wikipedia is only finding the proxy server in this case, not the individual IP address. One of the editors being inadvertently blocked has written to me a couple of times asking me to unblock him, which I've done, but it also means I'm unblocking the vandal. I don't know what the right thing to do is in a case like this. Best, SlimVirgin (talk) 22:13, Apr 11, 2005 (UTC)
Help Please
[edit]Sorry to bother you with this - I seem to have gotten myself in a mess shortly after registering my name - the "friend" that encouraged me to join said the only way I could defend the allegations that I am a sockpuppet or whatever of an anonymous account is to contact a developer - so I picked your name from http://meta.wikimedia.org/wiki/Developer which he sent me.
I have been accused of being an anonymous user on John Kerry. Knowing that I am not that user I am asking that you verify to the following users that I am not the anonymous user: http://wiki.riteme.site/wiki/User:Mel_Etitis, http://wiki.riteme.site/wiki/User:Mirv who made the allegations here: http://wiki.riteme.site/wiki/Wikipedia:Requests_for_page_protection#John_Kerry and http://wiki.riteme.site/wiki/User:Mirv as well as on my talk page.
I am not sure if this is worth the trouble - and am in fact just thinking of blowing this entire site off, but in the name of honesty and defending myself from false accusations - can you help me. I made edits last night at these spots, before complaining that the Kerry page was blocked while I was trying to edit it:
- http://wiki.riteme.site/w/index.php?title=FOX_News&diff=0 *http://wiki.riteme.site/w/index.php?title=FOX_News&diff=prev&oldid=12237521
- http://wiki.riteme.site/w/index.php?title=Republican_Party_%28United_States%29&diff=prev&oldid=12242369
- http://wiki.riteme.site/w/index.php?title=Republican_Party_%28United_States%29&diff=prev&oldid=12237400
- http://wiki.riteme.site/w/index.php?title=User_talk:Symes&diff=prev&oldid=12238469
- http://wiki.riteme.site/w/index.php?title=Joseph_Goebbels&diff=0
- http://wiki.riteme.site/w/index.php?title=Oklahoma_City_bombing&diff=prev&oldid=12264363
and then when I complained first http://wiki.riteme.site/w/index.php?title=User_talk:Mirv&diff=prev&oldid=12238373 and http://wiki.riteme.site/w/index.php?title=User_talk:Mirv&diff=prev&oldid=12238476
Granted because I have been being coached a little through IM I have done some stuff I don't quite understand. Could you please help me - or if you can't point me to someone who would be willing to help me. TIA Symes 02:38, 14 Apr 2005 (UTC)
Subst syntax
[edit]Substituting with subst:
is often better than transclusion; but I think it is not often used. It is a bit cumbersome. Is there any reason not to provide a shorter atom? I was thinking of this:
{{":sometemplate}}
The rationale is that both the colon and the doubletick are shifted characters, and near one another on both the standard QWERTY and the improved Dvorak keyboard layouts. Thus it should be possible to demand substitution with almost equal ease as transclusion. What do you think?
On a related matter, I've been trying to work out a consistent method of documenting templates on their Talk pages. {{doctl}} survived a TfD, but it is still broken.
When it is mis-used, as a transcluded template, it works fine -- but of course this is useless; the new template creator needs to substitute it on the new template's Talk page and re-edit it with appropriate documentation.
When it is used properly, that is: {{subst:doctl|newtemplatename}}
, it blows up in most hideous fashion. I have fiddled with the code no end, without success. I'd be very grateful if you could throw me a bone here. — Xiong熊talk 22:18, 2005 Apr 15 (UTC)
- Sorry, can't help right now. Leave for a week-long business trip in a few hours, then get the joys of 7 days of final packing before changing country and then another trip. Hopefully someone else will be able to assist.:) Failing that, I'll be around again in 3-4 weeks. Jamesday 05:18, 17 Apr 2005 (UTC)
Just an idea. Have a nice trip. — Xiong熊talk 23:53, 2005 Apr 18 (UTC)
Emergency measures
[edit]I did reply to your request for suggested emergency measures, on Wikipedia talk:Avoid using meta-templates#Emergency measures. I do sympathize with your need to do more with less, and I understand that it is not helpful now to look for new equipment later. Let's see if we can work together to raise community awareness of the actual issues, unclouded by the partisan bias of a certain user. — Xiong熊talk 01:48, 2005 Apr 16 (UTC)
Subst
[edit]When you have the time, check out Bug 2003: Allow templates to be marked call-by-value-only. I'd like to know whether this is a good idea or not, and if it would help. You would be the one to know. JRM · Talk 13:12, 2005 Apr 30 (UTC)
Interwiki Bots
[edit]Hi James. Seeing that you're a developer, perhaps you might have a different aspect on this matter. I've been thinking over the recent number of interwiki bot requests and I feel that introducing a more restrictive policy would slightly benefit the Wikipedia. I'd be delighted to hear your thoughts on the matter. Please see my comments regarding this matter at: Wikipedia:Village_pump_(policy)#Interwiki_Bot_Policy_Proposal. Thank you for your time. -- AllyUnion (talk) 08:26, 21 May 2005 (UTC)
Adding photos from space
[edit]Hello hello - I noticed you linked a beautiful space shuttle photo in Gulf of Suez. When you link these photos please include in the caption the orientation of the photo (eg in this case facing north). Please also disambiguate east and west by including left and right. Appreciate all your hard work! --Csnewton 20:29, 25 May 2005 (UTC)
Invitiation to join the Wikimedia Research Team
[edit]Hello Jamesday,
I'd like to invite you to join the Wikimedia Research Team which I'm building on Meta with support from the Foundation Board of Trustees. Our goal is to work together to systematically analyze the needs of the projects, conduct research and collect empirical data, interview users, build relationships with outside developers, examine project proposals, and make recommendations to the Board for targeted software development.
I'm contacting you because of your keen understanding of database and server issues; I can think of no better person to inject a dose of reality into the sort of "blue sky" discussions we might have. I know that you're always busy, and it's fine if you take a while to respoond. Your involvement wouldn't necessarily mean any further time commitment on your part, but it would be nice to see you at meetings, and share ideas on the present and future of the project with you. If you're interested, just add yourself to the list of Current Members, and I will inform you about all future developments.--Eloquence* 16:25, May 26, 2005 (UTC)
Meta-templates
[edit]Hi there! I was asked to write a Signpost article on recent policy/rule/guideline debates. And I would like to say some things about templates (CoffeeRoll, for instance). Would you mind if I cited your words re: meta-templates considered harmful? I think it's something people would like to know. Yours, Radiant_* 15:58, May 27, 2005 (UTC)
- Never mind, the article is done now. I've simply used a link to your text, hope you don't mind. Radiant_* 12:36, May 30, 2005 (UTC)
Article Lists and Copyright
[edit]If you can, could you comment on the copyright issue presented at Wikipedia talk:WikiProject Missing encyclopedic articles#Copyright?. Dragons flight 05:23, Jun 22, 2005 (UTC)
I realized after looking at the talk that an outsider might have difficulty following the issue, so I'm going to take a moment to elaborate on the issue, just in case. As you know, since you were involved in advocating its deletion ([6], see March 2), a list of Wikipedia:Columbia Encyclopedia article titles was created in March 2004 and shortly thereafter deleted over concerns related to its copyright status. Now it is 2005, and other people have been created a similar list Wikipedia:2004 Encyclopedia topics based on articles appearing in the 2004 Encyclopedia Brittanica. My concern on that talk page goes to how can the latter be acceptable if the former was considered a copyright violation. Some editors have mentioned but not referenced unspecified subsequent discussions or opinions that both lists ought to have been okay. Since you were involved in the deletion of the original Columbia list, I was hoping you might be able to comment on that determination and whether the same problem seems likely to apply to the 2004 Brittanica list. Thank you for your time and consideration. Dragons flight 17:29, Jun 22, 2005 (UTC)
Orphaned
[edit]You have links at the top of this page to the Lonelypages report. I hope they are a note to yourself to fix the report. It has been stuck at just showing 1000 titles for several months. -- RHaworth 16:46, 2005 July 12 (UTC)
Meta-templates vs Maintainability
[edit]I would be glad if you could spare a moment to look at Template talk:Coor#Discussion and give a developer's opinion. -- RHaworth 16:46, 2005 July 12 (UTC)
sep11.wikipedia.org
[edit]I don't think a September 11th Memorial is appropriate to have as part of Wikipedia. Ideally it should be transferred to a more appropriate organization for hosting and administration, or alternately, converted into a Wikibook. I'm not sure how the Sept 11 wiki came into existence, but I'm glad we're not doing new ones. I'm sure there are more appropriate places for such material. Kaldari 00:56, 14 July 2005 (UTC)
- The thing that bothers me about sep11.wikipedia.org isn't that it exists, but that it is ostensibly presented as if it were part of Wikipedia. sep11.wikipedia.org does not follow the rules or conventions of Wikipedia and for all extents and purposes it should be seperate from Wikipedia. A memorial does not belong in an encyclopedia. The easiest step that could be taken in this direction would simply be to change the logo of sep11.wikipedia.org so that it is not a Wikipedia logo. I also believe that the domain name should be changed as well, following the convention of other Wikipedia sister projects. I think the way it is set up currently is confusing. Kaldari 18:49, 15 July 2005 (UTC)
Merging edit histories...
[edit]... can we still do this? I thought that this was no longer possible! - Ta bu shi da yu 08:25, 18 July 2005 (UTC)
Yet Another London Wikimeet
[edit]Heya James,
We're organising another London meetup, for Sunday the 11th of September; specifics still to work out, but it will probably be fun as ever, and involve a few drinks and a nice chat in a pub. As a freshly British inhabitant, I thought you might want to know. We'd love to see you there...
James F. (talk) 22:48, 19 July 2005 (UTC)
Thanks for update ...
[edit]... however you do it ... of edit counts. Sfahey 21:56, 25 July 2005 (UTC)
- First, thanks for updating the list. Second, per Wikipedia_talk:List_of_Wikipedians_by_number_of_edits#Data the "past month" counts are done inconsistently (article space counts since June, main namespace counts just June). I'm not sure it's worth rerunning the script to fix this, if you don't can you let me know you're not going to or edit the page to explain the anomaly? Last, any idea why the numbers are different from the numbers from Kate's tool? Thanks. -- Rick Block (talk) 01:05, July 26, 2005 (UTC)
- Thanks for the update, Noel and I were working on using the dumps, but were getting major errors from gzip. I used your data to update Wikipedia:List of Wikipedians by number of recent edits, but have requests to include all users, and not just those with 1500+ edits. Do you think I can get a copy of your entire dump? Also, is it correct what Rick Block said about the main namespace only being June? If so, I need to fix the wording on the recent edits page. Thanks. ∞Who?¿? 20:19, 27 July 2005 (UTC)
- Thanks for your reply.
- Probably take care of it in a month or so, when it's time to update the page. Not a promise. Jamesday 04:29, 1 August 2005 (UTC)
- That's ok, no big hurry, we couldn't get db acs and had our probs, so whenever we can get a total data list from your scripts, we'll just make use of that. Thanks again. ∞Who?¿? 05:11, 1 August 2005 (UTC)
- Thanks for your reply.
response requested
[edit]Hi - Can you please respond at Wikipedia_talk:Avoid_using_meta-templates#Still_a_problem?? Thanks. -- Rick Block (talk) 12:40, August 2, 2005 (UTC)
User:Davidley lost password and bad email
[edit]From help desk:
- My password doesn't seem to work (Or I recall it incorrectly). When I click on the "E-mail new password button" I don't receive an email (I've waited a couple of days). Either the email functionality isn't working or I did not have the correct email address on my user preferences. My username is: Davidley, and my email address should be "ley (at) cs.dal.ca" . Can anyone help me reset my password? Thanks.
Well, I don't know what process we have in place for this sort of thing. We can't just email him a password at the address given here. The user page in question is rather un-anonymous; I would go so far as to say that if anyone can demonstrate his real identity is David Ley of U Toronto, he deserves control of the username whether he can be shown to have created it or not.
In the case of a user who creates an account User:Modbloofool, makes a few edits, and then claims to have lost password with bad email addy, I'd say, hey, too bad, go be somebody else. But I think this case merits developer attention. — Xiong熊talk* 02:46, 2005 August 13 (UTC)
- Being my usual buttinsky self, I have to say: can't he go be somebody else? He could register User:DavidLey and redirect his old page to his new one, making note of the how and why. He only has 61 edits, so I don't think edit count vanity would be important. JRM · Talk 03:11, 13 August 2005 (UTC)
- Silly me. Copying this to the help desk. JRM · Talk 03:11, 13 August 2005 (UTC)
- Hello, this is Davidley, as per the instructions on the help desk, I am posting a comment here in the hope that someone can reset/email me a password (email: ley @ cs.dal.ca) . Thank you. --64.231.174.234 13:44, 14 August 2005 (UTC)
- Davidley again here. Don't know how it is possible to "prove" that I am Davidley. My IP address listed here seems to be different from the one of my last post (I am on a Bell Canada DSL account, so I am pretty sure it is a dynamic IP). Other email addresses that might be more of a "proof" of who I am include: "david.ley (at) utoronto.ca" and "dave (at) ley.ca". I hope this is enought to convince someone to email me my password. Thanks, Davidley --64.231.174.234 13:50, 14 August 2005 (UTC)
- If you use the forgotten password link an email will be sent to you "david.ley (at) utoronto.ca" address. You can then change the email address to the one you prefer. Jamesday 23:22, 16 August 2005 (UTC)
- Thank you! --Davidley 15:26, 17 August 2005 (UTC)
- Mr. Bene here with a situation similar to the fictitious Modbloofool. My argument for maintaining specifically the Mr. Bene user ID is consistancy and a certain level of anonymity - especially in the Web analytics front where I've been contributing relatively anonymously at the request of my employers. Previous edits should have come from this IP, and also a residential Rogers Cable IP block. "mrbene at gmail dot com" mail address association can be seen on [http://bene.sitesled.com/about.htm] (skip or don't skip the coralize script, it serves the same page) also backed up by early contributions Filterset.G. If it can be done, I'd be much appreciative, if not then, well...
- Never mind, it arrived. Mr. Bene
- Was about to tell you that the email address was already there and that I'd confirmed the link required to change it, if that was necessary. Glad it's working for you now. Jamesday 19:15, 15 September 2005 (UTC)
new users
[edit]Hi - There's been some willy on wheels incidents lately where he uses pre-created accounts (to get around the move restrictions). A couple of folks have suggested a special:newusers would be helpful. Perhaps one way to do an equivalent action would be to add a parameter to special:listusers, so a URL like http://wiki.riteme.site/w/index.php?title=Special%3AListusers&from=20050710152751 (the from string is a date) would work. Assuming that such an enhancement won't be coming soon, do you think you could whip up a list of the most recently created 1000 or 10000 users, ordered by account creation date, and post it someplace? I believe this would be extremely helpful. Thanks. -- Rick Block (talk) 15:34, August 27, 2005 (UTC)
You might be interested to have a look. Regards. --Pgreenfinch 13:00, 3 September 2005 (UTC)
Ping
[edit]Replied on my talk page. --Gmaxwell 07:08, 18 September 2005 (UTC)
Request for moderator attention
[edit]Hello. Articles Derek Croxton and Anuschka Tischer are in AfD since September 9 but the AfD clearly failed. Articles are to be kept. I wonder if you´d be so kind as to remove them from AfD? Thanks. Doidimais Brasil 18:22, 18 September 2005 (UTC)
PostgreSQL
[edit]I just wanted to let you know I've replied to your comment re: MVCC on Talk:PostgreSQL.
While I've got your ear, I'm curious -- do you know if any thought has been devoted to using Postgres for Wikipedia? I realize the PG port for Mediawiki is less mature than the MySQL support, so it is probably not something to implement in the short-term, but if anyone's interested in considering it I would be happy to help in any way I can. Neilc 22:28, 24 September 2005 (UTC)
Hi, I know you are rather busy. I was wondering if you have time, if you could run your script on the new DB for September. You wouldn't have to update the page, there are a few of us who wouldn't mind parsing the data and updating it. If you get a chance, that would be great, but it's not important. Thanks. ∞Who?¿? 08:10, 26 September 2005 (UTC)
request for bureaucratship at tamil wiktionary
[edit]Hi, I am user:ravidreams, I would like to become a bureaucrat in the Tamil Wikitionary since there is no bureaucrat there till now. i have the same username there. I have got support from the community. you can find the elections page here . I was directed at meta wikimedia site to ask a developer regarding this and i hope i am asking the right person. thank you--Ravishankar 09:23, 30 September 2005 (UTC)
Sept11.wikipedia.org
[edit]The front page links to non-exisitant wikipedia articles, some more than once. Rich Farmbrough 22:02, 3 October 2005 (UTC)
CSS in wikipedia
[edit]I appreciate your comments about the use of CSS and site-wide style sheets as opposed to templates at WP:AUM#Alternatives. Is there a better discussion point for the further integration of CSS with mediawiki? ∴ here…♠ 19:48, 19 October 2005 (UTC)
Slovene Wikipedia
[edit]As you're one of the developers I'm turning to you with request to translate some on MediaWiki software, used on :sl. As of now we're still using english command for categories, but we wish to use slovene version (Kategorija instead of Category); some of associated commands were already translated, but this wasn't. Another translation is of Template to Predloga. Regards, --Klemen Kocjancic 10:51, 21 October 2005 (UTC)
Someone else noticed the shenanigans in CC-2.5!
[edit]I was thrilled when I hit your user page and saw that someone else has noticed the nonsense with CC-2.5! I wrote some pretty fuming stuff when they put out cc-wiki, and I was both shocked and not shocked to see it quietly slipped into 2.5. One thing I've noticed is that the previous versions of CC seem to include an 'or any later' clause directly in the license, which seems pretty bogus to me if they are going to substantially change the character of the license. It's quite unfortunate, creative commons has the nice little system of modifiers.. they should have made a 'CA' (community attributed) and left it at that... But I guess greater powers are at play. Do you have any idea why this hasn't gotten more attention? --Gmaxwell 06:00, 26 October 2005 (UTC)
- explain? I didn't see this addressed directly on the user page -- though I am curious about the whole 'opt out for info freedom' statement ∴ here…♠ 18:08, 26 October 2005 (UTC)
- See the difference between 4.c in cc-by-sa-2.0 and cc-by-sa-2.5. This is a concern because CC-BY-SA-2.5 incorporates aspects of CC-WIKI, a license which takes attribution from content creators and grants it to website operators merely because they operate a website. CC-BY-2.5 doesn't go quit as far a CC-WIKI because it's is very vague about the subject. Considering that there have been a number of cases where internet resources have later commercialized their user created content and shafted their users in the process, we shouldn't take such a thing likely. The argument behind terms like this is that with highly collaborative works that the contributors copyright interest is individually very small and that the work was indeed the product of the community. This argument has two problems in most cases: one is that the work is actually highly collaborative; In most cases I can find it isn't, for example on Wikipedia the majority our longer articles were written by single people or a very small group of people who each made a copyright worthy contribution, and a zillion tiny changes by others. The second problem with the argument is that there seems to be a misunderstanding that a website operator (whom we can attribute to) is the same thing as a community (which is too ephemeral to receive attribution). Even in the case where it would be fair to attribute to the community what we end up doing is attributing to some website which might represent the community today, but the community could fork or move inmass and then find themselves having to grant attribution to a site they now dislike. If users wanted to contribute under that new license that is there call, but I hope you can see how inserting terms related to this in CC-BY-2.5 was a substantial change in character and was a mistake from an ethical and legal perspective. Because CC could have just as easily produced a new modifier tag (and didn't adjust the layman version of the license that you see before the 'legal code'), I can only conclude they introduced that clause into CC-BY-2.5 with the express intention of changing the licensing of existing work without the consent of it's creators, which I consider to be an indefensible and morally reprehensible act. There is also a degree of confusion about who encouraged the addition of this language because I was told conflicting things by the Creative commons folks and the Wikimedia foundation board when CC-Wiki was first released. I haven't been able to follow up more on this because the subject upsets me somewhat (as you might guess by my rant here :) ). --Gmaxwell 19:15, 26 October 2005 (UTC)
- What is the correct course of action in protest to such an annoying development? Is phrasing such as the Jamesday's sidebar adequate? What about this opt out bs? Is there a better, more public, forum for this discussion? ∴ here…♠ 20:23, 26 October 2005 (UTC)
- The CC mailing list is one suitable venue for the CC side, since it does mean that an author can't trust the presene of a CC license to protect their own interests, a lamentable development. Lessig used the CC wiki license for the new version of his book, the site there also had a statement that any contributors were giving up their moral rights. The submission standards grant of an agency to send infringement notices was a threat to the work, via giving one licensee power over other licensees and threatening the ability of others to reproduce the work, either through action of the agent or through a legal judgment transferring the assets to another entity hostile to the work, or simply through undue heavy-handedness. Basically: any concentration of power or authority over the work itself is a threat to the ability to reproduce the work, so we need to watch for and prevent such concentrations.
- What is the correct course of action in protest to such an annoying development? Is phrasing such as the Jamesday's sidebar adequate? What about this opt out bs? Is there a better, more public, forum for this discussion? ∴ here…♠ 20:23, 26 October 2005 (UTC)
- See the difference between 4.c in cc-by-sa-2.0 and cc-by-sa-2.5. This is a concern because CC-BY-SA-2.5 incorporates aspects of CC-WIKI, a license which takes attribution from content creators and grants it to website operators merely because they operate a website. CC-BY-2.5 doesn't go quit as far a CC-WIKI because it's is very vague about the subject. Considering that there have been a number of cases where internet resources have later commercialized their user created content and shafted their users in the process, we shouldn't take such a thing likely. The argument behind terms like this is that with highly collaborative works that the contributors copyright interest is individually very small and that the work was indeed the product of the community. This argument has two problems in most cases: one is that the work is actually highly collaborative; In most cases I can find it isn't, for example on Wikipedia the majority our longer articles were written by single people or a very small group of people who each made a copyright worthy contribution, and a zillion tiny changes by others. The second problem with the argument is that there seems to be a misunderstanding that a website operator (whom we can attribute to) is the same thing as a community (which is too ephemeral to receive attribution). Even in the case where it would be fair to attribute to the community what we end up doing is attributing to some website which might represent the community today, but the community could fork or move inmass and then find themselves having to grant attribution to a site they now dislike. If users wanted to contribute under that new license that is there call, but I hope you can see how inserting terms related to this in CC-BY-2.5 was a substantial change in character and was a mistake from an ethical and legal perspective. Because CC could have just as easily produced a new modifier tag (and didn't adjust the layman version of the license that you see before the 'legal code'), I can only conclude they introduced that clause into CC-BY-2.5 with the express intention of changing the licensing of existing work without the consent of it's creators, which I consider to be an indefensible and morally reprehensible act. There is also a degree of confusion about who encouraged the addition of this language because I was told conflicting things by the Creative commons folks and the Wikimedia foundation board when CC-Wiki was first released. I haven't been able to follow up more on this because the subject upsets me somewhat (as you might guess by my rant here :) ). --Gmaxwell 19:15, 26 October 2005 (UTC)
- It's probably also getting to the time where we need to establish a second host for the whole work (meaning EVERYTHING in the database, including user accounts, and all configuration files), to provide a complete and secure full version if there's a problem with the first, be it technical disaster, hurricane, legal, political or whatever. Jamesday 21:45, 26 October 2005 (UTC)
- From a technical perspective this wouldn't be too challenging initally, the subject came up fairly recently what it would take to accomplish this which caused me to make some evaluations. I've secured an offer to provide solid hosting, and I could cover the capital costs of approiate hardware... I'm willing to do much of the work. I was planning of maintaining my own database for the purposes of analysis but after getting access to toolserver that mostly closed that need. OAI link will be fixed, but we'll need it for toolserver and I presume the new answers.com branded site will need it too. I think the biggest challenges will be mediawiki development progress breaking stuff, and of course political. Perhaps I should work with a local chapter to establish such an alternate source? Your thoughts?--Gmaxwell 22:11, 26 October 2005 (UTC)
- It's probably also getting to the time where we need to establish a second host for the whole work (meaning EVERYTHING in the database, including user accounts, and all configuration files), to provide a complete and secure full version if there's a problem with the first, be it technical disaster, hurricane, legal, political or whatever. Jamesday 21:45, 26 October 2005 (UTC)
Template transclusion
[edit]There has been some recent thought that certain templates should always be subst'ed, and a list is being compiled with the intent of having a bot automatically subst all those templates. The two main reasons are article stability, and server load. Since you're one of the experts on the latter, it would be appreciated if you could give your opinion on this. The relevant page is Wikipedia:Subst. Radiant_>|< 17:54, 1 November 2005 (UTC)
Hi James, I'm interested in launching that script for getting a list of wikipedians by number of edits in spanish wikipedia. For that I need few fields in user & user_rights tables. I wonder if you can provide me a dump of that tables just containing needed fields for querying my local database. Thanks very much. --() 08:37, 27 November 2005 (UTC)
- I would also like to request such script for Slovene Wikipedia (:sl), if you have any spare time! TIA! Regards, --Klemen Kocjancic 12:10, 30 November 2005 (UTC)
- Sounds as though I'll need to do some work on improving the script to make it a bit easier to run for all wikis. I'll see what I come up with... if I get something reasonably effective I'll run it myself on them all. Jamesday 03:07, 3 December 2005 (UTC)
Thanks, that would be great! Regards, --Klemen Kocjancic 21:59, 3 December 2005 (UTC)
More bad templates
[edit]Some new so-called "logical" templates are being created (see Category:If Templates and Category:Boolean Templates) by a couple "clever" individuals who've found a way to hack the template mechanism into doing things it was not intended for. Rather than petition the MediaWiki developers (or write code themselves), they've put this kludge into effect and it is unfortunately growing rapidly. I'd like you to take a look at those and please comment on Wikipedia talk:Avoid using meta-templates#Logic templates. Thanks very much. -- Netoholic @ 14:51, 9 December 2005 (UTC)
- Please also have a look at the discussion that emerged on User talk:AzaToth#Wikipedia:Avoid_using_meta-templates. – Adrian | Talk 15:18, 9 December 2005 (UTC)
- The discussion is now at Wikipedia talk:Avoid using meta-templates, and could really use some developer input. At the moment, the guideline tag has been removed from WP:AUM because there wasn't "consensus" about it. If you have a chance, I'm sure a comment from you would be very much appreciated. Thanks. -- Rick Block (talk) 00:46, 13 December 2005 (UTC)
- Sorry for nagging again. I tried to write a more complete discription of the dilemma under Wikipedia talk:Avoid using meta-templates#Proposal for "lazy templates". Thanks! – Adrian | Talk 08:25, 13 December 2005 (UTC)
Thanks for commenting (and I assume my descriptions of how things work are close enough). -- Rick Block (talk) 21:05, 17 December 2005 (UTC)
multiple DB servers?
[edit]HI - Random thought - would it be possible to introduce multiple DB servers partitioning the load by at least namespace? Seems like one of the primary issues with wikipedia scaling is the reliance on a single database on the ultimate back end, and distributing the database among multiple servers would allow a X N scaling to be employed. At the Apache layer there'd need to be connections to each and each Apache would have to know where to go for what, but at a coarse level it seems like at least the namespace could be used as a DB selector. Going further, perhaps the main article namespace could be split by first letter as well (e.g. A-L on DB1, M-Z on DB2). Imagine, for example, if just templates were off on their own DB server. This wouldn't fix the cache invalidation problem when they're changed, but seems like it would help the page generation issue. Anyway - just a thought. -- Rick Block (talk) 16:49, 19 December 2005 (UTC)
- Good thought and exactly right. Yes, partitioning is already happening. One of the issues is en load, which is more than 50% of the total, so there's a definite limit on how far we can go without partitioning within a project. That's something I said we'd need in 2005, back in the early spring of 2005, around Jan. We've dodged it so far by adding more RAM to the database servers so they can handle a bigger working set; also by partitioning away the text of old revisions on to sets of database servers running on the apache web servers, to exploit their disks rather than filling the main database server disks. For a long time now, we've been sending the queries to servers based on project, because that improves cache efficiency. We're also in some cases now splitting the replication as well, so some servers don't even have all the data. This has a reliability cost because it decreases the number of servers available to switch to if the server just doesn't have the data, but it's necessary, we just need to ensure that we have enough so its not too likely to be a problem.
- Changing the software to allow partitioning within a single project is going to be a massive task and it's not work which is glamorous, compared to things like adding nice new features, so it's not a surprise that it hasn't been done yet.
- Longer term, one of the growth issues is how to keep up with the update rate. It's already eliminated the viability of database servers with 4GB of RAM replicating the whole database. Eventually, we'll hit the point where even keeping up with only en is a problem. IN this, templates help, because they decrease he amount of work needed to be done to get a change across multiple articles. But, templates are in the more near term a threat because they take out lots of servers for a while if a popular template is changed, delaying pages for everyone for all servers which are replicating that particular database. It's not so nice for humans but splitting a template into ten different versions signnificantly decreases the problems, even if all ten are identical, just split by article name or template which includes them (that is, partitioning just as you described, but based on how big the chunk of pages to be modified with each update is). Here's an example from a few minutes ago:
- I was using 30 second refresh so that "touch" update took between 10 and 40 seconds and delayed requests of users hitting the slaves by that long (in theory. The load balancing tries to shift the work around after a while and some queries might have been switched to the master, which is a DOS threat to the master). Those lines showing MASTER_POS_WAIT are the ones being delayed.
- I've been asking for and largely getting schema changes to help deal with this and that's been of some use, but it's still a major concern, because we probably need to double 5 more times (takes us above Google's current traffic). Jamesday 21:23, 19 December 2005 (UTC)
Template redirects
[edit]Greetings.
It is a commonly cited Wikipedia maxim that "Redirects are cheap." This refers to the fact that article redirects have minimal cost in terms of disk space, bandwidth, and presumably server load.
A question has recently arisen as to whether or not template redirects are similarly cheap. The issue of the "cheapness" of template redirects has become a particular bone of contention with respect to stub redirects. One group of folks holds that a strict naming convention for stubs should be followed, and that stub redirects (Template:Bike-stub → Template:Cycling-stub, for example) should be deleted or otherwise deprecated. Another group of folks holds that redirects are useful, and should not be deleted or otherwise deprecated if they adhere to the redirect policies as outlined at Wikipedia:Redirect and Wikipedia:Redirects for deletion.
It was suggested that one of the developers be approached, hat in hand, to ask for their sage counsel. So here I am. Are template redirects sufficiently expensive in terms of server load that they should be avoided? Or are they sufficiently cheap that they can be thought of as a trivial increase to the server load? Or do they fall somewhere in between?
Thanks for your time. All the best.
Ξxtreme Unction|yakkity yak 10:15, 28 December 2005 (UTC)
- Don't take this as gospel until Jamesday confirms it (although I'm not a mediawiki developer I have a fairly good grasp of how the software works), but from my understanding article redirects should be cheap since the entire page corresponding to the redirected article can be cached in the squid front ends. Page views for such pages (that are in cache) are served entirely by these front end cache servers without hitting either the apache servers that run the PHP code that generates the page contents or the ultimate backend database.
- Template redirects amount to a template invoked within a template, which is a technique that should be avoided (see WP:AUM) because of the database and cache invalidation load that is created. In this specific case (redirects for stub templates) as long as the number of articles including the stub template by either name remains reasonable, the cache invalidation effects aren't increased (i.e. from this perspective it doesn't much matter whether all articles include the root template or some include the root and some include the redirect). On the other hand, every time an article including the redirect is changed the apache server generating the new page contents has to fetch both the redirect and then the root template. From a database perspective, this means the work involved in fetching the template is roughly doubled.
- The database is the one component in the architecture that can't be easily replicated (more money can buy more squids and more apaches, but architecturally there's a single database), so when generating the article contents (which happens at least once each time the article or any template it includes is changed) the database is usually the bottleneck. If all stub templates were invoked by a redirect the database load due to fetching stub templates would be double what it should be, so if this is X% of the total database workload eliminating the redirects would cut the total workload by (X/2)%. If 20% of stub templates are invoked by a redirect eliminating the redirects cuts this X% of the workload by 10%, i.e. reduces the total workload by (X/10)%. I wouldn't be surprised if X were in the neighborhood of something like 20 (meaning 20% of the total database workload is due to fetching stub templates), so even 5% of that would add up to 1% of the total workload.
- My bottom line guess is that anything that can be done to reduce the overall database load by more than 1% is well worth doing and that stub template redirects should be deleted. -- Rick Block (talk) 16:28, 28 December 2005 (UTC)
- On squid caching, note that normal redirects can be expected to cause a second copy of the page to be cached, wasting cache space, because of the "redirected from" text which needs to be added to the page. That's one technical reason why it's nice to avoid links to redirects in articles, though the technical issue wasn't a factor in our practice of avoiding doing that. This won't apply to template redirects though, since they don't generate such a page. Jamesday 00:12, 7 January 2006 (UTC)
{{us-street-stub}}
- I think it actually doesn't cause any extra load. If you click edit on this page, which uses {{us-street-stub}}, only {{US-road-stub}}, the "real" name, shows below. On the other hand, if us-street-stub had US-road-stub transcluded, both would show up. --SPUI (talk - don't use sorted stub templates!) 15:22, 6 January 2006 (UTC)
- I'd guess this is simply redirects being filtered out of the display (for example whatlinkshere for the redirect shows this page). Since the redirected template is stored in the source, it pretty much has to be fetched to regenerate the page It's perhaps possible that a database query for the contents of X, if X is redirected to Y, returns the contents of Y (X becoming a secondary key of some sort to Y), but I doubt it. If I were less busy I might look this up in the source. I'd expect Jamesday simply knows. -- Rick Block (talk) 20:01, 6 January 2006 (UTC)
- Your doubt is right - the redirect would be fetched, then the real page. Same for other redirects. Jamesday 00:12, 7 January 2006 (UTC)
- I think it actually doesn't cause any extra load. If you click edit on this page, which uses {{us-street-stub}}, only {{US-road-stub}}, the "real" name, shows below. On the other hand, if us-street-stub had US-road-stub transcluded, both would show up. --SPUI (talk - don't use sorted stub templates!) 15:22, 6 January 2006 (UTC)
- As costs go I expect them to be fairly modest. But I'd rather not see them. Here's a quick analysis:
- They are quite small so they probably don't add much extra to be cached. Will add one more page to be checked on the way to getting the content so it is an extra query when the page is being built. Probably fairly fast, but it's there and does need to be processed.
- Redirects are index entries to help people, mostly readers, find things. Template redirects don't serve readers, only authors, who can be expected to try to use the direct template if they know about it. But sometimes they don't.
- General practice is to seek to avoid redirects in links from one article to another, replacing the link to the redirect with a direct link.
- They are unlikely to be changed regularly, so the issues with replication lag and slowdown and the issues with purging many pages probably don't apply.
- But... they may prevent proper purging when the template they redirect to is changed. Now, I actually like this effect, because it reduces load... but it's probably something which would be unpopular with those who changed the template. I have not checked whether this supposition is accurate; it flows from the general design and there could be a special case to handle it. Probably isn't.
- What I suggest is:
- have templates like Template:Bike-stub contain text saying something like "Please replace this use of Template:Bike-stub with Template:Cycling-stub or Template:Motorycling-stub or whatever else might be appropriate".
- This alerts authors to the existence of the other template(s) they might use, thus fulfilling the purpose of a redirect (helping people to find a resource), trusts that authors will try to follow our general practice of avoiding redirects in article text, while reducing load. The text will be seen in preview, generally, so it'll also dodge the saving of the unnecessary revision and subsequent edit by another author to change this redirect to a direct link to the other template.
- Jamesday 00:12, 7 January 2006 (UTC)
- Thanks for your response. Discussion is now underway regarding how best to implement your suggestion. There is currently some difference of opinion as to how conservatively to interpret your comments. In the event that you are interested in such discussion, you can find them in the lower reaches of both Wikipedia talk:Redirects for deletion and Wikipedia talk:Stub types for deletion.
- All the best.
- Ξxtreme Unction|yakkity yak 13:09, 8 January 2006 (UTC)
- All the best.
Templates and server load
[edit]Are there any server load issues we should be aware of regarding often-used templates, categories on those templates, or images on those templates? Many editorial and/or userbox templates are frequently used and contain both category (which would be redundant with Special:Whatlinkshere) and image (which sometimes is a scaled down version of a really big image). Radiant_>|< 22:39, 15 January 2006 (UTC)
- Images are of most concern to me because image serving load has repeatedly taken the site down or caused major load problems and remains a major scalability challenge for the site. For this reason, I suggest minimising the use of "decorative", "icon" or "hint" images and using them for "content" only, whenever this is practical. Content = whatever the article is about, a picture of an author or book cover or statue or similar. The issue has generally been simply the use and need to check the image, not its size. Category links seem generally to be regarded as useful, though large categories with more than a few thousand entries have been problematic and breaking down huge categories into smaller ones is likely to be useful. Jamesday 03:15, 20 January 2006 (UTC)
- Thank you. I have put up a request to remove images from stub and userbox templates. Radiant_>|< 11:34, 20 January 2006 (UTC)
I was stopping by to ask a similar question. There has been alot of chaos surrounding 'nested' templates based on your comments that they cause server load, and I'm not sure people are understanding the server issues quite right. For instance, Template:User wikipedia was being changed from a 'meta-template' which used template:switch to display one of several userboxes into individual templates for each box... good so far. However, a decision was then made to immediately convert it to a single userbox because 'meta-templates are bad'... users whose pages were trying to call the meta version then started receiving incorrect displays and they reverted the template back to meta... so an admin reverted it back to the non-meta version and protected it... but that broke the display of another admin's user-page so he reverted it back... et cetera. Unless I am very much mistaken this kind of thing causes the server load problems we are seeking to avoid and just leaving the 'meta' version of the template in place until all calls to it had been switched over to the various new simple templates would have been better.
Likewise, there have been efforts to replace 'meta-templates' which call one of several other templates (see Template:P1, Template:P2, et cetera) with a single template that uses parameter switches to return the same results... but experimentation shows that evaluating 50 (or whatever) parameters takes longer to render than calling one of 50 sub-templates based on a single parameter check. Also, consolidating the 51 templates (50 + 1 calling them) into just one still impacts just as many pages when the template is updated (actually one page less) and thus doesn't seem particularly beneficial in terms of page caching/updates.
It would be very helpful to have some sort of 'sanity guideposts' for these server load issues. Do we really need to be going after templates which will only ever be linked to 25 pages because they use a 'meta' design? Are 'stub-templates with images' really that big a deal as you'll usually only see one or two stub-types (each with one image) on a page? A list of the top server load issues (such as the above about lots of pictures and large categories) would be very helpful, but metrics would also be good. Something like - 'templates linked to less than 50 pages (directly or through nesting) cause little server load', 'templates linked to more than 1000 pages (whether directly or through nesting) should be killed with a stick', 'pages with more than 20 images are evil', 'categories with more than 500 pages linked should be split into sub-cats', et cetera. Right now people are flying blind and sometimes 'fixing' problems which don't exist in ways which may be bigger problems than the original. If we can more clearly define the things which cause significant server strain it'll be alot easier to alleviate. --CBD ☎ ✉ 13:15, 20 January 2006 (UTC)
- I second this. A huge stink is being made of various interpretations of your words, and we really need some definite guidelines.
- Saying something simple like "don't use server resources unnecessarily" is not helpful at all. Should we stop editing pages for the sake of server load, too?
- Reading through your original comments on the talk page, it seems like you viewed subst'ing nested templates as a sort of last resort/"temporary expedient" for a temporary server load problem (you said "six months" in April; it's been nine), but the solutions people are using to "avoid meta-templates" since your comments are much more drastic, and continuing in full force. We need definitive advice about which templates are bad, why they are bad, and quantitative measurements of how badly each type harms the servers compared to other functions so that we can make informed decisions.
- You once mentioned a way to "add a feature to turn off template expansion" during periods of high server load.
- The short-term technical expedient which is likely to work is adding a switch to turn off template expansion and flipping that switch, causing template text values to be displayed instead of template contents.
- I think this would be a better solution. Does it exist yet or would it have to be written? I would much prefer a technical expedient to a poorly-implemented human one. The current "temporary expedient" is permanently removing links and dependencies, cluttering up the wiki markup with unnecessary HTML (remember that wiki is supposed to be editable by anyone) and using kludgy hacks to perform functions that could be done much more elegantly with the "forbidden" template functionality. — Omegatron 14:36, 20 January 2006 (UTC)
category proposal
[edit]Hi - Not sure if you've seen this, but I thought I'd draw your attention to Wikipedia:Village pump (technical)/Archive 64#Categories and tags. From a usability viewpoint, this seem like a great idea to me. On the other hand, I'm not entirely sure MySQL would be up to it. Definitely seems like something worth thinking about. -- Rick Block (talk) 04:35, 20 January 2006 (UTC)
Civil War Image Removal
[edit]Regarding this page, Template:AmericanCivilWar-stub At 15:04, 20 January 2006, Kirill_Lokshin Said this, "Removing decorative image per Jamesday's request." Why were these two images removed?
evrik 20:28, 20 January 2006 (UTC)
- See my answer in Templates and server load just before this question. Images in templates were contributing to major site performance problems for a while, including complete site outages, due to a hardware performance limit being reached. The request no longer applies because the problem was resolved with more hardware from a later fundraising. Nobody on the tech team back than liked such requests. They were just the most pragmatic harm-minimising workaround when we couldn't scale the hardware or software as fast as demand was growing. Back then we'd see a surge of growth then run out of hardware capacity and get slow or break. Repeat, doubling demand every three months or so. It was an interesting and fun race but not a recipe for perfection. In general, within a year or two of that request the large increase in audience resulted in similarly large increases in fund raisings (from £50-$100k to millions a year) to where it was possible to spend the way out of quite a few things that would have taken requests for restraint earlier. This one may well have been the last of those requests. Jamesday (talk) 01:45, 30 November 2013 (UTC)
re server load / userpage images
[edit]Hi Jamesday, I asked a few questions about the server load/userspace image thing at Wikipedia:Village pump (technical)# Questions re server load from images in userspace, you're highly invited to help out with any info if you have the time and inclination, thanks. Herostratus 22:56, 20 January 2006 (UTC)
Yellow Pig
[edit]My dearest sir, I noticed your name on the Yellow Pig page when we were showing an article sj created and couldn't help demonstrating to an audience how to edit someone's talk page. 01:12, 14 February 2006 (UTC) jkb
Commons Policy proposal:No deletion of improved versions of images
[edit]Hi Jamesday. Regarding your recent comments on the commons:COM:VP, you may be interested in commons:Commons:Village pump/Policy proposal:No deletion of improved versions of images. ([commons:User:pfctdayelise]]) pfctdayelise (translate?) 01:09, 21 February 2006 (UTC)
Template:CopyrightedFreeUse
[edit](This is a copy of my response at Template talk:CopyrightedFreeUse.) The problem is that the wording of this template allows interpretations that are clearly incompatible with Wikipedia policy (and the GFDL), such as [7]. The alternative template is indeed not equivalent: {{CopyrightedFreeUse}}-tagged images which cannot be converted to it are generally unfree, and need to be sent to WP:PUI. —Ilmari Karonen (talk) 11:43, 22 February 2006 (UTC)
Sept11 - Thomas McGuinness
[edit]Hi Jamesday I notice that you are one of the Administrators on Sept11.wikipedia.org and I was looking at the http://sep11.wikipedia.org/wiki/Thomas_McGuinness and also had a look through the history section and i was wondering can you delete the history section of it as some of the previous entries have got some comments in them from Chief100 that are not true
Thanks in advance Bob Bob ret 20:48, 22 February 2006 (UTC)
September 11 Wiki
[edit]James, I've applied for Admin status on Sept 11 as there are a lot of things that need fixing. Regards. Rich Farmbrough 01:23 9 March 2006 (UTC).
- Thanks. I've tracked down Archer on Simple, but Maximus Rex and "Dick Cheyney" both seem to be missing wikipedians. I'm reluctant to bother Jimbo as the other admin. The only users active in the last 30 days aprat from you me and Archer are new users and anons. Regards: Rich Farmbrough 00:53 10 March 2006 (UTC).
- Thanks, I needed a bit of good news, with a lot of warring going on today. Rich Farmbrough 22:14 26 March 2006 (UTC).
Sep11 Wiki
[edit]I have read through discussions at [8], [9], [10], and [11], done some editing on sep11:In Memoriam today, and thinking about what should be done with the wiki. MemoryWiki is interesting, but did they take http://sep11.wikipedia.org/wiki/Tributes_to_individuals? I know that most of these entries are stubs. And, if there are only 323 articles, then the list is obviously far from complete. In my view, the role of this wiki is to provide a place for people to writing articles about the victims (articles that don't necessarily belong on Wikipedia, itself) and pay tribute to them. I don't think that's so much a problem on Wikipedia anymore, but I don't think the project should be just deleted without moving or archiving it somewhere. I'm not sure if MemoryWiki is willing to take the http://sep11.wikipedia.org/wiki/Tributes_to_individuals? If not, I would be willing to take the database, set it up on a new domain outside of Wikipedia and host it, leaving it open to contributions. If vandalism or conspiracy advocates (currently an issue with Wikipedia articles) prove to be a real problem that I can't deal with(hope not), then access could be restricted in some way or just leave it up as an archive. -Aude (talk | contribs) 21:34, 30 March 2006 (UTC)
password and bad email (again)
[edit]Ah, how embarrassing. I've forgotten my wikipedia password. Unfortunately, the "e-mail new password" thingy doesn't seem to work. (I don't remember if I ever entered my email address in ... or perhaps I did but mis-typed it). I suppose I could just make up a new user account ... but that seems so wasteful.
Angela helpfully suggested "someone with at least shell access from the list of developers". I got your name from that list of developers.
Although I am supposedly on a dynamic IP, it doesn't appear to have changed for months. Is http://david.carybros.com/ enough evidence that I really am David Cary, and the appropriate email address to use?
p.s.: I was using the same password for Wikibooks:User:DavidCary. Would you reset that one as well?
-- User:DavidCary --70.189.75.148 05:18, 5 April 2006 (UTC)
9/11 Wiki
[edit]Please block Destroy Litecoveria, I just spent about an hour reverting his 100+ vandalism edits. Thanks. Timrem 22:19, 12 May 2006 (UTC)
Merge
[edit]Hallo. i want to merge my two useraccounts. who can i ask, or wath can i do? andDe:Benutzer:Robinhut --58.84.79.95 01:46, 4 June 2006 (UTC)
Further Help Changing a Username
[edit]I've had an ongoing issue with changing my username here on Wikipedia and was recently pointed to contact a developer. All of the information about the case can be found here [[12]] and here [[13]] but allow me to quickly summarize. I registered the account user:Mvelinder awhile ago but I failed to associate an email address with the account, taking away the possibility of me being able to retrieve it. I'm hoping a developer can finally resolve this issue for me and allow me to remain consistent with usernames across the internet by reverting back to my old account of user:Mvelinder. So in the end, I'm asking for the username of user:Mvelinder2 to be changed to user:Mvelinder. Thanks for the help. Mvelinder2 20:28, 19 June 2006 (UTC)
I was able to contact an admin who resolved the issue for me. Thanks to everyone who helped. Issue resolved, feel free to archive this. Mvelinder 15:33, 22 June 2006 (UTC)
Fair use case ruling
[edit]Interesting find! I posted the link to the en list for discussion there too, I hope you don't mind. There are many aspects of it which seem directly relevant to how Wikipedia should do things. --Fastfission 02:05, 22 June 2006 (UTC)
Thanks! I got busy at work and had to abandon things for a while. :) Jamesday 02:37, 22 June 2006 (UTC)
- Hi. First, my thanks for your considered points in the Corfu article. I would like to see the decision you mentioned in the discussion if you don't mind as well as any other points or suggestions you may have. Thanks again. Dr.K. 16:32, 22 June 2006 (UTC)
- Hi again. Maybe you would be interested in this Image:Achilleasthniskon.jpg. Thanks again. Dr.K. 15:10, 23 June 2006 (UTC)
- Sorry about this again but FYI there is a discussion at: Image:Corfustspyridonchurch.jpg that just started recently. Dr.K. 22:19, 27 June 2006 (UTC)
Change to amendment
[edit]Hi James, I've made some changes to the amendment that I'm proposing for fair use criteria. I haven't changed the time period, but have taken on board your other suggestions. - Ta bu shi da yu 07:55, 23 June 2006 (UTC)
Wikimania
[edit]Just a reminder that the early Wikimania registration ends on Sunday, July 9. After that, prices should increase. We'd love to see you, of course!
(It was worth a try ...)
Jkbaumga 20:58, 8 July 2006 (UTC)
coor
[edit]Egil Kvaleberg's brilliant 53°21′59″N 0°00′36″W / 53.36640°N 0.01010°W was introduced as a "proof of concept" 17 months ago. As it happens it is not working at the moment but Egil told me in an e-mail:
- I am looking at the problem. The ISP where this is hosted has changed equipment. Cannot promise a fix today. Of course, the help from anyone to make Wikipedia host the mapsource service on their own servers (where it belongs IMHO), is appreciated.
I think we can say that the concept is now proven and that the script should be moved "as is" on to the Wikimedia servers. How do we go about doing this?
I know that my redirector, eg. SK444332 is getting about 4000 hits a day so Egil's script may well be getting 40,000 hits a day and he deserves having the load taken off his servers. -- RHaworth 22:29, 18 July 2006 (UTC)
- Since the ISP recently switched their servers and software (which is the cause of the current problems) I do not have reliable statistics for anything but the last 2.5 days. They say:
Successful requests: 514,432 Average successful requests per day: 189,700 Successful requests for pages: 18,386 Average successful requests for pages per day: 6,779 Failed requests: 85,549 Redirected requests: 220 Distinct files requested: 18,523 Distinct hosts served: 25,716 Data transferred: 3.02 gigabytes Average data transferred per day: 1.11 gigabytes
The requests over the last 2.5 days are from the following Wikis:
39471 http://wiki.riteme.site/ 11441 http://de.wikipedia.org/ 5525 http://pl.wikipedia.org/ 1800 http://www.answers.com/ 1408 http://pt.wikipedia.org/ 1065 http://es.wikipedia.org/ 877 http://ja.wikipedia.org/ 692 http://it.wikipedia.org/ 571 http://fr.wikipedia.org/ 448 http://hu.wikipedia.org/ 264 http://nl.wikipedia.org/ 219 http://encyclopedia.thefreedictionary.com/ 143 http://ru.wikipedia.org/ 138 http://sv.wikipedia.org/ 121 http://cs.wikipedia.org/ 103 http://enciclopedia.tiosam.com/ 96 http://da.wikipedia.org/ 65 http://tr.wikipedia.org/ 59 http://www.infoslurp.com/ 53 http://ca.wikipedia.org/ 49 http://no.wikipedia.org/ 48 http://he.wikipedia.org/ 47 http://th.wikipedia.org/
- (I have removed some non-wiki addresses in the above)
- The current, really pressing issue is that the Wiki database was lost in the transfer. I have a pending request with the ISP to get it.
- Of course, being allowed to run on Wiki servers would also make it possible to enable a number of other services which I think would be very useful for an encyclopedia. It would also improve on the current, hacked markup. Details at http://meta.wikimedia.org/wiki/Gis
Oc logo
[edit]Hi! The name of occitan project has changed! I need help to change the word "Oiquipedià" into "Wikipèdia" in Wikivar... Can you help us?
Cedric31 17:48, 17 August 2006 (UTC)
WikiProject Award
[edit]A new barnstar for your WikiProject Computing has been proposed. Do you support it? -- Michaelas10 21:08, 18 August 2006 (UTC)
Email/Wikimedia Conference Netherlands
[edit]Wanted to Email you about Wikimedia Converence Netherlands, but your email is not working. In any case, you could crash at our place? Kim Bruning 20:12, 31 August 2006 (UTC)
- Should be working - was a few months back when I checked email from here. I'll send myself some from wiki to verify again... thanks formentioning it! Jamesday 15:19, 5 September 2006 (UTC)
- Oooh! That sounds like a lot of fun to me! Party at Kim's! Er, uh, hello there, Jamesday. Am borrowing some online access very quickly. Wanted to say hello! Catch you in a few days. Jkbaum 09:14, 5 September 2006 (UTC)
- Would have been if I hadn't found out too late to both shift my sleep schedule travel there. Maybe next time... :) Jamesday 15:19, 5 September 2006 (UTC)
Sep11 wiki - adminship?
[edit]Hey, looks like your email is still not working. Anyway, I was just over at http://sep11.wikipedia.org , which appears largely unmaintained. That's understandable given constant threat to close it, which I'm maybe agreeing with more now. Anyway, until if/when that happens, I'd like to be made sysop (I'm a sysop here) there so I can handle whatever maintenance issues needed. For one, the sitenotice hasn't been updated for a long time, as it's still announcing early registration for Wikimania. As a sysop, that's the kind of thing I could take care of. --Aude (talk contribs as tagcloud) 20:02, 7 September 2006 (UTC)
- PS - I used to be Kmf164 there (and here), but had my name changed on enwiki. --Aude (talk contribs as tagcloud) 20:04, 7 September 2006 (UTC)
- Fixed it now. I hope. :) Jamesday
Can you help?
[edit]List of articles without interwiki links in "el:", Greek wikipedia
Hi, I need some help for our wiki-project in the Greek Wikipedia (Βικιπαίδεια), to put interlanguage links in as many articles as possible called el:Βικιπαίδεια:Επιχείρηση Interwiki (Wikiproject Interwiki). I have found a page on pages without interwikis, here, however, it is not automatically updated. In fact that page is about 9 months old. The person who made it, said he used SQL, but when he tried this time he got stuck. Could you please run a query for articles which do not have interwikis and save the result here? It would be a great help for our wikiproject.
Many thanks in advance. (P.S. I saw your name in Meta, Requests for queries (section) and I thought that you might know how to do it.)
--FocalPoint 14:55, 26 September 2006 (UTC)
Angela Beesley
[edit]nominated for deletion. --Coroebus 16:14, 7 October 2006 (UTC)
Assistance with images.
[edit]Can you possibly get these images back? I am sorry about it, me getting these is crucial, I need them. They are:
File:Moreblah1.gif, File:Moreblah2.gif, File:Moreblah3.gif, File:Blah1.gif, File:Blah2.gif, File:Blah3.gif, File:Moreblahblah2.gif, File:Blah4.gif, File:Blah5.gif, File:Blah6.gif, File:Blah7.gif, File:Blah8.gif, File:Blah9.gif, File:Blah10.gif, Image:Blah11.gif, File:Blah12.gif, File:Lastblah.gif, and File:Blah7.gif. --RedPooka 04:22, 24 November 2006 (UTC)
Whatever happened to Jamesday?
[edit]- He used to be here, but now he isn't. - O^O
- Or rather he's here much, much less than he was. He ran out of money and had to find a paying job and is staying away much of the time lest he be tempted to spend too much here and go back to no way to live... which is frustrating sometimes and may change. I'm still alive and fine and care about this place... :) Best wishes to anyone who reads this. :) Jamesday 05:13, 15 March 2007 (UTC)
- Hi. Let me say that you are missed. Along with Heph, you are the "missing wikipedian" who represents the most significant deficit for the wellbeing of the project so far. People must do what people must do, but this is just as a message that your work was valued; at least by me. -- Cimon Avaro; on a pogostick. 09:52, 28 March 2007 (UTC)
fair use in portals
[edit]there is currently a proposed amendment to include fair use images in the portal space at Wikipedia:Fair use/Amendment/Fair use images in portals2. I have decided to contact you because you expressed interest in this topic in the past. Please know that I am contacting all editors who partipated in discussions regarding this at WT:FUC. If you feel I contactd you in error, or just don't care :) please ignore me. -ΖαππερΝαππερ BabelAlexandria 22:55, 26 March 2007 (UTC)
Help revert my talkpage edit
[edit]I would like you to help me out. I ended up with a warning message on my talk page about vandalism but i don't think i deserved it so i edited it out only later it re-apeard the exact same message . I'm asking you if you could help me out here please if you could . Thanks Richardson j 05:15, 14 April 2007 (UTC)
Utility userboxes and templates .
[edit]I was wandering if you could supply me a list of utility userboxes and templates that might be useful on my user page and if you could post the reply in User talk:Richardson j/Reply Request Richardson j 04:12, 12 May 2007 (UTC)
Login unsuccessful
[edit]Hello, I am the User:Bababoum and have been unable to login since logging out sometime on Saturday. Even though I'm sure I have tried to log in with the correct password (my username), I requested to be e-mailed with a new password, but it said "There is no e-mail address recorded for user "Bababoum". I took this to the admins where it was discussed here, WP:AN#Login unsuccessful, and I was told that you would possibly be able to retrieve my account. They also said that my account may have been disabled due to having the same username/password, although I wasn't aware that this happened. If proof is needed that I am indeed that user, please check my IP address (apparently a 'CheckUser' would be able to prove this). Any help would be greatly appreciated. Thank you. 82.29.19.104 19:41, 16 May 2007 (UTC)
- I don't have CheckUser access so I suggest that you seek someone who does. While a developer can do such things it's generally best to leave it to those who have the access specifically for the purpose. Jamesday 00:49, 17 May 2007 (UTC)
Thanks for the reply. Would you happen to know anyone with access to CheckUser? 82.29.19.104 18:45, 17 May 2007 (UTC)
Hello
[edit]I haven't seen you in a while, partially because I myself am scarce. Just found myself nowhere near your neighborhood & decided to drop by to say "Hello" & "Cheers!" Jkbaum 05:16, 21 May 2007 (UTC)
Page deletion
[edit]I wonder if you can delete User talk:Richardson j/Reply Request for me and please let me know on my talk page once you done thanks Richardson j 00:14, 1 June 2007 (UTC) Actually i didn't relise you were busy so i asked someone else to delete the page instead sorry for any inconvenience Richardson j 14:45, 3 June 2007 (UTC)
User account
[edit]Hello, I am User:Jalen and since the recent introduction of password restrictions I have been unable to login due to having the same username/password. I would like to ask whether you are prepared to restore my account or give some advice as to what I should do to prove I am its owner. Thanks --84.52.134.168 08:27, 10 June 2007 (UTC)
On your user page
[edit]On your user page, it says "All contributions © Copyright 2003, 2004, 2005 Jamesday. All rights reserved.".
I thought all contributions were always GFDL? From what I can see now, below this message, it says: "By submitting content, you agree to release your contributions under the GNU Free Documentation License."
Just out of curiosity, can suers override this with their own contribvutions? I also see it hasn't been updated (it only goes up to 2005) so maybe it changed recently?
Anyway, I just thought I would ponit that out. Thanks! Matt/TheFearow (Talk) (Contribs) (Bot) 22:42, 16 June 2007 (UTC)
Matt, you can only grant a GFDL license if you're the copyright holder or have some other license that allows you to sub-license. You, I and all of us are the copyright holders for this encyclopedia. The GFDL is not the same as a dedication to the public domain, which in the US and some other jurisdictions does eliminate the (automatic) copyrighted status of the work. A copyright notice like the one I use can help with legal action to enforce the copyright against a breacher of the GFDL. The GFDL or GPL licenses also don't prohibit the copyright holder from granting other licenses and you'll see that I grant many additional licenses.
For curiosity value it's also possible to both dedicate a work to the public domain and grant licenses to it, the licenses being effective in jurisdictions where the public domain dedication aren't valid.
The "all rights reserved" text also doesn't conflict wiht the granting of a GFDL or other licenses. It's a particular bit of wording that's required for a valid copyright notice in two countries. Just means all rights not otherwise granted to you by licenses like the GFDL, fair use or other bits of law - that is, the normal status of a copyrighted work.
Registration of a copyrihgt isn't required and the notice doesn't mean that a copyright has been registered. For some years now copyright has been automatic for original creative works from the moment they were fixed (saved) in some tangible (somewhat permanent) form.
Thanks for reminding me that I needed to update the dates in the copyright notice. Thanks for asking instead of just assuming I was wrong. :) Please let me know if you have any further questions about this. Jamesday 22:23, 24 June 2007 (UTC)
Usergroup
[edit]Hey, I am wondering whether you (as a developer) could comment on this bot discussion. The request may require another usergroup, specifically for editing protected pages, which I know is a minor change to LocalSettings.php, however as far as I am aware, it requires a server admin or dev to change.
I am posting this message to many developers talk pages, who are part of the developer group here on enwiki.
Thanks! Matt/TheFearow (Talk) (Contribs) (Bot) 21:23, 26 June 2007 (UTC)
Image:UN-Partition Plan For Palestine 1947.png listed for deletion
[edit]An image or media file that you uploaded or altered, Image:UN-Partition Plan For Palestine 1947.png, has been listed at Wikipedia:Images and media for deletion. Please see the discussion to see why this is (you may have to search for the title of the image to find its entry), if you are interested in it not being deleted. Thank you. Emmanuelm 15:53, 3 October 2007 (UTC) --Emmanuelm 15:53, 3 October 2007 (UTC)
Hello James, you wrote in my comment page today: "I'll see if I still have the version I originally produced from that and then compare it to the current one and give my view on whether it's better to change the links or upload a replacement image." Please do not edit this distorted image. The correct image, uploaded by you, is still available as Image:UN Partition Plan For Palestine 1947.png. All is needed now is to delete the distorted image. I requested its deletion almost a month ago, still waiting. Emmanuelm 18:41, 25 October 2007 (UTC)
Chavacano de Zamboanga Wikipedia
[edit]Hello. Would you please help us. I have several questions and Im getting frustrated coz I cant find help over at meta. I cant get any help from any steward of beureacrat. At metapub, I was asked to find a developer whom I can ask these questions.
I would like to know exactly when was the exact date Meta approved the creation of Chavacano Wikipedia http://cbk-zam.wikipedia.org. I have searched at ther archive meta, but I just really cannot determine what specific date it was approved for its creation.
When Chavacano wikipedia started, I didnt know how to go about the language file. I was just told by an admin of Spanish wikipedia to ask for admin permission and translate this: http://cbk-zam.wikipedia.org/wiki/Special:Allmessages
I already translated most of the messages and my question is, how come cbk-zam or Chavacano is not an option in the language preference of a user in another wikipedia? For example, here in English Wikipedia if you go to your user preferences, Chavacano is not included as an option for the language interface. How do we make it an option?
I would like to know where I can have the wikimedia configure the user preference in our Chavacano wikipedia. Whenever we configure the language in our user profile http://cbk-zam.wikipedia.org/wiki/Special:Preferences cbk-zam is listed as cbk-zam - cbk-zam which is wrong. It should be cbk-zam - Chavacano de Zamboanga. How do I do the correction? I am the sysop of cbk-zam.wikipedia.org And finally, where will I do the necessary translation of the wikipedia donation to Chavacano that appears on every page? Thanks. I would really appreciaye it if you can help us. --Weekeejames (talk) 20:04, 6 December 2007 (UTC)
Help (at meta...)
[edit]Hello James,
I was wondering if you could tell me when the Interwiki map was last "pushed through", and when the next time it is going to happen will be.
If possible, could you update it now? As far as i'm aware, the last time September, and quite a few new links have been added since then. As users of my site have added IW links, but it's not yet "live", there are also some redlinks hanging around!
Thanks in anticipation,
BG7 19:15, 4 February 2008 (UTC)
As an intial creater of the project, I thought you might be interested in this discussion. We welcome your comments -- TinuCherian (Wanna Talk?) - 11:27, 30 June 2008 (UTC)
Intergrated banner for WikiProject Computer networking
[edit]I have made a proposal for a intergrated banner for the project here . I invite you for your valuable comments in the discussion. You are receiving this note since I thought that you might be interested.. Thanks -- Tinu Cherian - 11:24, 1 August 2008 (UTC)
Wikinews has been hacked
[edit][14] has been hacked with a message saying: "This is the Zodiac speaking. Do you think you cowards can run from me? No you cannot, for I am above mortal things. ЕНКЁШКААНЛЁПЕЦЦААЭАН ДАЛЫЧЫНВКЁШКАШЕАНЦА АМЫНЮЛЛЕЯЬЦЦЫМЬЫНЕ НКЫЫЪЕХЦЫЬЕНДЁЪПХЫ НЦЕХЁККААМПЫАКЮЫНКЁ ЛМЕЦЮХАЦЦАЁЪВАШМЕЯ АШЕЁННЫЫНХАЮШКААШ ЫНЮНПЫЦЬЫШЫЙЪЫЦЦ ЬЬЦЕХДЬШЕНПЙШЬККЫЁ НЦЙПЕЪЫЬШЫКЁЯА! " and more not included. Please notify the appropriate person. This is message is going to all system admins. Calebrw (talk) 04:58, 15 August 2008 (UTC)
- Plain old template vandalism, nothing to worry about. -- Tim Starling (talk) 05:28, 15 August 2008 (UTC)
A tag has been placed on VASCO, requesting that it be speedily deleted from Wikipedia. This has been done under section G11 of the criteria for speedy deletion, because the article seems to be blatant advertising which only promotes a company, product, group, service or person and would need to be fundamentally rewritten in order to become an encyclopedia article. Please read the guidelines on spam as well as the Wikipedia:Business' FAQ for more information.
If you think that this notice was placed here in error, you may contest the deletion by adding {{hangon}}
to the top of the page that has been nominated for deletion (just below the existing speedy deletion or "db" tag), coupled with adding a note on the talk page explaining your position, but be aware that once tagged for speedy deletion, if the article meets the criterion it may be deleted without delay. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the article that would would render it more in conformance with Wikipedia's policies and guidelines. Lastly, please note that if the article does get deleted, you can contact one of these admins to request that a copy be emailed to you. Goochelaar (talk) 10:28, 4 September 2008 (UTC)
License for Image:Devonport Dockyard in 1909 plan.png
[edit]The image Devonport Dockyard in 1909 plan.png is a candidate to be copied to the Wikimedia Commons. When you uploaded this image, you licensed it for use under the GNU Free Documentation License (GFDL). On behalf of the Wikipedia and Commons communities, thank you. However, the GFDL requires that reproductions of the image (and any other GFDL-licenced works), must be accompanied by the full text of the GFDL. The GFDL is intended more for documentation and not images, so downstream re-users may be hindered by additional restrictions of the GFDL which may not work well on the use of one image.
Before I copy this image to the Commons, I wanted to ask whether you would be willing to multilicense your work under an additional license, such as a Creative Commons licence. Creative Commons licences, such as the Attribution Share-Alike license provide a similar copyleft permission to the GFDL, but without some of its requirements such as the distribution of the licence text. All you need to do, is place the additional license tag alongside your current license. Users can choose between which one they want to use the image under. There are many free licenses accepted on Wikipedia and Commons which can provide freedoms similar to the GFDL, but without some of its requirements.
You are under no obligation whatsoever to alter the license. Doing so merely cooperates with those members of the community who believe that multilicensing your work can ease the reuse of images outside of Wikipedia.
If you use a GFDL license tag which requires distribution of Wikipedia's general disclaimer (indicated by "Subject to disclamiers" in the template), it is also suggested that you switch it to one which does not apply them.
Whether or not you choose to dual-license your work, thank you for your consideration.
This message was placed using Template:Dual-licence. |
Thanks! --Sfan00 IMG (talk) 12:57, 5 November 2008 (UTC)
Moves to Commons
[edit]In terms of automated moves- you should also contact the authors of the automated move to commons script, because that has simmilar issues. Sfan00 IMG (talk) 21:06, 15 November 2008 (UTC)
GFDL Moves to Commons
[edit]Point taken, I will be removing the move to commons from GFDL images until this is resolved. Unfortunatly knowing enwiki this will probably end up with a refferal to WP:AN Again :( Sfan00 IMG (talk) 17:18, 15 November 2008 (UTC)
Possibly unfree File:George Clinton bronze statue by Henry Kirke Brown.jpg
[edit]A file that you uploaded or altered, File:George Clinton bronze statue by Henry Kirke Brown.jpg, has been listed at Wikipedia:Possibly unfree files because its copyright status is unclear or disputed. If the file's copyright status cannot be verified, it may be deleted. You may find more information on the file description page. You are welcome to add comments to its entry at the discussion if you are interested in it not being deleted. Thank you. --J Milburn (talk) 11:50, 10 July 2009 (UTC)
Unreferenced BLPs
[edit]Hello Jamesday! Thank you for your contributions. I am a bot alerting you that 1 of the articles that you created is tagged as an Unreferenced Biography of a Living Person. The biographies of living persons policy requires that all personal or potentially controversial information be sourced. In addition, to ensure verifiability, all biographies should be based on reliable sources. If you were to bring this article up to standards, it would greatly help us with the current 2 article backlog. Once the article is adequately referenced, please remove the {{unreferencedBLP}} tag. Here is the article:
- Nigel Jaquiss - Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL
Thanks!--DASHBot (talk) 06:31, 15 January 2010 (UTC)
Re: Chernobyl radiation map 1996
[edit]I don't understand what you want me to explain. I created the SVG map in French from the original CIA's JPEG one available on the UTexas' site, as stated in the description page. The SVG version in English was created later by other contributors, as stated, modifying my original SVG map by re-translating the names into that language. The thing which is missing in the later is a direct reference to my original SVG map, link I just added for clarification. Sting-fr (talk) 19:53, 14 April 2011 (UTC)
- I understand now after having seen your msg on the page of Jujutacular. You could have found your answer just googling a little bit. Sting-fr (talk) 14:47, 15 April 2011 (UTC)
MSU Interview
[edit]Dear Jamesday,
My name is Jonathan Obar user:Jaobar, I'm a professor in the College of Communication Arts and Sciences at Michigan State University and a Teaching Fellow with the Wikimedia Foundation's Education Program. This semester I've been running a little experiment at MSU, a class where we teach students about becoming Wikipedia administrators. Not a lot is known about your community, and our students (who are fascinated by wiki-culture by the way!) want to learn how you do what you do, and why you do it. A while back I proposed this idea (the class) to the communityHERE, where it was met mainly with positive feedback. Anyhow, I'd like my students to speak with a few administrators to get a sense of admin experiences, training, motivations, likes, dislikes, etc. We were wondering if you'd be interested in speaking with one of our students.
So a few things about the interviews:
- Interviews will last between 15 and 30 minutes.
- Interviews can be conducted over skype (preferred), IRC or email. (You choose the form of communication based upon your comfort level, time, etc.)
- All interviews will be completely anonymous, meaning that you (real name and/or pseudonym) will never be identified in any of our materials, unless you give the interviewer permission to do so.
- All interviews will be completely voluntary. You are under no obligation to say yes to an interview, and can say no and stop or leave the interview at any time.
- The entire interview process is being overseen by MSU's institutional review board (ethics review). This means that all questions have been approved by the university and all students have been trained how to conduct interviews ethically and properly.
Bottom line is that we really need your help, and would really appreciate the opportunity to speak with you. If interested, please send me an email at obar@msu.edu (to maintain anonymity) and I will add your name to my offline contact list. If you feel comfortable doing so, you can post your nameHERE instead.
If you have questions or concerns at any time, feel free to email me at obar@msu.edu. I will be more than happy to speak with you.
Thanks in advance for your help. We have a lot to learn from you.
Sincerely,
Jonathan Obar --Jaobar (talk) — Preceding unsigned comment added by Chlopeck (talk • contribs) 22:57, 15 February 2012 (UTC)
WP Computing in the Signpost
[edit]The WikiProject Report would like to focus on WikiProject Computing for a Signpost article. This is an excellent opportunity to draw attention to your efforts and attract new members to the project. Would you be willing to participate in an interview? If so, here are the questions for the interview. Just add your response below each question and feel free to skip any questions that you don't feel comfortable answering. Multiple editors will have an opportunity to respond to the interview questions, so be sure to sign your answers. If you know anyone else who would like to participate in the interview, please share this with them. Have a great day. –Mabeenot (talk) 21:23, 15 May 2013 (UTC)
MfD nomination of Wikipedia:Most frequently edited pages
[edit]Wikipedia:Most frequently edited pages, a page you substantially contributed to, has been nominated for deletion. Your opinions on the matter are welcome; please participate in the discussion by adding your comments at Wikipedia:Miscellany for deletion/Wikipedia:Most frequently edited pages and please be sure to sign your comments with four tildes (~~~~). You are free to edit the content of Wikipedia:Most frequently edited pages during the discussion but should not remove the miscellany for deletion template from the top of the page; such a removal will not end the deletion discussion. Thank you. Gaijin42 (talk) 21:50, 25 August 2014 (UTC)
Greetings!
[edit]That is all. Jkbaum (talk) 03:55, 8 November 2014 (UTC)
Yes, but ...
[edit]leaving you a note on your talk page gives you a tiny surprise within Wikipedia the next time you visit your talk page. Jkbaum (talk) 14:35, 17 September 2015 (UTC)
Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 08:52, 23 November 2015 (UTC)
January 2016
[edit]Hello, I'm BracketBot. I have automatically detected that your edit to Individual Savings Account may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.
- List of unpaired brackets remaining on the page:
- ISA limit for that year. [also see the draft guidance notes linked from actual bulletin text])}}</ref>
It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 13:10, 11 January 2016 (UTC)
Thanks on the whole MEDRS/country of origin thing
[edit]Hey I just wanted to thank you for making the effort to come up with a decision of sorts regarding the whole country of origin issue in MEDRS, and implementing that decision. It was a well-worded step-by-step procedural reminder that consensus is how we decide anything, yet ironically, (and sadly) it has been edit warred off by a couple of editors in a small minority who want their way, or no way. That's exactly what was experienced after Elvey's close, where a few editors edit warred the change after the RfC off the page. I haven't been the type to care to go toe to toe with people who want to edit war to have their way into existence, so I just let it go for awhile and tried settling things on the talk pages. Hasn't worked, obviously. I just thought you'd care to know that it's a big problem on that page and neither reason, nor following procedure, nor ignoring it has made it go away. Not sure what I should do next. At any rate, I want to thank you again for attempting to boldly solve this issue in a stance-compromising and policy-based way in a very heated area. LesVegas (talk) 15:54, 31 January 2016 (UTC)
Extended confirmed protection
[edit]Hello, Jamesday. This message is intended to notify administrators of important changes to the protection policy.
Extended confirmed protection (also known as "30/500 protection") is a new level of page protection that only allows edits from accounts at least 30 days old and with 500 edits. The automatically assigned "extended confirmed" user right was created for this purpose. The protection level was created following this community discussion with the primary intention of enforcing various arbitration remedies that prohibited editors under the "30 days/500 edits" threshold to edit certain topic areas.
In July and August 2016, a request for comment established consensus for community use of the new protection level. Administrators are authorized to apply extended confirmed protection to combat any form of disruption (e.g. vandalism, sock puppetry, edit warring, etc.) on any topic, subject to the following conditions:
- Extended confirmed protection may only be used in cases where semi-protection has proven ineffective. It should not be used as a first resort.
- A bot will post a notification at Wikipedia:Administrators' noticeboard of each use. MusikBot currently does this by updating a report, which is transcluded onto the noticeboard.
Please review the protection policy carefully before using this new level of protection on pages. Thank you.
This message was sent to the administrators' mass message list. To opt-out of future messages, please remove yourself from the list. 17:49, 23 September 2016 (UTC)
Two-Factor Authentication now available for admins
[edit]Hello,
Please note that TOTP based two-factor authentication is now available for all administrators. In light of the recent compromised accounts, you are encouraged to add this additional layer of security to your account. It may be enabled on your preferences page in the "User profile" tab under the "Basic information" section. For basic instructions on how to enable two-factor authentication, please see the developing help page for additional information. Important: Be sure to record the two-factor authentication key and the single use keys. If you lose your two factor authentication and do not have the keys, it's possible that your account will not be recoverable. Furthermore, you are encouraged to utilize a unique password and two-factor authentication for the email account associated with your Wikimedia account. This measure will assist in safeguarding your account from malicious password resets. Comments, questions, and concerns may be directed to the thread on the administrators' noticeboard. MediaWiki message delivery (talk) 20:33, 12 November 2016 (UTC)
A new user right for New Page Patrollers
[edit]Hi Jamesday.
A new user group, New Page Reviewer, has been created in a move to greatly improve the standard of new page patrolling. The user right can be granted by any admin at PERM. It is highly recommended that admins look beyond the simple numerical threshold and satisfy themselves that the candidates have the required skills of communication and an advanced knowledge of notability and deletion. Admins are automatically included in this user right.
It is anticipated that this user right will significantly reduce the work load of admins who patrol the performance of the patrollers. However,due to the complexity of the rollout, some rights may have been accorded that may later need to be withdrawn, so some help will still be needed to some extent when discovering wrongly applied deletion tags or inappropriate pages that escape the attention of less experienced reviewers, and above all, hasty and bitey tagging for maintenance. User warnings are available here but very often a friendly custom message works best.
If you have any questions about this user right, don't hesitate to join us at WT:NPR. (Sent to all admins).MediaWiki message delivery (talk) 13:47, 15 November 2016 (UTC)
ArbCom Elections 2016: Voting now open!
[edit]Hello, Jamesday. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. Mdann52 (talk) 22:08, 21 November 2016 (UTC)
ArbCom Elections 2016: Voting now open!
[edit]Hello, Jamesday. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)
Administrators' newsletter - February 2017
[edit]News and updates for administrators from the past month (January 2017). This first issue is being sent out to all administrators, if you wish to keep receiving it please subscribe. Your feedback is welcomed.
- NinjaRobotPirate • Schwede66 • K6ka • Ealdgyth • Ferret • Cyberpower678 • Mz7 • Primefac • Dodger67
- Briangotts • JeremyA • BU Rob13
- A discussion to workshop proposals to amend the administrator inactivity policy at Wikipedia talk:Administrators has been in process since late December 2016.
- Wikipedia:Pending changes/Request for Comment 2016 closed with no consensus for implementing Pending changes level 2 with new criteria for use.
- Following an RfC, an activity requirement is now in place for bots and bot operators.
- When performing some administrative actions the reason field briefly gave suggestions as text was typed. This change has since been reverted so that issues with the implementation can be addressed. (T34950)
- Following the latest RfC concluding that Pending Changes 2 should not be used on the English Wikipedia, an RfC closed with consensus to remove the options for using it from the page protection interface, a change which has now been made. (T156448)
- The Foundation has announced a new community health initiative to combat harassment. This should bring numerous improvements to tools for admins and CheckUsers in 2017.
- The Arbitration Committee released a response to the Wikimedia Foundation's statement on paid editing and outing.
- JohnCD (John Cameron Deas) passed away on 30 December 2016. John began editing Wikipedia seriously during 2007 and became an administrator in November 2009.
13:38, 1 February 2017 (UTC)
Administrators' newsletter – March 2017
[edit]News and updates for administrators from the past month (February 2017).
- Amortias • Deckiller • BU Rob13
- Ronnotel • Islander • Chamal N • Isomorphic • Keeper76 • Lord Voldemort • Shereth • Bdesham • Pjacobi
- A recent RfC has redefined how articles on schools are evaluated at AfD. Specifically, secondary schools are not presumed to be notable simply because they exist.
- AfDs that receive little participation should now be closed like an expired proposed deletion, following a deletion process RfC.
- Defender, HakanIST, Matiia and Sjoerddebruin are our newest stewards, following the 2017 steward elections.
- The 2017 appointees for the Ombudsman commission are Góngora, Krd, Lankiveil, Richwales and Vogone. They will serve for approximately 1 year.
- A recent query shows that only 16% of administrators on the English Wikipedia have enabled two-factor authentication. If you haven't already enabled it please consider doing so.
- Cookie blocks should be deployed to the English Wikipedia soon. This will extend the current autoblock system by setting a cookie for each block, which will then autoblock the user after they switch accounts under a new IP.
- A bot will now automatically place a protection template on protected pages when admins forget to do so.
Administrators' newsletter – April 2017
[edit]News and updates for administrators from the past month (March 2017).
- TheDJ
- Xnuala • CJ • Oldelpaso • Berean Hunter • Jimbo Wales • Andrew c • Karanacs • Modemac • Scott
- Following a discussion on the backlog of unpatrolled files, consensus was found to create a new user right for autopatrolling file uploads. Implementation progress can be tracked on Phabricator.
- The BLPPROD grandfather clause, which stated that unreferenced biographies of living persons were only eligible for proposed deletion if they were created after March 18, 2010, has been removed following an RfC.
- An RfC has closed with consensus to allow proposed deletion of files. The implementation process is ongoing.
- After an unsuccessful proposal to automatically grant IP block exemption, consensus was found to relax the criteria for granting the user right from needing it to wanting it.
- After a recent RfC, moved pages will soon be featured in a queue similar to Special:NewPagesFeed and require patrolling. Moves by administrators, page movers, and autopatrolled editors will be automatically marked as patrolled.
- Cookie blocks have been deployed. This extends the current autoblock system by setting a cookie for each block, which will then autoblock the user if they switch accounts, even under a new IP.
Administrators' newsletter – May 2017
[edit]News and updates for administrators from the past month (April 2017).
- Karanacs • Berean Hunter • GoldenRing • Dlohcierekim
- Gdr • Tyrenius • JYolkowski • Longhair • Master Thief Garrett • Aaron Brenneman • Laser brain • JzG • Dragons flight
- An RfC has clarified that user categories should be emptied upon deletion, but redlinked user categories should not be removed if re-added by the user.
- Discussions are ongoing regarding proposed changes to the COI policy. Changes so far have included clarification that adding a link on a Wikipedia forum to a job posting is not a violation of the harassment policy.
- You can now see a list of all autoblocks at Special:AutoblockList.
- There is a new tool for adding archives to dead links. Administrators are able to restrict other user's ability to use the tool, and have additional permissions when changing URL and domain data.
- Administrators, bureaucrats and stewards can now set an expiry date when granting user rights. (discuss, permalink)
- Following an RfC, the editing restrictions page is now split into a list of active restrictions and an archive of those that are old or on inactive accounts. Make sure to check both pages if searching for a restriction.
Administrators' newsletter – June 2017
[edit]News and updates for administrators from the past month (May 2017).
- Doug Bell • Dennis Brown • Clpo13 • ONUnicorn
- ThaddeusB • Yandman • Bjarki S • OldakQuill • Shyam • Jondel • Worm That Turned
- An RfC proposing an off-wiki LTA database has been closed. The proposal was broadly supported, with further discussion required regarding what to do with the existing LTA database and defining access requirements. Such a tool/database formed part of the Community health initiative's successful grant proposal.
- Some clarifications have been made to the community banning and unblocking policies that effectively sync them with current practice. Specifically, the community has reached a consensus that when blocking a user at WP:AN or WP:ANI, it is considered a "community sanction", and administrators cannot unblock unilaterally if the user has not successfully appealed the sanction to the community.
- An RfC regarding the bot policy has closed with changes to the section describing restrictions on cosmetic changes.
- Users will soon be able to blacklist specific users from sending them notifications.
- Following the 2017 elections, the new members of the Board of Trustees include Raystorm, Pundit and Doc James. They will serve three-year terms.
Administrators' newsletter – July 2017
[edit]News and updates for administrators from the past month (June 2017).
- The RFC discussion regarding WP:OUTING and WMF essay about paid editing and outing (see more at the ArbCom noticeboard archives) is now archived. Milieus #3 and #4 received support; so did concrete proposal #1.
- Fuzzy search will soon be added to Special:Undelete, allowing administrators to search for deleted page titles with results similar to the search query. You can test this by adding
?fuzzy=1
to the URL, as with Special:Undelete?fuzzy=1. Currently the search only finds pages that exactly match the search term. - A new bot will automatically revision delete unused file versions from files in Category:Non-free files with orphaned versions more than 7 days old.
- Fuzzy search will soon be added to Special:Undelete, allowing administrators to search for deleted page titles with results similar to the search query. You can test this by adding
- A newly revamped database report can help identify users who may be eligible to be autopatrolled.
- A potentially compromised account from 2001–2002 attempted to request resysop. Please practice appropriate account security by using a unique password for Wikipedia, and consider enabling two-factor authentication. Currently around 17% of admins have enabled 2FA, up from 16% in February 2017.
- Did you know: On 29 June 2017, there were 1,261 administrators on the English Wikipedia – the exact number of administrators as there were ten years ago on 29 June 2007. Since that time, the English Wikipedia has grown from 1.85 million articles to over 5.43 million.
Administrators' newsletter – August 2017
[edit]News and updates for administrators from the past month (July 2017).
- Anarchyte • GeneralizationsAreBad • Cullen328 (first RfA to reach WP:300)
- Cprompt • Rockpocket • Rambo's Revenge • Animum • TexasAndroid • Chuck SMITH • MikeLynch • Crazytales • Ad Orientem
- Following a series of discussions around new pages patrol, the WMF is helping implement a controlled autoconfirmed article creation trial as a research experiment, similar to the one proposed in 2011. You can learn more about the research plan at meta:Research:Autoconfirmed article creation trial. The exact start date of the experiment has yet to be determined.
- A new speedy deletion criterion, regarding articles created as a result undisclosed paid editing, is currently being discussed (permalink).
- An RfC (permalink) is currently open that proposes expanding WP:G13 to include all drafts, even if they weren't submitted through Articles for Creation.
- LoginNotify should soon be deployed to the English Wikipedia. This will notify users when there are suspicious login attempts on their account.
- The new version of XTools is nearing an official release. This suite of tools includes administrator statistics, an improved edit counter, among other tools that may benefit administrators. You can report issues on Phabricator and provide general feedback at mw:Talk:XTools.
Administrators' newsletter – September 2017
[edit]News and updates for administrators from the past month (August 2017).
- Nakon • Scott
- Sverdrup • Thespian • Elockid • James086 • Ffirehorse • Celestianpower • Boing! said Zebedee
- ACTRIAL, a research experiment that restricts article creation to autoconfirmed users, will begin on September 7. It will run for six months. You can learn more about the research specifics at meta:Research:Autoconfirmed article creation trial, while Wikipedia talk:Autoconfirmed article creation trial is probably the best venue for general discussion.
- Following an RfC, WP:G13 speedy deletion criterion now applies to any page in the draftspace that has not been edited in six months. There is a bot-generated report, updated daily, to help identify potentially qualifying drafts that have not been submitted through articles for creation.
- You will now get a notification when someone tries to log in to your account and fails. If they try from a device that has logged into your account before, you will be notified after five failed attempts. You can also set in your preferences to get an email when someone logs in to your account from a new device or IP address, which may be encouraged for admins and accounts with sensitive permissions.
- Syntax highlighting is now available as a beta feature (more info). This may assist administrators and template editors when dealing with intricate syntax of high-risk templates and system messages.
- In your notification preferences, you can now block specific users from pinging you. This functionality will soon be available for Special:EmailUser as well.
- Applications for CheckUser and Oversight are being accepted by the Arbitration Committee until September 12. Community discussion of the candidates will begin on September 18.
Administrators' newsletter – October 2017
[edit]News and updates for administrators from the past month (September 2017).
- Boing! said Zebedee • Ansh666 • Ad Orientem
- Tonywalton • AmiDaniel • Silence • BanyanTree • Magioladitis • Vanamonde93 • Mr.Z-man • Jdavidb • Jakec • Ram-Man • Yelyos • Kurt Shaped Box
- Following a successful proposal to create it, a new user right called "edit filter helper" is now assignable and revocable by administrators. The right allows non-administrators to view the details of private edit filters, but not to edit them.
- Following a discussion about mass-application of ECP and how the need for logging and other details of an evolving consensus may have been missed by some administrators, a rough guide to extended confirmed protection has been written. This information page describes how the extended-confirmed aspects of the protection policy are currently being applied by administrators.
- You can now search for IP ranges at Special:Contributions. Some log pages and Special:DeletedContributions are not yet supported. Wildcards (e.g. 192.168.0.*) are also not supported, but the popular contribsrange gadget will continue to work.
- Community consultation on the 2017 candidates for CheckUser and Oversight has concluded. The Arbitration Committee will appoint successful candidates by October 11.
- A request for comment is open regarding the structure, rules, and procedures of the December 2017 Arbitration Committee election, and how to resolve any issues not covered by existing rules.
Administrators' newsletter – November 2017
[edit]News and updates for administrators from the past month (October 2017).
- Longhair • Megalibrarygirl • TonyBallioni • Vanamonde93
- Allen3 • Eluchil404 • Arthur Rubin • Bencherlite
- The Wikimedia Foundation's Anti-Harassment Tools team is creating an "Interaction Timeline" tool that intends to assist administrators in resolving user conduct disputes. Feedback on the concept may be posted on the talk page.
- A new function is now available to edit filter managers that will make it easier to look for multiple strings containing spoofed text.
- Eligible editors will be invited to submit candidate statements for the 2017 Arbitration Committee Elections starting on November 12 until November 21. Voting will begin on November 27 and last until December 10.
- Following a request for comment, Ritchie333, Yunshui and Ymblanter will serve as the Electoral Commission for the 2017 ArbCom Elections.
- The Wikipedia community has recently learned that Allen3 (William Allen Peckham) passed away on December 30, 2016, the same day as JohnCD. Allen began editing in 2005 and became an administrator that same year.
Administrators' newsletter – December 2017
[edit]News and updates for administrators from the past month (November 2017).
- Following a request for comment, a new section has been added to the username policy which disallows usernames containing emoji, emoticons or otherwise "decorative" usernames, and usernames that use any non-language symbols. Administrators should discuss issues related to these types of usernames before blocking.
- Wikimedians are now invited to vote on the proposals in the 2017 Community Wishlist Survey on Meta Wiki until 10 December 2017. In particular, there is a section of the survey regarding new tools for administrators and for anti-harassment.
- A new function is available to edit filter managers which can be used to store matches from regular expressions.
- Voting in the 2017 Arbitration Committee elections is open until Sunday 23:59, 10 December 2017 (UTC). There are 12 candidates running for 8 vacant seats.
- Over the last few months, several users have reported backlogs that require administrator attention at WP:ANI, with the most common backlogs showing up on WP:SPI, WP:AIV and WP:RFPP. It is requested that all administrators take some time during this month to help clear backlogs wherever possible. It should be noted that AIV reports are not always valid; however, they still need to be cleared, which may include needing to remind users on what qualifies as vandalism.
- The Wikimedia Foundation Community health initiative is conducting a survey for English Wikipedia contributors on their experience and satisfaction level with Administrator’s Noticeboard/Incidents. This survey will be integral to gathering information about how this noticeboard works (i.e. which problems it deals with well and which problems it struggles with). If you would like to take this survey, please sign up on this page, and a link for the survey will be emailed to you via Special:EmailUser.
ArbCom 2017 election voter message
[edit]Hello, Jamesday. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)
Administrators' newsletter – January 2018
[edit]News and updates for administrators from the past month (December 2017).
- Muboshgu
- Anetode • Laser brain • Worm That Turned
- None
- A request for comment is in progress to determine whether the administrator policy should be amended to require disclosure of paid editing activity at WP:RFA and to prohibit the use of administrative tools as part of paid editing activity, with certain exceptions.
- The 2017 Community Wishlist Survey results have been posted. The Community Tech team will investigate and address the top ten results.
- The Anti-Harassment Tools team is inviting comments on new blocking tools and improvements to existing blocking tools for development in early 2018. Feedback can be left on the discussion page or by email.
- Following the results of the 2017 election, the following editors have been (re)appointed to the Arbitration Committee: Alex Shih, BU Rob13, Callanecc, KrakatoaKatie, Opabinia regalis, Premeditated Chaos, RickinBaltimore, Worm That Turned.
Administrators' newsletter – February 2018
[edit]News and updates for administrators from the past month (January 2018).
- None
- Blurpeace • Dana boomer • Deltabeignet • Denelson83 • Grandiose • Salvidrim! • Ymblanter
- An RfC has closed with a consensus that candidates at WP:RFA must disclose whether they have ever edited for pay and that administrators may never use administrative tools as part of any paid editing activity, except when they are acting as a Wikipedian-in-Residence or when the payment is made by the Wikimedia Foundation or an affiliate of the WMF.
- Editors responding to threats of harm can now contact the Wikimedia Foundation's emergency address by using Special:EmailUser/Emergency. If you don't have email enabled on Wikipedia, directly contacting the emergency address using your own email client remains an option.
- A tag will now be automatically applied to edits that blank a page, turn a page into a redirect, remove/replace almost all content in a page, undo an edit, or rollback an edit. These edits were previously denoted solely by automatic edit summaries.
- The Arbitration Committee has enacted a change to the discretionary sanctions procedure which requires administrators to add a standardized editnotice when placing page restrictions. Editors cannot be sanctioned for violations of page restrictions if this editnotice was not in place at the time of the violation.
Administrators' newsletter – March 2018
[edit]News and updates for administrators from the past month (February 2018).
- Lourdes†
- AngelOfSadness • Bhadani • Chris 73 • Coren • Friday • Midom • Mike V
- † Lourdes has requested that her admin rights be temporarily removed, pending her return from travel.
- The autoconfirmed article creation trial (ACTRIAL) is scheduled to end on 14 March 2018. The results of the research collected can be read on Meta Wiki.
- Community ban discussions must now stay open for at least 24 hours prior to being closed.
- A change to the administrator inactivity policy has been proposed. Under the proposal, if an administrator has not used their admin tools for a period of five years and is subsequently desysopped for inactivity, the administrator would have to file a new RfA in order to regain the tools.
- A change to the banning policy has been proposed which would specify conditions under which a repeat sockmaster may be considered de facto banned, reducing the need to start a community ban discussion for these users.
- CheckUsers are now able to view private data such as IP addresses from the edit filter log, e.g. when the filter prevents a user from creating an account. Previously, this information was unavailable to CheckUsers because access to it could not be logged.
- The edit filter has a new feature
contains_all
that edit filter managers may use to check if one or more strings are all contained in another given string.
- Following the 2018 Steward elections, the following users are our new stewards: -revi, Green Giant, Rxy, There'sNoTime, علاء.
- Bhadani (Gangadhar Bhadani) passed away on 8 February 2018. Bhadani joined Wikipedia in March 2005 and became an administrator in September 2005. While he was active, Bhadani was regarded as one of the most prolific Wikipedians from India.
Happy Spring!
[edit]I hope ... Yeah, I don't usually come around here often, either, but it's worth dropping you a line when I do. Jkbaum (talk) 23:25, 15 March 2018 (UTC)
Administrators' newsletter – April 2018
[edit]News and updates for administrators from the past month (March 2018).
- 331dot • Cordless Larry • ClueBot NG
- Gogo Dodo • Pb30 • Sebastiankessel • Seicer • SoLando
- Administrators who have been desysopped due to inactivity are now required to have performed at least one (logged) administrative action in the past 5 years in order to qualify for a resysop without going through a new RfA.
- Editors who have been found to have engaged in sockpuppetry on at least two occasions after an initial indefinite block, for whatever reason, are now automatically considered banned by the community without the need to start a ban discussion.
- The notability guideline for organizations and companies has been substantially rewritten following the closure of this request for comment. Among the changes, the guideline more clearly defines the sourcing requirements needed for organizations and companies to be considered notable.
- The six-month autoconfirmed article creation trial (ACTRIAL) ended on 14 March 2018. The post-trial research report has been published. A request for comment is now underway to determine whether the restrictions from ACTRIAL should be implemented permanently.
- There will soon be a calendar widget at Special:Block, making it easier to set expiries for a specific date and time.
- The Arbitration Committee is considering a change to the discretionary sanctions procedures which would require an editor to appeal a sanction to the community at WP:AE or WP:AN prior to appealing directly to the Arbitration Committee at WP:ARCA.
- A discussion has closed which concluded that administrators are not required to enable email, though many editors suggested doing so as a matter of best practice.
- The Foundations' Anti-Harassment Tools team has released the Interaction Timeline. This shows a chronologic history for two users on pages where they have both made edits, which may be helpful in identifying sockpuppetry and investigating editing disputes.
Select Survey Invite
[edit]I'm working on a study of political motivations and how they affect editing. I'd like to ask you to take a survey. The survey should take no more than 1-2 minutes. Your survey responses will be kept private. Our project is documented at https://meta.wikimedia.org/wiki/Research:Wikipedia_%2B_Politics.
Your survey Link: https://uchicago.co1.qualtrics.com/jfe/form/SV_9S3JByWf57fXEkR?Q_DL=56np5HpEZWkMlr7_9S3JByWf57fXEkR_MLRP_exuJG6G9X5V1aOV&Q_CHL=gl
I am asking you to participate in this study because you are a frequent editor of pages on Wikipedia that are of political interest. We would like to learn about your experiences in dealing with editors of different political orientations.
Sincere thanks for your help! Porteclefs (talk) 16:47, 19 April 2018 (UTC)
Administrators' newsletter – May 2018
[edit]News and updates for administrators from the past month (April 2018).
- None
- Chochopk • Coffee • Gryffindor • Jimp • Knowledge Seeker • Lankiveil • Peridon • Rjd0060
- The ability to create articles directly in mainspace is now indefinitely restricted to autoconfirmed users.
- A proposal is being discussed which would create a new "event coordinator" right that would allow users to temporarily add the "confirmed" flag to new user accounts and to create many new user accounts without being hindered by a rate limit.
- AbuseFilter has received numerous improvements, including an OOUI overhaul, syntax highlighting, ability to search existing filters, and a few new functions. In particular, the search feature can be used to ensure there aren't existing filters for what you need, and the new
equals_to_any
function can be used when checking multiple namespaces. One major upcoming change is the ability to see which filters are the slowest. This information is currently only available to those with access to Logstash. - When blocking anonymous users, a cookie will be applied that reloads the block if the user changes their IP. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. This currently only occurs when hard-blocking accounts.
- The block notice shown on mobile will soon be more informative and point users to a help page on how to request an unblock, just as it currently does on desktop.
- There will soon be a calendar widget at Special:Block, making it easier to set expiries for a specific date and time.
- AbuseFilter has received numerous improvements, including an OOUI overhaul, syntax highlighting, ability to search existing filters, and a few new functions. In particular, the search feature can be used to ensure there aren't existing filters for what you need, and the new
- The Arbitration Committee is seeking additional clerks to help with the arbitration process.
- Lankiveil (Craig Franklin) passed away in mid-April. Lankiveil joined Wikipedia on 12 August 2004 and became an administrator on 31 August 2008. During his time with the Wikimedia community, Lankiveil served as an oversighter for the English Wikipedia and as president of Wikimedia Australia.
Administrators' newsletter – June 2018
[edit]News and updates for administrators from the past month (May 2018).
- None
- Al Ameer son • AliveFreeHappy • Cenarium • Lupo • MichaelBillington
- Following a successful request for comment, administrators are now able to add and remove editors to the "event coordinator" group. Users in the event coordinator group have the ability to temporarily add the "confirmed" flag to new user accounts and to create many new user accounts without being hindered by a rate limit. Users will no longer need to be in the "account creator" group if they are in the event coordinator group.
- Following an AN discussion, all pages with content related to blockchain and cryptocurrencies, broadly construed, are now under indefinite general sanctions.
- IP-based cookie blocks should be deployed to English Wikipedia in June. This will cause the block of a logged-out user to be reloaded if they change IPs. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. For the time being, it only affects users of the desktop interface.
- The Wikimedia Foundation's Anti-Harassment Tools team will build granular types of blocks in 2018 (e.g. a block from uploading or editing specific pages, categories, or namespaces, as opposed to a full-site block). Feedback on the concept may be left at the talk page.
- There is now a checkbox on Special:ListUsers to let you see only users in temporary user groups.
- It is now easier for blocked mobile users to see why they were blocked.
- A recent technical issue with the Arbitration Committee's spam filter inadvertently caused all messages sent to the committee through Wikipedia (i.e. Special:EmailUser/Arbitration Committee) to be discarded. If you attempted to send an email to the Arbitration Committee via Wikipedia between May 16 and May 31, your message was not received and you are encouraged to resend it. Messages sent outside of these dates or directly to the Arbitration Committee email address were not affected by this issue.
- In early May, an unusually high level of failed login attempts was observed. The WMF has stated that this was an "external effort to gain unauthorized access to random accounts". Under Wikipedia policy, administrators are required to have strong passwords. To further reinforce security, administrators should also consider enabling two-factor authentication. A committed identity can be used to verify that you are the true account owner in the event that your account is compromised and/or you are unable to log in.
Administrators' newsletter – July 2018
[edit]News and updates for administrators from the past month (June 2018).
- Pbsouthwood • TheSandDoctor
- Gogo Dodo
- Andrevan • Doug • EVula • KaisaL • Tony Fox • WilyD
- An RfC about the deletion of drafts closed with a consensus to change the wording of WP:NMFD. Specifically, a draft that has been repeatedly resubmitted and declined at AfC without any substantial improvement may be deleted at MfD if consensus determines that it is unlikely to ever meet the requirements for mainspace and it otherwise meets one of the reasons for deletion outlined in the deletion policy.
- A request for comment closed with a consensus that the {{promising draft}} template cannot be used to indefinitely prevent a WP:G13 speedy deletion nomination.
- Starting on July 9, the WMF Security team, Trust & Safety, and the broader technical community will be seeking input on an upcoming change that will restrict editing of site-wide JavaScript and CSS to a new technical administrators user group. Bureaucrats and stewards will be able to grant this right per a community-defined process. The intention is to reduce the number of accounts who can edit frontend code to those who actually need to, which in turn lessens the risk of malicious code being added that compromises the security and privacy of everyone who accesses Wikipedia. For more information, please review the FAQ.
- Syntax highlighting has been graduated from a Beta feature on the English Wikipedia. To enable this feature, click the highlighter icon () in your editing toolbar (or under the hamburger menu in the 2017 wikitext editor). This feature can help prevent you from making mistakes when editing complex templates.
- IP-based cookie blocks should be deployed to English Wikipedia in July (previously scheduled for June). This will cause the block of a logged-out user to be reloaded if they change IPs. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. For the time being, it only affects users of the desktop interface.
- Currently around 20% of admins have enabled two-factor authentication, up from 17% a year ago. If you haven't already enabled it, please consider doing so. Regardless if you use 2FA, please practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
Administrators' newsletter – August 2018
[edit]News and updates for administrators from the past month (July 2018).
- After a discussion at Meta, a new user group called "interface administrators" (formerly "technical administrator") has been created. Come the end of August, interface admins will be the only users able to edit site-wide JavaScript and CSS pages like MediaWiki:Common.js and MediaWiki:Common.css, or edit other user's personal JavaScript and CSS. The intention is to improve security and privacy by reducing the number of accounts which could be used to compromise the site or another user's account through malicious code. The new user group can be assigned and revoked by bureaucrats. Discussion is ongoing to establish details for implementing the group on the English Wikipedia.
- Following a request for comment, the WP:SISTER style guideline now states that in the mainspace, interwiki links to Wikinews should only be made as per the external links guideline. This generally means that within the body of an article, you should not link to Wikinews about a particular event that is only a part of the larger topic. Wikinews links in "external links" sections can be used where helpful, but not automatically if an equivalent article from a reliable news outlet could be linked in the same manner.
- The WMF Anti-Harassment Tools team is seeking input on the second set of wireframes for the Special:Block redesign that will introduce partial blocks. The new functionality will allow you to block a user from editing a specific set of pages, pages in a category, a namespace, and for specific actions such as moving pages and uploading files.
Administrators' newsletter – September 2018
[edit]News and updates for administrators from the past month (August 2018).
- None
- Asterion • Crisco 1492 • KF • Kudpung • Liz • Randykitty • Spartaz
- Optimist on the run → Voice of Clam
Interface administrator changes
- Amorymeltzer • Mr. Stradivarius • MusikAnimal • MSGJ • TheDJ • Xaosflux
- Following a "stop-gap" discussion, six users have temporarily been made interface administrators while discussion is ongoing for a more permanent process for assigning the permission. Interface administrators are now the only editors allowed to edit sitewide CSS and JavaScript pages, as well as CSS/JS pages in another user's userspace. Previously, all administrators had this ability. The right can be granted and revoked by bureaucrats.
- Because of a data centre test you will be able to read but not edit the wikis for up to an hour on 12 September and 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. The time when you can't edit might be shorter than an hour.
- Some abuse filter variables have changed. They are now easier to understand for non-experts. The old variables will still work but filter editors are encouraged to replace them with the new ones. You can find the list of changed variables on mediawiki.org. They have a note which says
Deprecated. Use ... instead
. An example isarticle_text
which is nowpage_title
. - Abuse filters can now use how old a page is. The variable is
page_age
.
- The Arbitration Committee has resolved to perform a round of Checkuser and Oversight appointments. The usernames of all applicants will be shared with the Functionaries team, and they will be requested to assist in the vetting process. The deadline to submit an application is 23:59 UTC, 12 September, and the candidates that move forward will be published on-wiki for community comments on 18 September.
Administrators' newsletter – October 2018
[edit]News and updates for administrators from the past month (September 2018).
- Justlettersandnumbers • L235
- Bgwhite • HorsePunchKid • J Greb • KillerChihuahua • Rami R • Winhunter
Interface administrator changes
- Cyberpower678 • Deryck Chan • Oshwah • Pharos • Ragesoss • Ritchie333
- Guerillero • NativeForeigner • Snowolf • Xeno
- Following a request for comment, the process for appointing interface administrators has been established. Currently only existing admins can request these rights, while a new RfC has begun on whether it should be available to non-admins.
- There is an open request for comment on Meta regarding the creation a new user group for global edit filter management.
- Partial blocks should be available for testing in October on the Test Wikipedia and the Beta-Cluster. This new feature allows admins to block users from editing specific pages and in the near-future, namespaces and uploading files. You can expect more updates and an invitation to help with testing once it is available.
- The Foundations' Anti-Harassment Tools team is currently looking for input on how to measure the effectiveness of blocks. This is in particular related to how they will measure the success of the aforementioned partial blocks.
- Because of a data centre test, you will be able to read but not edit the Wikimedia projects for up to an hour on 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time.
- The Arbitration Committee has, by motion, amended the procedure on functionary inactivity.
- The community consultation for 2018 CheckUser and Oversight appointments has concluded. Appointments will be made by October 11.
- Following a request for comment, the size of the Arbitration Committee will be decreased to 13 arbitrators, starting in 2019. Additionally, the minimum support percentage required to be appointed to a two-year term on ArbCom has been increased to 60%. ArbCom candidates who receive between 50% and 60% support will be appointed to one-year terms instead.
- Nominations for the 2018 Arbitration Committee Electoral Commission are being accepted until 12 October. These are the editors who help run the ArbCom election smoothly. If you are interested in volunteering for this role, please consider nominating yourself.
Administrators' newsletter – November 2018
[edit]News and updates for administrators from the past month (October 2018).
- A request for comment determined that non-administrators will not be able to request interface admin access.
- A request for comment is in progress to determine whether the Mediation Committee should be closed and marked as historical.
- A village pump discussion has been ongoing about whether the proposed deletion policy (PROD) should be clarified or amended.
- A request for comment is in progress to determine whether pending changes protection should be applied automatically to today's featured article (TFA) in order to mitigate a recent trend of severe image vandalism.
- Partial blocks is now available for testing on the Test Wikipedia. The new functionality allows you to block users from editing specific pages. Bugs may exist and can be reported on the local talk page or on Meta. A discussion regarding deployment to English Wikipedia will be started by community liaisons sometime in the near future.
- A user script is now available to quickly review unblock requests.
- The 2019 Community Wishlist Survey is now accepting new proposals until November 11, 2018. The results of this survey will determine what software the Wikimedia Foundation's Community Tech team will work on next year. Voting on the proposals will take place from November 16 to November 30, 2018. Specifically, there is a proposal category for admins and stewards that may be of interest.
- Eligible editors will be invited to nominate themselves as candidates in the 2018 Arbitration Committee Elections starting on November 4 until November 13. Voting will begin on November 19 and last until December 2.
- The Arbitration Committee's email address has changed to arbcom-enwikimedia.org. Other email lists, such as functionaries-en and clerks-l, remain unchanged.
ArbCom 2018 election voter message
[edit]Hello, Jamesday. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)
Administrators' newsletter – December 2018
[edit]News and updates for administrators from the past month (November 2018).
- Al Ameer son • Randykitty • Spartaz
- Boson • Daniel J. Leivick • Efe • Esanchez7587 • Fred Bauder • Garzo • Martijn Hoekstra • Orangemike
Interface administrator changes
- Following a request for comment, the Mediation Committee is now closed and will no longer be accepting case requests.
- A request for comment is in progress to determine whether members of the Bot Approvals Group should satisfy activity requirements in order to remain in that role.
- A request for comment is in progress regarding whether to change the administrator inactivity policy, such that administrators "who have made no logged administrative actions for at least 12 months may be desysopped". Currently, the policy states that administrators "who have made neither edits nor administrative actions for at least 12 months may be desysopped".
- A proposal has been made to temporarily restrict editing of the Main Page to interface administrators in order to mitigate the impact of compromised accounts.
- Administrators and bureaucrats can no longer unblock themselves unless they placed the block initially. This change has been implemented globally. See also this ongoing village pump discussion (permalink).
- To complement the aforementioned change, blocked administrators will soon have the ability to block the administrator that placed their block to mitigate the possibility of a compromised administrator account blocking all other active administrators.
- Since deployment of Partial blocks on Test Wikipedia, several bugs were identified. Most of them are now fixed. Administrators are encouraged to test the new deployment and report new bugs on Phabricator or leave feedback on the Project's talk page. You can request administrator access on the Test Wiki here.
- Voting in the 2018 Arbitration Committee Elections is open to eligible editors until Monday 23:59, 3 December 2018. Please review the candidates and, if you wish to do so, submit your choices on the voting page.
- In late November, an attacker compromised multiple accounts, including at least four administrator accounts, and used them to vandalize Wikipedia. If you have ever used your current password on any other website, you should change it immediately. Sharing the same password across multiple websites makes your account vulnerable, especially if your password was used on a website that suffered a data breach. As these incidents have shown, these concerns are not pure fantasies.
- Wikipedia policy requires administrators to have strong passwords. To further reinforce security, administrators should also consider enabling two-factor authentication. A committed identity can be used to verify that you are the true account owner in the event that your account is compromised and/or you are unable to log in.
- Shock Brigade Harvester Boris (Raymond Arritt) passed away on 14 November 2018. Boris joined Wikipedia as Raymond arritt on 8 May 2006 and was an administrator from 30 July 2007 to 2 June 2008.
Administrators' newsletter – January 2019
[edit]News and updates for administrators from the past month (December 2018).
- There are a number of new or changed speedy deletion criteria, each previously part of WP:CSD#G6:
- G14 (new): Disambiguation pages that disambiguate only zero or one existing pages are now covered under the new G14 criterion (discussion). This is {{db-disambig}}; the text is unchanged and candidates may be found in Category:Candidates for speedy deletion as unnecessary disambiguation pages.
- R4 (new): Redirects in the file namespace (and no file links) that have the same name as a file or redirect at Commons are now covered under the new R4 criterion (discussion). This is {{db-redircom}}; the text is unchanged.
- G13 (expanded): Userspace drafts containing only the default Article Wizard text are now covered under G13 along with other drafts (discussion). Such blank drafts are now eligible after six months rather than one year, and taggers continue to use {{db-blankdraft}}.
- The Wikimedia Foundation now requires all interface administrators to enable two-factor authentication.
- Members of the Bot Approvals Group (BAG) are now subject to an activity requirement. After two years without any bot-related activity (e.g. operating a bot, posting on a bot-related talk page), BAG members will be retired from BAG following a one-week notice.
- Starting on December 13, the Wikimedia Foundation security team implemented new password policy and requirements. Privileged accounts (administrators, bureaucrats, checkusers, oversighters, interface administrators, bots, edit filter managers/helpers, template editors, et al.) must have a password at least 10 characters in length. All accounts must have a password:
- At least 8 characters in length
- Not in the 100,000 most popular passwords (defined by the Password Blacklist library)
- Different from their username
- User accounts not meeting these requirements will be prompted to update their password accordingly. More information is available on MediaWiki.org.
- Blocked administrators may now block the administrator that blocked them. This was done to mitigate the possibility that a compromised administrator account would block all other active administrators, complementing the removal of the ability to unblock oneself outside of self-imposed blocks. A request for comment is currently in progress to determine whether the blocking policy should be updated regarding this change.
- {{Copyvio-revdel}} now has a link to open the history with the RevDel checkboxes already filled in.
- Following the 2018 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: AGK, Courcelles, GorillaWarfare, Joe Roe, Mkdw, SilkTork.
- Accounts continue to be compromised on a regular basis. Evidence shows this is entirely due to the accounts having the same password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately.
- Around 22% of admins have enabled two-factor authentication, up from 20% in June 2018. If you haven't already enabled it, please consider doing so. Regardless of whether you use 2FA, please practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
Administrators' newsletter – February 2019
[edit]News and updates for administrators from the past month (January 2019).
Interface administrator changes
- A request for comment is currently open to reevaluate the activity requirements for administrators.
- Administrators who are blocked have the technical ability to block the administrator who blocked their own account. A recent request for comment has amended the blocking policy to clarify that this ability should only be used in exceptional circumstances, such as account compromises, where there is a clear and immediate need.
- A request for comment closed with a consensus in favor of deprecating The Sun as a permissible reference, and creating an edit filter to warn users who attempt to cite it.
- A discussion regarding an overhaul of the format and appearance of Wikipedia:Requests for page protection is in progress (permalink). The proposed changes will make it easier to create requests for those who are not using Twinkle. The workflow for administrators at this venue will largely be unchanged. Additionally, there are plans to archive requests similar to how it is done at WP:PERM, where historical records are kept so that prior requests can more easily be searched for.
- Voting in the 2019 Steward elections will begin on 08 February 2019, 14:00 (UTC) and end on 28 February 2019, 13:59 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
- A new IRC bot is available that allows you to subscribe to notifications when specific filters are tripped. This requires that your IRC handle be identified.
Administrators' newsletter – March 2019
[edit]News and updates for administrators from the past month (February 2019).
Interface administrator changes
|
|
- The RfC on administrator activity requirements failed to reach consensus for any proposal.
- Following discussions at the Bureaucrats' noticeboard and Wikipedia talk:Administrators, an earlier change to the restoration of adminship policy was reverted. If requested, bureaucrats will not restore administrator permissions removed due to inactivity if there have been five years without a logged administrator action; this "five year rule" does not apply to permissions removed voluntarily.
- A new tool is available to help determine if a given IP is an open proxy/VPN/webhost/compromised host.
- The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
- paid-en-wpwikipedia.org has been set up to receive private evidence related to abusive paid editing.
- checkuser-en-wpwikipedia.org has been set up to receive private requests for CheckUser. For instance, requests for IP block exemption for anonymous proxy editing should now be sent to this address instead of the functionaries-en list.
- The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
- Following the 2019 Steward Elections, the following editors have been appointed as stewards: Base, Einsbor, Jon Kolbert, Schniggendiller, and Wim b.
Administrators' newsletter – April 2019
[edit]News and updates for administrators from the past month (March 2019).
Interface administrator changes
|
|
- In Special:Preferences under "Appearance" → "Advanced options", there is now an option to show a confirmation prompt when clicking on a rollback link.
- The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Please see meta:Community health initiative/User reporting system consultation 2019 to provide your input on this idea.
- The Arbitration Committee clarified that the General 1RR prohibition for Palestine-Israel articles may only be enforced on pages with the {{ARBPIA 1RR editnotice}} edit notice.
- Two more administrator accounts were compromised. Evidence has shown that these attacks, like previous incidents, were due to reusing a password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately. All admins are strongly encouraged to enable two-factor authentication, please consider doing so. Please always practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
- As a reminder, according to WP:NOQUORUM, administrators looking to close or relist an AfD should evaluate a nomination that has received few or no comments as if it were a proposed deletion (PROD) prior to determining whether it should be relisted.
ArbCom 2019 special circular
[edit]Administrators must secure their accounts
The Arbitration Committee may require a new RfA if your account is compromised.
|
This message was sent to all administrators following a recent motion. Thank you for your attention. For the Arbitration Committee, Cameron11598 02:17, 4 May 2019 (UTC)
Administrator account security (Correction to Arbcom 2019 special circular)
[edit]ArbCom would like to apologise and correct our previous mass message in light of the response from the community.
Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.
We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.
For the Arbitration Committee, -Cameron11598 21:03, 4 May 2019 (UTC)
Administrators' newsletter – May 2019
[edit]News and updates for administrators from the past month (April 2019).
- A request for comment concluded that creating pages in the portal namespace should be restricted to autoconfirmed users.
- Following a request for comment, the subject-specific notability guideline for pornographic actors and models (WP:PORNBIO) was removed; in its place, editors should consult WP:ENT and WP:GNG.
- XTools Admin Stats, a tool to list admins by administrative actions, has been revamped to support more types of log entries such as AbuseFilter changes. Two additional tools have been integrated into it as well: Steward Stats and Patroller Stats.
- In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases,
the committee will review all available information to determine whether the administrator followed "appropriate personal security practices" before restoring permissions
; administrators found failing to have adequately done sowill not be resysopped automatically
. All current administrators have been notified of this change. - Following a formal ratification process, the arbitration policy has been amended (diff). Specifically, the two-thirds majority required to remove or suspend an arbitrator now excludes (1) the arbitrator facing suspension or removal, and (2) any inactive arbitrator who does not respond within 30 days to attempts to solicit their feedback on the resolution through all known methods of communication.
- In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases,
- A request for comment is currently open to amend the community sanctions procedure to exclude non XfD or CSD deletions.
- A proposal to remove pre-2009 indefinite IP blocks is currently open for discussion.
Administrators' newsletter – June 2019
[edit]News and updates for administrators from the past month (May 2019).
- Andonic • Consumed Crustacean • Enigmaman • Euryalus • EWS23 • HereToHelp • Nv8200pa • Peripitus • StringTheory11 • Vejvančický
- An RfC seeks to clarify whether WP:OUTING should include information on just the English Wikipedia or any Wikimedia project.
- An RfC on WT:RfA concluded that Requests for adminship and bureaucratship are discussions seeking to build consensus.
- An RfC proposal to make the templates for discussion (TfD) process more like the requested moves (RM) process, i.e. "as a clearinghouse of template discussions", was closed as successful.
- The CSD feature of Twinkle now allows admins to notify page creators of deletion if the page had not been tagged. The default behavior matches that of tagging notifications, and replaces the ability to open the user talk page upon deletion. You can customize which criteria receive notifications in your Twinkle preferences: look for Notify page creator when deleting under these criteria.
- Twinkle's d-batch (batch delete) feature now supports deleting subpages (and related redirects and talk pages) of each page. The pages will be listed first but use with caution! The und-batch (batch undelete) option can now also restore talk pages.
- The previously discussed unblocking of IP addresses indefinitely-blocked before 2009 was approved and has taken place.
- The 2019 talk pages consultation produced a report for Phase 1 and has entered Phase 2.
Administrators' newsletter – July 2019
[edit]News and updates for administrators from the past month (June 2019).
- 28bytes • Ad Orientem • Ansh666 • Beeblebrox • Boing! said Zebedee • BU Rob13 • Dennis Brown • Deor • DoRD • Floquenbeam1 • Flyguy649 • Fram2 • Gadfium • GB fan • Jonathunder • Kusma • Lectonar • Moink • MSGJ • Nick • Od Mishehu • Rama • Spartaz • Syrthiss • TheDJ • WJBscribe
- 1Floquenbeam's access was removed, then restored, then removed again.
- 2Fram's access was removed, then restored, then removed again.
|
|
- A request for comment seeking to alleviate pressures on the request an account (ACC) process proposes either raising the account creation limit for extended confirmed editors or granting the account creator permission on request to new ACC tool users.
- In a related matter, the account throttle has been restored to six creations per day as the mitigation activity completed.
- The scope of CSD criterion G8 has been tightened such that the only redirects that it now applies to are those which target non-existent pages.
- The scope of CSD criterion G14 has been expanded slightly to include orphan "Foo (disambiguation)" redirects that target pages that are not disambiguation pages or pages that perform a disambiguation-like function (such as set index articles or lists).
- A request for comment seeks to determine whether Wikipedia:Office actions should be a policy page or an information page.
- The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Community feedback is invited.
- In February 2019, the Wikimedia Foundation (WMF) changed its office actions policy to include temporary and project-specific bans. The WMF exercised this new ability for the first time on the English Wikipedia on 10 June 2019 to temporarily ban and desysop Fram. This action has resulted in significant community discussion, a request for arbitration (permalink), and, either directly or indirectly, the resignations of numerous administrators and functionaries. The WMF Board of Trustees is aware of the situation, and discussions continue on a statement and a way forward. The Arbitration Committee has sent an open letter to the WMF Board.
Administrators' newsletter – August 2019
[edit]News and updates for administrators from the past month (July 2019).
Interface administrator changes
|
|
- Following a request for comment, the page Wikipedia:Office actions has been changed from a policy page to an information page.
- A request for comment (permalink) is in progress regarding the administrator inactivity policy.
- Editors may now use the template {{Ds/aware}} to indicate that they are aware that discretionary sanctions are in force for a topic area, so it is unnecessary to alert them.
- Following a research project on masking IP addresses, the Foundation is starting a new project to improve the privacy of IP editors. The result of this project may significantly change administrative and counter-vandalism workflows. The project is in the very early stages of discussions and there is no concrete plan yet. Admins and the broader community are encouraged to leave feedback on the talk page.
- The new page reviewer right is bundled with the admin tool set. Many admins regularly help out at Special:NewPagesFeed, but they may not be aware of improvements, changes, and new tools for the Curation system. Stay up to date by subscribing here to the NPP newsletter that appears every two months, and/or putting the reviewers' talk page on your watchlist.
Since the introduction of temporary user rights, it is becoming more usual to accord the New Page Reviewer right on a probationary period of 3 to 6 months in the first instance. This avoids rights removal for inactivity at a later stage and enables a review of their work before according the right on a permanent basis.
Administrators' newsletter – September 2019
[edit]News and updates for administrators from the past month (August 2019).
- Bradv • Chetsford • Izno
- Floquenbeam • Lectonar
- DESiegel • Jake Wartenberg • Rjanag • Topbanana
- Callanecc • Fox • HJ Mitchell • LFaraone • There'sNoTime
- Editors using the mobile website on Wikipedia can opt-in to new advanced features via your settings page. This will give access to more interface links, special pages, and tools.
- The advanced version of the edit review pages (recent changes, watchlist, and related changes) now includes two new filters. These filters are for "All contents" and "All discussions". They will filter the view to just those namespaces.
- A request for comment is open to provide an opportunity to amend the structure, rules, and procedures of the 2019 English Wikipedia Arbitration Committee election and to resolve any issues not covered by existing rules.
- A global request for comment is in progress regarding whether a user group should be created that could modify edit filters across all public Wikimedia wikis.
Administrators' newsletter – October 2019
[edit]News and updates for administrators from the past month (September 2019).
Interface administrator changes
|
|
- Following a discussion, a new criterion for speedy category renaming was added: C2F: One eponymous article, which
applies if the category contains only an eponymous article or media file, provided that the category has not otherwise been emptied shortly before the nomination. The default outcome is an upmerge to the parent categories
.
- Following a discussion, a new criterion for speedy category renaming was added: C2F: One eponymous article, which
- As previously noted, tighter password requirements for Administrators were put in place last year. Wikipedia should now alert you if your password is less than 10 characters long and thus too short.
- The 2019 CheckUser and Oversight appointment process has begun. The community consultation period will take place October 4th to 10th.
- The arbitration case regarding Fram was closed. While there will be a local RfC
focus[ing] on how harassment and private complaints should be handled in the future
, there is currently a global community consultation on partial and temporary office actions in response to the incident. It will be open until October 30th.
- The Community Tech team has been working on a system for temporarily watching pages, and welcomes feedback.
Hi James! Boston misses you
[edit]We're having another wikiconf in Cambridge next month, J and I are thinking findly of you and hope you are well. – SJ + 14:54, 3 October 2019 (UTC)
Administrators' newsletter – November 2019
[edit]News and updates for administrators from the past month (October 2019).
Interface administrator changes
|
|
- An RfC was closed with the consensus that the resysop criteria should be made stricter.
- The follow-up RfC to develop that change is now open at Wikipedia:Requests for comment/2019 Resysop Criteria (2).
- A related RfC is seeking the community's sentiment for a binding desysop procedure.
- Eligible editors may now nominate themselves as candidates for the 2019 Arbitration Committee Elections. The self-nomination period will close November 12, with voting running from November 19 through December 2.
ArbCom 2019 election voter message
[edit]Administrators' newsletter – December 2019
[edit]News and updates for administrators from the past month (November 2019).
- EvergreenFir • ToBeFree
- Akhilleus • Athaenara • John Vandenberg • Melchoir • MichaelQSchmidt • NeilN • Youngamerican • 😂
Interface administrator changes
- An RfC on the administrator resysop criteria was closed. 18 proposals have been summarised with a variety of supported and opposed statements. The inactivity grace period within which a new request for adminship is not required has been reduced from three years to two. Additionally, Bureaucrats are permitted to use their discretion when returning administrator rights.
- Following a proposal, the edit filter mailing list has been opened up to users with the Edit Filter Helper right.
- Wikimedia projects can set a default block length for users via MediaWiki:ipb-default-expiry. A new page, MediaWiki:ipb-default-expiry-ip, allows the setting of a different default block length for IP editors. Neither is currently used. (T219126)
- Voting in the 2019 Arbitration Committee Elections is open to eligible editors until Monday 23:59, 2 December 2018 UTC. Please review the candidates and, if you wish to do so, submit your choices on the voting page.
- The global consultation on partial and temporary office actions that ended in October received a closing statement from staff concluding, among other things, that the WMF
will no longer use partial or temporary Office Action bans... until and unless community consensus that they are of value or Board directive
.
- The global consultation on partial and temporary office actions that ended in October received a closing statement from staff concluding, among other things, that the WMF
Administrators' newsletter – January 2020
[edit]News and updates for administrators from the past month (December 2019).
|
|
- A request for comment asks whether partial blocks should be enabled on the English Wikipedia. If enabled, this functionality would allow administrators to block users from editing specific pages or namespaces, rather than the entire site.
- A proposal asks whether admins who don't use their tools for a significant period of time (e.g. five years) should have the toolset procedurally removed.
- Following a successful RfC, a whitelist is now available for users whose redirects will be autopatrolled by a bot, removing them from the new pages patrol queue. Admins can add such users to Wikipedia:New pages patrol/Redirect whitelist after a discussion following the guidelines at Wikipedia talk:New pages patrol/Redirect whitelist.
- The fourth case on Palestine-Israel articles was closed. The case consolidated all previous remedies under one heading, which should make them easier to understand, apply, and enforce. In particular, the distinction between "primary articles" and "related content" has been clarified, with the former being
the entire set of articles whose topic relates to the Arab-Israeli conflict, broadly interpreted
rather thanreasonably construed
. - Following the 2019 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Beeblebrox, Bradv, Casliber, David Fuchs, DGG, KrakatoaKatie, Maxim, Newyorkbrad, SoWhy, Worm That Turned, Xeno.
- The fourth case on Palestine-Israel articles was closed. The case consolidated all previous remedies under one heading, which should make them easier to understand, apply, and enforce. In particular, the distinction between "primary articles" and "related content" has been clarified, with the former being
- This issue marks three full years of the Admin newsletter. Thanks for reading!
Administrators' newsletter – February 2020
[edit]News and updates for administrators from the past month (January 2020).
|
Interface administrator changes
|
- Following a request for comment, partial blocks are now enabled on the English Wikipedia. This functionality allows administrators to block users from editing specific pages or namespaces rather than the entire site. A draft policy is being workshopped at Wikipedia:Partial blocks.
- The request for comment seeking the community's sentiment for a binding desysop procedure closed with
wide-spread support for an alternative desysoping procedure based on community input
. No proposed process received consensus.
- Twinkle now supports partial blocking. There is a small checkbox that toggles the "partial" status for both blocks and templating. There is currently one template: {{uw-pblock}}.
- When trying to move a page, if the target title already exists then a warning message is shown. The warning message will now include a link to the target title. [15]
- Following a recent arbitration case, the Arbitration Committee reminded administrators
that checkuser and oversight blocks must not be reversed or modified without prior consultation with the checkuser or oversighter who placed the block, the respective functionary team, or the Arbitration Committee.
- Following a recent arbitration case, the Arbitration Committee reminded administrators
- Voting in the 2020 Steward elections will begin on 08 February 2020, 14:00 (UTC) and end on 28 February 2020, 13:59 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
- The English Wikipedia has reached six million articles. Thank you everyone for your contributions!
Possible example on Stable sorting
[edit]Would you be interested giving opinions or suggestions on a stable sorting example page I'm constructing. A first draft is found at Talk:Sorting_algorithm#How_is_this_stable_sort_example?
Also a newer, evolving, example is found in my sandbox at: User:Lent/sandbox .
And out of curiosity, did you know that a Shift-click on a Wikipedia sortable table column does a secondary sort?
Thanks!--Lent (talk) 11:47, 29 February 2020 (UTC)
Administrators' newsletter – March 2020
[edit]News and updates for administrators from the past month (February 2020).
|
- Following an RfC, the blocking policy was changed to state that sysops
must not
undo or alter CheckUser or Oversight blocks, rather thanshould not
. - A request for comment confirmed that sandboxes of established but inactive editors may not be blanked due solely to inactivity.
- Following an RfC, the blocking policy was changed to state that sysops
- Following a discussion, Twinkle's default CSD behavior will soon change, most likely this week. After the change, Twinkle will default to "tagging mode" if there is no CSD tag present, and default to "deletion mode" if there is a CSD tag present. You will be able to always default to "deletion mode" (the current behavior) using your Twinkle preferences.
- Following the 2020 Steward Elections, the following editors have been appointed as stewards: BRPever, Krd, Martin Urbanec, MusikAnimal, Sakretsu, Sotiale, and Tks4Fish. There are a total of seven editors that have been appointed as stewards, the most since 2014.
- The 2020 appointees for the Ombudsman commission are Ajraddatz and Uzoma Ozurumba; they will serve for one year.
Administrators' newsletter – April 2020
[edit]News and updates for administrators from the past month (March 2020).
|
- There is an ongoing request for comment to streamline the source deprecation and blacklisting process.
- There is a plan for new requirements for user signatures. You can give feedback.
- Following the banning of an editor by the WMF last year, the Arbitration Committee resolved to hold a
Arbcom RfC regarding on-wiki harassment
. A draft RfC has been posted at Wikipedia:Arbitration Committee/Anti-harassment RfC (Draft) and not open to comments from the community yet. Interested editors can comment on the RfC itself on its talk page.
- Following the banning of an editor by the WMF last year, the Arbitration Committee resolved to hold a
- The WMF has begun a pilot report of the pages most visited through various social media platforms to help with anti-vandalism and anti-disinformation efforts. The report is updated daily and will be available through the end of May.
Administrators' newsletter – May 2020
[edit]News and updates for administrators from the past month (April 2020).
- Discretionary sanctions have been authorized for all pages and edits related to COVID-19, to be logged at WP:GS/COVID19.
- Following a recent discussion on Meta-Wiki, the edit filter maintainer global group has been created.
- A request for comment has been proposed to create a new main page editor usergroup.
- A request for comment has been proposed to make the bureaucrat activity requirements more strict.
- The Editing team has been working on the talk pages project. You can review the proposed design and share your thoughts on the talk page.
- Enterprisey created a script that will show a link to the proper Special:Undelete page when viewing a since-deleted revision, see User:Enterprisey/link-deleted-revs.
- A request for comment closed with consensus to create a Village Pump-style page for communication with the Wikimedia Foundation.
Administrators' newsletter – June 2020
[edit]News and updates for administrators from the past month (May 2020).
- CaptainEek • Creffett • Cwmhiraeth
- Anna Frodesiak • Buckshot06 • Ronhjones • SQL
- A request for comment asks whether the Unblock Ticket Request System (UTRS) should allowed any unblock request or just private appeals.
- The Wikimedia Foundation announced that they will develop a universal code of conduct for all WMF projects. There is an open local discussion regarding the same.
Administrators' newsletter – July 2020
[edit]News and updates for administrators from the past month (June 2020).
- A request for comment is in progress to remove the T2 (template that misrepresents established policy) speedy deletion criterion.
- Protection templates on mainspace pages are now automatically added by User:MusikBot II (BRFA).
- Following the banning of an editor by the WMF last year, the Arbitration Committee resolved to hold an
RfC regarding on-wiki harassment
. The RfC has been posted at Wikipedia:Arbitration Committee/Anti-harassment RfC and is open to comments from the community. - The Medicine case was closed, with a remedy authorizing standard discretionary sanctions for
all discussions about pharmaceutical drug prices and pricing and for edits adding, changing, or removing pharmaceutical drug prices or pricing from articles
.
- Following the banning of an editor by the WMF last year, the Arbitration Committee resolved to hold an
Administrators' newsletter – August 2020
[edit]News and updates for administrators from the past month (July 2020).
- There is an open request for comment to decide whether to increase the minimum duration a sanction discussion has to remain open (currently 24 hours).
- Speedy deletion criterion T2 (template that misrepresents established policy) has been repealed following a request for comment.
- Speedy deletion criterion X2 (pages created by the content translation tool) has been repealed following a discussion.
- There is a proposal to restrict proposed deletion to confirmed users.
Administrators' newsletter – September 2020
[edit]News and updates for administrators from the past month (August 2020).
- Following a request for comment, the minimum length for site ban discussions was increased to 72 hours, up from 24.
- A request for comment is ongoing to determine whether paid editors
must
orshould
use the articles for creation process. - A request for comment is open to resolve inconsistencies between the draftification and alternative to deletion processes.
- A request for comment is open to provide an opportunity to amend the structure, rules, and procedures of the 2020 English Wikipedia Arbitration Committee election and to resolve any issues not covered by existing rules.
- An open request for comment asks whether active Arbitrators may serve on the Trust and Safety Case Review Committee or Ombudsman commission.
Administrators' newsletter – September 2020
[edit]News and updates for administrators from the past month (September 2020).
- Ajpolino • LuK3
- Jackmcbarn
- Ad Orientem • Harej • Lid • Lomn • Mentoz86 • Oliver Pereira • XJaM
- There'sNoTime → TheresNoTime
- A request for comment found consensus that incubation as an alternative to deletion should generally only be recommended when draftification is appropriate, namely
1) if the result of a deletion discussion is to draftify; or 2) if the article is newly created
.
- A request for comment found consensus that incubation as an alternative to deletion should generally only be recommended when draftification is appropriate, namely
- The filter log now provides links to view diffs of deleted revisions (phab:T261630).
- The 2020 CheckUser and Oversight appointment process has begun. The community consultation period will take place from September 27th to October 7th.
- Following a request for comment, sitting Committee members may not serve on either the Ombuds Commission or the WMF Case Review Committee. The Arbitration Committee passed a motion implementing those results into their procedures.
- The Universal Code of Conduct draft is open for community review and comment until October 6th, 2020.
- Office actions may now be appealed to the Interim Trust & Safety Case Review Committee.
Administrators' newsletter – November 2020
[edit]News and updates for administrators from the past month (October 2020).
Interface administrator changes
|
|
- Community sanctions now authorize administrators to place under indefinite semiprotection
any article on a beauty pageant, or biography of a person known as a beauty pageant contestant, which has been edited by a sockpuppet account or logged-out sockpuppet
, to be logged at WP:GS/PAGEANT.
- Community sanctions now authorize administrators to place under indefinite semiprotection
- Sysops will once again be able to view the deleted history of JS/CSS pages; this was restricted to interface administrators when that group was introduced.
- Twinkle's block module now includes the ability to note the specific case when applying a discretionary sanctions block and/or template.
- Sysops will be able to use Special:CreateLocalAccount to create a local account for a global user that is prevented from auto-creation locally (such as by a filter or range block). Administrators that are not sure if such a creation is appropriate should contact a checkuser.
- The 2020 Arbitration Committee Elections process has begun. Eligible editors will be able to nominate themselves as candidates from November 8 through November 17. The voting period will run from November 23 through December 6.
- The Anti-harassment RfC has concluded with a summary of the feedback provided.
- A reminder that
standard discretionary sanctions are authorized for all edits about, and all pages related to post-1932 politics of the United States and closely related people.
(American Politics 2 Arbitration case).
- A reminder that
ArbCom 2020 Elections voter message
[edit]Administrators' newsletter – December 2020
[edit]News and updates for administrators from the past month (November 2020).
- Andrwsc • Anetode • GoldenRing • JzG • LinguistAtLarge • Nehrams2020
Interface administrator changes
- There is a request for comment in progress to either remove T3 (duplicated and hardcoded instances) as a speedy deletion criterion or eliminate its seven-day waiting period.
- Voting for proposals in the 2021 Community Wishlist Survey, which determines what software the Wikimedia Foundation's Community Tech team will work on next year, will take place from 8 December through 21 December. In particular, there are sections regarding administrators and anti-harassment.
- Voting in the 2020 Arbitration Committee Elections is open to eligible editors until Monday 23:59, 7 December 2020 UTC. Please review the candidates and, if you wish to do so, submit your choices on the voting page.
Administrators' newsletter – January 2021
[edit]News and updates for administrators from the past month (December 2020).
|
|
- Speedy deletion criterion T3 (duplication and hardcoded instances) has been repealed following a request for comment.
- You can now put pages on your watchlist for a limited period of time.
- By motion, standard discretionary sanctions have been temporarily authorized
for all pages relating to the Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes)
. The effectiveness of the discretionary sanctions can be evaluated on the request by any editor after March 1, 2021 (or sooner if for a good reason). - Following the 2020 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Barkeep49, BDD, Bradv, CaptainEek, L235, Maxim, Primefac.
- By motion, standard discretionary sanctions have been temporarily authorized
Administrators' newsletter – February 2021
[edit]News and updates for administrators from the past month (January 2021).
|
|
- The standard discretionary sanctions authorized for American Politics were amended by motion to cover
post-1992 politics of United States and closely related people
, replacing the 1932 cutoff.
- The standard discretionary sanctions authorized for American Politics were amended by motion to cover
- Voting in the 2021 Steward elections will begin on 05 February 2021, 14:00 (UTC) and end on 26 February 2021, 13:59 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
- Wikipedia has now been around for 20 years, and recently saw its billionth edit!
Administrators' newsletter – March 2021
[edit]News and updates for administrators from the past month (February 2021).
Interface administrator changes
- A request for comment is open that proposes a process for the community to revoke administrative permissions. This follows a 2019 RfC in favor of creating one such a policy.
- A request for comment is in progress to remove F7 (invalid fair-use claim) subcriterion a, which covers immediate deletion of non-free media with invalid fair-use tags.
- A request for comment seeks to grant page movers the
delete-redirect
userright, which allows moving a page over a single-revision redirect, regardless of that redirect's target. The full proposal is at Wikipedia:Page mover/delete-redirect. - A request for comment asks if sysops may
place the General sanctions/Coronavirus disease 2019 editnotice template on pages in scope that do not have page-specific sanctions
? - There is a discussion in progress concerning automatic protection of each day's featured article with Pending Changes protection.
- When blocking an IPv6 address with Twinkle, there is now a checkbox with the option to just block the /64 range. When doing so, you can still leave a block template on the initial, single IP address' talkpage.
- When protecting a page with Twinkle, you can now add a note if doing so was in response to a request at WP:RfPP, and even link to the specific revision.
- There have been a number of reported issues with Pending Changes. Most problems setting protection appear to have been resolved (phab:T273317) but other issues with autoaccepting edits persist (phab:T275322).
- By motion, the discretionary sanctions originally authorized under the GamerGate case are now authorized under a new Gender and sexuality case, with sanctions
authorized for all edits about, and all pages related to, any gender-related dispute or controversy and associated people.
Sanctions issued under GamerGate are now considered Gender and sexuality sanctions. - The Kurds and Kurdistan case was closed, authorizing standard discretionary sanctions for
the topics of Kurds and Kurdistan, broadly construed
.
- By motion, the discretionary sanctions originally authorized under the GamerGate case are now authorized under a new Gender and sexuality case, with sanctions
- Following the 2021 Steward Elections, the following editors have been appointed as stewards: AmandaNP, Operator873, Stanglavine, Teles, and Wiki13.
Administrators' newsletter – April 2021
[edit]News and updates for administrators from the past month (March 2021).
- Alexandria • Happyme22 • RexxS
- Following a request for comment, F7 (invalid fair-use claim) subcriterion a has been deprecated; it covered immediate deletion of non-free media with invalid fair-use tags.
- Following a request for comment, page movers were granted the
delete-redirect
userright, which allows moving a page over a single-revision redirect, regardless of that redirect's target.
- When you move a page that many editors have on their watchlist the history can be split and it might also not be possible to move it again for a while. This is because of a job queue problem. (T278350)
- Code to support some very old web browsers is being removed. This could cause issues in those browsers. (T277803)
- A community consultation on the Arbitration Committee discretionary sanctions procedure is open until April 25.
Administrators' newsletter – May 2021
[edit]News and updates for administrators from the past month (April 2021).
Interface administrator changes
- Following an RfC, consensus was found that third party appeals are allowed but discouraged.
- The 2021 Desysop Policy RfC was closed with no consensus. Consensus was found in a previous RfC for a community based desysop procedure, though the procedure proposed in the 2021 RfC did not gain consensus.
- The user group
oversight
will be renamed tosuppress
. This is for technical reasons. You can comment at T112147 if you have objections.
- The user group
- The community consultation on the Arbitration Committee discretionary sanctions procedure was closed, and an initial draft based on feedback from the now closed consultation is expected to be released in early June to early July for community review.
Administrators' newsletter – June 2021
[edit]News and updates for administrators from the past month (May 2021).
- Ashleyyoursmile • Less Unless
- Husond • MattWade • MJCdetroit • Carioca • Vague Rant • Kingboyk • Thunderboltz • Gwen Gale • AniMate • SlimVirgin (deceased)
- Consensus was reached to deprecate Wikipedia:Editor assistance.
- Following a Request for Comment the Book namespace was deprecated.
- Wikimedia previously used the IRC network Freenode. However, due to changes over who controlled the network with reports of a forceful takeover by several ex-staff members, the Wikimedia IRC Group Contacts decided to move to the new Libera Chat network. It has been reported that Wikimedia related channels on Freenode have been forcibly taken over if they pointed members to Libera. There is a migration guide and Wikimedia discussions about this.
- After a Clarification request, the Arbitration Committee modified Remedy 5 of the Antisemitism in Poland case. This means sourcing expectations are a discretionary sanction instead of being present on all articles. It also details using the talk page or the Reliable Sources Noticeboard to discuss disputed sources.
Administrators' newsletter – July 2021
[edit]News and updates for administrators from the past month (June 2021).
Interface administrator changes
|
|
- Consensus has been reached to delete all books in the book namespace. There was rough consensus that the deleted books should still be available on request at WP:REFUND even after the namespace is removed.
- An RfC is open to discuss the next steps following a trial which automatically applied pending changes to TFAs.
- IP addresses of unregistered users are to be hidden from everyone. There is a rough draft of how IP addresses may be shown to users who need to see them. This currently details allowing administrators, checkusers, stewards and those with a new usergroup to view the full IP address of unregistered users. Editors with at least 500 edits and an account over a year old will be able to see all but the end of the IP address in the proposal. The ability to see the IP addresses hidden behind the mask would be dependent on agreeing to not share the parts of the IP address they can see with those who do not have access to the same information. Accessing part of or the full IP address of a masked editor would also be logged. Comments on the draft are being welcomed at the talk page.
- The community authorised COVID-19 general sanctions have been superseded by the COVID-19 discretionary sanctions following a motion at a case request. Alerts given and sanctions placed under the community authorised general sanctions are now considered alerts for and sanctions under the new discretionary sanctions.
Administrators' newsletter – July 2021
[edit]News and updates for administrators from the past month (July 2021).
|
|
- An RfC is open to add a delay of one week from nomination to deletion for G13 speedy deletions.
- Last week all wikis were very slow or not accessible for 30 minutes. This was due to server lag caused by regenerating dynamic lists on the Russian Wikinews after a large bulk import. (T287380)
- Following an amendment request, the committee has clarified that the Talk page exception to the 500/30 rule in remedy 5 of the Palestine-Israel articles 4 case does not apply to requested move discussions.
- You can vote for candidates in the 2021 Board of Trustees elections from 4 August to 17 August. Four community elected seats are up for election.
Administrators' newsletter – September 2021
[edit]News and updates for administrators from the past month (August 2021).
- Feedback is requested on the Universal Code of Conduct enforcement draft by the Universal Code of Conduct Phase 2 drafting committee.
- A RfC is open on whether to allow administrators to use extended confirmed protection on high-risk templates.
- A discussion is open to decide when, if ever, should discord logs be eligible for removal when posted onwiki (including whether to oversight them)
- A RfC on the next steps after the trial of pending changes on TFAs has resulted in a 30 day trial of automatic semi protection for TFAs.
- The Score extension has been re-enabled on public wikis. It has been updated, but has been placed in safe mode to address unresolved security issues. Further information on the security issues can be found on the mediawiki page.
- A request for comment is in progress to provide an opportunity to amend the structure, rules, and procedures of the Arbitration Committee election and resolve any issues not covered by existing rules. Comments and new proposals are welcome.
- The 2021 RfA review is now open for comments.
Administrators' newsletter – October 2021
[edit]News and updates for administrators from the past month (September 2021).
- Following an RfC, extended confirmed protection may be used preemptively on certain high-risk templates.
- Following a discussion at the Village Pump, there is consensus to treat discord logs the same as IRC logs. This means that discord logs will be oversighted if posted onwiki.
- DiscussionTools has superseded Enterprisey's reply-link script. Editors may switch using the "Discussion tools" checkbox under Preferences → Beta features.
- A motion has standardised the 500/30 (extended confirmed) restrictions placed by the Arbitration Committee. The standardised restriction is now listed in the Arbitration Committee's procedures.
- Following the closure of the Iranian politics case, standard discretionary sanctions are authorized for all edits about, and all pages related to, post-1978 Iranian politics, broadly construed.
- The Arbitration Committee encourages uninvolved administrators to use the discretionary sanctions procedure in topic areas where it is authorised to facilitate consensus in RfCs. This includes, but is not limited to, enforcing sectioned comments, word/diff limits and moratoriums on a particular topic from being brought in an RfC for up to a year.
- Editors have approved expanding the trial of Growth Features from 2% of new accounts to 25%, and the share of newcomers getting mentorship from 2% to 5%. Experienced editors are invited to add themselves to the mentor list.
- The community consultation phase of the 2021 CheckUser and Oversight appointments process is open for editors to provide comments and ask questions to candidates.
Administrators' newsletter – November 2021
[edit]News and updates for administrators from the past month (October 2021).
- Phase 2 of the 2021 RfA review has commenced which will discuss potential solutions to address the 8 issues found in Phase 1. Proposed solutions that achieve consensus will be implemented and you may propose solutions till 07 November 2021.
- Toolhub is a catalogue of tools which can be used on Wikimedia wikis. It is at https://toolhub.wikimedia.org/.
- GeneralNotability, Mz7 and Cyberpower678 have been appointed to the Electoral Commission for the 2021 Arbitration Committee Elections. Ivanvector and John M Wolfson are reserve commissioners.
- Eligible editors are invited to self-nominate themselves to stand in the 2021 Arbitration Committee elections from 07 November 2021 until 16 November 2021.
- The 2021 CheckUser and Oversight appointments process has concluded with the appointment of five new CheckUsers and two new Oversighters.
Administrators' newsletter – December 2021
[edit]News and updates for administrators from the past month (November 2021).
- Unregistered editors using the mobile website are now able to receive notices to indicate they have talk page messages. The notice looks similar to what is already present on desktop, and will be displayed on when viewing any page except mainspace and when editing any page. (T284642)
- The limit on the number of emails a user can send per day has been made global instead of per-wiki to help prevent abuse. (T293866)
- Voting in the 2021 Arbitration Committee Elections is open until 23:59, 06 December 2021 (UTC).
- The already authorized standard discretionary sanctions for all pages relating to the Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes), broadly construed, have been made permanent.
Administrators will no longer be autopatrolled
[edit]A recently closed Request for Comment (RFC) reached consensus to remove Autopatrolled from the administrator user group. You may, similarly as with Edit Filter Manager, choose to self-assign this permission to yourself. This will be implemented the week of December 13th, but if you wish to self-assign you may do so now. To find out when the change has gone live or if you have any questions please visit the Administrator's Noticeboard. 20:06, 7 December 2021 (UTC)
Pending suspension of administrative permissions due to inactivity
[edit]Established policy provides for removal of the administrative permissions of users who have not made any edits or logged actions in the preceding twelve months. Because you have been inactive, your administrative permissions will be removed if you do not return to activity within the next month.
Inactive administrators are encouraged to rejoin the project in earnest rather than to make token edits to avoid loss of administrative permissions. Resources and support for reengaging with the project are available at Wikipedia:WikiProject Editor Retention/administrators. If you do not intend to rejoin the project in the foreseeable future, please consider voluntarily resigning your administrative permissions by making a request at the bureaucrats' noticeboard.
Thank you for your past contributions to the project. — JJMC89 bot 00:03, 1 January 2022 (UTC)
Administrators' newsletter – January 2022
[edit]News and updates for administrators from the past month (December 2021).
Interface administrator changes
|
|
- Following consensus at the 2021 RfA review, the autopatrolled user right has been removed from the administrators user group; admins can grant themselves the autopatrolled permission if they wish to remain autopatrolled.
- Additionally, consensus for proposal 6C of the 2021 RfA review has led to the creation of an administrative action review process. The purpose of this process will be to review individual administrator actions and individual actions taken by users holding advanced permissions.
- Following the 2021 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Beeblebrox, Cabayi, Donald Albury, Enterprisey, Izno, Opabinia regalis, Worm That Turned, Wugapodes.
- The functionaries email list (functionaries-enlists.wikimedia.org) will no longer accept incoming emails apart from those sent by list members and WMF staff. Private concerns, apart from those requiring oversight, should be directly sent to the Arbitration Committee.
How we will see unregistered users
[edit]Hi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:12, 4 January 2022 (UTC)
Imminent suspension of administrative permissions due to inactivity
[edit]Established policy provides for removal of the administrative permissions of users who have not made any edits or logged actions in the preceding twelve months. Because you have been inactive, your administrative permissions will be removed if you do not return to activity within the next several days.
Inactive administrators are encouraged to rejoin the project in earnest rather than to make token edits to avoid loss of administrative permissions. Resources and support for reengaging with the project are available at Wikipedia:WikiProject Editor Retention/administrators. If you do not intend to rejoin the project in the foreseeable future, please consider voluntarily resigning your administrative permissions by making a request at the bureaucrats' noticeboard.
Thank you for your past contributions to the project. — JJMC89 bot 00:01, 25 January 2022 (UTC)
Suspension of administrative permissions due to inactivity
[edit]Established policy provides for removal of the administrative permissions of users who have not made any edits or logged actions in the preceding twelve months. Because you have been inactive, your administrative permissions have been removed.
Subject to certain time limits and other restrictions, your administrative permissions may be returned upon request at WP:BN.
Thank you for your past contributions to the project. — xaosflux Talk 00:14, 1 February 2022 (UTC)
Administrators' newsletter – February 2022
[edit]News and updates for administrators from the past month (January 2022).
- The Universal Code of Conduct enforcement guidelines have been published for consideration. Voting to ratify this guideline is planned to take place 7 March to 21 March. Comments can be made on the talk page.
- The user group
oversight
will be renamedsuppress
in around 3 weeks. This will not affect the name shown to users and is simply a change in the technical name of the user group. The change is being made for technical reasons. You can comment in Phabricator if you have objections. - The Reply Tool feature, which is a part of Discussion Tools, will be opt-out for everyone logged in or logged out starting 7 February 2022. Editors wishing to comment on this can do so in the relevant Village Pump discussion.
- The user group
- Community input is requested on several motions aimed at addressing discretionary sanctions that are no longer needed or overly broad.
- The Arbitration Committee has published a generalised comment regarding successful appeals of sanctions that it can review (such as checkuser blocks).
- A motion related to the Antisemitism in Poland case was passed following a declined case request.
- Voting in the 2022 Steward elections will begin on 07 February 2022, 14:00 (UTC) and end on 26 February 2022, 13:59 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
- Voting in the 2022 Community Wishlist Survey is open until 11 February 2022.
Administrators' newsletter – March 2022
[edit]News and updates for administrators from the past month (February 2022).
|
|
- A RfC is open to change the wording of revision deletion criterion 1 to remove the sentence relating to non-infringing contributions.
- A RfC is open to discuss prohibiting draftification of articles over 90 days old.
- The deployment of the reply tool as an opt-out feature, as announced in last month's newsletter, has been delayed to 7 March. Feedback and comments are being welcomed at Wikipedia talk:Talk pages project. (T296645)
- Special:Nuke will now allow the selection of standard deletion reasons to be used when mass-deleting pages. This was a Community Wishlist Survey request from 2022. (T25020)
- The ability to undelete the talk page when undeleting a page using Special:Undelete or the API will be added soon. This change was requested in the 2021 Community Wishlist Survey. (T295389)
- Several unused discretionary sanctions and article probation remedies have been rescinded. This follows the community feedback from the 2021 Discretionary Sanctions review.
- The 2022 appointees for the Ombuds commission are Érico, Faendalimas, Galahad, Infinite0694, Mykola7, Olugold, Udehb and Zabe as regular members and Ameisenigel and JJMC89 as advisory members.
- Following the 2022 Steward Elections, the following editors have been appointed as stewards: AntiCompositeNumber, BRPever, Hasley, TheresNoTime, and Vermont.
- The 2022 Community Wishlist Survey results have been published alongside the ranking of prioritized proposals.
Administrators' newsletter – April 2022
[edit]News and updates for administrators from the past month (March 2022).
- An RfC is open proposing a change to the minimum activity requirements for administrators.
- Access to Special:RevisionDelete has been expanded to include users who have the
deletelogentry
anddeletedhistory
rights. This means that those in the Researcher user group and Checkusers who are not administrators can now access Special:RevisionDelete. The users able to view the special page after this change are the 3 users in the Researcher group, as there are currently no checkusers who are not already administrators. (T301928) - When viewing deleted revisions or diffs on Special:Undelete a back link to the undelete page for the associated page is now present. (T284114)
- Wikipedia:Arbitration Committee/Procedures § Opening of proceedings has been updated to reflect current practice following a motion.
- A arbitration case regarding Skepticism and coordinated editing has been closed.
- A arbitration case regarding WikiProject Tropical Cyclones has been opened.
- Voting for the Universal Code of Conduct Enforcement guidelines has closed, and the results were that 56.98% of voters supported the guidelines. The results of this vote mean the Wikimedia Foundation Board will now review the guidelines.
Administrators' newsletter – May 2022
[edit]News and updates for administrators from the past month (April 2022).
|
|
- Following an RfC, a change has been made to the administrators inactivity policy. Under the new policy, if an administrator has not made at least 100 edits over a period of 5 years they may be desysopped for inactivity.
- Following a discussion on the bureaucrat's noticeboard, a change has been made to the bureaucrats inactivity policy.
- The ability to undelete the associated talk page when undeleting a page has been added. This was the 11th wish of the 2021 Community Wishlist Survey.
- A public status system for WMF wikis has been created. It is located at https://www.wikimediastatus.net/ and is hosted separately to WMF wikis so in the case of an outage it will remain viewable.
- Remedy 2 of the St Christopher case has been rescinded following a motion. The remedy previously authorised administrators to place a ban on single-purpose accounts who were disruptively editing on the article St Christopher Iba Mar Diop College of Medicine or related pages from those pages.
Administrators' newsletter – June 2022
[edit]News and updates for administrators from the past month (May 2022).
|
|
- Several areas of improvement collated from community member votes have been identified in the Universal Code of Conduct Enforcement guidelines. The areas of improvement have been sent back for review and you are invited to provide input on these areas.
- Administrators using the mobile web interface can now access Special:Block directly from user pages. (T307341)
- The IP Info feature has been deployed to all wikis as a Beta Feature. Any autoconfirmed user may enable the feature using the "IP info" checkbox under Preferences → Beta features. Autoconfirmed users will be able to access basic information about an IP address that includes the country and connection method. Those with advanced privileges (admin, bureaucrat, checkuser) will have access to extra information that includes the Internet Service Provider and more specific location.
- Remedy 2 of the Rachel Marsden case has been rescinded following a motion. The remedy previously authorised administrators to delete or reduce to a stub, together with their talk pages, articles related to Rachel Marsden when they violate Wikipedia's biographies of living persons policy.
- An arbitration case regarding WikiProject Tropical Cyclones has been closed.
Administrators' newsletter – July 2022
[edit]News and updates for administrators from the past month (June 2022).
|
Interface administrator changes
|
user_global_editcount
is a new variable that can be used in abuse filters to avoid affecting globally active users. (T130439)
- An arbitration case regarding conduct in deletion-related editing has been opened.
- The New Pages Patrol queue has around 10,000 articles to be reviewed. As all administrators have the patrol right, please consider helping out. The queue is here. For further information on the state of the project, see the latest NPP newsletter.
Administrators' newsletter – August 2022
[edit]News and updates for administrators from the past month (July 2022).
- An RfC has been closed with consensus to add javascript that will show edit notices for editors editing via a mobile device. This only works for users using a mobile browser, so iOS app editors will still not be able to see edit notices.
- An RfC has been closed with the consensus that train stations are not inherently notable.
- The Wikimania 2022 Hackathon will take place virtually from 11 August to 14 August.
- Administrators will now see links on user pages for "Change block" and "Unblock user" instead of just "Block user" if the user is already blocked. (T308570)
- The arbitration case request Geschichte has been automatically closed after a 3 month suspension of the case.
- You can vote for candidates in the 2022 Board of Trustees elections from 16 August to 30 August. Two community elected seats are up for election.
- Wikimania 2022 is taking place virtually from 11 August to 14 August. The schedule for wikimania is listed here. There are also a number of in-person events associated with Wikimania around the world.
- Tech tip: When revision-deleting on desktop, hold ⇧ Shift between clicking two checkboxes to select every box in that range.
Administrators' newsletter – September 2022
[edit]News and updates for administrators from the past month (August 2022).
- A discussion is open to define a process by which Vector 2022 can be made the default for all users.
- An RfC is open to gain consensus on whether Fox News is reliable for science and politics.
- The impact report on the effects of disabling IP editing on the Persian (Farsi) Wikipedia has been released.
- The WMF is looking into making a Private Incident Reporting System (PIRS) system to improve the reporting of harmful incidents through easier and safer reporting. You can leave comments on the talk page by answering the questions provided. Users who have faced harmful situations are also invited to join a PIRS interview to share the experience. To sign up please email Madalina Ana.
- An arbitration case regarding Conduct in deletion-related editing has been closed. The Arbitration Committee passed a remedy as part of the final decision to create a request for comment (RfC) on how to handle mass nominations at Articles for Deletion (AfD).
- The arbitration case request Jonathunder has been automatically closed after a 6 month suspension of the case.
- The new pages patrol (NPP) team has prepared an appeal to the Wikimedia Foundation (WMF) for assistance with addressing Page Curation bugs and requested features. You are encouraged to read the open letter before it is sent, and if you support it, consider signing it. It is not a discussion, just a signature will suffice.
- Voting for candidates for the Wikimedia Board of Trustees is open until 6 September.
Administrators' newsletter – October 2022
[edit]News and updates for administrators from the past month (September 2022).
- Following an RfC, consensus was found that if the rationale for a block depends on information that is not available to all administrators, that information should be sent to the Arbitration Committee, a checkuser or an oversighter for action (as applicable, per ArbCom's recent updated guidance) instead of the administrator making the block.
- Following an RfC, consensus has been found that, in the context of politics and science, the reliability of FoxNews.com is unclear and that additional considerations apply to its use.
- Community comment on the revised Universal Code of Conduct enforcement guidelines is requested until 8 October.
- The Articles for creation helper script now automatically recognises administrator accounts which means your name does not need to be listed at WP:AFCP to help out. If you wish to help out at AFC, enable AFCH by navigating to Preferences → Gadgets and checking the "Yet Another AfC Helper Script" box.
- Remedy 8.1 of the Muhammad images case will be rescinded 1 November following a motion.
- A modification to the deletion RfC remedy in the Conduct in deletion-related editing case has been made to reaffirm the independence of the RfC and allow the moderators to split the RfC in two.
- The second phase of the 2021-22 Discretionary Sanctions Review closes 3 October.
- An administrator's account was recently compromised. Administrators are encouraged to check that their passwords are secure, and reminded that ArbCom reserves the right to not restore adminship in cases of poor account security. You can also use two-factor authentication (2FA) to provide an extra level of security.
- Self-nominations for the electoral commission for the 2022 Arbitration Committee elections open 2 October and close 8 October.
- You are invited to comment on candidates in the 2022 CUOS appointments process.
- An RfC is open to discuss whether to make Vector 2022 the default skin on desktop.
- Tech tip: You can do a fuzzy search of all deleted page titles at Special:Undelete.
Administrators' newsletter – November 2022
[edit]News and updates for administrators from the past month (October 2022).
- The article creation at scale RfC opened on 3 October and will be open until at least 2 November.
- An RfC is open to discuss having open requests for adminship automatically placed on hold after the seven-day period has elapsed, pending closure or other action by a bureaucrat.
- Eligible editors are invited to self-nominate themselves from 13 November 2022 until 22 November 2022 to stand in the 2022 Arbitration Committee elections.
- The arbitration case request titled Athaenara has been resolved by motion.
- The arbitration case Reversal and reinstatement of Athaenara's block has entered the proposed decision stage.
- AmandaNP, Mz7 and Cyberpower678 have been appointed to the Electoral Commission for the 2022 Arbitration Committee Elections. Xaosflux and Dr vulpes are reserve commissioners.
- The 2022 CheckUser and Oversight appointments process has concluded with the appointment of two new CheckUsers.
- You can add yourself to the centralised page listing time zones of administrators.
- Tech tip: Wikimarkup in a block summary is parsed in the notice that the blockee sees. You can use templates with custom options to specify situations like
{{rangeblock|create=yes}}
or{{uw-ublock|contains profanity}}
.
ArbCom 2022 Elections voter message
[edit]Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}}
to your user talk page. MediaWiki message delivery (talk) 00:25, 29 November 2022 (UTC)
Administrators' newsletter – December 2022
[edit]News and updates for administrators from the past month (November 2022).
- Consensus has been found in an RfC to automatically place RfAs on hold after one week.
- The article creation at scale RfC has been closed.
- An RfC on the banners for the December 2022 fundraising campaign has been closed.
- A new preference named "Enable limited width mode" has been added to the Vector 2022 skin. The preference is also shown as a toggle on every page if your monitor is 1600 pixels or wider. When disabled it removes the whitespace added by Vector 2022 on the left and right of the page content. Disabling this preference has the same effect as enabling the wide-vector-2022 gadget. (T319449)
- Eligible users are invited to vote on candidates for the Arbitration Committee until 23:59 December 12, 2022 (UTC). Candidate statements can be seen here.
- The proposed decision for the 2021-22 review of the discretionary sanctions system is open.
- The arbitration case Reversal and reinstatement of Athaenara's block has been closed.
- The arbitration case Stephen has been opened and the proposed decision is expected 1 December 2022.
- A motion has modified the procedures for contacting an admin facing Level 2 desysop.
- Tech tip: A single IPv6 connection usually has access to a "subnet" of 18 quintillion IPs. Add
/64
to the end of an IP in Special:Contributions to see all of a subnet's edits, and consider blocking the whole subnet rather than an IP that may change within a minute.
Administrators' newsletter – January 2023
[edit]News and updates for administrators from the past month (December 2022).
- Speedy deletion criterion A5 (transwikied articles) has been repealed following an unopposed proposal.
- Following the 2022 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Barkeep49, CaptainEek, GeneralNotability, Guerillero, L235, Moneytrees, Primefac, SilkTork.
- The 2021-22 Discretionary Sanctions Review has concluded with many changes to the discretionary sanctions procedure including a change of the name to "contentious topics". The changes are being implemented over the coming month.
- The arbitration case Stephen has been closed.
- Voting for the Sound Logo has closed and the winner is expected to be announced February to April 2023.
- Tech tip: You can view information about IP addresses in a centralised location using bullseye which won the Newcomer award in the recent Coolest Tool Awards.
Administrators' newsletter – February 2023
[edit]News and updates for administrators from the past month (January 2023).
|
|
- Following an RfC, the administrator policy now requires that prior written consent be gained from the Arbitration Committee to mark a block as only appealable to the committee.
- Following a community discussion, consensus has been found to impose the extended-confirmed restriction over the topic areas of Armenia and Azerbaijan and Kurds and Kurdistan.
- The Vector 2022 skin has become the default for desktop users of the English Wikipedia.
- The arbitration case Armenia-Azerbaijan 3 has been opened and the proposed decision is expected 24 February 2023.
- In December, the contentious topics procedure was adopted which replaces the former discretionary sanctions system. The contentious topics procedure is now in effect following an initial implementation period. There is a detailed summary of the changes and administrator instructions for the new procedure. The arbitration clerk team are taking suggestions, concerns, and unresolved questions about this new system at their noticeboard.
- Voting in the 2023 Steward elections will begin on 05 February 2023, 21:00 (UTC) and end on 26 February 2023, 21:00 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
- Voting in the 2023 Community Wishlist Survey will begin on 10 February 2023 and end on 24 February 2023. You can submit, discuss and revise proposals until 6 February 2023.
- Tech tip: Syntax highlighting is available in both the 2011 and 2017 Wikitext editors. It can help make editing paragraphs with many references or complicated templates easier.
Administrators' newsletter – March 2023
[edit]News and updates for administrators from the past month (February 2023).
|
|
- Following a request for comment, F10 (useless non-media files) has been deprecated.
- Following a request for comment, the Portal CSD criteria (P1 (portal subject to CSD as an article) and P2 (underpopulated portal)) have been deprecated.
- A request for comment is open to discuss making the closing instructions for the requested moves process a guideline.
- The results of the 2023 Community Wishlist Survey have been posted.
- Remedy 11 ("Request for Comment") of the Conduct in deletion-related editing case has been rescinded.
- The proposed decision for the Armenia-Azerbaijan 3 case is expected 7 March 2023.
- A case related to the Holocaust in Poland is expected to be opened soon.
- The 2023 appointees for the Ombuds commission are AGK, Ameisenigel, Bennylin, Daniuu, Emufarmers, Faendalimas, JJMC89, MdsShakil, Minorax and Renvoy as regular members and Zabe as advisory members.
- Following the 2023 Steward Elections, the following editors have been appointed as stewards: Mykola7, Superpes15, and Xaosflux.
- The Terms of Use update cycle has started, which includes a
[p]roposal for better addressing undisclosed paid editing
. Feedback is being accepted until 24 April 2023.
Requesting inputs
[edit]- Requesting inputs @ Wikipedia talk:Manual of Style/Legal#Attention to updating of MOS guidelines
- This request has been made to you since you seem to have had started page Wikipedia:Manual of Style/Legal
Bookku (talk) 17:27, 2 April 2023 (UTC)
Administrators' newsletter – April 2023
[edit]News and updates for administrators from the past month (March 2023).
|
|
- A community RfC is open to discuss whether reports primarily involving gender-related disputes or controversies should be referred to the Arbitration enforcement noticeboard.
- Some older web browsers will not be able to use JavaScript on Wikimedia wikis starting this week. This mainly affects users of Internet Explorer 11. (T178356)
- The rollback of Vector 2022 RfC has found no consensus to rollback to Vector legacy, but has found rough consensus to disable "limited width" mode by default.
- A link to the user's Special:CentralAuth page will now appear in the subtitle links shown on Special:Contributions. This was voted #17 in the Community Wishlist Survey 2023.
- The Armenia-Azerbaijan 3 case has been closed.
- A case about World War II and the history of Jews in Poland has been opened, with the first evidence phase closing 6 April 2023.
Administrators' newsletter – May 2023
[edit]News and updates for administrators from the past month (April 2023).
|
|
- A request for comment about removing administrative privileges in specified situations is open for feedback.
- Progress has started on the Page Triage improvement project. This is to address the concerns raised by the community in their 2022 WMF letter that requested improvements be made to the tool.
- The proposed decision in the World War II and the history of Jews in Poland case is expected 11 May 2023.
- The Wikimedia Foundation annual plan 2023-2024 draft is open for comment and input through May 19. The final plan will be published in July 2023.
Administrators' newsletter – June 2023
[edit]News and updates for administrators from the past month (May 2023).
|
|
- Following an RfC, editors indefinitely site-banned by community consensus will now have all rights, including sysop, removed.
- As a part of the Wikimedia Foundation's IP Masking project, a new policy has been created that governs the access to temporary account IP addresses. An associated FAQ has been created and individual communities can increase the requirements to view temporary account IP addresses.
- Bot operators and tool maintainers should schedule time in the coming months to test and update their tools for the effects of IP masking. IP masking will not be deployed to any content wiki until at least October 2023 and is unlikely to be deployed to the English Wikipedia until some time in 2024.
- The arbitration case World War II and the history of Jews in Poland has been closed. The topic area of Polish history during World War II (1933-1945) and the history of Jews in Poland is subject to a "reliable source consensus-required" contentious topic restriction.
- Following a community referendum, the arbitration policy has been modified to remove the ability for users to appeal remedies to Jimbo Wales.
Administrators' newsletter – July 2023
[edit]News and updates for administrators from the past month (June 2023).
- Contributions to the English Wikipedia are now released under the Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0) license instead of CC BY-SA 3.0. Contributions are still also released under the GFDL license.
- Discussion is open regarding a proposed global policy regarding third-party resources. Third-party resources are computer resources that reside outside of Wikimedia production websites.
- Two arbitration cases are currently open. Proposed decisions are expected 5 July 2023 for the Scottywong case and 9 July 2023 for the AlisonW case.
Administrators' newsletter – August 2023
[edit]News and updates for administrators from the past month (July 2023).
Interface administrator changes
- The tag filter on Special:NewPages and revision history pages can now be inverted. This allows hiding edits made by automated tools. (T334338)
- Special:BlockedExternalDomains is a new tool that allows easier blocking of plain domains (and their subdomains). This is more easily searchable and is faster for the software to use than the existing MediaWiki:Spam-blacklist. It does not support regex (for complex cases), URL path-matching, or the MediaWiki:Spam-whitelist. (T337431)
- The arbitration cases named Scottywong and AlisonW closed 10 July and 16 July respectively.
- The SmallCat dispute arbitration case is in the workshop phase.
Administrators' newsletter – September 2023
[edit]News and updates for administrators from the past month (August 2023).
|
|
- Following an RfC, TFAs will be automatically semi-protected the day before it is on the main page and through the day after.
- A discussion at WP:VPP about revision deletion and oversight for dead names found that
[s]ysops can choose to use revdel if, in their view, it's the right tool for this situation, and they need not default to oversight. But oversight could well be right where there's a particularly high risk to the person. Use your judgment
.
- Special:Contributions now shows the user's local edit count and the account's creation date. (T324166)
- The SmallCat dispute case has closed. As part of the final decision, editors participating in XfD have been reminded to be careful about forming
local consensus which may or may not reflect the broader community consensus
. Regular closers of XfD forums were also encouraged tonote when broader community discussion, or changes to policies and guidelines, would be helpful
.
- Tech tip: The "Browse history interactively" banner shown at the top of Special:Diff can be used to easily look through a history, assemble composite diffs, or find out what archive something wound up in.
Administrators' newsletter – November 2023
[edit]News and updates for administrators from the past month (October 2023).
Interface administrator changes
- The WMF is working on making it possible for administrators to edit MediaWiki configuration directly. This is similar to previous work on Special:EditGrowthConfig. A technical RfC is running until November 08, where you can provide feedback.
- There is a proposed plan for re-enabling the Graph Extension. Feedback on this proposal is requested.
- Eligible editors are invited to self-nominate themselves from 12 November 2023 until 21 November 2023 to stand in the 2023 Arbitration Committee elections.
- Xaosflux, RoySmith and Cyberpower678 have been appointed to the Electoral Commission for the 2023 Arbitration Committee Elections. BusterD is the reserve commissioner.
- Following a motion, the contentious topic designation of Prem Rawat has been struck. Actions previously taken using this contentious topic designation are still in force.
- Following several motions, multiple topic areas are no longer designated as a contentious topic. These contentious topic designations were from the Editor conduct in e-cigs articles, Liancourt Rocks, Longevity, Medicine, September 11 conspiracy theories, and Shakespeare authorship question cases.
- Following a motion, remedies 3.1 (All related articles under 1RR whenever the dispute over naming is concerned), 6 (Stalemate resolution) and 30 (Administrative supervision) of the Macedonia 2 case have been rescinded.
- Following a motion, remedy 6 (One-revert rule) of the The Troubles case has been amended.
- An arbitration case named Industrial agriculture has been opened. Evidence submissions in this case close 8 November.
- The Articles for Creation backlog drive is happening in November 2023, with 700+ drafts pending reviews for in the last 4 months or so. In addition to the AfC participants, all administrators and New Page Patrollers can conduct reviews using the helper script, Yet Another AFC Helper Script, which can be enabled in the Gadgets settings. Sign up here to participate!
ArbCom 2023 Elections voter message
[edit]Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}}
to your user talk page. MediaWiki message delivery (talk) 00:20, 28 November 2023 (UTC)
Administrators' newsletter – December 2023
[edit]News and updates for administrators from the past month (November 2023).
- Following a talk page discussion, the Administrators' accountability policy has been updated to note that while it is considered best practice for administrators to have notifications (pings) enabled, this is not mandatory. Administrators who do not use notifications are now strongly encouraged to indicate this on their user page.
- Following a motion, the Extended Confirmed Restriction has been amended, removing the allowance for non-extended-confirmed editors to post constructive comments on the "Talk:" namespace. Now, non-extended-confirmed editors may use the "Talk:" namespace solely to make edit requests related to articles within the topic area, provided that their actions are not disruptive.
- The Arbitration Committee has announced a call for Checkusers and Oversighters, stating that it will currently be accepting applications for CheckUser and/or Oversight permissions at any point in the year.
- Eligible users are invited to vote on candidates for the Arbitration Committee until 23:59 December 11, 2023 (UTC). Candidate statements can be seen here.
Administrators' newsletter – January 2024
[edit]News and updates for administrators from the past month (December 2023).
- Following the 2023 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Aoidh, Cabayi, Firefly, HJ Mitchell, Maxim, Sdrqaz, ToBeFree, Z1720.
- Following a motion, the Arbitration Committee rescinded the restrictions on the page name move discussions for the two Ireland pages that were enacted in June 2009.
- The arbitration case Industrial agriculture has been closed.
- The New Pages Patrol backlog drive is happening in January 2024 to reduce the backlog of articles in the new pages feed. Currently, there is a backlog of over 13,000 unreviewed articles awaiting review. Sign up here to participate!
Administrators' newsletter – February 2024
[edit]News and updates for administrators from the past month (January 2024).
- An RfC about increasing the inactivity requirement for Interface administrators is open for feedback.
- Pages that use the JSON contentmodel will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. (T326065)
- Following a motion, the Arbitration Committee adopted a new enforcement restriction on January 4, 2024, wherein the Committee may apply the 'Reliable source consensus-required restriction' to specified topic areas.
- Community feedback is requested for a draft to replace the "Information for administrators processing requests" section at WP:AE.
- Voting in the 2024 Steward elections will begin on 06 February 2024, 14:00 (UTC) and end on 27 February 2024, 14:00 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
- A vote to ratify the charter for the Universal Code of Conduct Coordinating Committee (U4C) is open till 2 February 2024, 23:59:59 (UTC) via Secure Poll. All eligible voters within the Wikimedia community have the opportunity to either support or oppose the adoption of the U4C Charter and share their reasons. The details of the voting process and voter eligibility can be found here.
- Community Tech has made some preliminary decisions about the future of the Community Wishlist Survey. In summary, they aim to develop a new, continuous intake system for community technical requests that improves prioritization, resource allocation, and communication regarding wishes. Read more
- The Unreferenced articles backlog drive is happening in February 2024 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!
Administrators' newsletter – March 2024
[edit]News and updates for administrators from the past month (February 2024).
|
|
- Phase I of the 2024 RfA review is now open for participation. Editors are invited to review, comment on, and propose improvements to the requests for adminship process.
- Following an RfC, the inactivity requirement for the removal of the interface administrator right increased from 6 months to 12 months.
- The mobile site history pages now use the same HTML as the desktop history pages. (T353388)
- The 2024 appointees for the Ombuds commission are だ*ぜ, AGK, Ameisenigel, Bennylin, Daniuu, Doǵu, Emufarmers, Faendalimas, MdsShakil, Minorax, Nehaoua, Renvoy and RoySmith as members, with Vermont serving as steward-observer.
- Following the 2024 Steward Elections, the following editors have been appointed as stewards: Ajraddatz, Albertoleoncio, EPIC, JJMC89, Johannnes89, Melos and Yahya.
Administrators' newsletter – April 2024
[edit]News and updates for administrators from the past month (March 2024).
- An RfC is open to convert all current and future community discretionary sanctions to (community designated) contentious topics procedure.
- The Toolforge Grid Engine services have been shut down after the final migration process from Grid Engine to Kubernetes. (T313405)
- An arbitration case has been opened to look into "the intersection of managing conflict of interest editing with the harassment (outing) policy".
- Editors are invited to sign up for The Core Contest, an initiative running from April 15 to May 31, which aims to improve vital and other core articles on Wikipedia.
Administrators' newsletter – May 2024
[edit]News and updates for administrators from the past month (April 2024).
- Phase I of the 2024 requests for adminship review has concluded. Several proposals have passed outright and will proceed to implementation, including creating a discussion-only period (3b) and administrator elections (13) on a trial basis. Other successful proposals, such as creating a reminder of civility norms (2), will undergo further refinement in Phase II. Proposals passed on a trial basis will be discussed in Phase II, after their trials conclude. Further details on specific proposals can be found in the full report.
- Partial action blocks are now in effect on the English Wikipedia. This means that administrators have the ability to restrict users from certain actions, including uploading files, moving pages and files, creating new pages, and sending thanks. T280531
- The arbitration case Conflict of interest management has been closed.
- This may be a good time to reach out to potential nominees to ask if they would consider an RfA.
- A New Pages Patrol backlog drive is happening in May 2024 to reduce the number of unreviewed articles in the new pages feed. Currently, there is a backlog of over 15,000 articles awaiting review. Sign up here to participate!
- Voting for the Universal Code of Conduct Coordinating Committee (U4C) election is open until 9 May 2024. Read the voting page on Meta-Wiki and cast your vote here!
Administrators' newsletter – June 2024
[edit]News and updates for administrators from the past month (May 2024).
- Phase II of the 2024 RfA review has commenced to improve and refine the proposals passed in Phase I.
- The Nuke feature, which enables administrators to mass delete pages, will now correctly delete pages which were moved to another title. T43351
- The arbitration case Venezuelan politics has been closed.
- The Committee is seeking volunteers for various roles, including access to the conflict of interest VRT queue.
- WikiProject Reliability's unsourced statements drive is happening in June 2024 to replace {{citation needed}} tags with references! Sign up here to participate!
Administrators' newsletter – July 2024
[edit]News and updates for administrators from the past month (June 2024).
- Local administrators can now add new links to the bottom of the site Tools menu without using JavaScript. Documentation is available on MediaWiki. (T6086)
- The Community Wishlist is re-opening on 15 July 2024. Read more
Administrators' newsletter – August 2024
[edit]News and updates for administrators from the past month (July 2024).
- Global blocks may now target accounts as well as IP's. Administrators may locally unblock when appropriate.
- Users wishing to permanently leave may now request "vanishing" via Special:GlobalVanishRequest. Processed requests will result in the user being renamed, their recovery email being removed, and their account being globally locked.
- The Arbitration Committee appointed the following administrators to the conflict of interest volunteer response team: Bilby, Extraordinary Writ
Administrators' newsletter – September 2024
[edit]News and updates for administrators from the past month (August 2024).
- Following an RfC, there is a new criterion for speedy deletion: C4, which
applies to unused maintenance categories, such as empty dated maintenance categories for dates in the past
. - A request for comment is open to discuss whether Notability (species) should be adopted as a subject-specific notability guideline.
- Following a motion, remedies 5.1 and 5.2 of World War II and the history of Jews in Poland (the topic and interaction bans on My very best wishes, respectively) were repealed.
- Remedy 3C of the German war effort case ("Cinderella157 German history topic ban") was suspended for a period of six months.
- The arbitration case Historical Elections is currently open. Proposed decision is expected by 3 September 2024 for this case.
- Editors can now enter into good article review circles, an alternative for informal quid pro quo arrangements, to have a GAN reviewed in return for reviewing a different editor's nomination.
- A New Pages Patrol backlog drive is happening in September 2024 to reduce the number of unreviewed articles and redirects in the new pages feed. Currently, there is a backlog of over 13,900 articles and 26,200 redirects awaiting review. Sign up here to participate!
Administrators' newsletter – October 2024
[edit]News and updates for administrators from the past month (September 2024).
- Administrator elections are a proposed new process for selecting administrators, offering an alternative to requests for adminship (RfA). The first trial election will take place in October 2024, with candidate sign-up from October 8 to 14, a discussion phase from October 22 to 24, and SecurePoll voting from October 25 to 31. For questions or to help out, please visit the talk page at Wikipedia talk:Administrator elections.
- Following a discussion, the speedy deletion reason "File pages without a corresponding file" has been moved from criterion G8 to F2. This does not change what can be speedily deleted.
- A request for comment is open to discuss whether there is a consensus to have an administrator recall process.
- The arbitration case Historical elections has been closed.
- An arbitration case regarding Backlash to diversity and inclusion has been opened.
- Editors are invited to nominate themselves to serve on the 2024 Arbitration Committee Electoral Commission until 23:59 October 8, 2024 (UTC).
- If you are interested in stopping spammers, please put MediaWiki talk:Spam-whitelist and MediaWiki talk:Spam-blacklist on your watchlist, and help out when you can.
Administrators' newsletter – November 2024
[edit]News and updates for administrators from the past month (October 2024).
- Following a discussion, the discussion-only period proposal that went for a trial to refine the requests for adminship (RfA) process has been discontinued.
- Following a request for comment, Administrator recall is adopted as a policy.
- Mass deletions done with the Nuke tool now have the 'Nuke' tag. This change will make reviewing and analyzing deletions performed with the tool easier. T366068
- RoySmith, Barkeep49 and Cyberpower678 have been appointed to the Electoral Commission for the 2024 Arbitration Committee Elections. ThadeusOfNazereth and Dr vulpes are reserve commissioners.
- Eligible editors are invited to self-nominate from 3 November 2024 until 12 November 2024 to stand in the 2024 Arbitration Committee elections.
- The Arbitration Committee is seeking volunteers for roles such as clerks, access to the COI queue, checkuser, and oversight.
- An unreferenced articles backlog drive is happening in November 2024 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!
"Attitude flying" listed at Redirects for discussion
[edit]The redirect Attitude flying has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2024 November 23 § Attitude flying until a consensus is reached. Shhhnotsoloud (talk) 12:26, 23 November 2024 (UTC)
Administrators' newsletter – December 2024
[edit]News and updates for administrators from the past month (November 2024).
Interface administrator changes
- Following an RFC, the policy on restoration of adminship has been updated. All former administrators may now only regain the tools following a request at the Wikipedia:Bureaucrats' noticeboard within 5 years of their most recent admin action. Previously this applied only to administrators deysopped for inactivity.
- Following a request for comment, a new speedy deletion criterion, T5, has been enacted. This applies to template subpages that are no longer used.
- Technical volunteers can now register for the 2025 Wikimedia Hackathon, which will take place in Istanbul, Turkey. Application for travel and accommodation scholarships is open from November 12 to December 10, 2024.
- The arbitration case Yasuke (formerly titled Backlash to diversity and inclusion) has been closed.
- An arbitration case titled Palestine-Israel articles 5 has been opened. Evidence submissions in this case will close on 14 December.