One interesting thing that I noticed about the trending edits API is that it was fairly useful in identifying articles that were under attack by vandals or experiencing an edit war. A lot of times a vandal will just sit on an article and keep reverting back to the vandalized version until an admin shows up, which can sometimes take a while. If you tweak the parameters passed to the API, you can almost get it to show nothing but edit wars (high number of edits, low number of editors).
This makes me think that this API is actually useful, it's just targeted to the wrong use case. If we built something similar, but that just looked for high numbers of revert/undos (rather than edits), and combined it with something like Jon Robson's trending edits user script ( https://en.wikipedia.org/wiki/User:Jdlrobson/Gadget-trending-edits.js), we could create a really powerful tool for Wikipedia administrators to identify problems without having to wait for them to be reported at AN/I or AIV.
On Tue, Dec 12, 2017 at 7:25 AM, Corey Floyd cfloyd@wikimedia.org wrote:
Just a reminder that this is happening this Thursday. Please update any tools you have before then. Thanks!
On Fri, Dec 1, 2017 at 3:30 PM Corey Floyd cfloyd@wikimedia.org wrote:
Hi all,
The experimental Trending Service[1] will be sunset on December 14th,
We initially deployed this service to evaluate some real time features in the mobile apps centered on delivering more timely information to users. After some research [2], we found that it did not perform well with users in that use case.
At this point there are no further plans to integrate the service into
our
products and so we are going to sunset the service to reduce the maintenance burden for some of our teams.
We are going to do this more quickly than we would for a full stable production API as the usage of the end point is extremely low and mostly from our own internal projects. If you this adversely affects any of your work or you have any other concerns, please let the myself or the Reading Infrastructure team know.
Thanks to all the teams involved with developing, deploying, researching and maintaining this service.
P.S. This service was based off of prototypes Jon Robson had developed
for
detecting trending articles. He will be continuing his work in this
area. I
encourage you to reach out to him if you were interested in this project.
[1] https://en.wikipedia.org/api/rest_v1/#!/Feed/trendingEdits [2] https://meta.wikimedia.org/wiki/Research:Comparing_most_
read_and_trending_edits_for_Top_Articles_feature
-- Corey Floyd Engineering Manager Readers Wikimedia Foundation cfloyd@wikimedia.org
-- Corey Floyd Engineering Manager Readers Wikimedia Foundation cfloyd@wikimedia.org _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l