It happened all of a sudden. The feed from one POT Cert Class participant just wasn’t coming into the Pedagogy First aggregated blog. I spent hours trying to figure out why not – the feed finder screen would just go blank on only her feed. I Googled, I pounded, I went through what there is of FeedWordpress documentation. Mostly I wished I were Alan Levine or Tim Owens.
I have mentioned before that technologies known for doing some really cool things are becoming unreasonably complicated. This particular technological problem rests on a self-hosted installation of the software WordPress (built and maintained by a wonderful community) and the FeedWordpress plugin (built and maintained by a wonderful coding person). When one gets updated, it often doesn’t play nice with the other. And I can’t fix it. I say again unto you, I am not a coder. I find code, I steal code, I envy code, but I do not code.
I finally asked that a new blog be created for this participant, and it seems to be feeding. For now. Of course, the other one had fed too, all of the first semester. Given my own significant limitations, we will not be able to do this again this way next year.
The recipe at the moment is this. Start with recent adventures with self-hosted Moodle, add this new self-hosted WordPress crisis, mix with a dash of cloud failure (Google abandoning Reader, Posterous closing shop, and SeesmicWeb being bought and killed by the inferior HootSuite ). Stir and cook with a big dollop of my recent participation in reviewing a publisher-created program for grading student essays, and you have the kind of disillusionment you get by realizing you have already been devoured by the whale but didn’t know it.
The monsters (big proprietary systems, cloud-based sites, self-hosting) appeared to be separate, but were actually all parts of the same beast.
Self-hosting, a domain of ones own, the path of ds106 and the noble D’Arcy Norman – this has been the antidote to the bullying tactics of the LMS and publisher-created content. I have held it up as the way to avoid both big proprietary monsters and the vagaries of the disappearing web apps and fly-by-night cloud offerings. I have scoffed (quietly) at those who said they could not run their own blog, it was too hard. While I have not been guilty of encouraging anyone to run their own Moodle installation, I have persisted in doing it myself as a bulwark against Moodlling ignorance and exterally-run systems.
All this begins to seem like folly, a folly based on desire. An example: I want nested discussion forums where students can post multimedia, so I have Moodle. I find out today that (cloud-based) Schoology has nested forums! Yay! No! Wait! They are touted around the web as a “start up” of four years or so who use proprietary code (cue John Williams’ Empire Strikes Back music). I will have a free class, but never be able to access it otherwise, years down the line.
Fact is, none of these options are perfect, or even sufficient. The big LMS systems (including Moodle) upgrade and you can’t restore old courses and actually view student work – they say you can, but in fact it doesn’t work. I have all my courses backed up as Moodle .zip files, but now they’ve changed to .mbz. Out in the cloud, I can export my Posterous as they close down, but when I import it into WordPress a bunch of stuff is wrong or missing or ugly. These things weren’t built to be transferrable, or to cater to the archiving tendencies of the mere customer. Whether proprietary and exorbitantly priced, or open source and impossible to run without an IT degreee, none of the options have a sense of history, only a blindered vision of a future fulfilled by profits, market share, or geeky street cred.
Perhaps I am dissembling now to be running a class encouraging faculty to plunge into explorations of web tools and new technologies. I cannot in good conscience suggest anyone build a course around any of them. My colleague Todd Conaway says that it’s better to learn from creating, to meet the challenge of the occasional failure, to engage the technologies and learn from them even if they’re transient. I know that is true. But if you spend too much time in the belly of the beast (whether self-hosted, cloud-based, or LMSed) , things start to smell fishy.