Wed, Sep 23
@Lucas_Werkmeister_WMDE Seems to be gone for me (checking page source). Maybe it just took a bit of time to take effect?
Sep 17 2020
Sep 14 2020
Sep 10 2020
Sep 8 2020
Aug 24 2020
No founding principle of Wikipedia would be disrespected.
I recommend reading the second Wikimedia founding principle: "The ability of almost anyone to edit (most) articles without registration."
Jul 28 2020
Jun 14 2020
Jun 5 2020
Jun 4 2020
Jun 3 2020
May 13 2020
Removed most of the subscribers. Subscribing hundreds of people is not an appropriate way to notify them, and having everyone notified about every comment and change here is basically spam. Frankly, I'm surprised Phabricator even allowed that. It really shouldn't, IMO.
May 12 2020
wikimediafoundation.org is the corporate website of a particular Wikimedia organization, the Wikimedia Foundation. wikimedia.org is a movement site. Redirecting one to the other would not make sense.
Apr 23 2020
Apr 2 2020
Mar 30 2020
Mar 23 2020
Mar 19 2020
Mar 17 2020
I suspect that there may be a fair amount of new-ish users who patrol the recent changes, and wouldn't want every instance of reverted vandalism to result in another page they know nothing about added to their watchlist. Maybe the preference option can be split to not include reverts as regular edits?
@Reedy When I view that page, I don't see an "Active users" column. Also, the sentence "A maximum of 5,000 results are available in the cache." does not appear on the page.
The GadgetUsage system is maintained by Community-Tech, I think?
I notice that this runs on every wiki except for the English Wikipedia. Was this a deliberate decision (performance reasons, presumably?), or is it a bug?
Mar 5 2020
Mar 3 2020
When viewing a category on Commons, there's a link in the sidebar titled "RSS feed", linking to a feed of that category, generated by the CatFood tool hosted on the Toolserver. It can also generate RSS feeds of uploads from a particular account.
Mar 2 2020
Feb 26 2020
Most query results sets meant for human consumption would benefit from having the results sorted by pageviews. Needing to filter for a certain level of prominence is very common, and using the API isn't a workable solution for most people who would benefit from this.
Feb 25 2020
Feb 24 2020
Feb 17 2020
Feb 11 2020
Feb 10 2020
Feb 6 2020
APIs can't normally be used from wiki pages. And doing just a one-time upload of existing data sets means that Commons won't reliably have an up-to-date dataset, meaning wikis wouldn't be able to rely on them.
@Nuria Sorry, I didn't mean that it would be used on Commons itself. Data uploaded to Commons can be used on all Wikimedia wikis, via Lua modules. This would be useful on Meta and on some (statistics) project pages on some content wikis.
Feb 2 2020
Jan 1 2020
Dec 11 2019
Promoting the use of social networks from Wikimedia projects is really problematic, IMO.
Nov 18 2019
(Also relevant: T55740.)
Ideally, these would probably also be working like edittools, in the sense that clicking on the elements would add them to the code. This would depend on T55743 being fixed.
Nov 17 2019
For general issues with forking/merging pages, see T113004.
Nov 14 2019
Oct 23 2019
Oct 7 2019
How will this work for projects with a different main page for each language, eg Commons? The main page depends on the user's interface language. Normally, if you're a French-language user and you navigate to https://commons.wikimedia.org/ , you get redirected to https://commons.wikimedia.org/wiki/Accueil . Will https://commons.wikimedia.org/ still show the correct content to each user?
Sep 22 2019
We already have pings, and cross-wiki notifications, and there's a team working on increasing the usability of existing talk pages further.
Sep 12 2019
At first glance, this certainly sounds necessary. It's a multilingual site, and should work for everyone.
Sep 9 2019
Ideas to lower the number of potential problems:
- Make the numbers less precise, somehow? Something like making each unique editor have a 10% chance of being skipped in the count and 10% chance of being counted twice, or some such. (This would need to persist per editor between reports, I think. Maybe even do the same thing to the changes in numbers when someone leaves.)
- Don't generate a new report when only one editor has joined or left since the previous report. Perhaps even per-country, don't update unless there's a change of at least several counted users since the last report.
(Probably stupid question: Aren't there people who actually specialize in this kind of thing, with established methods for preventing leaking data on particular individuals?)
Sep 8 2019
Sep 1 2019
Okay, I know this was closed as declined, but the problems mentioned seem really easy to solve. Variable naming conflicts with keywords can be handled the same way any decent transpiler handles them (adding/removing underscores as necessary to avoid conflicts), and importing/exporting and cross-wiki maintenance can be handled by a "base" form in English not normally visible but easily accessible. Here's a working English-to/from-other Lua translator: https://gist.github.com/YairRand/e22aded969e6de8cbb283e62868153a1 .
Aug 29 2019
So, to be clear: This is about when developers need temporary local user rights necessary for software testing?
In what cases would T&S need to add local user rights to staff accounts?
Aug 28 2019
Aug 27 2019
I modified the Graph module to use the user-specified order (ie y1 goes before y2), rather than alphabetical order, and copied the changes to the version on mediawiki.org. Seems fixed.
Aug 25 2019
Aug 21 2019
Several examples of ways to find out a user's country: (Note: A lot of this depends on how frequently this report will be published.)
- Data is published, some time passes, during which precisely one new editor has shown up who wasn't there previously. The counter for one country goes up a step from, say, 20-30 to 30-40. This user's country has been revealed.
- A very small wiki that normally wouldn't have the data published has exactly one editor. A malicious user trying to determine that editor's country creates nine "active" accounts in a particular country. If the counter shows 10+, the country has been revealed. The malicious user can repeat, and also test many countries at once to narrow it down.
- Combination of the above tactics: A malicious user tries to keep several countries' counters at the boundary, so that either a new user will cause the count to increment, or a leaving user will cause it to decrement. If all users joining in the same duration but one can be ruled out by time-zone data or similar, the remaining user's country has been revealed.
- There are ten active editors on a project. One of the countries shows 10-20. The country of all of the editors has been revealed.
- There are 16 active editors on a project. A malicious user creates four active accounts in a country. The counter shows 20-30. The country of all of the editors has been revealed.
Aug 19 2019
For "Wikimedia", the original colored Wikimedia logo would be correct, IIRC.
Aug 18 2019
Unless I'm very much mistaken, the described system will make it possible to determine the country of specific editors, in some situations.
Aug 13 2019
Aug 9 2019
I've been working on a template on Meta for working with staff data at m:Template:WMF Staff, which can be used to automatically populate various kinds of navboxes and team galleries on Meta-Wiki. It also fills m:Wikimedia Foundation staff and contractors, which is in the process of being styled like the current WMF site's list in the hope that whoever manages that site might redirect the page to Meta, and fills m:Wikimedia Foundation staff and contractors/oldstyle (probably to be renamed at some point), which maintains the design of the old list, including subteams.
Aug 8 2019
Aug 6 2019
Aug 5 2019
Jul 31 2019
Jul 18 2019
I would recommend moving the contents of the docs on-wiki as well. Using Google Docs is very problematic in various ways (closed-source, non-transparent, far away from Wikimedia activities, privacy issues, etc).
Jul 4 2019
Agree, having all redirect special pages work preserve safemode would be a good thing.
Jun 27 2019
Jun 26 2019
Apr 30 2019
Mar 25 2019
@Nuria The WMF internal wiki isn't publicly accessible, making its contents unavailable to the community. Unless there's particular reason the guidelines need to be withheld, I would think that reasonable transparency would require that they not be hidden inside the WMF's private wiki.
Mar 19 2019
Couldn't the complex constraints be migrated to statements, if that's what it would take?
Mar 6 2019
Mar 5 2019
While that will solve many applications of linking to directly editing a statement, I suspect it will not solve all of them.
Mar 3 2019
Another suggestion: When ?x is declared as a variable, ?xLabel should be on the list of suggestions for variable names.
Feb 26 2019
Dec 10 2018
This should also work in the "Constraints" section, which, afaict, only allows the "property constraint" property (P 2302).
Nov 22 2018
The issue appears to have since been fixed, I think.
Nov 21 2018
The current policy of prohibiting passwords that are only lowercase letters prohibits the strongest passwords (eg correct horse battery staple) from being used. Adding extra requirements of this sort basically means that people will start recording their passwords in non-secure locations.
Oct 31 2018
This is basically going to force people into having bad passwords. Length is not a good indicator of password strength, and the current requirements prohibit the strongest memorable passwords. Forcing people to have less memorizable passwords means that they'll use more easily guessable passwords.
Oct 22 2018
This worked until recently. It showed a diff of everything that was added, which was quite useful. (My userscript relied on it, and is now getting errors as a result of this change.) Requiring a different API call to get all the added lines from the first revision as from all other revisions seems needlessly complicated.
Oct 21 2018
Is there a particular reason the draft data access guidelines linked above need to be specifically confidential? If not, could they be posted to a public wiki?