User talk:Evad37/EditWarChecker.js

I love it!

I love it, thank you so much! Testing now! --Signimu (talk) 02:39, 30 October 2019 (UTC)

Tested! I found only a few cases of "light/green" edit warring today, but so far the gadget seems to behave very well with no error (except once it said it failed loading on the frontpage on my smartphone, but I tested again now and it works fine, so I guess it was just a mishap of my mobile Firefox browser ). May I suggest one thing? Would it be possible to add a customizable parameter to set the time window, let's say up to 72h max? If of course that wouldn't make the gadget too resources hungry. I think this could be useful eg for admins to check on a longer timeframe Thanks again, that's awesome!!! --Signimu (talk) 11:44, 30 October 2019 (UTC)

 Done [1] - Evad37 [talk] 00:09, 31 October 2019 (UTC)

Also if you are open to contributions to the doc, I can suggest a few use cases and explain some of the code, like how it approximates the edit warring count (I have read the sourcecode, it's even better than what I suggested ) --Signimu (talk) 11:51, 30 October 2019 (UTC)

Sure thing, go ahead - Evad37 [talk] 00:09, 31 October 2019 (UTC)

Awesome! Thanks for the update I'll give the doc a try! --Signimu (talk) 03:15, 31 October 2019 (UTC)

• Hey, Evad37! I like this tool a lot. I was wondering if it could put something on my watchlist for actual red-status articles? —valereee (talk) 14:33, 1 November 2020 (UTC)

Fork

I've been using this for a long time--thanks, Evad37!--but the grey button always threw me off (the years went by, and I'd still think it meant a nuclear bomb had been detonated there--every.single.time). So I forked it, and took the chance to add more colours. I'm sure this would be pretty easy to make it customisable, with a declared variable in common.js (I might get to it sometime, a few more years down the track 😅). — Guarapiranga ☎ 04:04, 23 May 2022 (UTC)