This is an archive of past discussions with User:Meno25. 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.
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.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
More wikis are now testing visual editor section editing for mobile users. You can read more.
A map update caused some problems on 29 March and 30 March. It was rolled back. [4]
Pages on some Wikivoyages had problems with the top headline. This has been fixed. [5]
Changes later this week
When you add an edit summary the VisualEditor will search your recent edit summaries in case you want to re-use one. This works in both the visual and wikitext modes on desktop. It also works on the mobile site. [6]
The {{REVISIONID}} magic word will no longer work. This is for performance reasons. When you preview a page it will return "" (empty string). When you read a page it will return "-" (dash). For now this will only affect content namespaces. [8]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 April. It will be on non-Wikipedia wikis and some Wikipedias from 10 April. It will be on all wikis from 11 April (calendar).
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 10 April at 15:00 (UTC). See how to join.
Future changes
You will be able to preview references. This means that when you hover over the link you will get a popup that shows you a preview of the reference. It will work much like page previews. This is so you don't have to go to the bottom of the page to see a reference. This will now be available as a beta feature on German and Arabic Wikipedia. [9][10]
The Wikidata JSON output will change. Empty containers will be serialised as empty objects. This is a breaking change that will affect tools that use JSON outputs and APIs. It will happen on 30 April. You can read more and see how to test your code.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
All wikis now have the TemplateWizard for the wikitext editor.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 April. It will be on non-Wikipedia wikis and some Wikipedias from 17 April. It will be on all wikis from 18 April (calendar).
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 17 April at 15:00 (UTC). See how to join.
Future changes
Wikidata will get a new constraint status called suggestion. This will change how the WikibaseQualityConstraints constraint checking API works. [11][12]
You can test the depicts property for structured data on Commons.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
The advanced search function URL now shows which namespaces you search in. The namespace field is collapsed by default on the search page. You can also add new fields to the search interface through a hook. [13][14][15]
The wikis now look slightly different in the mobile web version. [16]
Changes later this week
There is no new MediaWiki version this week.
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 23 April at 15:00 (UTC). See how to join.
Future changes
Wikipedia articles will have the sameAsmeta property. It adds structured data. This makes it easier for search engines to find Wikipedia articles. It also makes it easier to reuse content. There will an A/B test. [17][18]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
The Wikipedia app for Android now invites users to add Wikidata descriptions to Wikidata objects that have Wikipedia articles but no Wikidata descriptions. It will only invite users who have added a number of Wikidata descriptions in the app without being reverted. This is to avoid spam and bad edits. [19][20]
Problems
Tech News was late last week because of a MassMessage bug. Other newsletters had the same problem. [21]
Changes later this week
You will see when you last refreshed the recent changes page. This is so you can see how recent the changes are. [22]
When you write a comment in Structured Discussions but have not posted it yet your web browser will save it in local storage instead of session storage. This means you do not lose them even if you close your web browser. Structured Discussions used to be called Flow. [23]
You will be able to turn off milestone notifications. Milestone notifications congratulate you when you have made certain numbers of edits. [24]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 30 April. It will be on non-Wikipedia wikis and some Wikipedias from 1 May. It will be on all wikis from 2 May (calendar).
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 1 May at 15:00 (UTC). See how to join.
Future changes
The Wikidata wb_terms table will be dropped. This will affect some Wikidata tools. They need to be updated. The table has become too big which is causing problems. This will happen on 29 May. You can read more. You can ask for help if you need it.
Wikimedia wikis will soon use a token when you log out. This changes how the API works. Some tools might need to be updated. [25]
Hi @Mahmudmasri: Thank you for your message. This is intentional as agreed on with Ghaly himself back in 2012. (See this old discussion.) If you wish, I can switch the bot to sign in with my name instead since Ghaly is not very active these days. Best wishes. --Meno25 (talk) 15:40, 2 May 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.
