Unfortunately the api will be changed and will be no longer backward compatible. Please fix your bots.
> Date: Tue, 2 Jun 2015 16:42:47 -0400
> From: bjorsch(a)wikimedia.org
> To: wikitech-l(a)lists.wikimedia.org; mediawiki-api-announce(a)lists.wikimedia.org
> Subject: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
> As has been announced several times (most recently at
> the default continuation mode for action=query requests to api.php will be
> changing to be easier for new coders to use correctly.
> *The date is now set:* we intend to merge the change to ride the deployment
> train at the end of June. That should be 1.26wmf12, to be deployed to test
> wikis on June 30, non-Wikipedias on July 1, and Wikipedias on July 2.
> If your bot or script is receiving the warning about this upcoming change
> (as seen here
> <https://www.mediawiki.org/w/api.php?action=query&list=allpages>, for
> example), it's time to fix your code!
> - The simple solution is to simply include the "rawcontinue" parameter
> with your request to continue receiving the raw continuation data (
> No other code changes should be necessary.
> - Or you could update your code to use the simplified continuation
> documented at https://www.mediawiki.org/wiki/API:Query#Continuing_queries
> which is much easier for clients to implement correctly.
> Either of the above solutions may be tested immediately, you'll know it
> works because you stop seeing the warning.
> I've compiled a list of bots that have hit the deprecation warning more
> than 10000 times over the course of the week May 23–29. If you are
> responsible for any of these bots, please fix them. If you know who is,
> please make sure they've seen this notification. Thanks.
> Brad Jorsch (Anomie)
> Software Engineer
> Wikimedia Foundation
> Wikitech-l mailing list
In reading the recent
summary I think that some of the principles apply to Commons as well,
tohugh of course we're talking of very different beasts.
* "Data should be enriched where possible (e.g. through multilinguality
or vocabularies)" is something we do better than most, even though
further integration with the Translate extension is needed;
* "using a preview portal as a means of data validation" is basically
covered by the CommonsMetadata tracking categories, also visible on
preview (though I don't know about GWT);
* "A thumbnail should be made available for all digital cultural
heritage objects" is easier for us but still a strength we tend to overlook.