Thu, Apr 11
Thu, Mar 28
It's pretty wild that this task remains unresolved. It was reported in July 2018 and we're entering April 2019 next week. Eight months!
Wed, Mar 27
Hi @smernst. Are you still interested in discussing this Python module?
Mar 18 2019
Jan 26 2019
What needs to happen to move this task forward? An e-mail to firstname.lastname@example.org?
Jan 15 2019
Related: https://commons.wikimedia.org/wiki/Commons:File_captions now exists.
@Aklapper: it's neither helpful nor constructive to call out "wtf" as swearing. You're quite aware of this.
Jan 4 2019
Dec 28 2018
Dec 19 2018
When visiting which URLs?
Dec 18 2018
Dec 12 2018
Dec 1 2018
Nov 30 2018
(I'm side-stepping whether this change should have been made at all or in this fashion to answer this specific question.)
Nov 11 2018
Nov 8 2018
Nov 1 2018
Oct 31 2018
Oct 27 2018
Oct 24 2018
Oct 17 2018
This task description says that "we don't actually support HTTP anymore" and @Bawolff said the same on IRC this evening. This statement feels misleading since we do support HTTP and will continue to do so indefinitely. Keeping the HTTP --> HTTPS redirects working means supporting HTTP, as far as I'm concerned.
Oct 14 2018
We could also add pages to a maintenance category such as "Pages that contain non-whitelisted external images" or similar.
Oct 11 2018
Oct 6 2018
Oct 2 2018
Sep 23 2018
Sep 18 2018
What's the upgrade process? I don't suppose one of us can just run apt-get upgrade or similar?
Sep 17 2018
Sep 6 2018
Aug 30 2018
I would really like the transclusions count at https://en.wikipedia.org/w/index.php?title=Template:Infobox_SCOTUS_case&action=info.
Aug 26 2018
Regarding the task description, is "Wikimedia's" more accurately "Wikimedia Foundation Inc.'s"?
Aug 3 2018
Jul 31 2018
Jul 29 2018
Jul 26 2018
Is there a maintenance script to add a bunch of users to a user group? It seems like that could potentially be a feature within this script and might be a more common case.
Jul 23 2018
Another report in the #mediawiki IRC channel just now:
Jul 22 2018
Jul 21 2018
I think the relationship between Wikimedia Foundation Inc. and Go Fish Digital has every appearance of being highly problematic, as I outlined here: https://lists.wikimedia.org/pipermail/wikimedia-l/2018-July/090737.html. And I don't think XML site maps are going to help Wikipedia's search engine optimization. Any discussion of improving Wikipedia's SEO has long been taken as a joke given Wikipedia's existing ridiculously high placement in Google search results. That said...
I'd really be interested to know what's potentially libelous about labeling activity such as this as whitewashing (from https://gofishdigital.com/online-reputation-management/):
Has the account approval queue been re-enabled? From the #wikimedia IRC channel this evening:
Jul 20 2018
This is an old topic. If you search this Phabricator installation for "password length", you'll find a bunch of related commits and tasks. There are also wiki pages such as https://www.mediawiki.org/wiki/Requests_for_comment/Passwords and mailing list posts about this.
Jul 8 2018
Jul 1 2018
Jun 28 2018
Yessir. Thank you for noting the behavior as of 2018-06-27 in this task!
Jun 22 2018
Jun 21 2018
Jun 19 2018
I agree with what Timo wrote in T189763#4055149.
Jun 18 2018
Am I understanding this issue correctly? The current behavior when a new user registers a Wikimedia Phabricator account to file a bug or report some kind of issue is presenting them with this screen?
I tried to create a test account just now and a verified e-mail address is required. Since when?
An issue that impairs the ability of a user to perform basic functions such as reading a task is a high priority to get resolved. Can you explain why you reset the priority here?
Jun 17 2018
@Framawiki notes that the "watchlist_count" table has gone missing at https://en.wikipedia.org/w/index.php?title=User_talk:MZMcBride&oldid=846197628#About_watchlist_table_on_replicas. I can confirm:
Jun 11 2018
Jun 10 2018
Jun 8 2018
May 23 2018
May 12 2018
I changed "reCAPTCHA" to "CAPTCHA" in the task title because we've typically avoided reCAPTCHA specifically, in favor of using our own CAPTCHA on the wikis.
May 11 2018
May 8 2018
May 4 2018
Apr 20 2018
Mar 29 2018
Thank you for the task description expansion!
Mar 28 2018
Since the "Removable" table column is not sortable, perhaps splitting the table into multiple tables would be useful? The current mix of removed, unremovable, and pending removal tables is somewhat confusing to digest.
Mar 21 2018
It's not totally clear to me how this task is distinct from older tasks such as T66475: Make crosswiki bits and pieces truly global (tracking). Is there something new here?
Re-opening this. I'm not sure how much clearer this request could be. It's very explicitly about uninstalling Flow from Commons. That's the title of the task ("Uninstall Flow from Commons") and the task description goes on to further clarify. According to https://commons.wikimedia.org/wiki/Special:Version, Flow is still installed.
Mar 13 2018
Mar 12 2018
Mar 8 2018
@Nemo_bis wrote the wiki report in September 2013: https://github.com/nemobis/gerrit-reports/commit/93858c6c829e17dc030af001f057f04282879685#diff-47f89ceb825fcc72b0b09ddfbf9f99a4.
Mar 7 2018
@Jdforrester-WMF weighed in on Commons in September 2017, apparently:
Mar 5 2018
Mar 3 2018
As far as I know, we have already invested time and energy into creating a proper process to remove Flow from a wiki. We did this with the English Wikipedia (cf. T148611: Plan to disable Flow on Enwiki). From my perspective, adding a configuration variable and additional complexity to the Flow extension and then indefinitely continuing to keep Flow installed on some wikis is a bad approach, both socially and technically. It saddles the wiki with technical debt, with no return on investment, and it creates a higher maintenance burden in order to achieve the same functional result as uninstalling the extension altogether. In the process, rather than respecting the community's wishes, you deliberately subvert them and engender ill will.
Feb 28 2018
Another potential wording: Please choose a password that is more difficult to guess.
Feb 26 2018
Another idea is to use the Linter extension and its framework to add a tracking category to redirect pages that have invalid/broken section anchors. This would require getting the Linter extension to work with a non-Parsoid "external service" and would require solving the challenges @Bawolff mentions about manually added IDs.
Feb 24 2018
What do you think this task is proposing? A whois service operated by Wikimedia Foundation Inc.? Or a Special page in a MediaWiki extension or in MediaWiki core that queries other whois services? Or some combination of the two?
What does further investigation mean in this context? What possible actions can result from this further investigation?
We already have a Special page that exposes a user's IP address information, of course: https://en.wikipedia.org/wiki/Special:Version. It's just not very visible information given the HTML:
Feb 23 2018
This sounds similar to https://www.mediawiki.org/wiki/Extension:Drafts.