Mediawiki-api-announce June 2015

mediawiki-api-announce@lists.wikimedia.org

3 participants
7 discussions

Deprecation of list=allusers 'recenteditcount' result property
by Brad Jorsch (Anomie) 16 Apr '19

16 Apr '19

When list=allusers is used with auactiveusers, a property 'recenteditcount' is returned in the result. In bug 67301[1] it was pointed out that this property is including various other logged actions, and so should really be named something like "recentactions". Gerrit change 130093,[2] merged today, adds the "recentactions" result property. "recenteditcount" is also returned for backwards compatability, but will be removed at some point during the MediaWiki 1.25 development cycle. Any clients using this property should be updated to use the new property name. The new property will be available on WMF wikis with 1.24wmf12, see https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap for the schedule. [1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=67301 [2]: https://gerrit.wikimedia.org/r/#/c/130093/ -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

1 1

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) 12 Jun '15

12 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) 02 Jun '15

02 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Mediawiki-api-announce June 2015