Yes, but as far as I understand, this API can not provide recent revisions information in real time. :(
So it is not directly usable for the wpcvn rc patrol tool as it continuously requires recent edits data.
It looks like they've published the code though. I'll try to find some tome and integrate their ratings into the wpcvn.
Their approach of fine-grained text origins sounds pretty solid. And their algorithm also had performed better than mine in the PAN 10 competition.
By the way, if anybody from the Wikitrust team is present here - congrats! And I've just skimmed over your paper - excellent work.
-- Cheers, Dmitry
Hi Dimitry:
Dmitry Chichkov schrieb:
> Some time ago as a Python/Django/JQuery/pywikipedia exercise I've hackedPerhaps have a look at the WikiTrust API: <http://www.wikitrust.net/vandalism-api>
> a web based recent changes patrol tool. An alpha version can be seen at
> the: http://www.wpcvn.com
>
> It includes a few interesting features that may be useful to the
> community (& researchers designing similar tools):
> 1. tool uses editors ratings, primarily based on user counters (includes
> reverted revisions counters) calculated using the wiki dump;
I'm currently prototyping an XMPP based RC feed, which has much more detailed
> WPCVN aggregates recent changes IRC feed, IRC feed from the
> MiszaBot and WPCVN user actions.
info, and is more reliable, than the IRC feed:
<http://meta.wikimedia.org/wiki/Recentchanges_via_XMPP#Prototype>
No *this* definitly sounds like WikiTrust, though I'm not sure if they expose
> It also uses pre-calculated Wikipedia
> users "karma" (based on the recent en-wiki dump analysis) to separate
> edits made by users with clearly good or bad reputation.
this info via the API.
-- daniel
_______________________________________________
Wiki-research-l mailing list
Wiki-research-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wiki-research-l