This is an archive of past discussions with User:Kirill Lokshin. 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.
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. Regards, Krishna Chaitanya Velaga (talk • mail) 15:22, 14 February 2018 (UTC)
Community ban discussions must now stay open for at least 24 hours prior to being closed.
A change to the administrator inactivity policy has been proposed. Under the proposal, if an administrator has not used their admin tools for a period of five years and is subsequently desysopped for inactivity, the administrator would have to file a new RfA in order to regain the tools.
A change to the banning policy has been proposed which would specify conditions under which a repeat sockmaster may be considered de facto banned, reducing the need to start a community ban discussion for these users.
Technical news
CheckUsers are now able to view private data such as IP addresses from the edit filter log, e.g. when the filter prevents a user from creating an account. Previously, this information was unavailable to CheckUsers because access to it could not be logged.
The edit filter has a new featurecontains_all that edit filter managers may use to check if one or more strings are all contained in another given string.
Bhadani (Gangadhar Bhadani) passed away on 8 February 2018. Bhadani joined Wikipedia in March 2005 and became an administrator in September 2005. While he was active, Bhadani was regarded as one of the most prolific Wikipedians from India.
G'day all, please be advised that throughout April 2018 the Military history Wikiproject is running its annual backlog elimination drive. This will focus on several key areas:
tagging and assessing articles that fall within the project's scope
adding or improving listed resources on Milhist's task force pages
updating the open tasks template on Milhist's task force pages
creating articles that are listed as "requested" on the project's various lists of missing articles.
As with past Milhist drives, there are points awarded for working on articles in the targeted areas, with barnstars being awarded at the end for different levels of achievement.
The drive is open to all Wikipedians, not just members of the Military history project, although only work on articles that fall (broadly) within the scope of military history will be considered eligible. This year, the Military history project would like to extend a specific welcome to members of Wikipedia:WikiProject Women in Red, and we would like to encourage all participants to consider working on helping to improve our coverage of women in the military. This is not the sole focus of the edit-a-thon, though, and there are aspects that hopefully will appeal to pretty much everyone.
The drive starts at 00:01 UTC on 1 April and runs until 23:59 UTC on 30 April 2018. Those interested in participating can sign up here.
Administrators who have been desysopped due to inactivity are now required to have performed at least one (logged) administrative action in the past 5 years in order to qualify for a resysop without going through a new RfA.
Editors who have been found to have engaged in sockpuppetry on at least two occasions after an initial indefinite block, for whatever reason, are now automatically considered banned by the community without the need to start a ban discussion.
There will soon be a calendar widget at Special:Block, making it easier to set expiries for a specific date and time.
Arbitration
The Arbitration Committee is considering a change to the discretionary sanctions procedures which would require an editor to appeal a sanction to the community at WP:AE or WP:AN prior to appealing directly to the Arbitration Committee at WP:ARCA.
Miscellaneous
A discussion has closed which concluded that administrators are not required to enable email, though many editors suggested doing so as a matter of best practice.
The Foundations' Anti-Harassment Tools team has released the Interaction Timeline. This shows a chronologic history for two users on pages where they have both made edits, which may be helpful in identifying sockpuppetry and investigating editing disputes.
Here's our first project-wide update. I hope you enjoy it...
Reboot
The WikiProject reboot has been a success: the new re-envisioned project is up and running, with new members, ongoing discussions about automation, design, and upkeep; maintained task queques; and updates to members, like this, the very first one!
As you know, there's a proposal to delete all portals. It started out looking pretty dismal for portals, with primarily posts supporting their demise. It turned out that the proposer didn't post a deletion notice on the very pages being nominated for deletion (a requirement for all deletion discussions). Once that was done, a flood of opposition came in and has apparently turned the tide.
RfCs generally run for 30 days. It started April 8th, and so it has about 14 more days to run its course.
The more work we can do during that time on the portals, the stronger the reasons for keeping them will be. And the more prepared we will be for any MfDs that follow the closing of the RfC.
You may be wondering why we asked for AWB experience in the member-sign-up list.
We are gearing up to do maintenance runs on the entire set of portals, and the more people we have who can use AWB, the better.
But we're not quite ready to start this yet.
To be able to use AWB on the portals, we first need to know what the end result needs to be. Like on the news sections, do we comment out the out-of-date ones, or do we place the code to activate the newsbot on those pages? That would require an assessment of WikiNews and its news generating performance (areas covered, volume in each area), etc.
Another area we're gearing up for, to do passes with AWB, are upgrades to the intro sections of portals. Many of these have static (copied/pasted) excerpts that go stale over time.
We need everybody's help on this. It's a big chore for one persons. But, many hands make light work. Please help chip away at this chore as much as you can. A little each day, form all of us, will get this done pretty quick.
Familiarize yourself with the portal system
In addition to browsing the portals in the 2 lists mentioned in the section above, you should take a look at the portal name space itself and what is in it.
In addition to the automation efforts mentioned above, we will be looking into how to automate the selection and display of alternating excerpts, and alternating pictures, for the various portal sections.
This new template is fantastic. I've added it to the intro sections of the portals on Australian cities (eg P:PER) and it works brilliantly. My compliments to its creators. It can probably also be used in other sections of many portals (eg "Selected article" and "Selected biography"), and, for that reason, will probably make the task of maintaining portals a great deal easier. Bahnfrend (talk) 09:02, 24 April 2018 (UTC)
I wrote a comment in the the April 26 section of the RfC explaining what we are up to. I liked the excerpt above so much, that I went back to my RfC posting, and inserted it.
A proposal is being discussed which would create a new "event coordinator" right that would allow users to temporarily add the "confirmed" flag to new user accounts and to create many new user accounts without being hindered by a rate limit.
Technical news
AbuseFilter has received numerous improvements, including an OOUI overhaul, syntax highlighting, ability to search existing filters, and a few new functions. In particular, the search feature can be used to ensure there aren't existing filters for what you need, and the new equals_to_any function can be used when checking multiple namespaces. One major upcoming change is the ability to see which filters are the slowest. This information is currently only available to those with access to Logstash.
When blocking anonymous users, a cookie will be applied that reloads the block if the user changes their IP. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. This currently only occurs when hard-blocking accounts.
The block notice shown on mobile will soon be more informative and point users to a help page on how to request an unblock, just as it currently does on desktop.
There will soon be a calendar widget at Special:Block, making it easier to set expiries for a specific date and time.
Lankiveil (Craig Franklin) passed away in mid-April. Lankiveil joined Wikipedia on 12 August 2004 and became an administrator on 31 August 2008. During his time with the Wikimedia community, Lankiveil served as an oversighter for the English Wikipedia and as president of Wikimedia Australia.
Thank you for being a member of the Portals WikiProject, and thank you for all the work you have all been doing on the portal namespace. To see the activity, check out the watchlist.
The top, and one of the most visible parts, of the portal system is Portal:Contents/Portals, which is intended to list all (completed) portals on Wikipedia.
About half of the missing existing portals have been added since this WikiProject's reboot (April 17th). Thank you to RockMagnetist, TriNitrobrick, Polyamorph, PratyushSinha101, Ganesha811, Bermicourt, Javert2113, Noyster, Ɱ, Lepricavark, XOR'easter, and Emir of Wikipedia, for working on this.
I hope you'll join me there. ("Many hands make light work").
Thank you.
Membership
We're at 66 members, with more joining daily. We even have 6 WikiGnomes!
Special thanks
I have awarded Certes with a portals barnstar on his talk page for his work on the new excerpt templates that are revolutionizing the portal system (Template:Transclude lead excerpt & Template:Transclude random excerpt). If you'd like to show your appreciation, please feel free to stop by his talk page and add your signature to the barnstar itself.
Thank you Certes. You are enabling this WikiProject to get the right things done, fast.
By the way, the templates have already gone international. After being told about the templates, Mossab wrote:
Thanks You very much!. Those are fantastic and great templates! I transferred them to Arabic Wikipedia and they do a magic great job. I worked to improve portal anatomy here and i do every thing i can to improve it and i am very sad for the nomination for deletion of portals :(. I am glad to be member on WikiProject Portals and i added my name with pleasure. Kind regards
RFC
As you know, the (April 8th) proposal to delete all portals and the portal namespace inspired the reboot of this WikiProject. RfCs typically run for 30 days, which means there are 5 days left including today, before the RfC will be closed. The !votes are predominantly "oppose", but many editors have shared their disappointment with the portal system. We have our work cut out for us in correcting the problems of the portals to address their concerns. Complaints ranged from being out of date and lacking maintenance, to taking up the time of editors that they felt (due to low traffic) would be better spent improving articles.
Anti-WikiProject drama
This past week has been somewhat stressful for me, with more than a little conflict...
It culminated with my being reported at the Administrator's Noticeboard "for spamming and canvassing". This is the second time I've been reported there during the RfC; the first one was for posting notices of the deletion discussion (the RfC) at the top of all portal pages.
The accusations were 1) Posting notices of the deletion discussion (the RfC) at the top of all portal pages, 2) Adding an Article alerts section to the Portals WikiProject page, and 3) posting notices (invitations) about this WikiProject on user talk and portal talk pages.
None of which fall under the Wikipedia definitions of spamming or canvassing.
Thank you, Lionelt and Lepricavark, for coming to my rescue. I don't know how the discussion would have turned out if you had not spoken up.
The discussion was closed as "no action necessary".
After that, the person responsible posted their thoughts to my talk page. Here they are, with my response:
Congratulations, it appears your relentless targeted advertising of the RFC, your beating the RFC Supporters with a stick by posting countless times there, your dishonest insistence that Current Events was on the chopping block, and your obstruction of clean up efforts at MfD are paying dividends. Have fun playing with Portal space where no one will read your work. I'm sure someone will eventually clean up the mess when your interest wanes. Cheers. Legacypac
Thank you. I accept your congratulations on behalf of Wikiproject Portals and the portal-loving community – it was a team effort. In addition, I'd like to clarify some things about your claims above...
Each page nominated for deletion must have a notice at the top of its page, per the deletion guideline. Not to have one there, would be unfair to those who use such pages, and would constitute a secret deletion tribunal. We don't do things that way on Wikipedia.
As new facts became available (e.g., a motivated and thriving WikiProject to support the portals, new building blocks, etc.), it was appropriate to post the developments to the RfC, to support informed decision making.
Proposals are literal, not figurative. The proposal specified "all portals". All means all.
The fact is, the rebooted WikiProject is cleaning up the mess, rather rapidly. By updating and upgrading the portals, rather than getting rid of them.
I think I'll be hanging around for awhile, but the project is more than likely to achieve critical mass and may outlive us all, due in part to the development of tools to assist editors in building, upgrading, and maintaining portals that are fully dynamic and self-updating.
Portals are more fun to work with than ever. Thank you for your role in making this happen. You made us try even harder, and inspired us to pull together as a team. You'll have a warm place in our hearts, forever. The Transhumanist
Automatically refreshed excerpts
The main advancement we've made so far is applying selective transclusion Transclusion is template technology, showing a page on another page. Selective transclusion shows only part of that page. We use it to show excerpts that always match the source. The two templates we have so far, are Template:Transclude lead excerpt and Template:Transclude random excerpt.
Obsoleting subpages
Excerpts are migrating toward the base page of each portal, and where this is done, a subpage is no longer needed.
Template:Transclude lead excerpt will be able to be used to put the intro excerpt directly on the portal page, rather than on an intro subpage, once we adapt a portal design to accommodate this.
Template:Transclude random excerpt is currently being used on 1st-level subpages, and eliminates the need for 2nd-level subpages. (Many portals have 2 levels of subpages).
There are about 1500 portals, but there are around 148,000 subpages in portal space. Further discussions are needed to develop designs and components that do not require them.
It is my hope that the portal of the future will be a single page, or close to it, pulling in excerpts from specified dynamic sources (like category pages), filtered by ratings. This would obviate the need for subpages at all (except for maybe the header and footer subpages, which store a portal's settings). A more likely near-term solution would be subpages with a list maintained by a bot, or editors using semi-automatic tools.
There's more in the works, like a rating system, further redesigns, etc. Keep an eye on the discussions on the project's talk page. They should start showing up there soon.
Following a successful request for comment, administrators are now able to add and remove editors to the "event coordinator" group. Users in the event coordinator group have the ability to temporarily add the "confirmed" flag to new user accounts and to create many new user accounts without being hindered by a rate limit. Users will no longer need to be in the "account creator" group if they are in the event coordinator group.
IP-based cookie blocks should be deployed to English Wikipedia in June. This will cause the block of a logged-out user to be reloaded if they change IPs. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. For the time being, it only affects users of the desktop interface.
The Wikimedia Foundation's Anti-Harassment Tools team will build granular types of blocks in 2018 (e.g. a block from uploading or editing specific pages, categories, or namespaces, as opposed to a full-site block). Feedback on the concept may be left at the talk page.
It is now easier for blocked mobile users to see why they were blocked.
Arbitration
A recent technical issue with the Arbitration Committee's spam filter inadvertently caused all messages sent to the committee through Wikipedia (i.e. Special:EmailUser/Arbitration Committee) to be discarded. If you attempted to send an email to the Arbitration Committee via Wikipedia between May 16 and May 31, your message was not received and you are encouraged to resend it. Messages sent outside of these dates or directly to the Arbitration Committee email address were not affected by this issue.
I am E. Whittaker, an intern at Wikimedia with the Scoring Team to create a labeled dataset, and potentially a tool, to help editors deal with incivility when they encounter it on talk pages. A full write-up of the study can be found here: m:Research:Civil_Behavior_Interviews.
We are currently recruiting editors to be interviewed about their experiences with incivility on talk pages. Would you be interested in being interviewed? I am contacting you because of your involvement in Wikipedia’s Women in Red project. The interviews should take ~1 hour, and will be conducted over BlueJeans (which does allow interviews to be recorded). If, so, please email me at ewhit@umich.edu in order to schedule an interview.
An RfC about the deletion of drafts closed with a consensus to change the wording of WP:NMFD. Specifically, a draft that has been repeatedly resubmitted and declined at AfC without any substantial improvement may be deleted at MfD if consensus determines that it is unlikely to ever meet the requirements for mainspace and it otherwise meets one of the reasons for deletion outlined in the deletion policy.
Starting on July 9, the WMF Security team, Trust & Safety, and the broader technical community will be seeking input on an upcoming change that will restrict editing of site-wide JavaScript and CSS to a new technical administrators user group. Bureaucrats and stewards will be able to grant this right per a community-defined process. The intention is to reduce the number of accounts who can edit frontend code to those who actually need to, which in turn lessens the risk of malicious code being added that compromises the security and privacy of everyone who accesses Wikipedia. For more information, please review the FAQ.
Syntax highlighting has been graduated from a Beta feature on the English Wikipedia. To enable this feature, click the highlighter icon () in your editing toolbar (or under the hamburger menu in the 2017 wikitext editor). This feature can help prevent you from making mistakes when editing complex templates.
IP-based cookie blocks should be deployed to English Wikipedia in July (previously scheduled for June). This will cause the block of a logged-out user to be reloaded if they change IPs. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. For the time being, it only affects users of the desktop interface.
Miscellaneous
Currently around 20% of admins have enabled two-factor authentication, up from 17% a year ago. If you haven't already enabled it, please consider doing so. Regardless if you use 2FA, please practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
After a discussion at Meta, a new user group called "interface administrators" (formerly "technical administrator") has been created. Come the end of August, interface admins will be the only users able to edit site-wide JavaScript and CSS pages like MediaWiki:Common.js and MediaWiki:Common.css, or edit other user's personal JavaScript and CSS. The intention is to improve security and privacy by reducing the number of accounts which could be used to compromise the site or another user's account through malicious code. The new user group can be assigned and revoked by bureaucrats. Discussion is ongoing to establish details for implementing the group on the English Wikipedia.
Following a request for comment, the WP:SISTER style guideline now states that in the mainspace, interwiki links to Wikinews should only be made as per the external links guideline. This generally means that within the body of an article, you should not link to Wikinews about a particular event that is only a part of the larger topic. Wikinews links in "external links" sections can be used where helpful, but not automatically if an equivalent article from a reliable news outlet could be linked in the same manner.
Technical news
The WMF Anti-Harassment Tools team is seeking input on the second set of wireframes for the Special:Block redesign that will introduce partial blocks. The new functionality will allow you to block a user from editing a specific set of pages, pages in a category, a namespace, and for specific actions such as moving pages and uploading files.
Wikiproject Military history coordinator election nominations open
Nominations for the upcoming project coordinator election are now open. A team of up to ten coordinators will be elected for the next year. The project coordinators are the designated points of contact for issues concerning the project, and are responsible for maintaining our internal structure and processes. They do not, however, have any authority over article content or editor conduct, or any other special powers. More information on being a coordinator is available here. If you are interested in running, please sign up here by 23:59 UTC on 14 September! Voting doesn't commence until 15 September. If you have any questions, you can contact any member of the coord team. Cheers, MediaWiki message delivery (talk) 00:53, 1 September 2018 (UTC)
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.
G'day everyone, voting for the 2018 Wikiproject Military history coordinator tranche is now open. This is a simple approval vote; only "support" votes should be made. Project members should vote for any candidates they support by 23:59 (UTC) on 28 September 2018. Thanks, MediaWiki message delivery (talk) 00:35, 15 September 2018 (UTC)
A barnstar for you!
The Original Barnstar
HI Kirill, your coordination of Wikipedia Military history is a big project. Kudos to you and your dedication to Wikipedia. I have some knowledge and I'd like to participate, but I'm new and do not know how to create tables. I'd appreciate your guidance, if you can spare sometime. Nat.Account (talk) 04:21, 15 September 2018 (UTC)
Milhist coordinator election voting has commenced
G'day everyone, voting for the 2018 Wikiproject Military history coordinator tranche is now open. This is a simple approval vote; only "support" votes should be made. Project members should vote for any candidates they support by 23:59 (UTC) on 28 September 2018. Thanks, MediaWiki message delivery (talk) 06:22, 15 September 2018 (UTC)
Note: the previous version omitted a link to the election page, therefore you are receiving this follow up message with a link to the election page to correct the previous version. We apologies for any inconvenience that this may have caused.
Have your say!
Hi everyone, just a quick reminder that voting for the WikiProject Military history coordinator election closes soon. You only have a day or so left to have your say about who should make up the coordination team for the next year. If you have already voted, thanks for participating! If you haven't and would like to, vote here before 23:59 UTC on 28 September. Thanks, MediaWiki message delivery (talk) 03:29, 26 September 2018 (UTC)
Interview request
Hi Kirill, To mark the 150th edition of The Bugle next month, we'd like to interview some of the key figures in the newsletter's history - from digging through some very old editions, it seems that you were one of the main people who started it off, and of course continue to contribute to it. If you have time, I'd be grateful if you could respond to the questions at Wikipedia:WikiProject Military history/News/October 2018/Interview by 1 October. Please let me know if you have any other suggestions for how we could mark this milestone! Regards, Nick-D (talk) 07:27, 22 September 2018 (UTC)
Hi Kirill, as a gentle reminder, we need to wrap up the next edition over the next few days, so grateful if you could post a response. No worries though if you have other demands on your time. Regards, Nick-D (talk) 09:25, 4 October 2018 (UTC)
There is an open request for comment on Meta regarding the creation a new user group for global edit filter management.
Technical news
Partial blocks should be available for testing in October on the Test Wikipedia and the Beta-Cluster. This new feature allows admins to block users from editing specific pages and in the near-future, namespaces and uploading files. You can expect more updates and an invitation to help with testing once it is available.
The Foundations' Anti-Harassment Tools team is currently looking for input on how to measure the effectiveness of blocks. This is in particular related to how they will measure the success of the aforementioned partial blocks.
Because of a data centre test, you will be able to read but not edit the Wikimedia projects for up to an hour on 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time.
Following a request for comment, the size of the Arbitration Committee will be decreased to 13 arbitrators, starting in 2019. Additionally, the minimum support percentage required to be appointed to a two-year term on ArbCom has been increased to 60%. ArbCom candidates who receive between 50% and 60% support will be appointed to one-year terms instead.
Nominations for the 2018 Arbitration Committee Electoral Commission are being accepted until 12 October. These are the editors who help run the ArbCom election smoothly. If you are interested in volunteering for this role, please consider nominating yourself.
Partial blocks is now available for testing on the Test Wikipedia. The new functionality allows you to block users from editing specific pages. Bugs may exist and can be reported on the local talk page or on Meta. A discussion regarding deployment to English Wikipedia will be started by community liaisons sometime in the near future.
A user script is now available to quickly review unblock requests.
The 2019 Community Wishlist Survey is now accepting new proposals until November 11, 2018. The results of this survey will determine what software the Wikimedia Foundation's Community Tech team will work on next year. Voting on the proposals will take place from November 16 to November 30, 2018. Specifically, there is a proposal category for admins and stewards that may be of interest.
Arbitration
Eligible editors will be invited to nominate themselves as candidates in the 2018 Arbitration Committee Elections starting on November 4 until November 13. Voting will begin on November 19 and last until December 2.
The Arbitration Committee's email address has changed to arbcom-enwikimedia.org. Other email lists, such as functionaries-en and clerks-l, remain unchanged.
Hello, Kirill Lokshin. Please check your email; you've got mail! The subject is Concerns From India. Message added 14:51, 23 October 2018 (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.
Hello, Kirill Lokshin. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
A request for comment is in progress to determine whether members of the Bot Approvals Group should satisfy activity requirements in order to remain in that role.
A request for comment is in progress regarding whether to change the administrator inactivity policy, such that administrators "who have made no logged administrative actions for at least 12 months may be desysopped". Currently, the policy states that administrators "who have made neither edits nor administrative actions for at least 12 months may be desysopped".
Administrators and bureaucrats can no longer unblock themselves unless they placed the block initially. This change has been implemented globally. See also this ongoing village pump discussion (permalink).
To complement the aforementioned change, blocked administrators will soon have the ability to block the administrator that placed their block to mitigate the possibility of a compromised administrator account blocking all other active administrators.
In late November, an attacker compromised multiple accounts, including at least four administrator accounts, and used them to vandalize Wikipedia. If you have ever used your current password on any other website, you should change it immediately. Sharing the same password across multiple websites makes your account vulnerable, especially if your password was used on a website that suffered a data breach. As these incidents have shown, these concerns are not pure fantasies.
Shock Brigade Harvester Boris (Raymond Arritt) passed away on 14 November 2018. Boris joined Wikipedia as Raymond arritt on 8 May 2006 and was an administrator from 30 July 2007 to 2 June 2008.
Hi. It's been a long time, I think, since we've spoken. I hope everything is going well. Years ago, you participated in some of the initiatives intended to resolve the problem of a serial policy violator. For some time now, I've been having trouble with an editor who's been exhibiting similar persistent behavior, and he seems to be escalating. I could really use your help. I've outlined the evidence of his behavior here. A summary list of his behavior is located near the bottom of that post, beneath the heading "Summary", in case you want to read that first. If you could offer your objective opinion on that evidence, I would appreciate it. Thanks. Nightscream (talk) 02:24, 12 December 2018 (UTC)
Voting now open for "Military historian of the year" and "Military history newcomer of the year" awards
Progress of the project has been generally delayed since September due to development issues (more bitrot than expected, some of the code just being genuinely confusing, etc) and personal injury (I suffered a concussion in October and was out of commission for almost two months as a result).
I currently expect to be putting out a proper call for CollaborationKit pilots in January/February, with estimated deployment in February/March if things don't go horribly wrong (they will, though, don't worry). As a part of that, I will properly update the page and send out announcement and reach out to all projects already signed up as pilots for WikiProject X in general, at which point those (still) interested can volunteer specifically to test the CollaborationKit extension.
Wikipedia:WikiProject X/Pilots was originally created for the first WikiProject X prototype, and given this is where the project has since gone, it's only logical to continue to use it. While I haven't yet updated the page to properly reflect this:
If you want to add your project to this page now, feel free. Just bear in mind that more information what to actually expect will be added later/included in the announcement, because by then I will have a much better idea myself.
Until then, you can find me in my corner working on making the CollaborationKit code do what we want and not just what we told it, per the workboard.
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.
I need your assistance and advice regarding my edits on Su-30 page I have repeatedly cited media from YouTube of a clip from a news channel in order to add content. However, being reverted. I would appreciate your advice. Thanks! Faraz (talk) 22:24, 3 March 2019 (UTC)
It is specifically related regarded of a news report on Indian News channel of a Su-30 MKI being shot down. Faraz (talk) 22:26, 3 March 2019 (UTC)
Following discussions at the Bureaucrats' noticeboard and Wikipedia talk:Administrators, an earlier change to the restoration of adminship policy was reverted. If requested, bureaucrats will not restore administrator permissions removed due to inactivity if there have been five years without a logged administrator action; this "five year rule" does not apply to permissions removed voluntarily.
Technical news
A new tool is available to help determine if a given IP is an open proxy/VPN/webhost/compromised host.
Arbitration
The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
paid-en-wpwikipedia.org has been set up to receive private evidence related to abusive paid editing.
checkuser-en-wpwikipedia.org has been set up to receive private requests for CheckUser. For instance, requests for IP block exemption for anonymous proxy editing should now be sent to this address instead of the functionaries-en list.
The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Please see meta:Community health initiative/User reporting system consultation 2019 to provide your input on this idea.
Two more administrator accounts were compromised. Evidence has shown that these attacks, like previous incidents, were due to reusing a password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately. All admins are strongly encouraged to enable two-factor authentication, please consider doing so. Please always practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
As a reminder, according to WP:NOQUORUM, administrators looking to close or relist an AfD should evaluate a nomination that has received few or no comments as if it were a proposed deletion (PROD) prior to determining whether it should be relisted.
G'day Kirill, just a query regarding Category:Military history articles needing attention to task force coverage. It is picking up pages that have no=yes in the syntax. That doesn't seem right to me, as it has been determined that a task force doesn't apply to them, so they don't actually need attention to task force coverage. Is this a new thing, I haven't noticed it before. Cheers, Peacemaker67 (click to talk to me) 07:26, 14 April 2019 (UTC)
Recently, several Wikipedia admin accounts were compromised. The admin accounts were desysopped on an emergency basis. In the past, the Committee often resysopped admin accounts as a matter of course once the admin was back in control of their account. The committee has updated its guidelines. Admins may now be required to undergo a fresh Request for Adminship (RfA) after losing control of their account.
What do I need to do?
Only to follow the instructions in this message.
Check that your password is unique (not reused across sites).
Check that your password is strong (not simple or guessable).
Enable Two-factor authentication (2FA), if you can, to create a second hurdle for attackers.
How can I find out more about two-factor authentication (2FA)?
Administrator account security (Correction to Arbcom 2019 special circular)
ArbCom would like to apologise and correct our previous mass message in light of the response from the community.
Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.
We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.
XTools Admin Stats, a tool to list admins by administrative actions, has been revamped to support more types of log entries such as AbuseFilter changes. Two additional tools have been integrated into it as well: Steward Stats and Patroller Stats.
Arbitration
In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases, the committee will review all available information to determine whether the administrator followed "appropriate personal security practices" before restoring permissions; administrators found failing to have adequately done so will not be resysopped automatically. All current administrators have been notified of this change.
Following a formal ratification process, the arbitration policy has been amended (diff). Specifically, the two-thirds majority required to remove or suspend an arbitrator now excludes (1) the arbitrator facing suspension or removal, and (2) any inactive arbitrator who does not respond within 30 days to attempts to solicit their feedback on the resolution through all known methods of communication.
The CSD feature of Twinkle now allows admins to notify page creators of deletion if the page had not been tagged. The default behavior matches that of tagging notifications, and replaces the ability to open the user talk page upon deletion. You can customize which criteria receive notifications in your Twinkle preferences: look for Notify page creator when deleting under these criteria.
Twinkle's d-batch (batch delete) feature now supports deleting subpages (and related redirects and talk pages) of each page. The pages will be listed first but use with caution! The und-batch (batch undelete) option can now also restore talk pages.
Miscellaneous
The previously discussed unblocking of IP addresses indefinitely-blocked before 2009 was approved and has taken place.
Updates: I've been focusing largely on the development side of things, so we are a lot closer now to being ready to actually start discussing deploying it and testing it out here.
There's just a few things left that need to be resolved:
A bunch of language support issues in particular, plus some other release blockers, such as the fact that currently there's no good way to find any hubs people do create.
We also probably need some proper documentation and examples up to even reference if we want a meaningful discussion. We have the extension documentation and some test projects, but we probably need a bit more. Also I need to be able to even find the test projects! How can I possibly write reports about this stuff if I can't find any of it?!
Some other stuff that's happened in the meantime:
Midpoint report is out for this round of the project, if you want to read in too much detail about all the problems I've been running into.
WikiProject Molecular Biology have successfully set up using the old module system that CollaborationKit is intended to replace (eventually), and it even seems to work, so go them. Based on the issues they ran into, it looks like the members signup thing on that system has some of the same problems as we've been unable to resolve in CK, though, which is... interesting. (Need to change the content model to the right thing for the formwizard config to take. Ugh, content models.)
Hi MJL! As Jehochman notes, the page was originally intended to be a central list of restrictions for use in arbitration enforcement. Prior to the page having been created, editing restrictions were only recorded on individual arbitration case pages; the lack of a central list made it difficult to determine what specific restriction a user was subject to (or, indeed, whether they were subject to a restriction at all) unless one already knew the case in which the restriction had been imposed. (It didn't help that Wikipedia's internal search wasn't particularly great at the time, so simply searching for the user's name wasn't necessarily productive.) Over time, the page has evolved in various ways, but I think its main purpose is still to serve as an reference for enforcement activity, whether related to arbitration or otherwise.
Given that point, I'm not sure that a list of WMF-imposed restrictions is going to be terribly useful; my understanding is that the WMF doesn't necessarily expect volunteers to enforce the restrictions it imposes (and, if the restrictions are all going to be project-level bans, rather than topic or interaction bans, there should be no particular need to enforce them except in the case of sockpuppetry). Having said that, I do understand the argument that we should have a record of at least the public restrictions for reference/historical/etc. purposes, and I'm not opposed to that approach. Kirill Lokshin (talk) 02:04, 26 June 2019 (UTC)
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.
If you had concerns, I have a talk page and you could ask me to explain before attacking me in a public forum. JehochmanTalk13:41, 2 July 2019 (UTC)
It may be mostly a "mates" reaction, Jehochman. There are a bunch of people from the Wikimedia DC board who have been implicitly or explicitly supporting the anti-Fram cause at a variety of venues and, amazingly, the board even issued a press release which was clearly triggered by it - I've not seen anything similar from any other outfit. Some of the names will be familiar to you. I have no particular opinion of Fram myself but have been appalled by recent events, hence this note on my talk page some weeks ago. - Sitush (talk) 13:53, 2 July 2019 (UTC)
Your transparent attempt to intimidate a harassment victim from coming forward—and it is very much transparent, Jehochman, for all that you've couched your talk of the sanctions they'll face in conditionals—says more about your character than I ever could. Kirill Lokshin (talk) 14:37, 2 July 2019 (UTC)
Does using the word "transparent" twice in a sentence make your attempt at mind-reading successful? You have no idea what I'm thinking. Please don't ascribe false motives to me. You're writing like you are flustered. Please think it over for a while and get back to me later. It is stupid for good faith contributors to fight with one another. JehochmanTalk14:41, 2 July 2019 (UTC)
Kirill started this. He came to WP:ARC and made irrelevant comments to a case request as an opportunity to attack me. I asked him to remove that, he refused and his friend doubled down. I wish he’d focus his statement on the question of whether the case should be accepted or not and why. As I said above, it’s stupid for good faith contributors to treat each other like this. I want to stop but he refuses to make peace. JehochmanTalk23:54, 6 July 2019 (UTC)
Kirill's comments in the RfArb seem relevant - as admins have a large degree of discretion to proactively remove material which violates WP:BLP, including when they are WP:INVOLVED, the question of whether they are using this discretion appropriately is relevant to whether an arbitration case is needed. Nick-D (talk) 00:13, 7 July 2019 (UTC)
Several arbs are already on record saying the deletion was proper, that they’d have requested it in any case. My action was obvious and correct under the circumstances. Not even one editor came to me and asked me to reverse it. It is rude to run straight to arbitration to complain about another administrator without even attempting to discuss the disagreement. Show me where Kirill came to my talk page and asked about the deletion. Anyhow, let’s end this discussion soon because it’s. Not fair to Kirill to use his talk page in this manner, and it’s a distraction from the main issue. JehochmanTalk00:22, 7 July 2019 (UTC)
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.
Wikiproject Military history coordinator election nominations open
Nominations for the upcoming project coordinator election are now open. A team of up to ten coordinators will be elected for the next year. The project coordinators are the designated points of contact for issues concerning the project, and are responsible for maintaining our internal structure and processes. They do not, however, have any authority over article content or editor conduct, or any other special powers. More information on being a coordinator is available here. If you are interested in running, please sign up here by 23:59 UTC on 14 September! Voting doesn't commence until 15 September. If you have any questions, you can contact any member of the coord team. Cheers, Peacemaker67 (click to talk to me) 02:38, 1 September 2019 (UTC)
Portal moves
Alas, we're down to just a few WP:MilHist portals, and now it has been proposed that Portal:War be moved. As the creator, I thought it was reasonable to notify you. BusterD (talk) 02:53, 6 September 2019 (UTC)
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.
