File talk:RW sysopship tree.png

This turned out every bit as unwieldy as I feared it would be. Does anyone know how I can force it so stop putting them all on one gigantic line? 00:56, 19 June 2010 (UTC)
 * I have no idea how you'd want to organise something like that... It really is quite epic and if anything makes it harder to visualise. 00:58, 19 June 2010 (UTC)
 * Yah, that's kind of the problem—and there's still 375+ to go. But I'll stop now if I can't get them to stop lining up.   01:05, 19 June 2010 (UTC)
 * I uploaded a new version using fdp rather than dot. It's a lot messier but easier to look at at-a-glance.  (Also, only about 30% done.)   01:16, 19 June 2010 (UTC)

My ultimate goal of this was to give the tiniest visual approximation to the total clusterfuck that our logs are. That's why I included every instance a user is sysopped and not just the first one—I wanted multiple lines running to the same person. 01:05, 19 June 2010 (UTC)

Issues raised while making this chart
01:00, 19 June 2010 (UTC)
 * I didn't know we ever had checkuser and oversight installed. Much less that we gave them to anyone.
 * Who the heck sysopped Abuse Filter?
 * Checkuser appeared briefly then was disabled. It was never really used. Well, Nx used it once to ID a troll/vandal, then there was a sort of "up in arms" HCM over it and it was disabled soon afterwards. If Nx checkusered anyone else while it was active, he's definitely not acted on it. 01:11, 19 June 2010 (UTC)
 * Actually Nx just looked at the logs. All check user does is given someone on the other side of the server the ability to check the logs. 01:24, 19 June 2010 (UTC)