The Arizona Indymedia website was badly broken for like, 17 days - since the new year - links to individual newswire stories were broken. As users discovered this, they stopped posting stories. The site was dying. This problem was noticed pretty quickly by somebody else on the editorial collective. I honestly hardly ever look at the site, much less the newswire, so I hadn't noticed. But immediately, I was the one people went to and asked about it.
Okay, so, often people that know me pigeonhole me as a "geek", as a "computer person" or "techie" - but the AZ IMC site is not in my power to fix. It's administered by ubergeeks in the bay area and belgium and pittsburgh, or god knows where else, and even if i knew how to futz with sf-active i don't have admin permissions on the machine.
So usually all I do when something goes wrong is go on the indymedia chat system, irc://irc.indymedia.org - and get on the sf-active channel there, and ask for help. And usually within a few hours someone sees my question and fixes it.
WHY can't someone else do that, ever? IRC is not rocket surgery. It's just not that hard.
So the site stayed broken for a couple weeks because, frankly, i was busy and, well, i wanted to see if anyone else would step up and do it. I refuse to be "the tech guy", when all that really entails in this case is knowing how to ask the real tech guys a question. I refuse.
I guess it's kind of like arriving at a burning building and sitting there watching it burn down while the other residents sit there next to a phone, because nobody wants to learn how to pick up the phone and call the fire department. eventually you can't sit there anymore and watch, but at the same time you're just going, WTF, why didn't someone call before? Why? And is it worth having that building if every time anything goes wrong with it I'm the only one that will bother to call the rescue crew?
Posted by steev at Enero 18, 2008 06:30 AM