On Thu, Jul 9, 2015 at 12:55 AM, Mr. Stradivarius misterst...@gmail.com
wrote:
Also, if anyone is interested, I have compiled a list of scripts on all WMF
wikis
that may need updating.[1] It has 129 pages in at the moment, although some
are
false positives, and some are personal scripts
All this unnecessary changes is just making wikicoders live hard. *sigh*
From: mai...@live.de
To: wikitech-l@lists.wikimedia.org
Date: Wed, 8 Jul 2015 08:17:41 +0200
Subject: Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for
action=query will change at the end of this
On *Wed, Jul 8, 2015 at 6:17 AM, Marco F *
*maic23 at live.de
+1
thanks for putting that list together!
On Wed, Jul 8, 2015 at 11:12 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Wed, Jul 8, 2015 at 11:55 AM, Mr. Stradivarius misterst...@gmail.com
wrote:
I'm sure there are still some out there, but probably not as many as you
think. I
On Wed, Jul 8, 2015 at 11:55 AM, Mr. Stradivarius misterst...@gmail.com
wrote:
I'm sure there are still some out there, but probably not as many as you
think. I know that there aren't any gadgets or user scripts on enwiki or
mediawikiwiki that use the old syntax, because I cleaned them up
Date: Tue, 7 Jul 2015 10:20:33 -0400
From: bjor...@wikimedia.org
On Mon, Jul 6, 2015 at 9:02 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Did the change go live?
Yes!
Did the wikis fall over?
If they did, no one told me about it or complained about it in any of the
Thank you so much for what you've done to help, Mr. Stradivarius :)
On Wed, Jul 8, 2015 at 1:37 PM, Jonathan Morgan jmor...@wikimedia.org
wrote:
+1
thanks for putting that list together!
On Wed, Jul 8, 2015 at 11:12 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org
wrote:
On Wed, Jul 8,
On Tue, Jul 7, 2015 at 4:20 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
Is there a common approach for gadgets to identify themselves to the
API - e.g. setting a custom user-agent?
Clients that cannot set the User-Agent header (such as gadgets and other
scripts running in a
On Mon, Jul 6, 2015 at 9:02 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Did the change go live?
Yes!
Did the wikis fall over?
If they did, no one told me about it or complained about it in any of the
places I looked. Not that I personally looked in extremely many places, but
I'd have
On Wed, Jun 24, 2015 at 2:43 AM, Andre Klapper aklap...@wikimedia.org wrote:
As there are seven days left, does someone have time / capacity to
provide an updated list of bots that likely haven't seen updates yet?
Also, in [1], Sitic came up with a query of de.wp *gadgets* affected:
I run GrantsBot, which is listed here.
I've updated all GrantsBot API requests to use rawcontinue=1. But as I read
through this thread, it's not clear to me that that's the problem. I can't
find a single instance in my code where I'm actually continuing a query.
Does this breaking change only
Jonathan, in theory, if you never use query continuation, you don't need to
do anything with your code - you just need to tell the community that the
bot is ok to use the new continuation system. This way noone will block the
bot just in case. It is much better than to use rawcontinue, because
Thanks Yuri and Brad!
On Mon, Jun 29, 2015 at 11:10 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Mon, Jun 29, 2015 at 1:53 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:
It is much better than to use rawcontinue, because
that flag will keep telling us someone needs the
On Mon, Jun 29, 2015 at 1:53 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:
It is much better than to use rawcontinue, because
that flag will keep telling us someone needs the old system.
I doubt we'll ever get rid of rawcontinue. There's practically no code to
maintain there (it's just a
Hi Brad,
Brad Jorsch (Anomie) schreef op 2-6-2015 om 22:42:
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
On Wed, 2015-06-10 at 15:01 -0400, Brad Jorsch (Anomie) wrote:
Legal recommended we only post the list of bots, not the human
accounts. These are:
AHbot
AsuraBot
[...]
Note this list is still from May 23–29; a bot appearing in this list
may have been updated since then.
As there are
On Fri, Jun 19, 2015 at 5:42 AM, John Mark Vandenberg jay...@gmail.com
wrote:
Why doesnt formatversion=2 assume continue= and utf8= ?
It does assume utf8= (there's an ascii= to request the old mode in
combination with formatversion=2).
It doesn't assume continue= because that belongs to
Before playing around with api serious bugs should be fixed... I see xxXx
unresolved bugs on pahricator. It is frustrating
Date: Thu, 18 Jun 2015 14:56:25 -0700
From: sp...@wikimedia.org
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] API BREAKING CHANGE: Default
On Fri, Jun 19, 2015 at 7:56 AM, S Page sp...@wikimedia.org wrote:
On Thu, Jun 18, 2015 at 9:26 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
I guess it comes down to is this: if we're going to continue supporting
old behavior, they should be accessible via the same old requests. *This
On Thu, Jun 18, 2015 at 12:13 PM, Yuri Astrakhan
yastrak...@wikimedia.org wrote:
On Wed, Jun 17, 2015 at 7:44 PM, John Mark Vandenberg jay...@gmail.com
wrote:
The API currently emits a warning if a query continuation mode isnt
selected.
I guess on July 1 the API could emit an error, and
On Thu, Jun 18, 2015 at 10:37 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
1. Current, change the default approach:
1. All clients start receiving warnings as *extra payload data* (how
does this even work for API's w/o a response payload?)
What module in api.php doesn't
Brad Jorsch (Anomie) wrote:
On Thu, Jun 18, 2015 at 10:37 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
1. Current, change the default approach:
1. All clients start receiving warnings as *extra payload data*
(how does this even work for API's w/o a response payload?)
What
On Thu, Jun 18, 2015 at 11:33 AM, MZMcBride z...@mzmcbride.com wrote:
Brad Jorsch (Anomie) wrote:
On Thu, Jun 18, 2015 at 10:37 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
1. Current, change the default approach:
1. All clients start receiving warnings as *extra payload data*
On Wed, Jun 17, 2015 at 10:13 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:
On Wed, Jun 17, 2015 at 7:44 PM, John Mark Vandenberg jay...@gmail.com
wrote:
The API currently emits a warning if a query continuation mode isnt
selected.
I guess on July 1 the API could emit an error,
I'm reluctant to interject again, but as a client of the API I feel the
need to speak up. Let's work through an example: Clients A, B, C are
using API 1 when the Server adds API 2:
1. Current, change the default approach:
1. All clients start receiving warnings as *extra payload data*
There is no such a thing like properly break. That's like if someone
was happily sad. Come on
On Thu, Jun 18, 2015 at 4:09 PM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Wed, Jun 17, 2015 at 10:13 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:
On Wed, Jun 17, 2015 at 7:44 PM,
I guess it comes down to is this: if we're going to continue supporting old
behavior, they should be accessible via the same old requests. *This
removes the need for existing clients to be updated in the first place*.
If we eventually want to delete the old code keeping the old behavior
separated
On Thu, Jun 18, 2015 at 9:26 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
I guess it comes down to is this: if we're going to continue supporting
old behavior, they should be accessible via the same old requests. *This
removes the need for existing clients to be updated in the first
On Wed, Jun 17, 2015 at 9:15 PM, Marco mai...@live.de wrote:
On Wed, 03 Jun 2015 18:29:08 +0700, John Mark Vandenberg wrote:
On Wed, Jun 3, 2015 at 3:42 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
...
I've compiled a list of bots that have hit the deprecation warning more
than
On Wed, Jun 17, 2015 at 7:44 PM, John Mark Vandenberg jay...@gmail.com
wrote:
The API currently emits a warning if a query continuation mode isnt
selected.
I guess on July 1 the API could emit an error, and not return any query
data.
Then the data isnt going to cause weird behaviour - it
On Wed, 03 Jun 2015 18:29:08 +0700, John Mark Vandenberg wrote:
On Wed, Jun 3, 2015 at 3:42 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
...
I've compiled a list of bots that have hit the deprecation warning more
than 1 times over the course of the week May 23–29. If you are
Il 09/06/2015 11:32, Steinsplitter Wiki ha scritto:
Maybe someone with enough time and knowledge can fork compat and keep it
alive...
Everyone is free to fork it, of course, but in this case it'd only bring
more fragmentation to the ecosystem.
As John said, patches are always welcome.
On Wed, Jun 3, 2015 at 12:43 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Wed, Jun 3, 2015 at 7:29 AM, John Mark Vandenberg jay...@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
Maybe someone with enough time and knowledge can fork compat and keep it
alive...
Date: Tue, 9 Jun 2015 13:03:03 +1000
From: jay...@gmail.com
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for
action=query will change at the end
On Tue, 2015-06-09 at 11:32 +0200, Steinsplitter Wiki wrote:
Maybe someone with enough time and knowledge can fork compat and keep
it alive...
As far as I understand it, there is no need to fork anything (no
disagreement with existing maintainers; no contribution barriers).
Anybody interested
It would be nice if MediaWiki API _AND_ pywikipedia bot do not deprecate
at once.
Now it looks as
API: we are deprecating what we promised to deprecated long ago - ok
pywikipedia compat: did not handle the deprecation of API before, and are
not going to fix copy-pasted in tens of places (not
On Tue, Jun 9, 2015 at 6:04 AM, Ilya Korniyko intra...@gmail.com wrote:
It would be nice if MediaWiki API _AND_ pywikipedia bot do not deprecate
at once.
Now it looks as
API: we are deprecating what we promised to deprecated long ago - ok
pywikipedia compat: did not handle the deprecation
I know about the phab ticket, but I'm glad you referenced it because I
found this:
(Anomie): I think feature flags to *select new behavior* and *a good
deprecation process* will take care of most things that actually need
improvement, to the point where we can do per-module versioning on an ad
On Thu, Jun 4, 2015 at 1:59 PM, Brian Gerstle bgers...@wikimedia.org
wrote:
IOW, why don't we continue w/ this feature flagging approach, which seems
like a decent way to version APIs and prevent breaking backwards
compatibility?
That's basically what this is, except it's named rawcontinue
Just found the deprecation process document
https://www.mediawiki.org/wiki/Requests_for_comment/API_roadmap,
specifically:
1. If not already present, a request parameter will be added to
specifically request the old behavior.
2. The change will be announced:
- A message will
Sorry, guess I'm also calling #1 into question, since the old behavior
should have already been the default or selectable by its own
flag/parameter/URL-path-component/content-type/whatever.
On Thu, Jun 4, 2015 at 2:08 PM, Brian Gerstle bgers...@wikimedia.org
wrote:
Just found the deprecation
On 06/04/2015 09:45 AM, Brian Gerstle wrote:
While it is (a little bit) nicer for new developers, they'll just burned
(along with all the other current API users) when you change the defaults.
What I'm trying to say is, changing the default seems like more work for
more people with very little
-announce
Maybe we should have a reply-to for api-announce mailings that prevent
accidental chatter?
On Thu, Jun 4, 2015 at 12:45 PM, Brian Gerstle bgers...@wikimedia.org
wrote:
On Wed, Jun 3, 2015 at 1:13 PM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Wed, Jun 3, 2015 at 10:04
On Wed, Jun 3, 2015 at 1:13 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Wed, Jun 3, 2015 at 10:04 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
My question is: why does the default behavior need to change? Wouldn't
continuing with the default behavior allow people to
Le 03/06/2015 15:43, MZMcBride a écrit :
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
I haven't followed this discussion, however i am wondering why api is not keep
backward compatible. This will break a lot of stuff and i am wondering why we
need such changes in the app---
Best :-)
Steinsplitter
Date: Tue, 2 Jun 2015 16:42:47 -0400
From: bjor...@wikimedia.org
To:
yes.
Date: Wed, 3 Jun 2015 04:25:10 -0700
From: ab...@wikimedia.org
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for
action=query will change at the end of this month
Steinsplitter, just to be clear, you meant API, not app,
On Wed, Jun 3, 2015 at 3:42 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
...
I've compiled a list of bots that have hit the deprecation warning more
than 1 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
Steinsplitter, just to be clear, you meant API, not app, correct?
On Wed, Jun 3, 2015 at 3:49 AM, Steinsplitter Wiki
steinsplitter-w...@live.com wrote:
I haven't followed this discussion, however i am wondering why api is not
keep backward compatible. This will break a lot of stuff and i am
- mediawiki-api-annnounce
Sorry, didn't mean to CC the api announcement list. Seems like my message
got bounced anyway.
On Wed, Jun 3, 2015 at 10:04 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
First, kudos to the API team for going the extra mile and reaching out to
the community to
First, kudos to the API team for going the extra mile and reaching out to
the community to guide them through this process. This doesn't effect the
apps at the moment, but it's good to know you guys are thinking about
clients and how API changes affect them.
My question is: why does the default
Most operator are volunteers and don't have time to change the code every month
because there is a change in the api. Because of this devs should keep the api
backward-compatible.
Also wondering why wee need this new api. The old one was imho perfectly.
Was the new api coded by WMF or by
Yuri Astrakhan wrote:
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
MZ: I feel that former MediaWiki Web API maintainers should actively pay
attention to which mailing lists they're posting to. ;-) I doubt you
intended to send this message to mediawiki-api-announce.
Mz, I don't think I ever spent much time maintaining it :)) But yes, good
point, reply all is
On Wed, Jun 3, 2015 at 6:49 AM, Steinsplitter Wiki
steinsplitter-w...@live.com wrote:
I haven't followed this discussion, however i am wondering why api is not
keep backward compatible. This will break a lot of stuff and i am wondering
why we need such changes in the [API]
We usually do. In
On Wed, Jun 3, 2015 at 10:04 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
My question is: why does the default behavior need to change? Wouldn't
continuing with the default behavior allow people to continue using the
rawcontinue behavior for as long as we want to support it—without making
On Wed, Jun 3, 2015 at 7:29 AM, John Mark Vandenberg jay...@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
On 6/3/15, Steinsplitter Wiki steinsplitter-w...@live.com wrote:
Most operator are volunteers and don't have time to change the code every
month because there is a change in the api. Because of this devs should keep
the api backward-compatible.
Also wondering why wee need this new api. The old
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
It means all compat bots will break and since pywikibot team won't support
compat and won't change the code to support the new API, We are planning to
deprecate it [1]
So please compat bot operators, do update your codes to core, read [2]
[1]: https://phabricator.wikimedia.org/T99365
[2]:
60 matches
Mail list logo
