This is an archive of past discussions. 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.
After a discussion at Meta, a new user group called "interface administrators" (formerly "technical administrator") has been created. Come the end of August, interface admins will be the only users able to edit site-wide JavaScript and CSS pages like MediaWiki:Common.js and MediaWiki:Common.css, or edit other user's personal JavaScript and CSS. The intention is to improve security and privacy by reducing the number of accounts which could be used to compromise the site or another user's account through malicious code. The new user group can be assigned and revoked by bureaucrats. Discussion is ongoing to establish details for implementing the group on the English Wikipedia.
Following a request for comment, the WP:SISTER style guideline now states that in the mainspace, interwiki links to Wikinews should only be made as per the external links guideline. This generally means that within the body of an article, you should not link to Wikinews about a particular event that is only a part of the larger topic. Wikinews links in "external links" sections can be used where helpful, but not automatically if an equivalent article from a reliable news outlet could be linked in the same manner.
Technical news
The WMF Anti-Harassment Tools team is seeking input on the second set of wireframes for the Special:Block redesign that will introduce partial blocks. The new functionality will allow you to block a user from editing a specific set of pages, pages in a category, a namespace, and for specific actions such as moving pages and uploading files.
Hello and welcome to the August 2018 GOCE newsletter. Thanks to everyone who participated in the Guild's June election; your new and returning coordinators are listed below. The next election will occur in December 2018; all Wikipedia editors in good standing may take part.
Our June blitz focused on Requests and articles tagged for copy edit in October 2017. Of the eleven people who signed up, eight editors recorded a total of 28 copy edits, including 3 articles of more than 10,000 words. Complete results, including barnstars awarded, are available here.
Thanks to everyone who participated in the July drive. Of the seventeen people who signed up, thirteen editors completed 194 copy edits, successfully removing all articles tagged in the last three months of 2017. Final results, including barnstars awarded, are here.
The August blitz will run for one week, from 19 to 25 August. Sign up now!
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators, Reidgreg, Baffle gab1978, Jonesey95, Miniapolis and Tdslk.
Following a "stop-gap" discussion, six users have temporarily been made interface administrators while discussion is ongoing for a more permanent process for assigning the permission. Interface administrators are now the only editors allowed to edit sitewide CSS and JavaScript pages, as well as CSS/JS pages in another user's userspace. Previously, all administrators had this ability. The right can be granted and revoked by bureaucrats.
Technical news
Because of a data centre test you will be able to read but not edit the wikis for up to an hour on 12 September and 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. The time when you can't edit might be shorter than an hour.
Some abuse filter variables have changed. They are now easier to understand for non-experts. The old variables will still work but filter editors are encouraged to replace them with the new ones. You can find the list of changed variables on mediawiki.org. They have a note which says Deprecated. Use ... instead. An example is article_text which is now page_title.
Abuse filters can now use how old a page is. The variable is page_age.
Arbitration
The Arbitration Committee has resolved to perform a round of Checkuser and Oversight appointments. The usernames of all applicants will be shared with the Functionaries team, and they will be requested to assist in the vetting process. The deadline to submit an application is 23:59 UTC, 12 September, and the candidates that move forward will be published on-wiki for community comments on 18 September.
There is an open request for comment on Meta regarding the creation a new user group for global edit filter management.
Technical news
Partial blocks should be available for testing in October on the Test Wikipedia and the Beta-Cluster. This new feature allows admins to block users from editing specific pages and in the near-future, namespaces and uploading files. You can expect more updates and an invitation to help with testing once it is available.
The Foundations' Anti-Harassment Tools team is currently looking for input on how to measure the effectiveness of blocks. This is in particular related to how they will measure the success of the aforementioned partial blocks.
Because of a data centre test, you will be able to read but not edit the Wikimedia projects for up to an hour on 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time.
Following a request for comment, the size of the Arbitration Committee will be decreased to 13 arbitrators, starting in 2019. Additionally, the minimum support percentage required to be appointed to a two-year term on ArbCom has been increased to 60%. ArbCom candidates who receive between 50% and 60% support will be appointed to one-year terms instead.
Nominations for the 2018 Arbitration Committee Electoral Commission are being accepted until 12 October. These are the editors who help run the ArbCom election smoothly. If you are interested in volunteering for this role, please consider nominating yourself.
Partial blocks is now available for testing on the Test Wikipedia. The new functionality allows you to block users from editing specific pages. Bugs may exist and can be reported on the local talk page or on Meta. A discussion regarding deployment to English Wikipedia will be started by community liaisons sometime in the near future.
A user script is now available to quickly review unblock requests.
The 2019 Community Wishlist Survey is now accepting new proposals until November 11, 2018. The results of this survey will determine what software the Wikimedia Foundation's Community Tech team will work on next year. Voting on the proposals will take place from November 16 to November 30, 2018. Specifically, there is a proposal category for admins and stewards that may be of interest.
Arbitration
Eligible editors will be invited to nominate themselves as candidates in the 2018 Arbitration Committee Elections starting on November 4 until November 13. Voting will begin on November 19 and last until December 2.
The Arbitration Committee's email address has changed to arbcom-enwikimedia.org. Other email lists, such as functionaries-en and clerks-l, remain unchanged.
Latest comment: 5 years ago1 comment1 person in discussion
Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. See User:RonBot for info on how to not get these messages. RonBot (talk) 18:09, 5 November 2018 (UTC)
ArbCom 2018 election voter message
Latest comment: 5 years ago1 comment1 person in discussion
Hello, Darkwind. 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.
Latest comment: 5 years ago1 comment1 person in discussion
Hello, Darkwind. 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.
Hello, Darkwind. 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.
Latest comment: 5 years ago1 comment1 person in discussion
Dear Darkwind, i wrote you an email. Kind regards, --Gyanda (talk) 20:30, 21 November 2018 (UTC)
Administrators' newsletter – December 2018
Latest comment: 5 years ago1 comment1 person in discussion
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.
Hello and welcome to the December 2018 GOCE newsletter. Here is what's been happening since the August edition.
Thanks to everyone who participated in the August blitz (results), which focused on Requests and the oldest backlog month. Of the twenty editors who signed up, eleven editors recorded 37 copy edits.
For the September drive (results), of the twenty-three people who signed up, nineteen editors completed 294 copy edits.
Our October blitz (results) focused on Requests, geography, and food and drink articles. Of the fourteen people who signed up, eleven recorded a total of 57 copy edits.
For the November drive (results), twenty-two people signed up, and eighteen editors recorded 273 copy edits. This helped to bring the backlog to a six-month low of 825 articles.
The December blitz will run for one week, from 16 to 22 December. Sign up now!
Elections: Nominations for the Guild's coordinators for the first half of 2019 will be open from 1 to 15 December. Voting will then take place and the election will close on 31 December at 23:59 UTC. Positions for Guild coordinators, who perform the important behind-the-scenes tasks that keep our project running smoothly, are open to all Wikipedians in good standing. We welcome self-nominations, so please consider nominating yourself if you've ever thought about helping out; it's your Guild and it doesn't run itself!
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators; Reidgreg, Baffle gab1978, Jonesey95, Miniapolis and Tdslk.
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.
Hello and welcome to the March newsletter, a brief update of Guild activities since December 2018. All being well, we're planning to issue these quarterly in 2019, balancing the need to communicate widely with the avoidance of filling up talk pages. Don't forget you can unsubscribe at any time; see below.
January Drive: Thanks to everyone for the splendid work in January's Backlog Elimination Drive. We removed copyedit tags from all of the articles tagged in our original target months of June, July and August 2018, and by 24 January we ran out of articles. After adding September, we finished the month with 8 target articles remaining and 842 left in the backlog. GOCE copyeditors also completed 48 requests for copyedit in January. Of the 31 people who signed up for this drive, 24 copyedited at least one article. Final results, including barnstars awarded, are available here.
Blitz: Thanks to everyone who participated in the February Blitz. Of the 15 people who signed up, 13 copyedited at least one article. Participants claimed 32 copyedits, including 15 requests. Final results, including barnstars awarded, are available here.
Progress report: As of 23:39, 18 March 2019 (UTC), GOCE copyeditors have completed 108 requests since 1 January and the backlog stands at 851 articles.
March Drive: The month-long March drive is now underway; the target months are October and November 2018. Awards will be given to everyone who copyedits at least one article from the backlog. Sign up here!
Election reminder: It may only be March but don't forget our mid-year Election of Coordinators opens for nominations on 1 June. Coordinators normally serve a six-month term and are elected on an approval basis. Self-nominations are welcome. If you've thought of helping out at the Guild, or know of another editor who would make a good coordinator, please consider standing for election or nominating them here.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Miniapolis, Baffle gab1978, Jonesey95, Reidgreg and Tdslk.
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Please see meta:Community health initiative/User reporting system consultation 2019 to provide your input on this idea.
Two more administrator accounts were compromised. Evidence has shown that these attacks, like previous incidents, were due to reusing a password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately. All admins are strongly encouraged to enable two-factor authentication, please consider doing so. Please always practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
As a reminder, according to WP:NOQUORUM, administrators looking to close or relist an AfD should evaluate a nomination that has received few or no comments as if it were a proposed deletion (PROD) prior to determining whether it should be relisted.
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: 4 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.
For the Arbitration Committee, -Cameron11598 21:03, 4 May 2019 (UTC)
Administrators' newsletter – May 2019
Latest comment: 4 years ago1 comment1 person in discussion
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.
Hello and welcome to the June newsletter, a brief update of Guild activities since March 2019. You can unsubscribe from our mailings at any time; see below.
Election time: Nomination of candidates in our mid-year Election of Coordinators opened on 1 June, and voting will take place from 16 June. Coordinators normally serve a six-month term and are elected on an approval basis. Self-nominations are welcome. If you've thought of helping out at the Guild, or know of another editor who would make a good coordinator, please consider standing for election or nominating them here.
June Blitz: Our June blitz will soon be upon us; it will begin at 00:01 on 16 June (UTC) and will close at 23:59 on 22 June (UTC). The themes are "nature and the environment" and all requests.
March Drive: Thanks to everyone for their work in March's Backlog Elimination Drive. We removed copyedit tags from 182 of the articles tagged in our original target months October and November 2018, and the month finished with 64 target articles remaining from November and 811 in the backlog. GOCE copyeditors also completed 22 requests for copyedit in March; the month ended with 34 requests pending. Of the 32 people who signed up for this drive, 24 copyedited at least one article. Final results, including barnstars awarded, are available here.
April Blitz: Thanks to everyone who participated in the April Blitz; the blitz ran from 14 to 20 April (UTC) inclusive and the themes were Sports and Entertainment. Of the 15 people who signed up, 13 copyedited at least one article. Participants claimed 60 copyedits. Final results, including barnstars awarded, are available here.
Progress report: As of 04:36, 3 June 2019 (UTC), GOCE copyeditors have completed 267 requests since 1 January. The backlog of tagged articles stands at 605 articles.
May Drive: During the May Backlog Elimination Drive, Guild copy-editors removed copyedit tags from 191 of the 192 articles tagged in our original target months of November and December 2018, and January 2019 was added on 22 May. We finished the month with 81 target articles remaining and a record low of 598 articles in the backlog. GOCE copyeditors also completed 24 requests for copyedit during the May drive, and the month ended with 35 requests pending. Of the 26 people who signed up for this drive, 21 copyedited at least one article. Final results, including barnstars awarded, are available here.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Miniapolis, Baffle gab1978, Jonesey95, Reidgreg and Tdslk.
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
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.
I have reviewed the copyright claim and found a flaw in the method, most specifically that the "copyrighted" words belong to a list of the subject's published works and awards. I am of the opinion that this claim was not properly investigated and should never have been lodged. I write so because I did not commit plagiarism, rather I listed the published works and awards in order of their publication/reception. Can you help me resolve this issue? Whether it is a suggestion on what to change or where there is a flaw in my writing?
Whatever your decision, thank you for your time and consideration.
Aquariusveritas (talk) 15:56, 25 July 2019 (UTC)
Administrators' newsletter – August 2019
Latest comment: 4 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.
Latest comment: 4 years ago2 comments2 people in discussion
Since your addition of protection to FEDOR (robot), a named single-purpose account has repeatedly added more WP:ELNO links, and pointless duplicate references. (Hohum@) 23:23, 12 September 2019 (UTC)
@Hohum: Although it does seem suspicious that an autoconfirmed user comes out of the woodwork as soon as the page was protected, there's only one account besides yourself presently editing this article. That's well within your ability to handle with normal dispute resolution techniques (e.g. post on their talk page or the article's page, escalate as necessary, etc.) I don't see any need for further admin intervention at this point. –Darkwind (talk) 06:19, 13 September 2019 (UTC)
A barnstar for you!
Latest comment: 4 years ago1 comment1 person in discussion
The Civility Barnstar
Thanks for helping me become a better Wikipedia editor! Phipperz (talk) 23:59, 21 September 2019 (UTC)
Administrator changes
Guideline and policy news
Technical news
None
Asterion • Crisco 1492 • KF • Kudpung • Liz • Randykitty • Spartaz
Optimist on the run → Voice of Clam
Arbitration
Interface administrator changes
Oversight changes
wikimedia.org. Other email lists, such as functionaries-en and clerks-l, remain unchanged.
Al Ameer son • Randykitty • Spartaz
Miscellaneous
Obituaries
CheckUser changes
