This is an archive of past discussions with User:SQL. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
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)
Bots Newsletter, December 2021
Bots Newsletter, December 2021
Graphs are unavailable due to technical issues. Updates on reimplementing the Graph extension, which will be known as the Chart extension, can be found on Phabricator and on MediaWiki.org.
BRFA activity by month
Welcome to the eighth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Maintainers disappeared to parts unknown... bots awakening from the slumber of æons... hundreds of thousands of short descriptions... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.
Our last issue was in August 2019, so there's quite a bit of catching up to do. Due to the vast quantity of things that have happened, the next few issues will only cover a few months at a time. This month, we'll go from September 2019 through the end of the year. I won't bore you with further introductions — instead, I'll bore you with a newsletter about bots.
Overall
Between September and December 2019, there were 33 BRFAs. Of these, Y 25 were approved, and 8 were unsuccessful (N2 3 denied, ? 3 withdrawn, and 2 expired).
TParis goes away, UTRSBot goes kaput: Beeblebroxnoted that the bot for maintaining on-wiki records of UTRS appeals stopped working a while ago. TParis, the semi-retired user who had previously run it, said they were "unlikely to return to actively editing Wikipedia", and the bot had been vanquished by trolls submitting bogus UTRS requests on behalf of real blocked users. While OAuth was a potential fix, neither maintainer had time to implement it. TParis offered to access to the UTRS WMFLabs account to any admin identified with the WMF: "I miss you guys a whole lot [...] but I've also moved on with my life. Good luck, let me know how I can help". Ultimately, SQL ended up in charge. Some progress was made, and the bot continued to work another couple months — but as of press time, UTRSBot has not edited since November 2019.
Curb Safe Charmer adopts reFill: TAnthonypointed out that reFill 2's bug reports were going unanswered; creator Zhaofeng Li had retired from Wikipedia, and a maintainer was needed. As of June 2021, Curb Safe Charmer had taken up the mantle, saying: "Not that I have all the skills needed but better me than nobody! 'Maintainer' might be too strong a term though. Volunteers welcome!"
(You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)
Scripts++ Newsletter – Issue 22
Hello everyone, and welcome to the 22nd issue of the Wikipedia Scripts++ Newsletter. This issue will be covering new and updated user scripts from the past seven months (June through December 2021).
Got anything good? Tell us about your new, improved, old, or messed-up script here!
Featured script
LuckyRename, by Alexis Jazz, is this month's featured script. LuckyRename makes requesting file moves easier, and automates the many steps in file moving (including automatic replacement of existing usage). Give it a shot!
Updated scripts
SD0001: hide-reverted-edits has been updated to take into account changes in reversion tools like Twinkle and RedWarn.
ClaudineChionh: SkinSwitcher (a fork and update of Eizen's script) provides an options menu/toolbox/toolbar allowing users to view a given page in MediaWiki's default skins.
Wikipedia:User scripts/Ranking is a sortable table of Wikipedia's thousand-or-so most commonly used scripts; it includes their author, last modification date, installation count, and sometimes a short description.
Toolhub is a community managed catalog of software tools used in the Wikimedia movement. Technical volunteers can use Toolhub to document the tools that they create or maintain. All Wikimedians can use Toolhub to search for tools to help with their workflows and to create lists of useful tools to share with others.
draft-sorter sorts AfC drafts by adding WikiProject banners to their talk pages. It supersedes User:Enterprisey/draft-sorter, adding a few features and fixing some bugs.
BooksToSfn adds a portlet link in Visual Editor's source mode editing, in main namespace articles or in the user's Sandbox. When clicked, it converts one {{cite book}} inside a <ref>...</ref> tag block into an {{Sfn}}.
diffedit enables editing directly from viewing a diff "when, for instance, you notice a tiny mistake deep into an article, and don't want to edit the entire article and re-find that one line to fix that tiny mistake".
warnOnLargeFile warns you if you're about to open a very large file (width/height >10,000px or file size >100 MB) from a file page.
QuickDiff (by OneTwoThreeFall at Fandom) lets you quickly view any diff link on a wiki, whether on Recent Changes, contribs pages, history pages, the diff view itself, or elsewhere. For more information, view its page on Fandom.
talkback creates links after user talk page links like this: |C|TB (with the first linking to the user's contributions, and the latter giving the option of sending a {{talkback}} notice). It also adds a [copy] link next to section headers.
diff-link shows "copy" links on history and contributions pages that copy an internal link to the diff (e.g., Special:Diff/1026402230) to your clipboard when clicked.
auto-watchlist-expiry automatically watchlists every page you edit for a user-definable duration (you can still pick a different time using the dropdown, though).
generate pings generates the wikitext needed to ping all members of a category, up to 50 editors (the limit defined by MediaWiki).
share ExpandTemplates url allows for easy sharing of your inputs to Special:ExpandTemplates. It adds a button that, when clicked, copies a shareable URL to your exact invocation of the page, like this. Other editors do not need to have this script installed in order to access the URL generated.
show tag names shows the real names of tags next to their display names in places such as page revision histories or the watchlist.
ColourContrib color-codes the user contributions page so that pages you've edited last are sharply distinguished from pages where another editor was the last to edit the page.
All in all, some very neat scripts were written in these last few months. Hoping to see many more in the next issue -- drop us a line on the talk page if you've been writing (or seeing) anything cool and good. Filling in for DannyS712, this has been jp×g. Take care, and merry Christmas! jp×g07:30, 24 December 2021 (UTC)
Season's greetings and Merry Christmas to you and your family. Have a wonderful holiday season. Cheers! RV (talk) 03:50, 25 December 2021 (UTC)
Merry Christmas, SQL!
Good morning, SQL! I wish you and your family the best for Christmas and the new year. Here's hoping that 2022 is a better year for us all. Thank you for everything that you do for the project...regardless of how it may sometimes seem, your work is very greatly appreciated. Be well.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. jp×g14:56, 29 December 2021 (UTC)
Merchandise giveaway nomination
A token of thanks
Hi SQL! I've nominated you (along with all other active admins) to receive a solstice season gift from the WMF. Talk page stalkers are invited to comment at the nomination. Enjoy! Cheers, {{u|Sdkb}}talk ~~~~~
@Sdkb - I sincerely appreciate the nomination, but I'm going to respectfully decline. Someday, when they come back in stock, I'll just buy one out of my own pocket. SQLQuery Me!02:07, 2 January 2022 (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.
What I have seen that Luckyernie aka Blogs19 is always creating a new account and creating self-promotional article 'Susovan Sonu Roy' through different spelling; randomly editing articles at beginning for some days rapidly so that they gain EC status so that he can move pages. Also, adding his name and sponsered/paid reference to his claim in Bengali TV soaps. He is also doing the same with other language Wikipedia projects like Bengali, Hindi, German, French etc. He has also posted many admins and editors to create his page and review them directly posting at their talk pages with his email addresses in English Wikipedia. All detais are available in SPI report.42.105.0.17 (talk) 14:05, 17 January 2022 (UTC)
Hello, SQL. Please check your email; you've got mail! Message added 12:27, 16 January 2022 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
Graphs are unavailable due to technical issues. Updates on reimplementing the Graph extension, which will be known as the Chart extension, can be found on Phabricator and on MediaWiki.org.
BRFA activity by month
Welcome to the ninth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Vicious bot-on-bot edit warring... superseded tasks... policy proposals... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.
After a long hiatus between August 2019 and December 2021, there's quite a bit of ground to cover. Due to the vastness, I decided in December to split the coverage up into a few installments that covered six months each. Some people thought this was a good idea, since covering an entire year in a single issue would make it unmanageably large. Others thought this was stupid, since they were getting talk page messages about crap from almost three years ago. Ultimately, the question of whether each issue covers six months or a year is only relevant for a couple more of them, and then the problem will be behind us forever.
Of course, you can also look on the bright side – we are making progress, and this issue will only be about crap from almost two years ago. Today we will pick up where we left off in December, and go through the first half of 2020.
Overall
In the first half of 2020, there were 71 BRFAs. Of these, Y 59 were approved, and 12 were unsuccessful (with N2 8 denied, ? 2 withdrawn, and 2 expired).
January 2020
Yeah, you're not gonna be able to get away with this anymore.
A new Pywikibot release dropped support for Python 3.4, and it was expected that support for Python 2.7 would be removed in coming updates. Toolforge itself planned to drop Python 2 support in 2022.
On February 1, some concerns were raised about ListeriaBot performing "nonsense" edits. Semi-active operator Magnus Manske (who originally coded the Phase II software|precursor of MediaWiki) was pinged. Meanwhile, the bot was temporarily blocked for several hours until the issue was diagnosed and resolved.
In March, a long discussion was started at Wikipedia talk:Bot policy by Skdb about the troubling trend of bots "expiring" without explanation after their owners became inactive. This can happen for a variety of reasons -- API changes break code, hosting providers' software updates break code, hosting accounts lapse, software changes make bots' edits unnecessary, and policy changes make bots' edits unwanted. The most promising solution seemed to be Toolforge hosting (although it has some problems of its own, like the occasional necessity of refactoring code).
A discussion on the bot noticeboard, "Re-examination of ListeriaBot", was started by Barkeep49, who pointed out repeated operation outside the scope of its BRFA (i.e. editing pages in mainspace, and adding non-free images to others). Some said it was doing good work, and others said it was operating beyond its remit. It was blocked on April 10; the next day it was unblocked, reblocked from article space, reblocked "for specified non-editing actions", unblocked, and indeffed. The next week, several safeguards were implemented in its code by Magnus; the bot was allowed to roam free once more on April 18.
Issues and enquiries are typically expected to be handled on the English Wikipedia. Pages reachable via unified login, like a talk page at Commons or at Italian Wikipedia could also be acceptable [...] External sites like Phabricator or GitHub (which require separate registration or do not allow for IP comments) and email (which can compromise anonymity) can supplement on-wiki communication, but do not replace it.
May 2020
We heard you like bots, so we made a bot that reports the status of your bots, so now you can use bots while you use bots
MajavahBot 3, an impressively meta bot task, was approved this month for maintaining a list of bots running on the English Wikipedia. The page, located at User:MajavahBot/Bot status report, is updated every 24 hours; it contains a list of all accounts with the bot flag, as well as their operator, edit count, last activity date, last edit date, last logged action date, user groups and block status.
In July 2017, Headbomb made a proposal that a section of the Wikipedia:Dashboard be devoted to bots and technical issues. In November 2019, Lua code was written superseding Legobot's tasks on that page, and operator Legoktm was asked to stop them so that the new code could be deployed. After no response to pings, a partial-block of Legobot for the dashboard was proposed. Some months later, on June 16, Headbomb said: "A full block serves nothing. A partial block solves all current issues [...] Just fucking do it. It's been 3 years now." The next day, however, Legoktm disabled the task, and the dashboard was successfully refactored.
On June 7, RexxS blocked Citation bot for disruptive editing, saying it was "still removing links after request to stop". A couple weeks later, a discussion on the bots noticeboard was opened, saying "it is a widely-used and useful bot, but it has one of the longest block logs for any recently-operating bot on Wikipedia". While its last BRFA approval was in 2011, its code and functionality had changed dramatically since then, and AntiCompositeNumber requested that BAG require a new BRFA. Maintainer AManWithNoPlan responded that most blocks were from years ago (when it lacked a proper test suite), and problems since then had mostly been one-off errors (like a June 2019 incident in which a LTA had "weaponized" the bot to harass editors).
David Tornheim opened a discussion about whether bots based on closed-source code should be permitted, and proposed that they not. He cited a recent case in which a maintainer had said "I can only suppose that the code that is available on GitHub is not the actual code that was running on [the bot]". Some disagreed: Naypta said that "I like free software as much as the next person, and I strongly believe that bot operators should make their bot code public, but I don't think it should be that they must do so".
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.
Hello, SQL. Please check your email; you've got mail! It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
Hello! I wanted to drop a quick note for all of our AFC participants; nothing huge and fancy like a newsletter, but a few points of interest.
AFCH will now show live previews of the comment to be left on a decline.
The template {{db-afc-move}} has been created - this template is similar to {{db-move}} when there is a redirect in the way of an acceptance, but specifically tells the patrolling admin to let you (the draft reviewer) take care of the actual move.
I'd like to extend a cordial invitation to you to join the Fifteen Year Society, an informal group for editors who've been participating in the Wikipedia project for fifteen years or more.
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)
I was not logged in when making these two revisions. My IP is now visible, could you please help me delete these two? Thanks. Here are the two entries: (Redacted) — Preceding unsigned comment added by (Redacted) 13:11, 27 March 2022 (UTC)
It appears that after the recent block expired, this editor immediately resumed disruption, making mass unsourced changes to the leads of multiple articles. If you're able to look into it and perform a mass rollback, it would be greatly appreciated! --GoneIn60 (talk) 05:52, 31 March 2022 (UTC)
Apologies. On second glance, it appears you only reviewed an unblock request and did not institute the earlier block. If you'd still like to review this user's activity, please do, but I have also left a personalized message on that user's talk page, which may hopefully lead to some kind of resolution. --GoneIn60 (talk) 09:42, 31 March 2022 (UTC)
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)
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.
@Ohnoitsjamie: I looked at Cam5643 as a part of evaluating the unblock request, and did not see any other accounts. It's probably better to take that to SPI. SQLQuery Me!17:46, 30 May 2022 (UTC)
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 following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi SQL,
Thanks for responding about my block. I wrote a concise appeal, but as the days went on without an answer, I added many more facts.[3] My account block was only for a week, so it's already timed out.
Simply: I made an article. An admin disliked it, so I decided to focus elsewhere. I left him to delete everything I added. I left Wikipedia and retired this account, making no further edits with it. Against the rules, the admin blocked me; blocking is for prevention not punishment, and if an account is retired, there is nothing to prevent. I have always edited in good faith, never vandalised or broken any Wikipedia rules. All this was is a content dispute.
The admin blocked my IP to force me to edit using my account rather than the IP, so they could further hound me. My IP block remains in place, but it (and the block of ThirteenToThirty) should be removed as the blocks were against many Wikipedia policies, as listed in my appeal. The admin abused their privileges in this instance. RandomBlobby (talk) 21:54, 17 June 2022 (UTC)
Thank you, yes, I intend to write to the Arbitration Committee when I have time. The conduct of the admin was extremely poor and flouted a number of rules. How do I get the other two blocks against me lifted, because the IP block is 1 month, and the block on ThirteenToThirty is infedinite! This account I'm using is retired... I want to be able to log out of it and never log in again. RandomBlobby (talk) 01:30, 18 June 2022 (UTC)
P.S. The Guide to Appealing Blocks also isn't really clear what you're supposed to do in the event of multiple blocks, like an account and an IP, possibly because such extreme measures should only be taken in extreme circumstances. It would be useful if it explained that though. I did copy the appeal to my then-IP address (my address moves about within a range)[4] because I thought I had to appeal each one individually, but then I got told that's "abusive", which did not seem like AGF given that my appeal was in good faith. I just want all the blocks lifted as there was no reason compliant with Wikipedia's policies for blocking me in the first instance. RandomBlobby (talk) 02:17, 18 June 2022 (UTC)
Your appeal (at least the one I saw) was so overly verbose that I didn't read it. I don't know the circumstances that you are facing. I responded trying to provide helpful feedback to give you a better chance of getting your request reviewed, and once I realized that you weren't blocked, I closed the open request on your talkpage. The appropriate way forward for a complaint of abuse w/r/t Drmies is the administrators noticeboard. SQLQuery Me!04:32, 18 June 2022 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Have you ever purchased a project car, which you were going to dump all sorts of time and effort into?
It's always awesome at first. You start ordering parts, getting things soaking - or even into the ultrasonic, and start replacing stuff. You're super amped every time UPS arrives with new goodies.
Then life hits. Summer comes about, and you have to fix the gutters. You've got to work on plumbing issues. You have to mow the lawn more frequently. It's always something.
"I'll get to it next week". Then, it's "I'll get to it in a few weeks", then "I'll get to it when I get free time".
At some point, one has to make the hard decision to give it to friends like "Bubba", and "Hacksaw" in the hopes that they finish the restoration, and don't take it to the demolition derby.
In all seriousness, I had intended to redouble my efforts recently - to buckle down as it were - but I simply can't find the time.
Those that know - well, they know - the last year or so has been a massive change to my life. I've completely changed careers, which is nothing short of terrifying, but has landed as a smashing success.
I unfortunately do not see my free time becoming more abundant in the next year or so. The opposite seems to be the way things are going.
The last three years have been a wild ride. It's been fun, I've made some friends, and I've learned a lot.
Thank you to each member of every committee I've had the pleasure of helping. I've gotten to know many of you on a personal level, and many of you have provided me with valuable advice and feedback.
Well, I for one would like to say thank you for doing the thankless job. I've said before that I couldn't be an arbitrator without the clerks, and really do appreciate the time that each and every one takes to basically make my life easier. I hope you really enjoy your vacation and focus on real life, which is what matters. I'm sure there will be a clerk position available if you like in the future. WormTT(talk) 09:00, 24 June 2022 (UTC)
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.
I think I edited and wrote on Wikipedia in 2017 but I checked today and came to know that I am blocked in May 2022. I'm surprised. I think someone used my ID and and did some mistake because I'm a teacher and I'm very careful about knowledge sharing. AsadSurani (talk) 12:18, 24 July 2022 (UTC)
Feedback request: Wikipedia proposals request for comment
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.
Hello, SQL! Being in a country/region in the world with inconvenient Internet access, I've been using proxies to bypass the "fire wall" and IPBE to edit on en Wikipedia. However, my IPBE will be expired in this month. Can you grant me another one? It will be more appreciated if you can grant me a longer exemption. Thanks!--波斯波莉斯 (talk) 09:05, 3 September 2022 (UTC)
Please vote in the 2022 Wikimedia Foundation Inc. Board of Trustees election
Hello SQL, not sure if you're using a script for reviewing unblock requests, but at the moment CAT:DUPARG has a few dozen replies with duplicate "1=" arguments in the {{unblock reviewed}} template. Not sure how best to fix these, so just flagging it up. Thanks, Storchy (talk) 11:06, 24 September 2022 (UTC)
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.
Hi SQL,
I see you were on the ArbCom election commission the year before last. The nominations for this year's EC close in 2 days, and so far we have one nomination, and they've never been on the EC before. Would you consider joining them on the nomination page? IMHO, the EC should have at least one person who has done it before, so we don't lose institutional memory, and can pass it down to newbies who join this year. I guess it looks like you're not terribly active these days, so maybe this doesn't fit with your schedule this year. But I hope you have the time and the inclination. --Floquenbeam (talk) 22:05, 5 October 2022 (UTC)
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.
Whatever you celebrate at this time of year, whether it's Christmas or some other festival, I hope you and those close to you have a happy, restful time! Have fun, Donner60 (talk) 00:16, 23 December 2022 (UTC)}}
.jpg)
.jpg)
,_cropped.jpg)
.jpg)
.jpg)
.jpg)
_(cropped_to_40%25).jpg){kind=small}
_shown_in_her_laboratory_in_1947.jpg)
