Dear friends,
We have been working for some months in a wikidata project, and we have found an issue with edition performance, I began to work with wikidata java api, and when I tried to increase the edition speed the java system held editions, and inserted delays, which reduced edition output as well.
I chose the option to edit with pywikibot, but my experience was that this reduced more the edition.
At the end we use the procedure indicated here:
https://www.mediawiki.org/wiki/API:Edit#Example
With multithreading, and we reach a maximum of 10,6 edition per second.
my questions is if there is some experience when has been possible to have a higher speed?.
Currently we need to write 1.500.000 items, and we would require 5 working days for such a task.
Best regards
Luis Ramos
Senior Java Developer
(Semantic Web Developer)
PST.AG
Jena, Germany.
Hello,
in 2016 I wrote a small Android app, that is making use of the Wikipedia ActionApi to search for articles at the current location of a user.
Due to legal considerations I am currently trying to take down the app.
It’s not available any more in the Google PlayStore, but there are still installations out there.
That’s why I want to make these installations unusable by deactivating all backend services, that the app is using.
Unfortunately the app is (partially) directly communicating with wikipedia servers and not via a proxy under my control.
The app sends a special User-Agent HTTP header with every request to identify itself:
tagorama/v1.0.0.283-release (http://tagorama.rocks/ <http://tagorama.rocks/>; info(a)tagorama.rocks <mailto:info@tagorama.rocks>)
Is there any way for you to block requests from this app?
Who would I contact?
Thanks for your help,
Frank Wunderlich
לא יודע
חסום לי
בתאריך יום א׳, 29 בדצמ׳ 2019 ב-14:01 מאת <
mediawiki-api-request@lists.wikimedia.org>:
> Send Mediawiki-api mailing list submissions to
> mediawiki-api(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-api
> or, via email, send a message with subject or body 'help' to
> mediawiki-api-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> mediawiki-api-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mediawiki-api digest..."
>
>
> Today's Topics:
>
> 1. API search issue (Alessandro Vallin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 29 Dec 2019 11:42:50 +0100
> From: Alessandro Vallin <alessandro.vallin(a)gmail.com>
> To: mediawiki-api(a)lists.wikimedia.org
> Subject: [Mediawiki-api] API search issue
> Message-ID:
> <CAO6zDE6nJkUJShL1S=
> M8Jg2qT-KZUjK3uQ3pVt-5Z-YFVatxxw(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Good morning
>
> I am using the following API search, which used to return title, content
> and link of a Wikipedia entry:
>
>
> https://it.wikipedia.org/w/api.php?action=opensearch&search=alessandro%20le…
>
> Just recently I noticed that it is always returning an empty content part
> ([""]):
>
> ["alessandro leogrande",["Alessandro Leogrande"],[""],["
> https://it.wikipedia.org/wiki/Alessandro_Leogrande"]]
>
> Can you please give me any insight?
> Thanks,
> Alessandro
>
Hi all,
action=helppanelquestionposter is an API meant for internal use by the
GrowthExperiments extension's web UI, but it has not been formally marked
as internal, so I'm announcing the recent changes [1] to it just in case:
- the 'email' and 'resendconfirmation' parameters have been removed;
- the 'email' response field has been removed;
- the API is now marked as internal.
The functionality provided by the API is not really useful outside of the
web-based workflow it supports, and can be approximated with other, public
APIs, so this is not expected to cause problems to any clients.
[1]
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GrowthExperiments/+/5…
_______________________________________________
Mediawiki-api-announce mailing list
Mediawiki-api-announce(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce
The format of block expiry timestamps returned from list=users and
list=allusers has long been inconsistent. It was being returned in an
internal format (e.g. "20190918201053"), rather than the ISO 8601 format
used by the rest of the API (e.g. "2019-09-18T20:10:53Z").
The 'blockexpiry' property from these two modules will be changing to the
standard ISO 8601 format with 1.34.0-wmf.24. See
https://www.mediawiki.org/wiki/MediaWiki_1.34/Roadmap for a schedule of
deployment to Wikimedia wikis.
This change also brings the block information returned by list=users and
list=allusers fully in line with that already used for meta=userinfo and
'blocked' errors from various actions.
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
_______________________________________________
Mediawiki-api-announce mailing list
Mediawiki-api-announce(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce
When saving an edit is prevented by the AbuseFilter or SpamBlacklist
extensions, the error is currently reported as a successful API response
with a 'failure' code in the body.[1][2]
In the future, these will be reported as standard API errors.[3][4]
This change should be deployed to Wikimedia wikis with 1.34.0-wmf.23. See
https://www.mediawiki.org/wiki/MediaWiki_1.34/Roadmap for a schedule.
Clients that do not need to specially handle failures due to AbuseFilter or
SpamBlacklist will likely need no changes, as they probably already include
code to generically handle API error responses.
Clients that do handle AbuseFilter or SpamBlacklist failures specially will
need to be updated to check for error codes 'abusefilter-warning',
'abusefilter-disallowed', and/or 'spamblacklist' and handle them as they do
the current AbuseFilter and SpamBlacklist failures, if they want to
preserve their current special handling.
Note that edit failures due to CAPTCHAs from ConfirmEdit are not being
changed at this time. They will continue to be reported as before.[5]
[1]: AbuseFilter: https://phabricator.wikimedia.org/P8988
[2]: SpamBlacklist: https://phabricator.wikimedia.org/P8990
[3]: AbuseFilter: https://phabricator.wikimedia.org/P8989
[4]: SpamBlacklist: https://phabricator.wikimedia.org/P8991
[5]: ConfirmEdit: https://phabricator.wikimedia.org/P9076
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
_______________________________________________
Mediawiki-api-announce mailing list
Mediawiki-api-announce(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce