Fri, May 10
+1 to @Joe
Mar 13 2019
Six months on, I again request that this be re-triaged. Perhaps some volunteer devs could be steered to consider fixing this?
Jan 25 2019
Dec 23 2018
Experience suggests that stabilizing the @Magnus tools would be a likelier path than getting WMF to allocate feature development resources.
Dec 18 2018
@Aklapper - this is probably a trivial fix. Could you get this a few minutes of attention to be triaged, at least?
Dec 8 2018
Nov 20 2018
(unfortunately, videoconvert does not seem to be tracking issues here on Phabricator...)
(@Tgr - my concern is for end-users not using Pywikibot, but the videoconvert tool. Thanks to @zhuyifei1999 and @Harej I learned that video2commons supports uploads (perhaps it used to not support uploads?), so there is a workaround for end-users for the moment. This, then, becomes a videoconvert tool limitation, rather than a blocker for end-user video uploads for people not familiar with the command line (ffmpeg etc.).)
Hello. I seem to have run up against this problem. This seems like a serious barrier to contributing core content (media files into Commons). Can this receive higher priority, please?
Aug 28 2018
Aug 8 2018
(Also, it's not just on the Visual Editor. It doesn't work with wikitext editing either, on mobile.)
Hello. I request this be re-triaged. It's been 2.5 years. And it breaks more than Wikinews. For example, it makes it impossible for mobile users (remember some people *don't* have a non-mobile device) to request hardware in [[m:Hardware donation program]].
Jun 25 2018
Thanks for the insight on the difference between those two versions. That is indeed usable, for this particular count.
Jun 13 2018
Thank you, @Jdlrobson, for the forthright comments!
Jun 9 2018
Jun 4 2018
Yes. Another example of a query timing out without lots of output is this simple count of scholarly articles (millions)
Jun 2 2018
Hello. This seems to have languished for years; clearly, Wikisource contributors lack the technical know-how to fix this along the lines @Jdlrobson suggested. Or perhaps @Tpt just hasn't noticed this?
May 11 2018
Feb 6 2018
It looks like it has been deployed, but it does not work:
Jan 31 2018
Dec 9 2017
Dec 4 2017
Thanks. It is not a critical issue, and no need to spend any time recovering it. The availability of this data to our community is the important thing. Are we still on track for this to be tackled in Q3?
Nov 7 2017
Nov 6 2017
Oct 2 2017
Thank you, @Milimetric. That would be great.
Sep 29 2017
Sep 27 2017
Thank you for the quick response, @Nuria. It sounds as though there is a worthwhile discussion to be had on whether and how we can achieve the statistics requested in this ticket. Unless I misunderstood what you just said, it sounds as though even in Q3, the geo location would not, in fact, be part of the available data, unless Someone Does Something. So I am asking that Someone Do Something. If you need me to escalate this yet again before Someone can Do Something, please let me know and I shall do so.
Thank you, @Nuria, for the clear update. Do we have a solid solution for the concerns your team has had about leaking a user's country due to insufficient bucketing? I'd like some assurance that come Q3, the feature can finally be implemented, rather than someone discovering then that the privacy concern is still there, and us descending into yet another spiral on that question.
Forgive me if you hear a bitter overtone in the above question, but, really, we've been waiting for this data for over four years now, and it's been more than two years since Legal declared bucketing sufficient, so I am wary of additional delays and am seeking to ensure only unavoidable delays continue to delay us.
Jul 23 2017
Can someone offer a comment on why it was decided to move it from Q4 of last year to Q3 of this year? As a stakeholder, I wish I were included in the conversation that resulted in deprioritizing this.
Jul 18 2017
Is there a planned timeline for the remaining tasks here?
Feb 13 2017
Agree re lowering to High. But it does seem like a bug and not etwiki's using inappropriate magic words.
Feb 12 2017
Thanks, @bd808! That's helpful insight. I guess the Estonian main page needs to be fixed not to use those.
I have changed this to Unbreak Now! -- it's not okay that our readers are getting stale versions of the main page, on any wiki. It should have been handled long ago.
Feb 11 2017
Feb 5 2017
Jan 27 2017
Yes, either would work.
Jan 26 2017
Very happy to do it, but my talk is designed for 2.5 to 3 hours. It covers not just what Wikidata is, but how to contribute, how to embed Wikidata into articles, tools like the Wikidata Game, and how to query Wikidata (including SPARQL examples). As such, it would take more than "lunchtime". I suppose it can be split into two parts and done on consecutive weeks, but in my opinion teaching all of these topics together helps demonstrate the importance of Wikidata and gives a more rounded view.
Jan 10 2017
I believe we discussed this verbally a few months ago, but for the record, let me record answers to Nuria's questions here as well:
Nov 7 2016
@D3r1ck01 - please be more careful in phrasing. At the moment, there is no recognized user group in Cameroon. I understand you are interested in founding one, and that you are in contact with the Affiliation Committee about it; that's great! But until the group is actually recognized by the Wikimedia Foundation, you should not bill yourself as "Wikimedia Community User Group Cameroon", especially in contact with partners.
Oct 19 2016
Pinging @Arrbee once again.
Sep 25 2016
Sep 8 2016
Any news, @Arrbee ?
Aug 30 2016
@ManosHacker - indeed, would it not be enough to clearly say, in the template, something like "If you're not seeing a page you've just saved, CLICK HERE."?
Aug 28 2016
Aug 25 2016
Aug 24 2016
Aug 20 2016
Aug 11 2016
A little more patience, @hindustanilanguage. It's being resolved, but isn't deployed on the wiki just yet.
Aug 10 2016
Per discussion with @Arrbee during WikiConference India, I am recording here that I was told the Russian fallback *will* be removed from Ukrainian wiki projects, per community wishes, and explicitly recognizing that linguistic concerns are not the only factors in such a decision.
Wikimedia-IN-CIS is okay too (though that might confuse people into looking for a major Indian city abbreviated as CIS).
Aug 7 2016
Jul 29 2016
Hello, @Niharika -- I have no experience with other languages and Tesseract. It worked well enough for English, and I made it available as a service at the time in response to an expressed need, but have not looked at it since. I'm not sure anyone has been using it, so I'm not taking the time to look into that 502 just yet.
Jun 21 2016
Jun 11 2016
Thanks for quickly looking into it, @matmarex :)
Jun 10 2016
Jun 6 2016
- "WMF" in that we've just used it for the "ED Search" survey
- the WMF Community Engagement department (multiple teams)
- WMF grantees and community program leaders use it (using WMF-provided licenses) to run surveys in their communities.
Jun 5 2016
Jun 4 2016
May 14 2016
This fails too:
May 12 2016
(I had filed T134926 against the API itself.)
(or indeed, if the API was case insensitive re wiki names.)
@Nemo_bis has identified the bug -- @Esh77 used a PagePile that had the wiki name as 'He' rather than 'he'. That's enough to cause the PageViews API to fail. I actually encountered it myself as I was building my own tool, and quickly added lowercasing of the input, without thinking that might be the reason Magnus's tool was not getting results too.
May 10 2016
Apr 30 2016
It would also be nice to have number of pages automatically populated.
Apr 15 2016
Apr 11 2016
Apr 9 2016
Apr 1 2016
I'm interested in maybe tackling this.
I suggest the answer to both is "yes, and yes". i.e. yes, associate users and (separately) courses with a home wiki, and yes, make it optional.
Mar 26 2016
Yeah, it works after fixing the jwt issue and using a newish nodejs. upgrading from my distro's 0.x to a recentish 4.x from the custom nodejs package archive made the npm install run work.
Mar 11 2016
Fixed the string on Translatewiki.
Caused by inappropriate use of GRAMMAR in the translated message.