Page MenuHomePhabricator

Map current use of Wikimedia web APIs
Open, LowPublic

Description

  • List of known users of Wikimedia web APIs specifying main uses.
  • Metrics of quantitative use of these APIs

There are two ways to discover this

  • WMF staff and community update page(s) about users of the API based on what they know, e.g. "I met with LoveMyMusic and they show artist details" or "Here's a screenshot of Wikipedia lookup on Kindle"
  • we analyze the user agents and possibly hosts from the improved action API logs and other API logs

Note (also on the public page) there are also people building services from Wikipedia dumps, the RecentChanges stream, and (possibly?) the Wikimedia update feed services. They are not clients of our web APIs.

Issue how much of this is private, on an office.wikimedia.org page rather than a public page [[ API:Clients of Wikimedia APIs]]? It seems mentioning use of Wikimedia by a public service or app is uncontroversial, but if a client uses Wikimedia APIs for a private internal use, is it OK to list it? And should the quantitative metrics be public?

See also:

Related Objects

StatusAssignedTask
OpenNone
OpenNone
ResolvedTgr
OpenTgr
ResolvedArielGlenn
Resolvedbd808
ResolvedNone
ResolvedDzahn
Resolvedbd808
ResolvedJoe
ResolvedJoe
ResolvedJoe
ResolvedJAllemandou
ResolvedOttomata
Resolvedbd808
Resolvedbd808
OpenNone
OpenNone
Resolvedbd808
StalledEvanProdromou
OpenNone

Event Timeline

Spage raised the priority of this task from to Normal.
Spage updated the task description. (Show Details)
Spage added a project: Developer-Advocacy.
Spage added a subscriber: Qgil.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 28 2015, 8:06 PM
Elitre added a subscriber: Elitre.Sep 29 2015, 4:54 PM
Qgil updated the task description. (Show Details)
Qgil set Security to None.
Qgil added a comment.Oct 13 2015, 10:26 PM

Someone mentioned http://histography.io/, and I wonder where could we store these URLs of interesting projects allegedly using our Web APIs.

When the privacy thing is sorted out, and if there's no better way to do this, maybe we could ask the community to add tools they know/use/authored to that page (putting such a request on wikitech-l and Tech News for example)?

Spage raised the priority of this task from Normal to High.Nov 3 2015, 7:33 PM
Qgil removed Spage as the assignee of this task.Jan 12 2016, 7:21 AM
Qgil lowered the priority of this task from High to Low.
Qgil added a subscriber: Spage.
Qgil added a subscriber: SVentura.
Qgil added a comment.Jan 12 2016, 3:40 PM

This task was one of the T109829: Developer Relations quarterly goals for October-December 2015. The success criteria was

List of known users of Wikimedia web APIs specifying main uses. Metrics of quantitative use of these APIs

Due to personal problems, S Page could not work on this goal and we didn't have any substitute for him.

@SVentura, does your team have a list of known users of Wikimedia web APIs specifying main uses? You have been working on a survey and more, so hopefully you have an initial list to work with. (I understand that a different question is whether we can publish this information). Our quarterly review is next week, and any information you can provide will be useful.

About quantitative metrics, as far as I'm aware this is still blocked by T102079: Metrics about the use of the Wikimedia web APIs and out of the control / skill of the Developer-Advocacy team.

@SVentura: Could you answer the last comment, please?

@Qgil, @Aklapper, Sorry guys, just seeing these.

Yes, we ran a small survey (160 respondents) which gave us limited insight on our current API users - big a small. This is of course a fraction of total 450 million API requests we get a day but it's a start. Here's the live form of the survey FYI https://docs.google.com/a/wikimedia.org/forms/d/1yUrHzyLABN419RCDbzepjoRWCbaWYV4wbtbKPa95C4o/viewform

I am not sharing the actual raw responses here because of existing personal contact information in the forms, we are finalizing a report which I'll share with the product teams. The findings are not actionable because of the small sample size, but the survey confirmed that there is a wealth of information we can get from speaking with our users that will help inform our organization strategy.

I added this task to Reading-Admin with the hope that someone there can file it under the appropriate project. Currently this task is only under Developer-Advocacy team radar, even if the question seems to be still relevant.

dr0ptp4kt moved this task from Backlog to Tracking on the Reading-Admin board.Jul 20 2017, 9:45 PM