We've decided to use the API where possible, so time we start using a framework instead of cURL. We'll also want to change all of our current API logic to use the framework.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T116957 Plagiarism detection tools for text (tracking) | |||
Resolved | • TBolliger | T120435 Improve the plagiarism detection bot | |||
Resolved | • TBolliger | T131583 Epic: Make a tool labs interface for Plagiabot aka Eranbot | |||
Resolved | MusikAnimal | T134289 Filter out pages that have been deleted from CopyPatrol interface | |||
Duplicate | None | T138984 "No editor found" lasts for hours | |||
Resolved | MusikAnimal | T139082 Add API framework to CopyPatrol |
Event Timeline
Pull request at https://github.com/Niharika29/PlagiabotWeb/pull/16/files and currently running on http://tools.wmflabs.org/plagiabot (no visible changes)
Using the API over the labs database to get the edit counts is about 500ms slower it looks like, but it will ensure we always have production data. I'm proposing we go with this API solution until we are reassured the replication lag issue has been resolved. I have a few ideas to make it go even faster that I will explore at a later time.
Either way by introducing an API framework to CopyPatrol we will be able to fulfill T138058, T135301 and I hope to also (on my free time) add a revision delete button for admins, since we procedurally do this on enwiki.
Awaiting minor changes to getRevisionDetails() per discussion at https://github.com/Niharika29/PlagiabotWeb/pull/16/files.
I logged in to Plagiabot instance and git log (on master) didn't show the API commit. The latest commit was:
commit c411bd74baefc51c9a65b46aaa258590c8c92178 Author: MusikAnimal <ziemba0123@gmail.com> Date: Tue Jul 5 10:49:42 2016 -0400 Fix wrapping of text in compare pane
So I went ahead and did a git pull (to test the API changes along with mine for letting users not undo others' reviews). And now https://tools.wmflabs.org/plagiabot seems broken. :(
Sorry, wasn't removing nulls from the list of username given to the API. I've fixed and deployed this.