Please sign and date your entry by adding "~~~~" at the end.
Please indent your posts with ":" if replying to an existing topic (or "::" if replying to a reply).
I will generally respond here to comments that are posted here, rather than replying via your Talk page (or the article Talk page, if you are writing to me here about an article), so you may want to watch this page until you are responded to, or specifically let me know where you'd prefer the reply.
This user talk page might be watched by friendly talk page stalkers, which means that someone other than me might reply to your query. Their input is welcome and their help with messages that I cannot reply to quickly is appreciated.
Lutici/Pomerania-Medcom closure
Dear Feezo, I am pretty much at loss about what to do after your closure of the Lutici/Pomerania-Medcom. Per its own definition, Medcom is the final step in content dispute resolution, so there are no other steps in DR to pursue at this point. What I had preferred was the mediated RfC you suggested, what I am missing is a statement pointing out the course of action that needs to follow now. If the dispute can not be resolved even with a mediator, it is even more unlikely to be resolved without a mediator, and if the final stage of DR is aborted, it seems pointless to start the DR process anew. Skäpperöd (talk) 07:52, 2 May 2013 (UTC)[reply]
Skäpperöd—this dispute is unusual in that up to this point it has been almost entirely between you and VM. Most cases that are accepted for mediation involve more than two editors. There is little that a mediator can do when one side is unwilling to participate. Per Medcom policy, mediation is a voluntary process.
There are still a number of avenues of dispute resolution open, with the best option being RfC. Unfortunately, I do not believe you will receive much cooperation from VM in running it. His proposed question "why hasn't Skapperod presented any sources but just keeps endlessly arguing in circles" indicates that either he is not taking the dispute resolution process seriously, or that he is treating this as a user conduct issue. In either case, mediation is no longer appropriate.
I did/do take the process seriously and I rather think that the inability to provide sources (despite repeated requests) would be more indicative of "not taking the dispute resolution process seriously". And like I said at the page, if the central question is the reliability of Michalek as a source, then the natural thing to do would be to re-list it at WP:RSN.Volunteer Marek17:13, 2 May 2013 (UTC)[reply]
Thank you for your response, Feezo. I have copypasted the thoughts I presented on the Medcom page for an RfC draft [1] to a sandbox page - User:Skäpperöd/MedcomRfC - and intend to go from there atp, per your advice. And yes, I would appreciate it very much if you reviewed/advised there, feel free to edit that page as you want.
VM, are you willing to participate in preparing the RfC draft? There are more issues than merely the reliability question, so RSN again would not resolve the dispute. Skäpperöd (talk) 20:24, 2 May 2013 (UTC)[reply]
It would help to resolve the part of the dispute that we keep getting stuck on. I think it might also be worth while to try RSN regardless of whether an RfC happens or not.Volunteer Marek20:28, 2 May 2013 (UTC)[reply]
I don't think the issue can be resolved by RSN alone. For example, if the consensus is that Michalek is reliable, how do we resolve the perceived conflicts between Michalek and other sources? If Michalek is found unreliable, it doesn't necessarily mean the map is inaccurate. These are the judgement calls for which we should seek consensus through an RfC. RSN isn't really intended for dispute resolution.
Note that closing the mediation doesn't mean I've given up on this — just that I considered a continuing back-and-forth discussion unlikely to succeed. If we focus on accurately and neutrally framing the issues, I think we can make progress. Feezo(send a signal | watch the sky)23:58, 2 May 2013 (UTC)[reply]
But there are no conflicts between Michalek and other sources. That's the key thing here. And if Michalek's reliability isn't question then that should be dropped from the RfC. Reliability of sources shouldn't be determined by RfC, which in my experience is often driven as much by various political alliances and fillibustering as well as consideration of policy.Volunteer Marek03:41, 3 May 2013 (UTC)[reply]
It is not necessary for there to be conflicts in order to ask this question—the only condition is that conflicts are perceived. In any case, it is not necessary to try to persuade me. My role as mediator—now in unofficial capacity—means that I am restricting myself to defining the parameters of the dispute. Clearly, Skäpperöd believes that Michalek conflicts with other sources, or his inclusion would not be an issue. He may be right, or he may be wrong. But either way, we must present both your cases to the community so that a consensus may be reached. Feezo(send a signal | watch the sky)23:35, 3 May 2013 (UTC)[reply]
Hey Feezo, I have not noticed that a discussion had continued here, and it seems moot to comment there now. I am about done with the draft, it took me longer than I had initially thought (RL), and I appreciate that you had tweaked it a bit. You are welcome to make changes. I am not certain how we proceed though, since VM has not proposed anything until now. I again asked him on his tp but so far I got no response. I think the best course of action would be to wait some time for a response (VM) and allow further tweaking (two days?), and then run the RfC either on the Medcom page or on talk:Pomerania during the High Middle Ages (that article would be affected by all proposals, whereas Lutici is only affected by the 1121/map proposals)? Maybe the 1121 proposal won't be challenged by VM though and could be implemented w/o RfC. Skäpperöd (talk) 19:18, 7 May 2013 (UTC)[reply]
The article will be discussed at Wikipedia:Articles for deletion/Arthur Bowen until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. DoctorKubla (talk) 19:32, 14 May 2013 (UTC)[reply]
Entertainment Publications
Hi Feezo,
I'm wondering why Entertainment Publications page was deleted. We value our Wikipedia page and want people to know about the business. We just obtained it and the text of the old Wikipedia page is of sentimental value to us.
There is another issue—Wikipedia's function is that of an encyclopedia, not a business directory or marketing service, and articles are expected to be written from a neutral point of view. I encourage you to read our FAQ for organizations for more information. You will also find instructions there on how to proceed should you wish to recreate the article.
On the subject of the status of Puerto Rico, I'm not exactly a newbie, but the discussion is off the rails. I'm accused of being the IP who started the discussion unreasonably, when I tried to make it reasonable. My instinct now is to do more research and return to the topic in a year, except other editors keep bringing it up on United States, Puerto Rico, Insular articles. In this round, I suggested to Ahnoneemoos that language be crafted for a RfC, he ran it to a DRN, and no volunteer took it. Four editors showed up for unequivocal “unincorporated” without notice of a controversy, three editors showed up for allowing a statement of the controversy without losing “unincorporated”. It seemed to be a runaway train without a volunteer. That can't be good.
At the article Puerto Rico it reports its status as “unincorporated”, which it is for some purposes, as sourced, such as the revenue clause of the Constitution at the Downes" Supreme Court case. I source the existence of a scholarly controversy over the status of Puerto Rico at Foreign in a Domestic Sense, p. 17, and an element of the controversy “incorporated” at Boston College Law Review, p.1175 which is not currently reflected in the article.
To me, the issue revolves around including sourced material in the article narrative. -- Whether to allow both sides of a controversy into the article introduction -- how PR is "unincorporated" and "incorporated" as alternately sourced. And the bias of WP should be to include sourced information. But I am missing something, it cannot be easy, TransporterMan recused himself at the DRN.
The response of opposing editors is, there is no controversy but my original research and soapboxing. If I point out editors here have not supported the “unincorporated” with scholarly sources, -- including articles found in “Foreign in a Domestic Sense” -- the answer seems to be that scholarly sources have no place in the discussion in the face of their individual interpretation of online “official” sources. At some basic level I sought to improve the article with reliably sourced information, and I got my hat handed to me. What do you think is reasonable for a maturing editor to do? TheVirginiaHistorian (talk) 20:43, 5 February 2014 (UTC)[reply]
Tony the Marine's post on your talk page explains the situation pretty well, I think. Political disputes are among the most difficult to resolve, since viewpoints tend to be inflexible and subjective. For this reason, I've found that structured processes like RfC, which can establish consensus within a larger body of editors, tend to be more successful than freeform debate in the original group. Feezo(send a signal | watch the sky)10:23, 7 February 2014 (UTC)[reply]
Okay, I kicked off an RfC at Puerto Rico, but for this round I don't think there is much more that I can say on the subject to be more persuasive. I placed a notice of the RfC on the project pages which list Puerto Rico as priority, Puerto Rico, Latin America, United States, to publicized it. In the mean time I want to double check my interpretation of sources with a notice on reliable sources noticeboard. Thanks. TheVirginiaHistorian (talk) 10:40, 7 February 2014 (UTC)[reply]
Mediation
Dear Feezo,
I noticed you were an on the Mediation Committee. I appreciate your guidance. I have politely the discussed a recent addition to the article Israel on the talk page. Some editors Talk:Israel#Palestinian state are refusing to cooperate in any form of dispute resolution. One is willing, but only if the resolution is binding. I strongly believe this issue requires the assistance of an admin and I favor dispute resolution and/or mediation, but their resistance is bring us to a standstill. I strongly support resolving this issue peacefully and I ask for your assistance and/or advice.
You may read the talk page yourself. If you would like my summary of the dispute, I say it as follows:
There is currently a dispute as to how to describe the geography of Israel in the lead of the article. Originally, the article read that Israel shared borders with the West Bank and Gaza Strip (among other borders). Some editors have insisted on adding "the Palestinian territories (or State of Palestine) comprising the West Bank and Gaza Strip on the east and southwest respectively," ignoring WP:UNDUE for the lead.
All reliable secondary sources put forward do not refer to the territories of the West Bank and Gaza as Palestine. In addition, encyclopedias and other sources that have country profiles for Israel do not refer to Israel as bordering "Palestine," nor do they have entries on any country called Palestine. (See, e.g., Encyclopedia Britannica; Encyclopedia Columbia; Library of Congress Country Studies, Washington Post Country Profiles; Infoplease). All sources indicate a Palestinian state is yet to be established, and it does not appear on any mainstream maps. AP, NY Times. The sources likewise never use terms like "president of Palestine," etc. In addition, they identify incidents originating there as from the West Bank or Gaza Strip, never as Palestine. Same with most Wikipedia articles.[2]
Indeed, discussion of the status of Palestinian statehood is important, and it is included in the following paragraph, where it discusses the status of Israeli–Palestinian negotiations in the lead. Further explanation is included in the body. The intro describing Israel's geography should be kept neutral and factual. Reliable secondary sources guide us and they are in agreement with their terminology (using West Bank & Gaza Strip, or Palestinian territories).
Hello—I notice that Georgewilliamherbert has imposed a temporary editing restriction on you regarding the article in question. While your frustration is understandable, I highly suggest allowing it to expire before deciding whether to pursue this topic further. Feezo(send a signal | watch the sky)23:23, 17 February 2014 (UTC)[reply]
Please consider edit on handcuff article
Dear Freezo,
I see that you have monitored the edit request page of the Handcuff article. Could you please consider the proposed edit that I posted there on Feb. 28, 2014. Thank you.
Include "Robotic Handcuff" Article
Dear Wikipedia, I would like to resubmit my Robo Restraint article for inclusion in the Handcuffs page. It was removed because the remover said it was a failed technology. I don't think that was a fair appraisal for removal, in that many items discussed in Wikipedia are not in use at the present time. The USPTO has issued a patent on this device and it has been demonstrated successfully at several law enforcement trade shows. Additionally, I don't think that the article is written as an advertisement and would ask that any lines that sound like an advertisement be pointed out to me specifically. I also would like to upload a picture of the device for the article. Thank you for your time and consideration.
Article as follows:
A recent development in restraint technology is robotic handcuffs. According to Officer.com magazine, the device is mounted to the inside rear window sill of a police vehicle. The automated restraint system is operated by the officer activating a belt worn remote control. The system allows the officer to maintain a safe distance, while commanding the suspect to place his hands in the extended Kevlar loops. He then closes the loops, using the remote control. [1] The loops automatically tighten, until they contact the wrists, and then the bands are loosened slightly to achieve the correct fit. This takes place in about 1/2 second. The officer can then proceed with his investigation, or turn his/her attention to a second suspect. The officer can subsequently, apply standard handcuffs to the suspect and then releases him/her from the robo restraint for transport. Robo Restraint can be used in conjunction with a law enforcement or military robot to restraint an individual without officer intervention. [2] Bshul (talk) 22:07, 28 February 2014 (UTC) — Preceding unsigned comment added by Bshul (talk • contribs)
Sorry for the delay in replying — you're correct that a failed or obsolete technology may be valid for inclusion in Wikipedia. However, to avoid the problem of giving the technology undue weight, you'll need to demonstrate its significance: for example, did the it result in some kind of social change, or spur further technical advancement? This would have to be supported by reliable, third party sources; a patent and a magazine article probably aren't sufficient. Let me know if you have any questions. Feezo(send a signal | watch the sky)21:35, 30 March 2014 (UTC)[reply]
Telford Memories
Hi there,
My Wiki page Telford Memories was deleted, using the speedy deletion option, what can I do to get my page re-instated?
The Telford Memories page is of great importance in the Telford area of Shropshire in the UK, in a time of economic downturn & recession, this page has lifted the spirits of a whole town, most Facebook pages have around 1,000 Members, Telford Memories is fast approaching 10.000 Members, this Local History page has stirred up some kind of self pride & community spirit among it's residents, would the inclusion of a local press release added onto the page about how the page came to prominence ?
Because of this page, it is expected that on 21st September 2014, that over 21,000 people will assemble at the base of the Wrekin Hill in Shropshire Uk to break four Guinness World Records on the same day, Telford Memories has started something that will go down in the History of the Uk.
Welcome to Wikipedia! — I deleted the page under Wikipedia's criteria for speedy deletion A7 — no disrespect intended towards Telford or this organization.
Although anyone is allowed to create an article, the page needs to demonstrate that the subject meets the relevant notability guidelines to be eligible for permanent inclusion. In this case, the guideline is Wikipedia:Notability (web) — particularly, the criteria section. If you think you can show that the page meets the criteria, feel free to submit an articles for creation request or create a userspace draft. I can recover the deleted contents for you if you like, but it would probably not be a good idea to recreate the article until another editor has had a chance to review it. Wikipedia:Your first article may be helpful in getting started. If it turns out that the website doesn't meet the notability requirements, you could help improve the Telford article instead.
dear freezo,
May I please have the wiki definition of "failed invention"...without a stated wiki definition, wouldn't labeling my newly patented invention as a "failed invention" seems arbitrary and invalid....please advise.
Failure alone doesn't disqualify an invention from inclusion, but a section on a "failed invention that did not have a substantive or lasting impact documented by secondary sources" (my interpretation) would likely constitute undue weight. Feezo(send a signal | watch the sky)05:30, 31 March 2014 (UTC)[reply]
The user Blokni mě, whom you blocked about a month ago, is using their talk page to make personal attacks [3] - it might be a good idea to remove their editing rights to that page. Cheers, --bonadeacontributionstalk10:06, 1 June 2014 (UTC)[reply]
Feezo, I have added the Pro case for using M's quote. However, could you please sign your RfC draft proposal so that other editors don't get the idea that I put that forward. Btw, I think the draft looks good.shaidar cuebiyar (talk) 11:04, 14 August 2014 (UTC)[reply]
Request for removal of semi-protection from my userpage
Hi, a few years back you helped me out by semi-protecting my userpage (at the time it drew ire from vandals due to anti-vandalism work). Nowadays I work in quieter areas so I think it'll be fine as unprotected, if you wouldn't mind. Many thanks, benmoore15:04, 29 July 2014 (UTC)[reply]
Hi, just writing to say sorry, but I don't think I'll be chiming in on the RfC. I'm a bit frazzled from my own months-long, drawn-out battle over content on a different page, and I will be quite busy this month with offline concerns. Chubbles (talk) 14:50, 3 October 2014 (UTC)[reply]
Re: Ayers Rock RfM
Feezo, my undiluted thanks to you for your patience, wisdom, and above all the enormous amount of time given to the RfM. You could see that I was getting cabin fever due to the extended nature of the negotiations. It was like being in a meeting at work for six months! I don't like meetings. CaesarsPalaceDude (talk) 01:30, 2 November 2014 (UTC)[reply]
I was scanning WP:TOPRED and I noticed Anthony Ilott, which says you said it was deleted from a deletion discussion. Is that accurate? I didn't see a deletion discussion linked there, as is normally done on redlink pages. I'm not 100% sure the guy is notable, but google news threw out some hits. For example: www.ex@miner.com/article/british-actor-anthony-llott (bl@cklisted) Because you said it was deleted as a result of a deletion discussion, do I need special permission to re-create it? Thanks. Biosthmors (talk) pls notify me (i.e. {{U}}) while signing a reply, thx 21:33, 21 November 2014 (UTC)[reply]
Ayers Rock: possible COI
Having dealt with CPD in an adversarial situation I may not be impartial in judging whether he has crossed over from being a general editor at Ayers Rock to display conflicts of issue. He has acknowledged communicating, via intermediaries, with former band members and a family member of one. He has modified content in the article based on those communications and on discussions held with individuals he acknowledges are OR. Some of this is discussed at the talkpage's subsection How close? I proposed that a template be added to the talkpage to alert editors to the situation. CPD has not yet responded to that request.shaidar cuebiyar (talk) 23:41, 12 January 2015 (UTC)[reply]
Ayers Rock (band):creation of new lead
Feezo, following your participation at Ayers Rock (band), there has been a growing level of cooperation between the warring parties. With more work having been done, and issues resolved, I have written a draft of the new lead, which you may read at the sandbox. Your thoughts, and opinions are sought on every aspect re suitability as the new lead. Thanking you in advance. CaesarsPalaceDude (talk) 10:24, 1 March 2015 (UTC)[reply]
More problems at Ayers Rock (band)
Feezo, a hostile atmosphere has descended at Ayers Rock, in that editors are refusing to listen to each other (again), and the situation has escalated to the extent that the participation of an administrator or a very experienced editor is required. Discussion/arguments have centred on proposed major changes to the structure of the article. These discussions became deadlocked. Recently, I have requested that shaidar cuebiyar participate with me in "some form of mediation or RfC or Third Party opinion process." See [4] In spite of this, and the fact that he does not have a consensus for such change, shaidar cuebiyar has forged ahead regardless, dismissing my opposition. These important changes require a more thorough examination by the community, or the opinion of an expert Third Party. shaidar cuebiyar's actions of 21 May (see these diffs [5], and [6]) in radically altering the structure are examples of behaviour described in Examples of disruptive editing point 4. Could you or another suitably qualified editor please join us to restore order? Could you advise, please, if I should take further action such as posting at ANI? CaesarsPalaceDude 06:31, 21 May 2015 (UTC)
I dispute CaesarsPalaceDude's contention here, I believe he himself made changes to the structure of the article while a discussion was in progress between three editors. Myself, CaeserPalaceDude and Nøkkenbuer.
During that discussion, CaesarsPalaceDude attempted to limit my responses both in time and in position on the article's talkpage.
I supported Nøkkenbuer's call for the article to be more in tune with best practices at FA and GA music articles on artists. Hence a consensus of two editors against a third had been reached.
CaesarsPalaceDude's phrase "I have guillotined the discussion, and taken pre-emptive action by transfering the proposed article into article space" some five days ago summarises his position.
I pointed out that he was not listening to the advice of two others: both Nøkkenbuer and I preferred a different structure to the article's or to his more recent proposal but he forged ahead with his preferred option without stopping.
Once he made the changes he wanted, he called on me to not edit the article from its then-form for some three weeks. I refused to adhere to his injunction.
I believe CaesarsPalaceDude is attempting to exert ownership of the article and its talkpage.
I believe I have the right to present the article in a better style than it was and one which is more in tune with FA and GA music article criteria than the one which existed at that time.shaidar cuebiyar (talk) 07:15, 21 May 2015 (UTC)[reply]
CaesarsPalaceDude, I think Shaidar cuebiyar's concerns over the namespacing of the draft are worth consideration. The principle I think applies here is "be bold, but not reckless". Perhaps it was worth trying to jump-start the discussion—we're always free to admit that it didn't work and go back, after all. Feezo(send a signal | watch the sky)01:27, 23 May 2015 (UTC)[reply]
Feezo, thankyou for your thoughtful reply, which I will continue to study, and consider. The recent activities at this article are like some people's golf swings; there is so much which is wrong that it's difficult to know where to start. Viewed from another angle, the "very early" placing of the draft into namespace precipitated a large amount of editing, and much more focused discussion at the Talk page. I'm interested in your comment: "we're always free to admit that it didn't work and go back". I don't wish to focus on "didn't work", but rather on "go back". I'm not sure I understand, and could you, please, expand on that thought? Also, is the discussion about the structure of the article dead, and does Shaidar cuebiyar's flimsy majority count as a consensus now that he has gone ahead, and changed the article to his structure without my agreement? The benefit of your experience would be greatly appreciated. CaesarsPalaceDude (talk) 02:09, 23 May 2015 (UTC)[reply]
Orphaned non-free image File:Onion 64x64.png
⚠
Thanks for uploading File:Onion 64x64.png. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Invitation to subscribe to the edit filter mailing list
Hi, as a user in the edit filter manager user group we wanted to let you know about the new wikipedia-en-editfilters mailing list. As part of our recent efforts to improve the use of edit filters on the English Wikipedia it has been established as a venue for internal discussion by edit filter managers regarding private filters (those only viewable by administrators and edit filter managers) and also as a means by which non-admins can ask questions about hidden filters that wouldn't be appropriate to discuss on-wiki. As an edit filter manager we encourage you to subscribe; the more users we have in the mailing list the more useful it will be to the community. If you subscribe we will send a short email to you through Wikipedia to confirm your subscription, but let us know if you'd prefer another method of verification. I'd also like to take the opportunity to invite you to contribute to the proposed guideline for edit filter use at WP:Edit filter/Draft and the associated talk page. Thank you! Sam Walton (talk) and MusikAnimaltalk18:22, 9 September 2015 (UTC)[reply]
Hello, Feezo. You have new messages at Feezo's talk page. You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
Hello,
A page I created, Niyya Farms. Sorry if it did not meet Wikipedia's guidelines. I will remove every biased reference and make the article very neutral if you can please restore it and give me pointers where necessary.
Thank you
RE: Deleted Page
Hello, Feezo. You have new messages at Feezo's talk page. You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
No, I am not an affiliate of the company but I did lift content from their website. That was poorly done now that I have ready the copyright policy. How do I fix this?
Hello there, sorry just remembered to check this. Yes I was interested in asking for rollback. I know my numbers are down but I am interested in helping out more and as the holidays have passed, I will have more time to assist. :) --Giooo95 (talk) 05:19, 10 January 2016 (UTC)[reply]
The standard minimum is 200 mainspace edits. Your contributions look good so far, but I don't see a lot of reversion work yet. I recommend you keep using Twinkle and then ask again after building a record of good reverts. Let me know if you have any questions. Feezo(send a signal | watch the sky)17:10, 10 January 2016 (UTC)[reply]
Deletion of OC&C Strategy Consultants page - clarity on reason would be helpful
You have today deleted the OC&C Strategy Consultants page and I'd like some clarity on why. The user who put the page up for speedy deletion said it replicated an earlier deleted page, while it is based on some of the same content (it is a company, it's core business is just that and can't be changed) it has had an overhaul. The content is factual, has multiple links, increased notability which is all verifiable. What is the reason for deletion other than it speaks of the core business as per a previous page? (Alltherightthings (talk) 08:40, 26 July 2016 (UTC))[reply]
Thanks for your continued support to help us get this right. I've read the additional links you shared and have again reviewed the content and also run a comparison against other consultancy pages. Hopefully you will agree this is a purely fact based page that can be promoted back to the live site. ThanksAlltherightthings (talk) 18:24, 16 September 2016 (UTC)[reply]
For some reason I am accused of making edits on Wikipedia. I read Wikipedia, but I have never edited it. I just wanted you to clear that up, please. Either that, or someone is using my IP to do some stupid stuff.
Hi — if you didn't make the edits, then don't worry about the warnings. We know that IP addresses, especially mobile ones, are often shared. If people are making bad edits on an address you share, the worst that's likely to happen is a temporary block from editing. You can avoid this in most cases by creating an account. Let me know if you have any further questions or concerns. Feezo(send a signal | watch the sky)04:40, 20 August 2016 (UTC)[reply]
Extended confirmed protection
Hello, Feezo. 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.
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:47, 23 September 2016 (UTC)
Please consider reactivation at MedCom
This is being sent to you because you are listed as an emeritus member of MedComand an examination of your contribution page suggests that you are still active at en-Wikipedia. MedCom is currently down to three or four active members (there are more than that on the active member list, but some of them have not edited Wikipedia in quite awhile). We have a current case awaiting a mediator which is receiving no response from the request for a mediator sent on the MedCom mailing list a couple of days ago, Wikipedia:Requests for mediation/Expulsion of Cham Albanians. Would you please consider reactivating your membership, taking that case, or both? If you're interested in doing so and are not still on the MedCom mailing list, please just let me know and I'll reactivate you and add you to the list. Best regards, TransporterMan (talk·contribs) 19:43, 5 October 2016 (UTC) (current MedCom chairperson)[reply]
Hi, The online custom framing page should not have been deleted. Online custom framing is not an alternative to picture framing (like block printing) it is the process of ordering a custom picture frame through an online retailer.
Please reinstate the page.
Thanks,
Zach — Preceding unsigned comment added by Zacharysegal (talk • contribs) 18:13, 25 October 2016 (UTC)[reply]
At the time of deletion, the article, in its entirety, read:
Online Custom Framing refers to the growing market in the United States of getting art, photography, memorabilia custom framed via online retailers.
Two-Factor Authentication now available for admins
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:32, 12 November 2016 (UTC)[reply]
A new user right for New Page Patrollers
Hi Feezo.
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.
Hello, Feezo. 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.
shift2 deleted pageKaarenwv (talk) 00:08, 26 November 2016 (UTC)
not sure why you deleted my page? was in process of working on it. not sure why it violates any rules. was just going to state what the company is and what we do, just like any other company on wikipedia. perhaps i am confused as i have never created a page before....if you can help me that would be great thank you.
Following an RfC, an activity requirement is now in place for bots and bot operators.
Technical news
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.
JohnCD (John Cameron Deas) passed away on 30 December 2016. John began editing Wikipedia seriously during 2007 and became an administrator in November 2009.
Hello, Feezo. 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.
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.
Please be aware that your signature uses deprecated <font> tags, which are causing Obsolete HTML tags lint errors. Also, your signature uses a font color control that has no effect because it is overridden by automatic wikilink colors.
You are encouraged to change
<span style="font-family: Palatino Linotype, Book Antiqua, Palatino, serif;" color="#BBAED0">[[User:Feezo|Feezo]] <font size="-2">[[User_talk:Feezo|(send a signal]] | [[Special:Contributions/Feezo|watch the sky]])</font></span> : Feezo(send a signal | watch the sky)
to
<span style="font-family: Palatino Linotype, Book Antiqua, Palatino, serif;">[[User:Feezo|Feezo]] <span style="font-size: x-small">[[User_talk:Feezo|(send a signal]] | [[Special:Contributions/Feezo|watch the sky]])</span></span> : Feezo(send a signal | watch the sky)
I think you selected the wrong option when blocking Special:Contributions/107.77.241.11, 'cause they're blocked indefinitely. Given that it was the first block and over four months ago, I've unblocked the IP. I'll monitor their contributions for a few days, but please let me know if for some reason you did mean to indef an IP. ~ Amory(u • t • c)20:56, 3 February 2018 (UTC)[reply]
Thanks for the heads up - I don't recall any special reason for an indef block other than the continuing bad behavior after multiple Cluebot warnings. But I agree with your reasoning, so I have no objection to removing it. Feezo(send a signal | watch the sky)22:25, 3 February 2018 (UTC)[reply]
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.
Technical news
A tagwill 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.
Arbitration
The Arbitration Committee has enacted a change to the discretionary sanctions procedure which requires administrators to add a standardizededitnotice 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.
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.
Technical news
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 featurecontains_all that edit filter managers may use to check if one or more strings are all contained in another given string.
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.
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.
There will soon be a calendar widget at Special:Block, making it easier to set expiries for a specific date and time.
Arbitration
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.
Miscellaneous
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.
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.
Technical news
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.
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.
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.
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.
It is now easier for blocked mobile users to see why they were blocked.
Arbitration
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.
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.
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.
Miscellaneous
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.
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.
Technical news
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.
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.
Technical news
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 is article_text which is now page_title.
Abuse filters can now use how old a page is. The variable is page_age.
Arbitration
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.
There is an open request for comment on Meta regarding the creation a new user group for global edit filter management.
Technical news
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.
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.
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.
Arbitration
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.
Hello, Feezo. 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.
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".
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.
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.
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.
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}}.
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.
Technical news
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:
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.
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.
7&6=thirteen (☎) has given you a Dobos torte to enjoy! Seven layers of fun because you deserve it.
To give a Dobos torte and spread the WikiLove, just place {{subst:Dobos Torte}} on someone else's talkpage, whether it be someone you have had disagreements with in the past or a good friend.
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.
Technical news
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.
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.
Hi, you recently deleted the page I created about Casey Christopher, you gave the reason that it does not have enough citation and it looks like mare advertisements.
I failed to understand why you think that? If you had any questions, then you should have nominated the article for deletion and not speedy deletion. So that I had a fare chance to contest for it.
I understand writing biography of living people are the hardest but I did my research and I believe this to be on wikipedia.
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.
Technical news
A new tool is available to help determine if a given IP is an open proxy/VPN/webhost/compromised host.
Arbitration
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 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.
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.
Hi, please clarify your block rationale for blocking KeithCu as per NOTHERE. I see a few talk page contributions and no mainspace edits that are disruptive. I see your block as a bad block. Sir Joseph(talk)15:39, 16 April 2019 (UTC)[reply]
If you don't plan to be active on the site, you should consider resigning your administrator privileges. There's been a push lately to make it easier to remove the permissions due to inactivity. When I look at your edit history over the last 7 years, I don't see any compelling reason or activity that requires you to keep them. Mr Ernie (talk) 18:07, 17 April 2019 (UTC)[reply]
Recently, several Wikipedia admin accounts were compromised. The admin accounts were desysopped on an emergency basis. In the past, the Committee often resysopped admin accounts as a matter of course once the admin was back in control of their account. The committee has updated its guidelines. Admins may now be required to undergo a fresh Request for Adminship (RfA) after losing control of their account.
What do I need to do?
Only to follow the instructions in this message.
Check that your password is unique (not reused across sites).
Check that your password is strong (not simple or guessable).
Enable Two-factor authentication (2FA), if you can, to create a second hurdle for attackers.
How can I find out more about two-factor authentication (2FA)?
Administrator account security (Correction to Arbcom 2019 special circular)
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.
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.
Arbitration
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 so will 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.
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.
Miscellaneous
The previously discussed unblocking of IP addresses indefinitely-blocked before 2009 was approved and has taken place.
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).
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.
Miscellaneous
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.
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.
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.
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 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.
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.
Technical news
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 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.
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.
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.
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 than reasonably construed.
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.
Technical news
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. [7]
Arbitration
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 an RfC, the blocking policy was changed to state that sysops must not undo or alter CheckUser or Oversight blocks, rather than should not.
A request for comment confirmed that sandboxes of established but inactive editors may not be blanked due solely to inactivity.
Technical news
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 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.
Miscellaneous
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.
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.
Arbitration
A motion was passed to enact a 500/30 restriction on articles related to the history of Jews and antisemitism in Poland during World War II (1933–45), including the Holocaust in Poland. Article talk pages where disruption occurs may also be managed with the stated restriction.
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.
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.
Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. 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.
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.
By motion, standard discretionary sanctions have been temporarily authorizedfor 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).
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 asks if sysops may place the General sanctions/Coronavirus disease 2019 editnotice template on pages in scope that do not have page-specific sanctions?
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.
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.
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.
Technical news
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)
The user group oversight will be renamed to suppress. This is for technical reasons. You can comment at T112147 if you have objections.
Arbitration
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.
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.
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.
Technical news
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.
Arbitration
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.
An RfC is open to add a delay of one week from nomination to deletion for G13 speedy deletions.
Technical news
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)
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.
Technical news
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.
Arbitration
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.
Hi there. I was going to create a page for Erik Wolf of the WFTA but received the message "A page with this title has previously been moved or deleted.
If you are creating a new page with different content, please continue. If you are recreating a page similar to the previously deleted page, or are unsure, please first contact the user(s) who performed the action(s) listed below." Just wanted to verify if these are different subjects or the same one. Thanks! EpicCupcake19 (talk) 10:10, 6 September 2021 (UTC)[reply]
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.
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.
Miscellaneous
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.
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.
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. 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.
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)
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.
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:05, 7 December 2021 (UTC)
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.
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.
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.
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.
The user group oversight will be renamed suppress 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.
A RfC is open to discuss prohibiting draftification of articles over 90 days old.
Technical news
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)
Access to Special:RevisionDelete has been expanded to include users who have the deletelogentry and deletedhistory 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)
Hey I was hoping for a long time if you would interview me I'm kind of shy so I would like if we could matey do it low key plus I realy want to get in your ear I have had so many things that happend realy rraly crazy unreal stuff that I can't tell all I was going to wait till I got my money or least till my gut told me it was time and also this ain't the first time for me doing God's work this is my time I first time I'm not I. A war but is the icing on the cake so I want to get done like the way no one else thinks I can this is the plan I always wanted to tell my story so please keep this in mind THANK YOU and I understand if you think it's not right for if anything it would be awesome to sit down — Preceding unsigned comment added by 2600:1009:B015:594E:3958:43A9:418F:F6D3 (talk) 23:35, 2 May 2022 (UTC)[reply]
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.
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.
Arbitration
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 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.
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.
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.
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)
Arbitration
The arbitration case request Geschichte has been automatically closed after a 3 month suspension of the case.
Miscellaneous
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.
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.
Technical news
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 emailMadalina Ana.
Arbitration
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.
Miscellaneous
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.
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.
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.
Arbitration
Remedy 8.1 of the Muhammad images case will be rescinded 1 November following a motion.
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.
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}}.
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.
An RfC on the banners for the December 2022 fundraising campaign has been closed.
Technical news
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)
Arbitration
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 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.
Miscellaneous
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.
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.
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.
Following a request for comment, the Portal CSD criteria (P1 (portal subject to CSD as an article) and P2 (underpopulated portal)) have been deprecated.
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.
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 request for comment about removing administrative privileges in specified situations is open for feedback.
Technical news
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.
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.
Technical news
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.
Arbitration
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 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.
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 to note when broader community discussion, or changes to policies and guidelines, would be helpful.
Miscellaneous
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.
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.
Miscellaneous
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!
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.
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.
Arbitration
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.
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.
An RfC about increasing the inactivity requirement for Interface administrators is open for feedback.
Technical news
Pages that use the JSON contentmodel will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. (T326065)
Arbitration
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.
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 Toolforge Grid Engine services have been shut down after the final migration process from Grid Engine to Kubernetes. (T313405)
Arbitration
An arbitration case has been opened to look into "the intersection of managing conflict of interest editing with the harassment (outing) policy".
Miscellaneous
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.
Administrative permissions and inactivity reminder
This is a reminder that established policy provides for removal of the administrative permissions of users who have made fewer than 100 edits over a 60-month period. You are receiving this annual reminder since you have averaged less than 50 edits per year over the last 5 years.
Inactive administrators are encouraged to reengage with 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 be engaged with the project in the foreseeable future, please consider voluntarily resigning your administrative permissions by making a request at the bureaucrats' noticeboard.
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
Local administrators can now add new links to the bottom of the site Tools menu without using JavaScript. Documentation is available on MediaWiki. (T6086)
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.
Thanks for uploading File:Onion 64x64.png. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
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.
The arbitration case Historical Elections is currently open. Proposed decision is expected by 3 September 2024 for this case.
Miscellaneous
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.
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.
The Wikimedia Foundation is conducting a survey of Wikipedians to better understand what draws administrators to contribute to Wikipedia, and what affects administrator retention. We will use this research to improve experiences for Wikipedians, and address common problems and needs. We have identified you as a good candidate for this research, and would greatly appreciate your participation in this anonymous survey.
You do not have to be an Administrator to participate.
The survey should take around 10-15 minutes to complete. You may read more about the study on its Meta page and view its privacy statement .
Please find our contact on the project Meta page if you have any questions or concerns.
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
I recently invited you to take a survey about administration on Wikipedia. If you haven’t yet had a chance, there is still time to participate– we’d truly appreciate your feedback. The survey is anonymous and should take about 10-15 minutes to complete. You may read more about the study on its Meta page and view its privacy statement.
Hello! Voting in the 2024 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 2 December 2024. 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.
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.
.jpg)
