This is an archive of past discussions with User:Tyrol5. 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 request for comment asks whether partial blocks should be enabled on the English Wikipedia. If enabled, this functionality would allow administrators to block users from editing specific pages or namespaces, rather than the entire site.
A proposal asks whether admins who don't use their tools for a significant period of time (e.g. five years) should have the toolset procedurally removed.
The fourth case on Palestine-Israel articles was closed. The case consolidated all previous remedies under one heading, which should make them easier to understand, apply, and enforce. In particular, the distinction between "primary articles" and "related content" has been clarified, with the former being the entire set of articles whose topic relates to the Arab-Israeli conflict, broadly interpreted rather than reasonably construed.
Following a request for comment, partial blocks are now enabled on the English Wikipedia. This functionality allows administrators to block users from editing specific pages or namespaces rather than the entire site. A draft policy is being workshopped at Wikipedia:Partial blocks.
The request for comment seeking the community's sentiment for a binding desysop procedure closed with wide-spread support for an alternative desysoping procedure based on community input. No proposed process received consensus.
Technical news
Twinkle now supports partial blocking. There is a small checkbox that toggles the "partial" status for both blocks and templating. There is currently one template: {{uw-pblock}}.
When trying to move a page, if the target title already exists then a warning message is shown. The warning message will now include a link to the target title. [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.
The article will be discussed at Wikipedia:Articles for deletion/Lenard (crater) 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. Renerpho (talk) 01:56, 27 June 2020 (UTC)
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.
Hello WikiProject Anatomy participant! This is our seventh newsletter, documenting what's going on in WikiProject Anatomy, news, current projects and other items of interest.
I value feedback, and if you think I've missed something, or don't wish to receive this again, please leave a note on my talk page, or remove your name from the mailing list.
We reach a project goal of 150 B-class articles in July 2020, increasing by about 50% over five years, and are one good article away from our goal of 40 GAs, doubling over the last five years
I have been asked to write up something introducing the Featured article (FA) process to anatomy editors, but I took a more general approach to explaining why one might want to contribute featured content and the benefits to the editor and to Wikipedia. I also tried to address some misconceptions about the FA process, and give you a guide that is somewhat specific to health content should you decide to take the dive.
A vital purpose of Featured articles is to serve as examples for new and aspiring Wikipedia editors. FAs are often uniquely comprehensive for the Internet. They showcase some of our best articles, and can enhance Wikipedia's reputation if they are maintained to standard—but in an "anyone can edit" environment, they can easily fall out of standard if not maintained. Benefits to the writer include developing collaborative partnerships and learning new skills, while improving your writing and seeing it exposed to a broader audience—all that Wikipedia is about!
Looking more specifically at WP Anatomy's featured content, the Featured media is impressive and seems to be an Anatomy Project strength. The Anatomy WikiProject has tagged 4 FAs, 1 Featured list, and 30 Featured media. Working towards upgrading and maintaining older Featured articles could be a worthwhile goal. Immune system is a 2007 FA promotion, and bringing it up to date would make a nice collaboration between WikiProject Medicine and the Anatomy WikiProject. Hippocampus is another dated promotion that is almost 50% larger than when promoted, having taken on a bit of uncited text and new text that might benefit from a tune-up.
@Balon Greyjoy: Somehow I missed this. In any event, you deserve a brew yourself for shoring up the the John Young article, a difference I noticed immediately upon clicking the link — excellent work there. I'll look forward to seeing it over at GAN. Tyrol5[Talk]23:10, 23 October 2020 (UTC)
Sysops will once again be able to view the deleted history of JS/CSS pages; this was restricted to interface administrators when that group was introduced.
Twinkle's block module now includes the ability to note the specific case when applying a discretionary sanctions block and/or template.
Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Voting for proposals in the 2021 Community Wishlist Survey, which determines what software the Wikimedia Foundation's Community Tech team will work on next year, will take place from 8 December through 21 December. In particular, there are sections regarding administrators and anti-harassment.
By motion, standard discretionary sanctions have been temporarily authorizedfor all pages relating to the Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes). The effectiveness of the discretionary sanctions can be evaluated on the request by any editor after March 1, 2021 (or sooner if for a good reason).
A request for comment is open that proposes a process for the community to revoke administrative permissions. This follows a 2019 RfC in favor of creating one such a policy.
A request for comment is in progress to remove F7 (invalid fair-use claim) subcriterion a, which covers immediate deletion of non-free media with invalid fair-use tags.
A request for comment asks if sysops may place the General sanctions/Coronavirus disease 2019 editnotice template on pages in scope that do not have page-specific sanctions?
When blocking an IPv6 address with Twinkle, there is now a checkbox with the option to just block the /64 range. When doing so, you can still leave a block template on the initial, single IP address' talkpage.
When protecting a page with Twinkle, you can now add a note if doing so was in response to a request at WP:RfPP, and even link to the specific revision.
By motion, the discretionary sanctions originally authorized under the GamerGate case are now authorized under a new Gender and sexuality case, with sanctions authorized for all edits about, and all pages related to, any gender-related dispute or controversy and associated people. Sanctions issued under GamerGate are now considered Gender and sexuality sanctions.
They have continued to vandalise the page they're vandalising. Sorry to ask directly it's just much quicker. ThanksNEDOCHAN (talk) 15:45, 25 March 2021 (UTC)
@NEDOCHAN: Hi, thanks for the note. I've had a quick look, and seems to me the edits since the block have narrowed from fairly wholesale disruption to a dispute over the result of a particular fight, in a table that does not appear to be sourced or footnoted, no less. I'd suggest, instead of my inflammatorily swinging the mop around the room, approaching the individual with a reliable source or two citing what you're indicating was the result, asking what they're looking at, and doing so without accusation of vandalism in this particular instance. Or perhaps raise the issue on the article's talk page. I'm admittedly not well-versed in mixed martial arts, but I suspect a content-based substantive resolution is the sound course. Tyrol5[Talk]17:25, 25 March 2021 (UTC)
The source is in the infobox. I wouldn't have a problem with helping an editor with such things but they haven't responded to anyone yet, only edit one page and are quite clearly NOTHERE.NEDOCHAN (talk) 22:41, 25 March 2021 (UTC)
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)
Yea, always nice to see another PA related editor about. (probably where I first saw your username) Eagles247 is still around too. Sorry I missed your RfA, think I was on one of my "ugh, I don't need this" breaks. Doubt there's very many "0-oppose" editors still around since I suspect most of those were in 2002-2006 era. Have to admit that I checked your contribs, and I'm looking forward to the Ike article getting rolled out - that's some impressive work. Outside the WP:FRAMGATE and WP:ARBREX stuff, I tend to keep to myself these day (that "short description" stuff is pretty safe usually). Anyway, always a pleasure and best wishes. — Ched (talk) 00:53, 8 April 2021 (UTC)
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)
Orphaned non-free image File:Penn State Fayette Logo.svg
⚠
Thanks for uploading File:Penn State Fayette Logo.svg. 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).
Orphaned non-free image File:Penn State Brandywine Logo.svg
⚠
Thanks for uploading File:Penn State Brandywine Logo.svg. 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).
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.
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.
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.
Phase 2 of the 2021 RfA review has commenced which will discuss potential solutions to address the 8 issues found in Phase 1. Proposed solutions that achieve consensus will be implemented and you may propose solutions till 07 November 2021.
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Unregistered editors using the mobile website are now able to receive notices to indicate they have talk page messages. The notice looks similar to what is already present on desktop, and will be displayed on when viewing any page except mainspace and when editing any page. (T284642)
The limit on the number of emails a user can send per day has been made global instead of per-wiki to help prevent abuse. (T293866)
The already authorized standard discretionary sanctions for all pages relating to the Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes), broadly construed, have been made permanent.
A recently closed Request for Comment (RFC) reached consensus to remove Autopatrolled from the administrator user group. You may, similarly as with Edit Filter Manager, choose to self-assign this permission to yourself. This will be implemented the week of December 13th, but if you wish to self-assign you may do so now. To find out when the change has gone live or if you have any questions please visit the Administrator's Noticeboard. 20:07, 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:47, 30 December 2021 (UTC)
Merchandise giveaway nomination
A token of thanks
Hi Tyrol5! 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 ~~~~~
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.
