Mediawiki-api-announce

mediawiki-api-announce@lists.wikimedia.org

143 discussions

BREAKING CHANGE: Removal for wddx and dump output formats (and reminder of future removal of yaml, txt, and dbg formats)
by Brad Jorsch (Anomie) 01 Jul '15

01 Jul '15

Per the RfC a while back,[1] we've now removed the wddx and dump output formats from the API. This is expected to be a very low-impact change, as logs don't show anyone actually using these anymore. This change should be deployed to WMF wikis with 1.26wmf13, see https://www.mediawiki.org/wiki/MediaWiki_1.26/Roadmap for the schedule. Note that the yaml, txt, and dbg output formats are scheduled for removal in November 2015. Users using yaml should be able to easily change to json as it's entirely identical. [1]: https://www.mediawiki.org/wiki/Requests_for_comment/Ditch_crappy_API_formats -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

Deprecation of generatexml parameter to action=parse, prop=revisions, and prop=deletedrevisions
by Brad Jorsch (Anomie) 01 Jul '15

01 Jul '15

With the merge of Gerrit change 216048,[1] the 'generatexml' parameter to action=parse, action=query&prop=revisions, and action=query&prop=deletedrevisions is deprecated in favor of a new 'parsetree' prop. This should be deployed to WMF wikis with 1.26wmf13, see https://www.mediawiki.org/wiki/MediaWiki_1.26/Roadmap for the schedule. [1]: https://gerrit.wikimedia.org/r/#/c/216048/ -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

Changes to meta=siteinfo with formatversion=2
by Brad Jorsch (Anomie) 23 Jun '15

23 Jun '15

Note that formatversion=2 is still considered slightly experimental, in that backwards-incompatible changes like this can still happen. If you see any other changes like this that should be made, please report them! Starting in 1.26wmf11, the following changes will be made in the output from meta=siteinfo when formatversion=2 is in use: - Output from siprop=namespaces will be an array, rather than an object indexed by namespace number. See T102645.[1] - The 'add', 'remove', 'add-self', and 'remove-self' subarrays in siprop=usergroups will always be arrays, never objects with numeric keys. - The (sub)arrays in the output from siprops restrictions, extensiontags, functionhooks, variables, protocols, and showhooks are now guaranteed to be arrays. Getting objects with numeric keys from these seems to have been unlikely or impossible anyway, but now it's guaranteed. [1]: https://phabricator.wikimedia.org/T102645 -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

2 2

The move of all Wikimedia sites to HTTPS affects the API
by Brad Jorsch (Anomie) 13 Jun '15

13 Jun '15

See the announcement at https://lists.wikimedia.org/pipermail/wikimedia-l/2015-June/078214.html For the avoidance of confusion: Yes, the move to HTTPS will affect API requests as well. Your HTTP library should be handling HTTPS for you transparently, but if for some reason it doesn't you may have to update your client. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

New warning if action=parse is used with prop=modules and not jsconfigvars/encodedjsconfigvars
by Brad Jorsch (Anomie) 05 Jun '15

05 Jun '15

If anyone is using action=parse with prop=modules and not including either jsconfigvars or encodedjsconfigvars in the prop parameter, you will start receiving a warning suggesting you do so. Also, action=expandtemplates will now have prop=modules, jsconfigvars, and encodedjsconfigvars available. This change should be deployed to WMF wikis with 1.26wmf9, see https://www.mediawiki.org/wiki/MediaWiki_1.26/Roadmap for the schedule. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

Re: [Mediawiki-api-announce] [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Brad Jorsch (Anomie) 03 Jun '15

03 Jun '15

On Wed, Jun 3, 2015 at 7:29 AM, John Mark Vandenberg <jayvdb(a)gmail.com> wrote: > If possible, could you compile a list of bots affected at a lower > threshold - maybe 1,000. That will give us a better idea of the scale > of bots operators that will be affected when this lands - currently in > one months time. > I already have the list of *accounts* affected: there are 510 with between 1000 and 10000 hits. Of those, 454 do not contain "bot" (case insensitively), so they might be human users with user scripts, or AWB if that's not fixed (someone please check!), or the like. For comparison, in the over-10000 group there were 30 such that I filtered out. I'll want to check with Legal to make sure the additional release of account names is still compliant with the privacy policy (I'm almost but not entirely sure it would be ok). > Will the deploy date be moved back if the impact doesnt diminish by > bots being fixed? > That's not impossible, but I wouldn't count on it. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

Re: [Mediawiki-api-announce] [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Yuri Astrakhan 03 Jun '15

03 Jun '15

I feel that bot operators should actively pay attention to the technical aspects of the community and the mailing lists. So, the bot operator who never updates their software, doesn't pay attention to the announcements, and ignores api warnings should be blocked after the deadline. Bot operators do not operate in a vacuum, and should never run bots just for the sake of running them. Community should always be able to find and communicate with the bot operators. Obviously we should not make sudden changes (except in the security/breaking matters), and try to make the process as easy as possible. The rawcontinue param is exactly that, simply adding it will keep the logic as before. Lastly, I again would like to promote the idea discussed at the hackathon -- a client side minimalistic library that bigger frameworks like pywikibot rely on, and that is designed in part by the core developers. See the proposal at https://www.mediawiki.org/wiki/Requests_for_comment/Minimalistic_MW_API_Cli… On Jun 3, 2015 2:29 PM, "John Mark Vandenberg" <jayvdb(a)gmail.com> wrote: > On Wed, Jun 3, 2015 at 3:42 AM, Brad Jorsch (Anomie) > <bjorsch(a)wikimedia.org> wrote: > > ... > > 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. > > Thank you Brad for doing impact analysis and providing a list of the > 71 bots with more than 10,000 problems per week. We can try to solve > those by working with the bot operators. > > If possible, could you compile a list of bots affected at a lower > threshold - maybe 1,000. That will give us a better idea of the scale > of bots operators that will be affected when this lands - currently in > one months time. > > Will the deploy date be moved back if the impact doesnt diminish by > bots being fixed? > > -- > John Vandenberg > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Brad Jorsch (Anomie) 03 Jun '15

03 Jun '15

As has been announced several times (most recently at https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081559.html), 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 ( example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1>). 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 (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue=>), 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. AAlertBot AboHeidiBot AbshirBot Acebot Ameenbot ArnauBot Beau.bot Begemot-Bot BeneBot* BeriBot BOT-Superzerocool CalakBot CamelBot CandalBot CategorizationBot CatWatchBot ClueBot_III ClueBot_NG CobainBot CorenSearchBot Cyberbot_I Cyberbot_II DanmicholoBot DeltaQuadBot Dexbot Dibot EdinBot ElphiBot ErfgoedBot Faebot Fatemibot FawikiPatroller HAL HasteurBot HerculeBot Hexabot HRoestBot IluvatarBot Invadibot Irclogbot Irfan-bot Jimmy-abot JYBot Krdbot Legobot Lowercase_sigmabot_III MahdiBot MalarzBOT MastiBot Merge_bot NaggoBot NasirkhanBot NirvanaBot Obaid-bot PatruBOT PBot Phe-bot Rezabot RMCD_bot Shuaib-bot SineBot SteinsplitterBot SvickBOT TaxonBot Theo's_Little_Bot W2Bot WLE-SpainBot Xqbot YaCBot ZedlikBot ZkBot -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

Breaking changes in action=import
by Brad Jorsch (Anomie) 18 May '15

18 May '15

Since last month,[1] action=import would ignore the rootpage parameter when the namespace parameter was specified, due to underlying changes in MediaWiki to make Special:Import clearer. Starting with 1.26wmf7,[2][3] it will instead give an error if both parameters are specified to avoid incorrect importing by code expecting the old behavior. [1]: https://gerrit.wikimedia.org/r/#/c/179116/ [2]: https://gerrit.wikimedia.org/r/#/c/210945/ [3]: See https://www.mediawiki.org/wiki/MediaWiki_1.26/Roadmap for the deployment schedule. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

API result formatting changes for JSON (formatversion=2)
by Brad Jorsch (Anomie) 01 May '15

01 May '15

After a lot of work, we're ready to provide a more sensible data layout for format=json results (and also format=php). You can enable this in your requests by adding "&formatversion=2", but do note that the output formatting isn't entirely stable yet and might change without warning. Without specifying formatversion=2, things should be backwards-compatible. But there are some caveats: - Modules that were previously outputting raw booleans in JSON may now have those properties being output using the standard convention: empty-string for true and absent for false. Instances of this should be reported in Phabricator <https://phabricator.wikimedia.org/> to be fixed, please tag with #MediaWiki-API <https://phabricator.wikimedia.org/project/profile/200/> and the tag for the relevant extension. - format=xml will now reversibly mangle tag and attribute names that are not valid XML, instead of just outputting invalid XML. - Previously-announced breaking changes to log entry parameter formatting, that are not actually part of this general result formatting change but were made at about the same time. With formatversion=2, we can make some useful changes: - Return booleans as boolean true instead of empty-string. Where appropriate,[1] return boolean false instead of omitting the property. - Return empty objects in JSON as {}, rather than []. - Have action=query's "pages" be an array, instead of an object with page ids as keys that can be difficult to iterate. - Provide useful property names instead of '*'. - Eliminate useless indirection, e.g. {"text":"..."} instead of {"text":{"*":"..."}} and {"key1":"value1","key2":"value2"} instead of [{"name":"key1","*":"value1"},{"name":"key2","*":"value2"}]. If you see missed opportunities to make the above changes in existing formatversion=2 output, or if there are other changes that would make API output easier to use in JSON, please let me know! Phabricator <https://phabricator.wikimedia.org/> would be ideal (tag with #MediaWiki-API <https://phabricator.wikimedia.org/project/profile/200/>, and the appropriate extension's tag if applicable), or reply on the mediawiki-api mailing list <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api>. Thanks. [1]: Where the property is usually false, it's sometimes just bloat to include it. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Mediawiki-api-announce