(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
FWIW, I did the research comparing Trending edits to top pageviews, and I
*also* think Trending edits is a promising tool and am glad to hear that it
going forward in some fashion even if it's being pulled from production
(for now?). I hope we can continue to develop the model, and I'm confident
Admin assistance is definitely an interesting use case… there is also the
possibility of including incorporating ORES scores to see what changes are
actually good or not.
Since the API is primarily based off of edits, it isn’t too surprising that
a contributor / admin use case may be a better fit
On Tue, Dec 12, 2017 at 12:12 PM, Jon Robson wrote:
> 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.
>
Hopefully that gets fixed soon, Cloud VPS / Toolforge is the foundation for
out
> 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.
EventStreams isn’t as good as using Kafka, but an outage shouldn’t be a
reason to lose data. Store the Last-Event-ID
Since there is some confusion on the thread, I would like to clarify that I
am using EventStreams in the labs version. There is no way too use Kafka
outside production and no way to replay historical events (which was what
made this so much better in production).
(code for this is mostly in
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
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
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best
Hi Gilles,
Thank you for the very interesting read and generally for a job well
done, as most of the users will never know that critical part of the
infrastructure changed. :)
Where can we find more information about the thumb caching policy
change that you mention in one of the posts?
Also,
I wrote a blog series that just got picked up on the main Wikimedia blog
about my work migrating Wikimedia wikis to Thumbor for media thumbnailing:
Part 1: https://blog.wikimedia.org/2017/12/09/thumbor-journey-rationale/
Part 2: https://blog.wikimedia.org/2017/12/09/thumbor-journey-
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 wrote:
> Hi all,
>
> The experimental Trending Service[1] will be sunset on December 14th, 2017.
>
> We initially
12 matches
Mail list logo