This is an archive of past discussions with User:Psantora. 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.
Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Apple Watch, you added links pointing to the disambiguation pages GB, LTE and MB (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)
Part of Wikipedia's global 17th birthday celebration, Wikipedia Day NYC 2018 at Ace Hotel will include a mini-conference of scheduled panels as well as unconference style talks and discussions proposed by attendees on the day of the event. We are very excited to announce speakers such as Jason Scott (Internet Archive), Jackie Koerner (Visiting Scholar, Wiki Ed), and Andrew Lih (Wikimedia DC), as well as a fantastic line-up of panels that highlight projects and issues of relevance to the Wikimedia NYC community.
We also hope for the participation of our friends from the Free Culture movement and from educational and cultural institutions interested in developing free knowledge projects.
I see. I added some language with that information at the bottom of the template. Feel free to update it as needed. Thanks for the clarification! ~ PaulT+/C20:08, 12 February 2018 (UTC)
Nomination for deletion of Template:MacOS derivations
You are invited to join the Wikimedia NYC community for our monthly "WikiWednesday" evening salon (7-9pm) and knowledge-sharing workshop at Babycastles gallery by 14th Street / Union Square in Manhattan.
We will include a look at the organization and planning for our chapter, and expanding volunteer roles for both regular Wikipedia editors and new participants.
We will also follow up on plans for recent and upcoming edit-a-thons, museum and library projects, education initiatives, and other outreach activities.
We welcome the participation of our friends from the Free Culture movement and from all educational and cultural institutions interested in developing free knowledge projects.
After the main meeting, pizza/chicken/vegetables and refreshments and video games in the gallery!
You are absolutely correct. I have changed those stats to match a new reference. The are v7s, not the 64bit v8. Thanks! ~ PaulT+/C04:18, 11 February 2018 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Page Previews has been updated to use HTML for previews. This has fixed many issues. An A/B test was done on English and German Wikipedia to measure how it is used. Other changes were also made. [2]
Some edits have to be checked against too many conditions before they can trigger an abuse filter. If that is the reason no filter is triggered the edit will be tagged for review. [3]
Auto-saving has been added to the visual editor and the 2017 wikitext editor. Right now it is meant to help if your browser crashes or if you accidentally close a tab. [4]
Problems
The abuse filter did not tag all edits that should have been tagged after last week's MediaWiki version had come to the wikis. It was fixed on 9 March (UTC). [5]
Changes later this week
You can notify users in edit summaries. They will get a ping just as if they had been mentioned on a wiki page. This was originally planned to happen last week. [6]
It is now possible to specify the block parameters for each filter in Special:AbuseFilter. The parameters include block duration and if the user should be blocked from editing their own talk page. The block duration is separate for anonymous and registered users. [7][8]
A hundred Wikimedia wikis will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 13 and 14 March. Other wikis will be recommended to switch soon when they have fixed the errors that must be fixed. Tidy will be removed in the middle of 2018. [9][10][11]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 March. It will be on non-Wikipedia wikis and some Wikipedias from 14 March. It will be on all wikis from 15 March (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 13 March at 19:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 14 March at 16:00 (UTC). See how to join.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Problems
On March 12 early morning UTC, the number of 503 error messages increased due to an issue on esams datacenter. It has been fixed. [12]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 20 March. It will be on non-Wikipedia wikis and some Wikipedias from 21 March. It will be on all wikis from 22 March (calendar).
Meetings
There is no Editing team meeting this week.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 21 March at 16:00 (UTC). See how to join.
Future changes
From April 4, the autopatrol status of edits will only be accessible in the Recent Changes database table, so only for 30 days. [13][14]
In-Context Help and Onboarding is a new project, aiming to improve retention of new wiki editors. The goal is to give them short tutorials and other training experiences based on their activity. Collaboration team is expecting feedback and comments on the project talk page, especially from people working with newcomers.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Changes later this week
Some of the interface icons and text sizes will change slightly, as part of the updates for improved accessibility and consistency. These icons are used in many features, including Notifications, Recent Changes, Beta Features, Visual Editor, 2017 Wikitext Editor, Code Editor, and others. While editor toolbars, dialogs, and menus will appear slightly bigger; elements on special pages will be slightly smaller. Functionality will not change. [15][16]
The deprecated #toc and #toctitle CSS ids have been removed. If your wiki was still using these for fake Tables of Content (ToC) then these might lose their styling. They can be replaced with .toc and .toctitle classes where appropriate. [17]
TemplateStyles will be deployed to the Wikivoyages on 28 March 2018. [18]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 March. It will be on non-Wikipedia wikis and some Wikipedias from 28 March. It will be on all wikis from 29 March (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 27 March at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be one hour earlier than usual on 28 March at 15:00 (UTC). See how to join.
Future changes
From 9 April, the sort order of categories will be distorted for a short time. We are upgrading versions of an internationalisation library (ICU) and using a maintenance script to update existing database entries. This will last anywhere from a few hours to a few days, depending on wiki size. Read more details. [19]
Changes are coming to search for Serbian projects. Cyrillic and Latin variants of a word and different grammatical forms of a word will be able to find each other. Read more on MediaWiki in Serbian or English.
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
Template Wizard script available for testing. It will show up as a puzzle-piece icon in the 2010 WikiEditor. You can click on the icon to insert a template.
The Wikimedia Communities and Contributors survey is to be sent to participants around the world this week. If you are volunteer developer, and have contributed code to any pieces of MediaWiki, gadgets, or tools, please take 20 to 40 minutes to complete the survey.
Problems
MediaWiki deployment train has been rolled back to version 1.31.0-wmf.26 on week 13, due to a multiplication of lost connections during MySQL queries. Some of the recent changes may have not been applied. They will be deployed next week. [20][21][22]
The Notifications badge icons were overlapping other links. This has been fixed. [23]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 3 April. It will be on non-Wikipedia wikis and some Wikipedias from 4 April. It will be on all wikis from 5 April (calendar).
User subpages ending in .json will now be protected from other people editing them, like .js and .css pages already are. If you have a tool that stores static configuration, you can now use a subpage like User:Example/mygadget.json to do this without concerns. [24]
Tidy will be replaced by RemexHtml on the next set of wikis. On April 4, we plan to turn off Tidy on all Wikiquotes (except frwikiquote) and Wikimedia chapters and user groups wikis. 23 wikis will have Tidy replaced this time. [25][26][27]
AbuseFilter will transition to use OOUI starting April 4, and the rule editor will also be changed to a CodeEditor (ACE) similar to what is found on user JavaScript pages. The move to OOUI will continue over the next few weeks. [28][29]
In Special:Preferences, the preference "Reload the watchlist automatically whenever a filter is changed (JavaScript required)" is now only visible for users who have opt-out the New Filters for the Watchlist. [30]
You can see names of individual abuse filters in Special:AbuseLog. Now if the name of an abuse filter contains some wikisyntax like links, it will not change to a link when displayed. [31]
You can now search through filter patterns at Special:AbuseFilter. You may specify either a plain string or a regular expression and the matching filters will show a snippet of their pattern with the match highlighted. [32]
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 3 April at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 4 April at 15:00 (UTC). See how to join.
Future changes
If you're using, creating or improving Lua modules, you can give your feedback to help harmonizing the modules across wikis and add more useful functions.
On April 11th, we plan to turn off Tidy on all wikis with less than 50 entries in all high priority linter categories. About 60 wikis will have Tidy replaced. Currently about 600 wikis have had Tidy replaced and we have another 300 wikis to go. We plan to finish this transition from Tidy to RemexHtml by end of June 2018. Please follow T175706 to monitor progress of Tidy replacement. [33][34]
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
Some pages have templates that describe problems with that article. There is now more information for mobile readers and what is wrong with the article and how they could help fix it. [35]
The sort order of categories will have errors for a short time starting Monday 9 April (UTC). We are upgrading versions of an internationalisation library (ICU) and using a script to update the database. This will take between a few hours and a few days depending on wiki size. You can read more details. [37]
Tag filter titles will now work better on wikis where the tag filter title is in a language that is written in another direction than the language of that wiki. This could for example be an English title (written from left to right) on a Hebrew or an Arabic wiki (written from right to left). [38]
Problems
The bookmark icon for saved filters on the recent changes page disappeared because of new icon changes. This has now been fixed. [39]
For a week in March rollbacks got both the rollback and the undo tag on the recent changes page and other pages where you see tags. This has now been fixed. [40]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 10 April. It will be on non-Wikipedia wikis and some Wikipedias from 11 April. It will be on all wikis from 12 April (calendar).
Patrolled edits now have three states instead of two. Recent changes filters are updated to show unpatrolled, autopatrolled and manually patrolled edits. [41]
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 10 April at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 11 April at 15:00 (UTC). See how to join.
Hi ViperSnake151, leancrew just happens to be the name of the domain. The author and publisher is Dr. Drang. A well-known, influential, and pseudo-anonymousengineer and techblogger. A number of othermorevisiblesiteslinked to his articles about reminders and HomePod, but I thought the reference should be to the original, most comprehensive source of the information, which are Drang's posts on the subject. His postsareoftenreferencedelsewhere. I can add those additional "more popular" sources that reference Drang if you think it will add to the article. Regardless, this discussion easily could have happened on the talk page of the article if you had just explained your actions in the first place. Maybe consider that in the future instead of using an impersonal warning template? - PaulT+/C16:51, 10 April 2018 (UTC)
"Except with very good reason, do not usepx (e.g. thumb|300px), which forces a fixed image width. In most cases upright=scaling factor should be used, thereby respecting the user's base preference (which may have been selected for that user's particular devices)."
After I removed the fixed image size, linking to IMGSIZE in my edit summary, you reversed that change without giving a "very good reason". There is no indication you even read IMGSIZE, let alone understood it. Please don't do this, and please stop using fixed image sizes at that article and all other articles. IMGSIZE explains how to convert a px value to an equivalent |upright= value.
Editors are gradually converting articles to use |upright= values instead of px values, and that effort is not helped when other editors reverse the changes without basis. If you have any questions, please ping me here. Thank you. ―Mandruss☎07:18, 11 April 2018 (UTC)
Take it easy there Mandruss and maybe WP:AGF? I don't think it is reasonable to expect someone to read an article's history before making their first edit to a page, so I had no idea you had linked WP:IMGSIZE. It is a relatively recent change and while I had done some reading on |upright= there (and at MOS:IMGSIZE where the explanation and rationale is much more explicit) in the recent past I hadn't actually seen or edited with it until this page. Additionally, at some point in the past I changed my default image size to 400px, which caused both images in the article to be rendered way too large. I've since reverted my preferences back to the default 220px and I'll be using |upright= going forward with the default image size in mind.
I'd appreciate it if you weren't condescending (There is no indication you even read IMGSIZE, let alone understood it.). You'll find you generally get much more favorable results when interacting with other editors if you assume good faith. After all, this is a collaborative project and having productive discussions with other wikipedians is essential to that objective. My edit was a perfectly acceptable part of the WP:BRD cycle and all you had to do was mention me on the talk page of the article with a short explanation of the policy. I would have seen it and agreed with you and even thanked you for bringing it to my attention. There is no reason to negatively question if I read or understood a policy correctly. It just isn't productive. Happy editing, - PaulT+/C14:57, 11 April 2018 (UTC)
First, I didn't question your good faith. I questioned your judgment in one small area, that of recent page history awareness. Good faith is about honesty, as seen in the dictionary entry, and I have no reason to doubt your honesty. It's important to understand WP:AGF and avoid misapplying it, and there is no WP:AGJ. I admit I thought you had edited there before, and my apologies for that error. Still I don't know why, after reading MOS:IMGSIZE, one would use a px value for any ordinary thumbnail, let alone change an existing upright to a px value. Thanks for the response. ―Mandruss☎15:16, 11 April 2018 (UTC)
I was about to reference WP:AVOIDYOU and then saw my hypocrisy. My apologies for responding with that 2nd paragraph, consider it redacted. Regarding judgement vs faith... really? It's generally about working toward improving the project, which I think we are both trying to do. Regardless, it wasn't fair for me to reference it in the first place and so I've redacted it as well. - PaulT+/C15:56, 11 April 2018 (UTC)
I don't wish to badger, but I'll take the question mark as an invitation to continue. Yes, "please AGF" is very often a response to constructive criticism, and that's incorrect as I understand it. Constructive criticism is essential to the work, and precious few editors have the ability to give it without sometimes hurting one's feelings or sounding condescending. I'm not one of them, to my regret. Had I realized that was your first edit at the article, my tone would have been a bit softer, however. ―Mandruss☎16:21, 11 April 2018 (UTC)
Badger isn't accurate, or at least not to me. I think we are generally in agreement. I think the only point I'm trying to make is regarding "the ability" you referenced. It is something I need to work on too (see the redactions) and I've found that being "a bit softer" is almost always better.¯\_(ツ)_/¯ I read your response as splitting hairs regarding the spirit vs letter of the guideline, hence the "really?". I didn't interpret all of what you wrote as constructive criticism, but I see now that was your intent. My responses here have been attempts at constructive criticism as well. I think a better approach would have been to revert and discuss on the article talk page with a bit more of an open mind. Having said all that, I think I'm bordering on badgering now... - PaulT+/C17:02, 11 April 2018 (UTC)
Special Counsel investigation (2017–present) revert
You'd have to ask User:Dispenser, but I'm pretty sure it's not a bug to remove those links and instead intentional cleanup per WP:DUPLINK. I'm indifferent toward them, though, and it does look like it was applied inconsistently. Sorry for the time you took to check it out and revert. —Ost (talk) 16:52, 12 April 2018 (UTC)
Hi Ost316, no worries it didn't take very long to fix. I mainly wanted to make you aware of the issue. Just FYI, links in references are preferred per WP:DUPLINK: Generally, a link should appear only once in an article, but if helpful for readers, a link may be repeated in infoboxes, tables, image captions, footnotes, hatnotes, and at the first occurrence after the lead. (I added bold for emphasis). The idea is that if someone is checking up on a reference they haven't necessarily seen an earlier link in the article and it is generally considered good practice to include links in references where possible and useful. Thanks for the follow-up. - PaulT+/C16:59, 12 April 2018 (UTC)
Thanks for the clarification so that I can be more careful in the future. I like your rationale for why the link would be "helpful to the readers" and repeatable, though I recall consensus being less clear on that at one point. —Ost (talk) 17:10, 12 April 2018 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Changes later this week
Profiling statistics for an abuse filter tell how often edits match the filter. The statistics for the abuse filters were reset after 10000 actions. Wikis can now decide to reset it more or less often. They can file a phabricator task to do so. [42]
Abuse filters will now treat integers and floats more precisely. For example, 5/2 was rounded down to 2 but will now be 2.5 and 2*4 will be the integer 8 and not the floating-point number 8.0. Division values are the only ones changed. For the rest only strict comparisons (=== and !==) will be affected leaving the values unchanged. [43][44]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 April. It will be on non-Wikipedia wikis and some Wikipedias from 18 April. It will be on all wikis from 19 April (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 17 April at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 18 April at 15:00 (UTC). See how to join.
Future changes
The new PDF renderer could not create PDFs from books. Books are in this case collections of pages on a Wikimedia wiki. PediaPress will take over development of the books-to-PDF function. [45]
Pywikibot will no longer support Python 2.7.2 and 2.7.3. [46]
Hi there Beyond My Ken, I do not think you are right about that. See MOS:DUPLINK where it states: if helpful for readers, a link may be repeated in ... footnotes. I'm happy to have a larger discussion about this with others in a more appropriate place, but I do not agree that "we generally do not do this" is accurate. Can you cite a policy somewhere disputing this? - PaulT+/C14:57, 17 April 2018 (UTC)
Well, let's say in my almost 13 years and 220,000 edits of experience, 70+% to articles, I have not come across it often, very rarely, actually. Beyond My Ken (talk) 15:00, 17 April 2018 (UTC)
Um, ok? Doesn't change the fact that "We generally do not do this." is not accurate just because you do not generally do this. Please cite some policy supporting your assertion. - PaulT+/C15:02, 17 April 2018 (UTC)
I've reverted the linking of locations since those are generally redundant per the language here: Template:Citation#Publisher. I think the links to publishers are relevant and so I left them in.
Note that you also removed other improvements to those templates when you wholesale reverted my changes, including the addition of |page= and |pages= in one case. Please be more careful when making changes in the future. - PaulT+/C15:20, 17 April 2018 (UTC)
No one looks at a reference and says to themselves "Oh, I've just got to learn more about Yale University Press", so your links are definitely violations of WP:OVERLINK. Beyond My Ken (talk) 20:11, 17 April 2018 (UTC)
In the context of a reference, the publisher is absolutely relevant and WP:OVERLINK encourages that kind of link. For example, someone may want to get a better understanding of the quality of the reference and something published by Yale University Press would carry more weight than something published by Phoenix University, but unless you are already familiar with both entities you wouldn't know that without the aid of the link. Your opinion isn't the only thing under consideration for these disputed links. This is an encyclopedia, not BMK's playground. - PaulT+/C04:47, 18 April 2018 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
The iOS and Android apps now have synced reading lists. This means you can save articles to a private list that can be seen on your other devices if you use the apps.
The visual editor and the 2017 wikitext ask you to write an edit summary after you press Publish. This button now also shows an ellipsis. This is to show that pressing Publish is not the last step. [48]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 April. It will be on non-Wikipedia wikis and some Wikipedias from 25 April. It will be on all wikis from 26 April (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 24 April at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 25 April at 15:00 (UTC). See how to join.
Future changes
<mapframe> will come to most Wikipedias in May. This means that you can put interactive maps in the articles. Nine Wikipedias that use a strict version of flagged revisions will not get this feature in May. [49]
The rollback function could change. This was a German community request. All editors with rollback rights can leave feedback on the proposed solution. The last day to leave feedback is 4 May (UTC).
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 parameter for unpatrolled edits in recent changes filters changed name. You might need to update saved filters and links. [50]
Problems
We are migrating wikis from Tidy to Remex. Because of a bug the 250 wikis which do not yet use Remex were switched on 23 April. This is two months early. This meant that pages with broken wikitext showed wrongly to readers. The bug was undone the next day. You can help fix broken wikitext to avoid this problem when your wiki switches. Tidy will be removed on all wikis before July 2018. You can follow the process on Phabricator. [51]
When an administrator blocks someone they will have a calendar they can use to choose when the block ends. This is to make it easier to pick a specific date. [53]
You can soon turn on the Performance Inspector in the Editing section in your preferences. It shows information about the performance of pages. This could be the size of modules in the page, how many CSS selectors are defined on the page and how many are used, or the size of the images on the page. This tool is intended to help editors fix pages that load slowly. [54]
There is a new abuse filter function called equals_to_any. You can use it to check if its first argument is equal (===) to any of the following ones. For example you can use it to check if the page's namespace is amongst a given set of values in a more compact way than you could earlier. You can read more on mediawiki.org.
The new version of MediaWiki will be on test wikis and MediaWiki.org from 1 May. It will be on non-Wikipedia wikis and some Wikipedias from 2 May. It will be on all wikis from 3 May (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 1 May at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 2 May at 15:00 (UTC). See how to join.
Future changes
The Wikimedia Cloud Services team is working on a new project called Toolhub. The goal is to make it easier for Wikimedians to discover software tools they can use. You can leave feedback on the talk page or email jharewikimedia.org to leave private feedback.
All wikis with fewer than 100 high-priority linter errors in all namespaces will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 2 May. Other wikis will be recommended to switch soon when they have fixed the errors that must be fixed. Wikibooks wikis with fewer than 100 high-priority linter errors in the main namespace will switch on 9 May. Tidy will be removed on all wikis before July 2018. [55][56][57]
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 Wikimedia Commons mobile app has a new version. It is now easier to find nearby places that need pictures. It helps you with direct uploads and title and category suggestions. The app only works on Android phones. [58]
Problems
The abuse filters had a problem with blocks where you had changed how long they last. It used the default length everywhere. This was in late April. Abuse filter users should make sure the right block length is used and change them if needed. This is only for filters where how long blocks last had been changed. [59]
Changes later this week
The advanced search function beta feature will be on all Wikimedia wikis. It makes it easier to use some of the special search functions that most editors don't know exist. [60]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 May. It will be on non-Wikipedia wikis and some Wikipedias from 9 May. It will be on all wikis from 10 May (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 8 May at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 9 May at 15:00 (UTC). See how to join.
Future changes
All wikis with fewer than 100 high-priority linter errors in the main namespace will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 16 May. Other wikis will switch soon when they have fixed the errors that must be fixed. Tidy will be removed on all wikis before July 2018. [61][62]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
The new Advanced Search interface is now available as a Beta Feature on all wikis. This makes it easier to learn about and to use many of the powerful options in our search. Feedback is appreciated. [63]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 May. It will be on non-Wikipedia wikis and some Wikipedias from 16 May. It will be on all wikis from 17 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 16 May at 15:00 (UTC). See how to join.
Future changes
In the mobile view, warnings for when something is wrong with a page are not as clear as they should be. The developers are working on this. You can give feedback and suggestions.
The developers are working on making the Wikipedia Android app available in more languages. You can give feedback, suggestions and help test it. Read more on mediawiki.org[64]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 22 May. It will be on non-Wikipedia wikis and some Wikipedias from 23 May. It will be on all wikis from 24 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 23 May at 15:00 (UTC). See how to join.
Future changes
It could become easier to reference different pages of a book in an article. You can give feedback. The last day for feedback is 27 May.
You are invited to join the Wikimedia NYC community for our monthly "WikiWednesday" evening salon (7-9pm) and knowledge-sharing workshop at Babycastles gallery by 14th Street / Union Square in Manhattan.
We will include a look at the organization and planning for our chapter, and expanding volunteer roles for both regular Wikipedia editors and new participants.
We will also follow up on plans for recent and upcoming edit-a-thons, museum and library projects, education initiatives, and other outreach activities.
We welcome the participation of our friends from the Free Culture movement and from all educational and cultural institutions interested in developing free knowledge projects.
After the main meeting, pizza/chicken/vegetables and refreshments and video games in the gallery!
7:00pm - 9:00 pm at Babycastles gallery, 145 West 14th Street
(note the new address, a couple of doors down from the former Babycastles location)
We especially encourage folks to add your 5-minute lightning talks to our roster, and otherwise join in the "open space" experience! Newcomers are very welcome! Bring your friends and colleagues! --Pharos (talk) 03:12, 23 May 2018 (UTC)
Jeannie Rhee, which you submitted to Articles for creation, has been created. The article has been assessed as Start-Class, which is recorded on the article's talk page. You may like to take a look at the grading scheme to see how you can improve the article.
You are more than welcome to continue making quality contributions to Wikipedia. If your account is more than four days old and you have made at least 10 edits you can create articles yourself without posting a request. However, you may continue submitting work to Articles for Creation if you prefer.
If you have any questions, you are welcome to ask at the help desk.
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
You can now use global preferences on most wikis. This means you can set preferences for all wikis at the same time. Before this you had to change them on each individual wiki. Global preferences will come to the Wikipedias later this week. [65][66]
It is now easier for blocked mobile users to see why they were blocked. [67]
There is now a checkbox on Special:ListUsers to let you see only users in temporary user groups. [68]
Some rare invisible Unicode characters have recently been banned from page titles. This includes soft hyphens (U+00AD) and left-to-right (U+2066) and right-to-left (U+2067) isolate markers. Existing pages with these characters will soon be moved by a script. [69]
There's a new Wikimedia Foundation team to support the Wikimedia technical communities. It's called the Technical Engagement team. Most of the team members did similar work in other teams before this. [70]
Problems
Some translatable pages are showing old translations instead of latest ones. The cause of this issue has been fixed. We will update all pages automatically to show the latest translations. [71]
Changes later this week
There will be a new special page named PasswordPolicies. This page gives information about the password rules for each user group on that wiki. [72]
A new way to see moved paragraphs in diffs is coming to most wikis. This is to make it easier to find the moved paragraphs and the changes in them. [73]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 May. It will be on non-Wikipedia wikis and some Wikipedias from 30 May. It will be on all wikis from 31 May (calendar).
Wikis can enable Citoid to provide automatic reference look-up in the visual editor and the 2017 wikitext editor. This is complex. The tool will now disable itself if the configuration isn't correct. It has warned about this in the JavaScript console since February. Check that your wiki is configured correctly. You can ask for help if you need it. [74]
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 29 May at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 30 May at 15:00 (UTC). See how to join.
Future changes
Content Translation drafts which have not been updated in over a year will be removed. This allows other users to translate those articles. [75]
A survey is collecting information on what users think about how Wikimedia wiki pages are loaded. This information could be used in future development. [76]
Some wikis will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 30 May and 13 June. Wikis with fewer than 100 linter issues in the main namespace in all high-priority linter categories will switch. This includes Wikidata. Tidy will probably be removed on all wikis in the first week of July. [77][78]
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 MonoBook skin has been optimised for mobile devices. It now looks different. [79]
Redirect links in Special:WhatLinksHere now link to the original page and not the target page. This was done earlier and changed the used messages on some pages. This was a problem for wikis that customized the message. A new change fixed this by using the old messages with one more parameter for customization. Wikis that already changed their customized messages will have to move the customization back again. [82]
Problems
You will not be able to edit some wikis between 06:00 and 06:30 UTC on 13 June. You can see if your wiki is one of them.
MassMessage did not work 24–28 May. This is also why last week's Tech News was late. [83]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 June. It will be on non-Wikipedia wikis and some Wikipedias from 6 June. It will be on all wikis from 7 June (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 5 June at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 6 June at 15:00 (UTC). See how to join.
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
In the Wikipedia app for Android or iOS users can create reading lists. The reading lists can be seen on different devices if you are logged in to your account. There is now a browser extension so you can add pages to your reading list from a web browser. At the moment it works with Firefox and Chrome. [86]
There is a new version of Pywikibot. Pywikibot is a tool to automate tasks on MediaWiki wikis. [87]
Problems
The MonoBook skin was changed to make it work better for mobile users. This caused some problems. The change was rolled back to fix them. The new version is now back on the wikis. MonoBook users can opt out from the new responsive design. [88]
Changes later this week
The new filters for edit review tools and interface for watchlists will leave beta. For most wikis this will happen on 18 June. For the rest it will happen on 25 June. [89][90]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 June. It will be on non-Wikipedia wikis and some Wikipedias from 13 June. It will be on all wikis from 14 June (calendar).
Meetings
You can join the Readers Web team IRC office hour. There you can discuss tools to contribute on the mobile web for the existing MediaWiki skins. The meeting will be on 18 June at 16:00 (UTC). See how to join.
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 12 June at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 13 June at 15:00 (UTC). See how to join.
