I'm pretty sure all 20 worst nodes of the year is going to prove out of reach, at least I've never seen it done
I've been proved wrong! This rare feat has finally been achieved.
It lasted only for a few days though, towards the end of March 2018 (one example shown below).
This is a mind-bogglingly difficult feat to pull off, so much so that only
one monk in the entire history of Perl Monks has been able to do it, and even then only for a few days.
Though BrowserUk tried for a little while, he lacked the persistence, the staying power, week after week, month after month,
year after year, to keep on relentlessly posting the utter rubbish required to pull it off.
Worst Nodes of The Week
As of Mar 27, 2018 at 23:44 UTC, Next refresh in 1 hour and 15 mins ±15 min
Worst Nodes of The Month
As of Mar 27, 2018 at 12:21 UTC, Next refresh in 9 hours and 45 mins ±15 min
Worst Nodes of The Year
As of Mar 27, 2018 at 12:21 UTC, Next refresh in 9 hours and 45 mins ±15 min
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
I'm pretty sure that's neither the first nor longest time he did it
Though he did it for a number of days after March 18 2018, I don't believe he ever did it before then because I've been checking regularly.
Note that for Worst Nodes of the Year you only need to check once a year or so
whenever there's a "blocker" (i.e. a huge negative reputation node written by someone else) on the Worst Nodes list.
That is why it is such a rare feat: you need a full year without some random troll posting an absolute shocker.
The last such shocker was Re^4: Canonization Without Representation (rep:-27) by trippledubs - which disappeared from Worst Nodes of the Year on March 18 2018.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |