wikipedia_abuse_checker VS plotly-resampler

The code for the project is available at https://github.com/shijithpk/wikipedia_abuse_checker.

Hi, my name is Shijith, and I'm a freelance data journalist from India (Worked previously at Hindustan Times and IndiaSpend).

Just posting a data story I did recently about wikipedia abuse in India. Such abuse is an old problem, but it's getting more media attention with users distorting facts on pages about the Delhi riots or farmer protests. Sometimes users engage in straight out vandalism where they delete whole sections from a page.

I tried to determine which wikipedia pages faced the most abuse this year, and also introduce a twitter account that allows people to track wikipedia abuse weekly.

This is the twitter account for tracking wikipedia abuse every week: http://twitter.com/abuse_checker

And here's the python code I used for the project: https://github.com/shijithpk/wikipedia_abuse_checker

(Am in the process of re-working the code. Right now it's querying the wikipedia API every week for edit histories of over 150k articles, and the whole run is taking 2 days now. Discovered an API endpoint for recent changes that should make things more efficient.)

Have any questions or feedback, do let me know below!

We plan to integrate this in our (already quite scalable) time series visualization library https://github.com/predict-idlab/plotly-resampler - should further increase the scalability by a factor 10 :)