I recognize that this user page belongs to the Wikipedia project and not to me personally. As such, I recognize that I am expected to respectfully abide by community standards as to the presentation and content of this page, and that if I do not like these guidelines, I am welcome either to engage in reasonable discussion about it, to publish my material elsewhere, or to leave the project.
My real name is Larry Pieniazek and I like LEGO(r) Brand building elements. Feel free to mail me with comments or concerns if you don't want to post. As a note, I rarely get involved in anything any more, I confine my activity at WMF projects to a little light editing here and there, so your email is most likely to get a response on your talk page that I got it and I'm not going to do anything about it.
Here about a BLP that's persistently getting vandalized and you want me to semi protect it? Leave a note below, (User:Lar/Liberal Semi is no longer in use) and I or one of my TPWs will get it.
Here to leave me a message? Response time varies depending on where I'm active... Ping me if it's truly urgent, or find another admin.
Here about accountability? see my accountability page. Note: The apparent listification of the category (it's back but may go away again) does not change my commitment to my recallability in any way
Being a "grumpy old curmudgeon", I have certain principles governing this talk page which I expect you to adhere to if you post here. (This talk page is my "territory", (although I acknowledge it's not really mine, it's the community's) and I assume janitorial responsibility for it.)
I may, without notice, refactor comments to put like with like, correct indents, or retitle sections to reflect their contents more clearly. If I inadvertently change the meaning of anything, please let me know so I can fix it!
While I reserve the right to delete comments I find egregiously poor form, I am normally opposed to doing so and use monthly random archives instead. If you post here, your words will remain here and eventually in the archives, so please do not delete them, use strikeouts. In other words, think carefully about what you say rather than posting hastily or heatedly.
Edit warring here is particularly bad form. One of my WP:TPW's may well issue a short block, so don't do it.
Interpersonal communication does not work when messages are left on individual users' talk pages rather than threaded, especially when a third party wishes to read or reply.
Being a "bear of very little brain", I get easily confused when trying to follow conversations that bounce back and forth, so I've decided to try the convention that many others seem to use, aggregation of messages on either your talk page or my talk page. If the conversation is about an article I will try to aggregate on the article's talk page.
If the conversation is on your talk page or an article talk page, I will watch it.
If the conversation is on my talk page or an article talk page and I think that you may not be watching it, I will link to it in a note on your talk page, or in the edit summary of an empty edit. But if you start a thread here, please watch it.
I may mess up, don't worry, I'll find it eventually. Ping me if you really need to.
please note this is a personal preference rather than a matter of site policy
Latest comment: 5 years ago1 comment1 person in discussion
Hello, Lar. 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.
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.
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.
Latest comment: 5 years ago2 comments2 people in discussion
To ask for deletion or not, I'll have to pass this idea off to you, the local contact on that page, since my real-life limitations have temporarily worsened to include a 3rd-degree burn up my shin. More pictures (eventually) for the Commons, though! However, I did fix a redlink on the above-mentioned page (see also the Edit summary) based on the following discussing the deleted, redlinked page:
14:59, April 21, 2015 Maintenance script (talk | contribs) moved page User:CommonsTickerBot to User:CommonsTickerBot~enwiki without leaving a redirect (Automatically moved page while renaming the user "CommonsTickerBot" to "CommonsTickerBot~enwiki") (revert)
TBH I have completely forgotten what this is. It was a long time ago. IIRC I set up the page at the request of some folks on Commons working on it. Near as I can tell, it's not actually doing anything, and if you follow the links to Commons, it isn't running at that end either. I have no issue if the consensus is to delete. It's not hurting anything being there but it also could confuse people. ++Lar: t/c22:18, 3 April 2019 (UTC)Reply
Administrators' newsletter – April 2019
Latest comment: 5 years ago1 comment1 person in discussion
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.
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)
Latest comment: 5 years ago1 comment1 person in discussion
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.
Latest comment: 5 years ago3 comments2 people in discussion
I'm just dropping in to say hello and find out how you're doing (and if you remember me!). Haven't seen you in ages. --kingboyk (talk) 17:38, 22 July 2019 (UTC) (Steve)Reply
Hi! Yes indeed I do. I'm around sporadically. I kept my admin bit and use it for this and that but haven't edited as much as back in the day. I don't think I've edited a Beatles article in a coons age. I did not realise you had gotten so many KLF articles to FA! Well done. ++Lar: t/c17:33, 23 July 2019 (UTC)Reply
Good stuff. Yep, we had a really good run with the KLF articles - 4 featured, 3 remain so (4/5 if you include The Orb). My partner in crime on that project retired so we called it a day. I still check into WP:BEATLES occasionally. --kingboyk (talk) 19:22, 23 July 2019 (UTC)Reply
Administrators' newsletter – August 2019
Latest comment: 5 years ago1 comment1 person in discussion
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.
Latest comment: 4 years ago7 comments2 people in discussion
I am wondering about Wiki burnout. How long do editors stay and why do they leave. I found a retired section listing missing editors. For some reason I found your site. Are you still an administrator? You seem to have had an active past and set opinions. Are you still an editor? Do you know of any Wiki research on average length of editor participation? It may just be ones own life that keeps people to come and go. Anyway feel free to ignore this question if you like. Eschoryii (talk) 06:23, 25 January 2020 (UTC)Reply
Hi. First, some housekeeping, I moved your section to the bottom where it belongs. Talk page sections should usually be created in chronological order.
To answer your questions... I'm still an admin here, but I gave up all other permissions on all other wikis. That was 98% by choice after I was not reconfirmed as a Steward (the 2%) in a process that I found highly controversial, not transparent, and unfair. That took some wind out of my sails so I stepped back. However if you review my contribution history, you'll see I still keep my hand in. Mostly I fix typos and other small things. I am very aware that WMF is very concerned about burnout but I don't know where to find particular studies that they have done. I suggest you ask at the wp:Village Pump for more info.(you probably want the miscellaneous section.) More active editors will have resources to share. Be prepared to explain why you want ot know, beyond curiosity... I hope that helps. ++Lar: t/c17:32, 26 January 2020 (UTC)Reply
Thanks for your response. It was timely so you are still active. I am a political scientist. Who is in control and how is power used? I only edit films I have recently watched. I spend most of my time reading talk pages. I love to watch edit wars. Wiki likes to eat its young and offend and lose their most experienced contributors. I learn more each year but I have not taken the full plunge. Reliable sourcing is more important than truth and accuracy. Consensus changes. Be bold only means do as we say in our guidelines. Any one can edit but do not offend an editor that watches his own set of articles. A watchlist is good to protect an article that suddenly is in the news. I just found an editor called Isaacsorry. He has been around only 4 months and just makes major edits in areas of music and Michael Jackson. I do not understand why he can just come in and take over. He has encountered pushback but the system is not served by a self appointed prolific actor. New editors need mentors. Your advice telling to be prepared to explain my motives is good advice. However there are days I just want to leave. I like the concept of Wikipedia but it is not my project. The first editor I followed was Lugnuts. I do not know him. He takes no prisoners. He knows the rules and is one of the top editors. He is everywhere. Someone asked him whether he had time for a real world job and he gets all offended. He has created a new article for any person who ever competed in the Olympics. The rules state you are notable if you are an Olympian. How is the encyclopedia improved with one line separate articles on each Olympic participant? The man is excellent on film and cricket. He knows and advises editors on the Wiki way. Sorry to take your time for me to express my frustrations about the Wiki world. Your approach to come and go as you please may need to be my answer.Eschoryii (talk) 01:16, 27 January 2020 (UTC)Reply
Greetings from Indonesia. I don't agree with all your characterizations but I do agree with enough of them to validate your discomfort. Taking a wikibreak is often a good approach. Don't get too invested in things. I avoid using WP for research into current events. But when I want to know how dragonflies mate, it's superb. HTH ++Lar: t/c02:07, 31 January 2020 (UTC)Reply
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. [1]
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.
Latest comment: 4 years ago1 comment1 person in discussion
Happy First Edit Day!
Have a very happy first edit anniversary!
I'll be honest, when I took a lot at your contribs I actually said aloud ″Wow.″ Even with your substantial contributions, you still prioritise quality over quantity! Over 15 years you have contributed a great lot to Wikipedia. Thank you for all the effort you have made.
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.
12 years makes less difference than you might think.
Latest comment: 3 years ago1 comment1 person in discussion
I wrote this article ( Royal_Papua_New_Guinea_Constabulary ) basically in one long blast, 12 years ago. This diff shows that it hasn't changed that much since...
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.
Latest comment: 3 years ago1 comment1 person in discussion
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).
I was just mulling over some details of the LEGO oeuvre at AfD. I was thinking that we need an expert and recalled that you were such. But the LEGO catalogue is now so extensive that perhaps you are burnt out on that too? But I am pleased to find that you still maintain a token presence here. Happy New Year! Andrew🐉(talk) 15:59, 23 January 2021 (UTC)Reply
Thanks. I don't see much LEGO activity at AfD or elsewhere but, as it happens, today we have LUGNET which has been relisted twice and so is in need of input. For balance, perhaps we should also notify @Lugnuts:! Andrew🐉(talk) 09:26, 25 January 2021 (UTC)Reply
I think the deletion case was 11 years ago. That was a long time ago. I'm not sure I have any value to add, sorry. ++Lar: t/c02:57, 1 March 2021 (UTC)Reply
Administrators' newsletter – March 2021
Latest comment: 3 years ago1 comment1 person in discussion
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.
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.
Latest comment: 2 years ago1 comment1 person in discussion
Thanks so much for participating in Phase 1 of the RfA 2021 review. 8 out of the 21 issues discussed were found to have consensus. Thanks to our closers of Phase 1, Primefac and Wugapodes.
The following had consensus support of participating editors:
Corrosive RfA atmosphere
The atmosphere at RfA is deeply unpleasant. This makes it so fewer candidates wish to run and also means that some members of our community don't comment/vote.
Level of scrutiny
Many editors believe it would be unpleasant to have so much attention focused on them. This includes being indirectly a part of watchlists and editors going through your edit history with the chance that some event, possibly a relatively trivial event, becomes the focus of editor discussion for up to a week.
Standards needed to pass keep rising
It used to be far easier to pass RfA however the standards necessary to pass have continued to rise such that only "perfect" candidates will pass now.
Too few candidates
There are too few candidates. This not only limits the number of new admin we get but also makes it harder to identify other RfA issues because we have such a small sample size.
"No need for the tools" is a poor reason as we can find work for new admins
The following issues had a rough consensus of support from editors:
Lifetime tenure (high stakes atmosphere) Because RfA carries with it lifetime tenure, granting any given editor sysop feels incredibly important. This creates a risk adverse and high stakes atmosphere.
Admin permissions and unbundling There is a large gap between the permissions an editor can obtain and the admin toolset. This brings increased scrutiny for RFA candidates, as editors evaluate their feasibility in lots of areas.
RfA should not be the only road to adminship Right now, RfA is the only way we can get new admins, but it doesn't have to be.
Please consider joining the brainstorming which will last for the next 1-2 weeks. This will be followed by Phase 2, a 30 day discussion to consider solutions to the problems identified in Phase 1.
There are 2 future mailings planned. One when Phase 2 opens and one with the results of Phase 2. To opt-out of future mailings, please remove yourself here.
If you have uploaded other non-free media, consider checking that you have specified the non-free rationale on those pages too. You can find a list of 'file' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "File" from the dropdown box. Note that any non-free media lacking such an explanation will be deleted one week after they have been tagged, as described in section F6 of the criteria for speedy deletion. If the file is already gone, you can still make a request for undeletion and ask for a chance to fix the problem. If you have any questions, please ask them at the Media copyright questions page. Thank you.
This bot DID NOT nominate any file(s) for deletion; please refer to the page history of each individual file for details. Thanks, FastilyBot (talk) 10:00, 25 October 2021 (UTC)Reply
For the record, I initially created the article where this image is used. On review, I don't think the article really needs it. Any fair use rationale I could imagine seems a bit of a stretch, to be honest. So I am going to remove the image and let it be deleted. ++Lar: t/c22:49, 25 October 2021 (UTC)Reply
RfA Reform 2021 Phase 2 has begun
Following a 2 week brainstorming period and a 1 week proposal period, the 30 day discussion of changes to our Request for Adminship process has begun. Following feedback on Phase 1, in order to ensure that the largest number of people possible can see all proposals, new proposals will only be accepted for the for the first 7 days of Phase 2. The 30 day discussion is scheduled to last until November 30. Please join the discussion or even submit your own proposal.
There is 1 future mailing planned with the results of Phase 2. To opt-out of future mailings, please remove yourself here.
16:13, 31 October 2021 (UTC)
Administrators' newsletter – November 2021
Latest comment: 2 years ago1 comment1 person in discussion
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.
Latest comment: 2 years ago1 comment1 person in discussion
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:06, 7 December 2021 (UTC)
RFA 2021 Completed
The 2021 re-examination of RFA has been completed. 23 (plus 2 variants) ideas were proposed. Over 200 editors participated in this final phase. Three changes gained consensus and two proposals were identified by the closers as having the potential to gain consensus with some further discussion and iteration. Thanks to all who helped to close the discussion, and in particular Primefac, Lee Vilenski, and Ymblanter for closing the most difficult conversations and for TonyBallioni for closing the review of one of the closes.
The following proposals gained consensus and have all been implemented:
Revision of standard question 1 to Why are you interested in becoming an administrator? Special thanks to xaosflux for help with implementation.
A new process, Administrative Action Review (XRV) designed to review if an editor's specific use of an advanced permission, including the admin tools, is consistent with policy in a process similar to that of deletion review and move review. Thanks to all the editors who contributed (and are continuing to contribute) to the discussion of how to implement this proposal.
Removal of autopatrol from the administrator's toolkit. Special thanks to Wugapodes and Seddon for their help with implementation.
The following proposals were identified by the closers as having the potential to gain consensus with some further discussion and iteration:
Editors who wish to discuss these ideas or other ideas on how to try to address any of the six issues identified during phase 1 for which no proposal gained are encouraged to do so at RFA's talk page or an appropriate village pump.
A final and huge thanks all those who participated in this effort to improve our RFA process over the last 4 months.
This is the final update with no further talk page messages planned.
01:46, 30 December 2021 (UTC)
Administrators' newsletter – January 2022
Latest comment: 2 years ago1 comment1 person in discussion
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.
Latest comment: 2 years ago1 comment1 person in discussion
Do I still have any Talk Page Watchers? I was recently involved in Sarah Gillis and there was a merge, but it was botched. The person who did it was not paying attention to WP:CWW and did the merge via copypaste. So the bulk of the history is lost. It needs to be undone, and the merge done properly. I can do it but lack time and lack the knowledge of modern tools. If there's a TPW (with admin) that might want to take this on, please let me know... Thanks!!! ++Lar: t/c17:40, 17 February 2022 (UTC)Reply
Administrators' newsletter – March 2022
Latest comment: 2 years ago1 comment1 person in 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)
The article will be discussed at Wikipedia:Articles for deletion/Pghbridges.com (3rd nomination) until a consensus is reached, and anyone, including you, 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.
Thanks for letting me know, I have commented there. This is a nom by an IP who seems to be on a deletion nom run. What has changed since the last two times it was kept, I wonder? ++Lar: t/c04:14, 23 April 2022 (UTC)Reply
Administrators' newsletter – May 2022
Latest comment: 2 years ago1 comment1 person in discussion
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.
Orphaned non-free image File:Royal Papua New Guinea Constabulary logo.jpg
Latest comment: 2 years ago2 comments2 people in discussion
⚠ Thanks for uploading File:Royal Papua New Guinea Constabulary logo.jpg. 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).
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.
Latest comment: 1 year ago2 comments2 people in discussion
The Original Barnstar
Because someone who's been around as long as you and done as much good work as you have, probably doesn't have enough barnstars. Andre🚐16:17, 2 September 2022 (UTC)Reply
Why, thank you! I only pop in from time to time these days... but I appreciate it. I'll add it to my collection :) ++Lar: t/c16:19, 2 September 2022 (UTC)Reply
Please vote in the 2022 Wikimedia Foundation Inc. Board of Trustees election
Latest comment: 1 year ago1 comment1 person in discussion
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}}.
Latest comment: 1 year ago1 comment1 person in discussion
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.
Administrative permissions and inactivity reminder
Latest comment: 1 year ago3 comments2 people in discussion
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.Thank you for your past contributions to the project. — JJMC89 bot00:28, 1 January 2023 (UTC)Reply
Thanks for letting me know, dear robot... (so this message is for my talk page watchers more than anything else). My edit frequency has been increasing again although not to original levels, and I wish to retain my admin privs, I have enabled 2FA. ++Lar: t/c05:54, 2 January 2023 (UTC)Reply
Checking my contribs by eye, it looks like I'm not THAT far below the average, and most of the shortfall is in the very earliest year of the 5 year period... Time to find some interesting topics and get to work, I guess :) ++Lar: t/c06:05, 2 January 2023 (UTC)Reply
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.Thank you for your past contributions to the project. — JJMC89 bot 00:28, 1 January 2023 (UTC)
