Hi, in the new rewrite branch, what is the best way to do this?
* Get all links from a set of pages. If some pages are redirects - get
their targets. Only the link ns+titles are needed, no need to check
existence/pageid/etc. All this is one API call:
* Get all links and categories from the result of a generator or a list of
titles (from a file). Similar to the above, except for optional generator
and there is no redirect param. Once a bad page is found, I will load its
content and fix it. The links and categories names are needed only as text
P.S. I have started
http://www.mediawiki.org/wiki/Manual:Pywikipediabot/Recipes that should
list all encountered bot scenarios and how various versions of pywiki
should be used to solve it. Please help by adding your bot's core workflow
to that list, and core developers could either suggest better code or alter
pywiki framework to better handle such cases.
I want to use the api entry point for a windows 8 rt app I am developing. The application is not a bot, as the requests originate from the users of the app. The also do not originate from a browser, but rather in c# code on the device. The guidelines for api usage indicate that I should send a User Agent, but I’m not sure what I should send in this case. If I have many users of my app, then it may look like I am abusing the api. But it’s the users of my app that are initiating the requests, not a bot.
So what should I use as the User Agent in this case? I could use the action=raw parameter of the normal url, but I would prefer using the api as it has more options.
Sent from Windows Mail
A few weeks ago, a few Wikia and Wikimedia people started talking about
rewriting MediaWiki's web API for greater flexibility, usability, and
standardization. Notes from that meeting:
Federico Lucignano is one of the main developers on this effort. He
will be doing API stuff for Wikia for the next 5 months. Wikia wants to
attract motivated app developers and companies using Wikia's products to
use the API. They also want to make the APIs more standards-compliant
(a RESTful interface, using HTTP verbs), but that's a high-level goal.
Mobile-related work is first, driving the direction of some of
Federico's work, but this redesign would improve the whole platform,
including the enterprise.
Wikimedia and Wikia want to work together on this. Wikimedia Foundation
also wants to avoid boxing ourselves into special-purpose, specific
apps. Right now we're in the very early stages and I believe Wikia's
going to put out an RFC -- the initial research we discussed during the
kickoff meeting is starting this week.
Some people have also begun talking about this issue on the bug " Make
MediaWiki more RESTful":
https://bugzilla.wikimedia.org/show_bug.cgi?id=41837 in case you want to
check that out.
Engineering Community Manager