It's an incredibly useful tool for people outside of our existing community — who use Wikipedia to determine what's resonating worldwide. I've tweeted about it several times and it always gets pickup from journalists:
https://twitter.com/mkramer/status/940676642636206091 Happy to put you in touch if you ever want to do user research interviews. On Tue, Dec 12, 2017 at 3:12 PM, Jon Robson <[email protected]> wrote: > (Volunteer hat on) > > I'm a little sad we didn't find a place for this in the Wikipedia apps or > web products, but I plan to maintain a labs instance going forward: > https://wikipedia-trending.wmflabs.org/ > And a web presentation with a push notification feature (which notified be > this morning of the death of Ed Lee > <https://trending.wmflabs.org/en.wikipedia/Ed%20Lee%20(politician)>): > https://trending.wmflabs.org/ > > This is a little inferior to the production version as it is unable to use > production kafka and if it has any outages it will lose data. > > I'm hoping to get this onto IFTTT <https://ifttt.com/wikipedia> with help > from Stephen Laporte in my volunteer time, as I think this feature is a > pretty powerful one which has failed to find its use case in the wiki > world. As Kaldari points out it's incredibly good at detecting edit wars > and I personally have learned a lot about what our editors see as important > and notable in the world (our editors really seem to like wrestling). I > think there are ample and exciting things people could build on top of this > api. > > The gadget script is crude (as there is no way to install a service worker > via a user script) but will continue to work if you want to try it (but > Firefox only) - I just updated it to use the new endpoint. > > I will continue to explore trending's place in the Wikimedia universe :) > > > On Tue, 12 Dec 2017 at 10:43 Ryan Kaldari <[email protected]> wrote: > > > 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 <[email protected]> > 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 <[email protected]> > wrote: > > > > > > > Hi all, > > > > > > > > The experimental Trending Service[1] will be sunset on December 14th, > > > 2017. > > > > > > > > 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 > > > > [email protected] > > > > > > > -- > > > Corey Floyd > > > Engineering Manager > > > Readers > > > Wikimedia Foundation > > > [email protected] > > > _______________________________________________ > > > Wikitech-l mailing list > > > [email protected] > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > > > _______________________________________________ > > Wikitech-l mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Melody Kramer <https://www.mediawiki.org/wiki/User:MKramer_(WMF)> Senior Audience Development Manager Read a random featured article from Wikipedia! <https://en.wikipedia.org/wiki/Special:RandomInCategory/Featured_articles> [email protected] _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
