This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
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
If you forget your password you can ask for a new one to be sent to your email address. You need to know your email address or your username. You can choose that you need to enter both your email address and your username. This is a preference. This is to get fewer password reset emails someone else asked for. This is now available on all Wikimedia wikis. [1][2]
Problems
There is a bug that creates problems for iPhone users with iOS 13 and Safari. If you use an iPhone to read or edit Wikipedia and see bugs on the mobile site you can report them. [3]
Several wikis including Wikidata will be on read-only for a few minutes on 19 May. This will happen around 05:00 UTC. English Wikipedia will be on read-only for a few minutes on 21 May 05:00 UTC. This is for database maintenance. [4][5]
Graphs will be rendered in the reader's browser. This will use Javascript. Graphs will hopefully work better for everyone who uses Javascript. It will not work for users who don't use Javascript. This will not affect diagrams in image files. [7]
Some CSS for the skins has been simplified. This affects div#p-personal, div#p-navigation, div#p-interaction, div#p-tb, div#p-lang, div#p-namespaces, div#p-variants and div#footer. They will have to remove div. You will have to update your gadgets, scripts or user styles. This is so we can use HTML5. [8]
Some CSS for the Vector skin has been changed. This affects #p-variants, #p-namespaces, #p-personal, #p-views and #p-cactions. They can no longer use > ul. You might need to update your gadgets, scripts or user styles. See how.
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 visual editor will now work in the Modern skin. The changes that needed to happen for this to work could cause problems for some scripts or gadgets. [9]
The new version of MediaWiki will be on test wikis and MediaWiki.org from May 26. It will be on non-Wikipedia wikis and some Wikipedias from May 27. It will be on all wikis from May 28 (calendar).
... but I'm not happy about the talk page inclusion of DYK noms. I'd remove it the latest when the credit arrives, but don't understand for whom it would be helpful before. If this was discussed, I missed it, sorry. --Gerda Arendt (talk) 07:00, 21 April 2020 (UTC)
Gerda Arendt, are you talking about the dyk helper bot that transcludes the nom to the article talk? —valereee (talk) 11:10, 27 April 2020 (UTC)
discussed on WP:DYK, sorry for not marking moot here --Gerda Arendt (talk) 11:25, 27 April 2020 (UTC)
same: today, I was on an article talk page, saw the entry about the DYK nomination, and for first time was glad because I looked for the former hook, which had been changed in the queue (and I forgot that before appearing, it's not there yet, my mistake). In order to copy it, I had to click on "comment" in a discussion marked as closed. Could that be improved? ... could we perhaps have a direct link to the template, on top of the substitution? --Gerda Arendt (talk) 08:24, 10 May 2020 (UTC)
@Gerda Arendt: I'm glad you found it useful! I recently changed it per the above discussion with Mandarax, but I'll look into restoring it in a way that makes everyone happy! — Wug·a·po·des 22:06, 12 May 2020 (UTC)
Thank you for article improvements in May! - DYK my list of people for whose life I'm thankful enough to improve their articles? - I have a FAC open, one of Monteverdi's exceptional works, in memory of Brian who passed me his collected sources. --Gerda Arendt (talk) 20:47, 17 May 2020 (UTC)
The Wikimedia Foundation announced that they will develop a universal code of conduct for all WMF projects. There is an open local discussion regarding the same.
Arbitration
A motion was passed to enact a 500/30 restriction on articles related to the history of Jews and antisemitism in Poland during World War II (1933–45), including the Holocaust in Poland. Article talk pages where disruption occurs may also be managed with the stated restriction.
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
There is a new beta version of the Wikimedia Commons app for Android. It has a new zoom function when you look at images. It can also suggest places when you upload geotagged photos. [10]
Problems
There was a problem with the Commons database on 27 May. Commons could not be edited for eight minutes. Because of this problem the database was moved. This caused another short read-only time on 29 May. [11][12][13]
The Vector skin had a problem where you couldn't add links to the article in other languages. You couldn't see the section if there were no links to other languages already. It also removed content translation links and links to language settings. This has now been fixed. [14]
Changes later this week
You can get a notification when someone links to a page you created. You can turn these notifications off for individual pages. You can soon turn them off also in the notifications you get. [15]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 June. It will be on non-Wikipedia wikis and some Wikipedias from 3 June. It will be on all wikis from 4 June (calendar).
Thanks! Heard of the concept, did initial research to find the first clue, but really had no idea. :D —valereee (talk) 03:52, 5 June 2020 (UTC)
@Valereee: You did a good job starting it; those sources are really good! Verso currently is offering The End of Policing as an e-book for free, so if you want to read it or use it as a source it's available from their website. — Wug·a·po·des 04:00, 5 June 2020 (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
Some articles have tables that can be sorted in different ways. For example a list of countries can be sorted alphabetically but you can click on the size column to sort them by size. If you clicked on the column a second time it would sort the countries from the bottom to the top instead. A third click will now take you back to the original sorting. [16]
Self-closed tags now work as in the HTML5 specifications. This means you should stop using some of them. <b/> is an example of a self-closed tag that won't work. area, base, br, col, embed, hr, img, input, keygen, link, meta, param, source, track, wbr can be self-closed. Pages with tags that should not be self-closed have been listed in a tracking category since 2016. They will be listed in Special:LintErrors/self-closed-tag. This doesn't affect <references /> or <ref />. [17]
There is a banner called WikidataPageBanner. It is for example used by the Wikivoyages, Wikimedia Russia and the Catalan, Basque, Galician and Turkish Wikipedias. It will now been seen by mobile visitors too. Before this it was only seen on desktop. The wikis should update instructions on MediaWiki:Sitenotice so that editors know to test and style for mobile too. [18][19]
Changes later this week
You can now edit MassMessage descriptions through the API. This is useful for tools and gadgets. [20]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 June. It will be on non-Wikipedia wikis and some Wikipedias from 10 June. It will be on all wikis from 11 June (calendar).
Future changes
A temporary fix helped wikis make their main pages more mobile friendly. This was in 2012. It has not been recommended since 2017. It will not work after 13 July. Wikis should use TemplateStyles instead. 118 wikis need to fix this. You can read more and see if your wiki is affected. [21]
A page you fully protected for 7 days (https://en.wikipedia.org/w/index.php?title=Assyrian_people&diff=960450782&oldid=960430632) last week is now has no protection. It was under the indefinite semi-protection for persistent unconstructive edits before the additional full-protection (https://en.wikipedia.org/w/index.php?title=Special:Log&page=Assyrian+people) but after the full protection has been expired, the previous semi-protection has also been automatically removed. I thought this was not your intention, so I just wanted to let you know as you might want to restore the previous protection level (before the full protection). This is one of the high-visibility pages in Wikipedia and is notorious for its conflicts. Kind regards, 85.111.53.62 (talk) 09:15, 11 June 2020 (UTC)
Done, thanks Anon for letting me know. — Wug·a·po·des 19:02, 11 June 2020 (UTC)
It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 06:18, 12 June 2020 (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
Toolforge hosts several tools created by the Wikimedia community like edit counters or enhanced editors. It is changing the domain from tools.wmflabs.org to toolforge.org. The routing scheme is moving from tools.wmflabs.org/toolname to toolname.toolforge.org. You can read the details. Tools that use OAuth will have to be updated to keep working. You can ask for help.
Problems
There is a Wikidata item link in the sidebar on many pages. This disappeared for a couple of days for users who have the Monobook skin. This was because of a bug. It has now been fixed. [22]
Editing, logging in and logging out didn't work properly for a short period of time last week. It was soon fixed. [23]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 June. It will be on non-Wikipedia wikis and some Wikipedias from 17 June. It will be on all wikis from 18 June (calendar).
Future changes
Pywikibot is a Python library to automate work on wikis. It will not support Python 2 after the new version in July. Support for Python 3.4 and MediaWiki below 1.19 will also be dropped. You should migrate to Python 3. You can ask for help. [24]
The selectors .menu and .vectorMenu will no longer work in the Vector skin. This can affect gadgets and user scripts. .menu should be replaced by ul. .vectorMenu should be replaced by .vector-menu. [25]
NPP Sorting can be a great way to find pages needing new page patrolling that match your strengths and interests. Using ORES, it divides articles into topics such as Literature or Chemistry and on Geography. Take a look and see if you can find time to patrol a couple pages a day. With over 10,000 pages in the queue, the highest it's been since ACPERM, your help could really make a difference.
Google Adds New Languages to Google Translate
In late February, Google added 5 new languages to Google Translate: Kinyarwanda, Odia (Oriya), Tatar, Turkmen and Uyghur. This expands our ability to find and evaluate sources in those languages.
Discussions and Resources
A discussion on handling new article creation by paid editors is ongoing at the Village Pump.
Also at the Village Pump is a discussion about limiting participation at Articles for Deletion discussion.
Well, thank you! I was under the impression that whoever promotes a set to the queue has to check all the hooks; I hope you get some help! Best, Yoninah (talk) 23:35, 20 June 2020 (UTC)
Yup, but the checking isn't really that hard, just tedious. There's a lot of tabs and edit windows open at once, so I sometimes forget which ones I need to hit save on. It tends to be fine though, the DYK regulars are very good about letting me know when I mess up! Hope my promotion of prep 2 didn't mess you up; my thinking was that more empty preps would be helpful. — Wug·a·po·des 23:45, 20 June 2020 (UTC)
Well, I had just built Prep 2 tonight, and usually Ravenpuff edits it before it's promoted. But he also posts at ERRORS if there's any problem with the wording. So all's good on this end. Thanks again, Yoninah (talk) 23:50, 20 June 2020 (UTC)
No problem, you did most of the hard work! It's still pretty early in my time zone, so if there are any changes that need made to Q2 just ping me or post here and I'll be happy to fix them. Worst case I can just revert the promotion pretty easily. — Wug·a·po·des 23:55, 20 June 2020 (UTC)
Noted with thanks, Yoninah. I've noticed only a couple minor errors – the Boie's frog and Banhado frog should read instead "Boie's frog and the Banhado frog", and the last hook includes the contraction can't, which should normally be avoided, though perhaps we could let this one slide because it's in the quirky slot. — RAVENPVFF·talk· 03:48, 21 June 2020 (UTC)
@Ravenpuff: I fixed the first one; The Cock hook was actually my favorite, so I'd like it if we could let it slide, but I also thought "that taking pictures of The Cock is prohibited?" might be okay. — Wug·a·po·des 06:16, 21 June 2020 (UTC)
Yeah, that seems fine by me. Pinging nominator Armadillopteryx as a courtesy. — RAVENPVFF·talk· 10:02, 21 June 2020 (UTC)
Personally, I like the current phrasing in The Cock hook. Using words like is prohibited is much more formal and cues the reader that we're talking about a place.
Also, in the second hook, 16-year-old needs a second hyphen. Yoninah (talk) 11:05, 21 June 2020 (UTC)
I also think The Cock hook loses some of its hookiness/quirkiness if we change the wording. I guess something like ... that The Cock cannot be photographed? would also work, though I prefer the current version. Armadillopteryxtalk 12:02, 21 June 2020 (UTC)
re Healthynox Corporation
Not sure how semiprotecting creation will help on Healthynox Corporation, given that non-confirmed users can't create mainspace articles anyways... –Majavahtalk · edits 15:34, 21 June 2020 (UTC)
Oh duh, right. I've removed it. — Wug·a·po·des 23:01, 21 June 2020 (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.
Problems
There are some new tools to make it easier for newcomers to start editing. They are available on some wikis. These wikis had a problem with the visual editor for a short period of time last week. This was because of a bug in the new tools. It was soon fixed. [26]
Some user scripts and gadgets stopped working because of a change to CSS selectors. .vectorTabs should be replaced with .vector-menu-tabs to fix this. [27]
Changes later this week
The developers are working on a new interface to solve edit conflicts on talk pages. This will be released on 24 June. You can give feedback. [28]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 23 June. It will be on non-Wikipedia wikis and some Wikipedias from 24 June. It will be on all wikis from 25 June (calendar).
Future changes
A temporary fix helped wikis make their main pages more mobile friendly. This was in 2012. It has not been recommended since 2017. It will not work after 13 July. Wikis should use TemplateStyles instead. 91 wikis still need to fix this. You can read more and see if your wiki is affected. [29]
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
Everyone was logged out. This was because a few users saw the wikis as if they were logged in to someone else's account. The problem should be fixed now. [30]
Some readers didn't see new edits to pages. If the page had been recently changed they saw an older version of the page instead. This only affected readers who were logged out. It lasted for ten days. It has been fixed. [31]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 30 June. It will be on non-Wikipedia wikis and some Wikipedias from 1 July. It will be on all wikis from 1 July (calendar).
Future changes
The Modern and Monobook skins use the ID searchGoButton for the go button. This is searchButton for Vector. To have the same ID for all skins it will change to searchButton in Monobook and Modern too. This will affect gadgets and user scripts. It will happen on 23 July. They should be updated to use searchButton. You can read more and see a list of affected scripts.
Hi Wugapodes. You blocked this IP after I requested page protection for Bourla. Many thanks for that but I see they are back doing the same thing from a different IP address. Could you possibly take a look please. Robvanvee 06:08, 29 June 2020 (UTC)
Hi Robvanvee it looks like Johnuniq got there before I did and has protected the page for a few days. Hopefully that helps, but let either of us know if the person comes back after protection expires. — Wug·a·po·des 19:26, 29 June 2020 (UTC)
Doh! I forgot to let you know, yes. Many thanks for all your help Wugapodes! Robvanvee 19:33, 29 June 2020 (UTC)
The Medicine case was closed, with a remedy authorizing standard discretionary sanctions for all discussions about pharmaceutical drug prices and pricing and for edits adding, changing, or removing pharmaceutical drug prices or pricing from articles.
The third round of the 2020 WikiCup has now come to an end. The 16 users who made it into the fourth round each had at least 353 points (compared to 68 in 2019). It was a highly competitive round, and a number of contestants were eliminated who would have moved on in earlier years. Our top scorers in round 3 were:
Epicgenius, with one featured article, 28 good articles and 17 DYKs, amassing 1836 points
The Rambling Man , with 1672 points gained from four featured articles and seventeen good articles, plus reviews of a large number of FACs and GAs
Gog the Mild, a first time contestant, with 1540 points, a tally built largely on 4 featured articles and related bonus points.
Between them, contestants managed 14 featured articles, 9 featured lists, 3 featured pictures, 152 good articles, 136 DYK entries, 55 ITN entries, 65 featured article candidate reviews and 221 good article reviews. Additionally, MPJ-DK added 3 items to featured topics and 44 to good topics. Over the course of the competition, contestants have completed 710 good article reviews, in comparison to 387 good articles submitted for review and promoted. These large numbers are probably linked to a GAN backlog drive in April and May, and the changed patterns of editing during the COVID-19 pandemic. As we enter the fourth round, remember that any content promoted after the end of round 3 but before the start of round 4 can be claimed in round 4. Please also remember that you must claim your points within 14 days of "earning" them. When doing GARs, please make sure that you check that all the GA criteria are fully met. Please also remember that all submissions must meet core Wikipedia policies, regardless of the review process.
Hi Wugapodes, I think T202989 is waiting for you right now? If so, could you check in on it if you have the time? Best regards, — xaosfluxTalk 14:34, 30 June 2020 (UTC)
@Xaosflux: It's next on my to do list; I got sidetracked by some meatspace business. I'm still trying to understand the code better, and I've recently switched operating systems so have run into some problems getting the tests set up again. Slow going but I'm on it! — Wug·a·po·des 20:34, 2 July 2020 (UTC)
Nomination for merging of Template:Manner of articulation
Speaking of The Sounds of the World's Languages, I never quite understood why that page is a redirect to Ladefoged when the book is cited in so many articles it has a dedicated template and he isn't the sole author. It's been cited by thousands of publications (if Google Scholar is anything to go by) and has reviews in some prominent journals, so I have to assume it passes WP:NBOOK. But I don't know what to write beyond a substub so I've been having second thoughts, then I realized you're the perfect one to take a stab at it. Just an idea. Nardog (talk) 08:58, 5 July 2020 (UTC)
Article created. Feel free to do whatever you want to do with it. Nardog (talk) 02:54, 6 July 2020 (UTC)
@Nardog: Thanks for doing this! It looks good, and the sources you added will be very useful for expanding it. I'll be occupied the next couple days with the LabPhon conference, but I look forward to working on it soon! — Wug·a·po·des 05:00, 6 July 2020 (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.
Problems
The Score extension has been disabled for now. This is because of a security issue. It will work again as soon as the security issue has been fixed. [32]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 July. It will be on non-Wikipedia wikis and some Wikipedias from 8 July. It will be on all wikis from 9 July (calendar).
Future changes
Abstract Wikipedia is a new Wikimedia project. It will collect language-independent information that can be easily read in different languages. It builds on Wikidata. The name is preliminary. You can read more. [33]
Some rules for user signatures will soon be enforced. Lint errors and invalid HTML will no longer be allowed in user signatures. Nested substitution will not be allowed. A link to your user page, user talk page or user contributions will be required. You can check if your signature works with the new rules. This is because the signatures can cause problems for tools or other text on the page.
Hi, I want to use User:WugBot's updating covid-19 datas function in TR Wikipedia. Can you help me? Tekask1903 (talk) 06:28, 23 June 2020 (UTC)
Hi Tekask1903 I can gladly help. The source code is on GitHub if you want to see it. The easiest way to have WugBot update data on trWikipedia would be to update its code to edit the Turkish pages at the same time it edits the English pages. I see that TR Wikipedia has a bot policy and an approval process. I can't read Turkish, so you would be the one who should ask for approval. You can look at my request to help you fill out the form. While that process happens, I will work on setting the bot to run on the Turkish Wikipedia. — Wug·a·po·des 06:43, 23 June 2020 (UTC)
Okay I will refer. Tekask1903 (talk) 06:56, 23 June 2020 (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
Users can thank others for their edits. Checkusers can now see user data related to that action. This can help identify sock puppets who harass others using thanks. [34]
Problems
Everyone was logged out a couple of weeks ago to fix a security problem. The problem was not entirely fixed. Because of this everyone was logged out once again last week. [35][36]
Changes later this week
Wikis that are not for one specific language can translate pages. Sometimes parts of translations are outdated or missing. Outdated translations are marked with a pink background. Missing translations will also be marked in the future. This markup can sometimes break things. It can soon be disabled by using <translate nowrap></translate> on the source page. [37]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 14 July. It will be on non-Wikipedia wikis and some Wikipedias from 15 July. It will be on all wikis from 16 July (calendar).
Future changes
Wikimedia code review plans to use GitLab. It would be hosted on Wikimedia servers. [38][39][40][41]
I just saw this, as you'd linked it from the RfArb. Thank you for putting that together—it was interesting to see a formal approach to the question of trend lines. It's always intuitively struck me as a faulty concept, and an example of confirmation bias and overinterpetation of noise. Sort of like repeating statistical significance testing again and again, and then stopping a study once the p value crosses the 0.05 threshold. But it's neat to see formal validation. Thank you for that—I'll remember to bring my R questions to you in the future. :) MastCellTalk 17:59, 9 July 2020 (UTC)
@MastCell: Thanks, it was actually pretty fun to put together. Interpreting trends in discussions is an attractive concept because of the psychological basis of the gambler's fallacy. Used correctly, analyzing trend lines at RfA could give interesting insight into voter behavior, and it probably wouldn't require too complex a model. If we suspect some piece of information (exhibit A) at time t changed the underlying support probability, we could build two models (1) a model similar to the one in that essay and (2) a model where the underlying support probability stayed constant (probably whatever the final percentage was) and then use model comparison to figure out which one is more likely given the actual RfA data. If the one with the switch parameter is a better fit, then we can reasonably conclude that exhibit A caused a change in opinion. It's definitely something that can be done, probably in a reasonable length of time too, but making claims about trends with any confidence would require a more rigorous methodology than just looking at the graph. So yeah, that's probably the more nuanced takeaway from that essay: trend lines aren't useless if you want to put in the leg work but most of the time we don't put in the leg work so it's best to just ignore them. And I'm always happy to answer R questions! — Wug·a·po·des 20:23, 13 July 2020 (UTC)
Interesting... I see what you're saying. But in this specific case, wouldn't you still be left with the underlying problem of HARKing? I mean, people are looking at a completed/closed discussion, retrospectively picking out a timepoint at which the tide ostensibly turned, then statistically "validating" the timepoint they've chosen. Regardless of the sophistication of the statistical approach, they're formulating a hypothesis retroactively with perfect knowledge of the course of the discussion/dataset. Internally, no doubt, they've considered and rejected a bunch of other potential "turning points", because those don't fit with the data. Formally, these are data-dependent analyses, and, if we were using null-hypothesis significance testing, this would constitute p-hacking. Does that sound right to you?
Like, if I look at the box score of a completed baseball game and notice a scoring trend, and then pick an event that happened somewhere around the time that the trend started, that would be really weak sauce in terms of causal inference. I suppose that if, at the time of a specific comment or event, an editor identified it as a potential tide-turner in real time and then prospectively validated that hypothesis, that might be somewhat stronger—analogous to pre-registration of clinical trials and pre-specification of endpoints.
Anyhow, just thinking out loud. It's a pleasure to have someone to discuss these questions with, and I'm curious about your thoughts. Take care. MastCellTalk 21:28, 13 July 2020 (UTC)
@MastCell: I think it's definitely a grey area of HARKing (that article also needs an MOS cleanup but that's for another time). I don't think it's completely correct to say we know the results, at least, of whether and when the tide has turned. We have hypotheses based on a lot of a priori knowledge, but it's completely possible to say "I think this comment or piece of evidence caused a major shift" and then test and reject that hypothesis. The problem is as you're saying though, if we're picking a bunch of points haphazardly without justification or performing multiple tests then we're just p-hacking.You're right that using frequentist methods, there's a lot of issues here, and I think some of these problems could be sidestepped by a Bayesian change point analysis. We would be forced to incorporate our prior knowledge into our model gives us an estimate of just how informative that prior is compared to others (there's a good article on analyzing the efficacy of COVID-19 responses using change point analysis in Science Mag: Dehning, et al 2020). We could say that the probability of the p parameter of the binomial distirbution switching to some other value p′ follows a half-normal distribution centered on the time the comment/evidence was posted (impossible before, and less likely as you get further from the time of comment). We could compare that to a model where the switch point probability followed a uniform distribution, and one where we don't have a switch point.This allows us to better answer the questions we started out with. For example, the uniform prior model would be what you were saying; what if it's just modeling random noise or we've implicitly rejected a switch point that better fits the data (but which is inconsistent with our hypothesis)? If our informed prior is actually important, it should be much better than the uniform prior and the ratio of their Bayesian Information Criteria should be large. Even if it was, we would also be able to estimate whether the change is actually consequential. It's possible that we could infer a switch point at the expected time, but that it's only a shift of one or two percentage points and wouldn't actually change the result. I've used rational speech act models which are Bayesian models of pragmatic inference, but switch point problems pretty much never come up so I haven't done one myself. It seems like it would be a good fit for this problem, and it could probably be run on old crat chats. The data should probably be anonymized though since it could be used spuriously to undermine trust in crats and administrative decisions. And no worries about thinking out loud. It's an interesting problem, and it led to two redlinks that should be turned blue so it's helping build the encyclopedia in more ways than one. — Wug·a·po·des 22:43, 13 July 2020 (UTC)
@Mandarax: I believe I've fixed it; also good news BlueMoonset, |subpage= is now added to all DYKmake templates. Let me know if either of you see issues with the update. — Wug·a·po·des 00:05, 14 July 2020 (UTC)
Hi. Please could you remove Category:Example_category from ((Editnotices/Page/User:Wugapodes/sandbox))? At the moment it's adding to the backlog at Special:WantedCategories. Not only should you never add red-linked categories to any page per WP:REDNOT, arguably it's a user page and so should never have any categories per WP:USERNOCAT.FYI, the "official" test categories are in the Category:Xn hierarchy. TIA Le Deluge (talk) 13:59, 14 July 2020 (UTC)
Done. It was a test page I forgot to delete after updating ((Editnotice)) , thanks for letting me know! — Wug·a·po·des 20:20, 14 July 2020 (UTC)
Racial views of Joe Biden
Given the proposed version is contested, I've copied the discussion to Talk:Racial views of Joe Biden for wider comment on what version we should return to. — Wug·a·po·des 00:50, 20 July 2020 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I object to locking the article right after user:Volunteer Marek removed large portions of material. This is an attempt to influence the AfD by removing content and sources. He also falsely claimed he was removing BLP violations when everything was sourced to reliable sources. He removed CNN, the Washington Post, and Politico as sources. How can people fairly evaluate the article at AfD when he basically just blanked the article? Please reconsider.--Rusf10 (talk) 21:49, 19 July 2020 (UTC)
@Rusf10: Per the banner I left: "This protection is not an endorsement of the current version". If you can identify a stable version prior to the edit war, I will consider reverting to that (see WP:PREFER). Personally, I had a hard time finding one, so I just protected the version it was at when I got there. As someone familiar with the article, you may have an easier time identifying one. You can also discuss changes on the talk page to establish consensus and then request an edit. — Wug·a·po·des 21:57, 19 July 2020 (UTC)
Also, I'm about to go offline, so unless you see me making some edits, you may want to ask an admin who's active at the time. — Wug·a·po·des 22:16, 19 July 2020 (UTC)
I don't fault you for locking it. But, since the article is at AfD, the version presented should not have large amounts of content removed. I would support this version just prior to the mass removal (blanking) of content.--Rusf10 (talk) 22:18, 19 July 2020 (UTC)
That version is a BLP vio. You don’t get to “commit BLP vio because the article is being considered for deletion”. Lol. Volunteer Marek 22:32, 19 July 2020 (UTC)
That's a false claim. Where is the BLP vio. You even removed direct unedited Biden quotes from reliable sources. Something is not a BLP violation just because it makes Joe Biden look bad. Also, if you were serious about BLP violation, you wouldn't be laughing.(I certainly don't find anything funny about this)--Rusf10 (talk) 00:05, 20 July 2020 (UTC)
Rusf10, that version was full of BLP violations. And what's the rationale provided by the tiny minority of editors who have not voted to delete the article? That, based only on their own OR and with no source making the comparison, they would like to hold up random remarks from Biden's 77 year life as somehow equivalent to Trump locking up dark-skinned children to die in filth behind chain-link fences in South Texas? Or any of the other well-sourced, RS-verified content in the Racial views of Trump article. Nobody's with you on this. Drop it. SPECIFICOtalk 00:26, 20 July 2020 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Not clear why we would discuss reinstating BLP smears that are not based on the weight of or for that matter on any RS interpretation that supports them. SPECIFICOtalk 01:19, 20 July 2020 (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
A temporary fix helped wikis make their main pages more mobile friendly. This was in 2012. It has not been recommended since 2017. The mobile main page special casing stopped working 14 July. 60 wikis now have main pages that don't work well on mobile. You can see which ones, how to fix it and how to get help in Phabricator. This is the same problem that was reported in Tech News 2020/24 and 2020/26.
Problems
There is a problem with the interlanguage links. The interlanguage links are the links that help you find a specific page in a different language. The sorting is broken. The developers are working on a solution. [42]
Some users keep getting the notifications for the same event. Some of these are old events. [43]
Some users have trouble logging in. This is probably a browser cookie problem. The developers are working on understanding the problem. If you have trouble logging in you can see the details on Phabricator. [44]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 July. It will be on non-Wikipedia wikis and some Wikipedias from 22 July. It will be on all wikis from 23 July (calendar).
Future changes
There is a Printable version link. This will disappear. That is because web browsers today can create a printable version or show how it will look in print anyway. [45]