Today I was hoping to finish RSS with enclosures with students, and then move onto making video collages in QuickTime. Except we hit the automatic-enclosures-in-WordPress 1.5 problem. This is where WordPress auto-writes an enclosure if it finds a media file in a post. It seems to sort of work, but if you have a poster movie, for example, and so the embed tag combines a src and a href attribute, then WordPress seems to just keep adding enclosures. Which is a problem given there should only be one.
To solve it we could have:
- updated all the blogs to WordPress 2.x
- not embedded video and just provided some sort of link to the media file
- hacked the functions.php inside wp-functions in the blog installation
- and probably a few other possibilities too
The point of all this? Well, we hacked the functions.php file so that it no longer automatically writes the enclosure. By the time we had done this, then got the RSS enclosures happening, and subscribed, most of the class was done. Now, one view of this is that it disrupted the ‘scheduled’ class. On the other hand lets make a list of what might have been found out, even learnt, through this ‘disruption’.
Computers are noisy. Things regularly don’t go to plan (what other tools do you use that have ‘bugs’ as a given? Where crashing is standard operating procedure and where you must continue on continuous upgrade cycles to keep your tools ‘current’?).
Being able to read and edit code, even where you don’t necessarily know what exactly it might be doing, means you can fix, alter, change, amend, improve, and otherwise work around things. This has the corollary that code is malleable, quite accessible, and also that if you find out what to do, you are perfectly capable and empowered to do it.
Hence of course it also modeled how to find out these sorts of answers (I simply googled the phrase “multiple enclosures in RSS WordPress 1.5 and found a series of entries in the WordPress support pages), and that these answers are readily available online, as long as you have enough literacies to know a) what you need to ask, b) what it is you’re actually trying to fix and c) what counts as a good enough answer or solution.
What we’re doing, even though it has been around for a few years (though only a few years) is not so much leading edge as bleeding edge. While there are now more bloggers than you can poke a stick at, the same cannot be said for videoblogging and even podcasting. We are ‘rolling our own tools’ here, cobbling things together since there is not (yet) something that just does it all, as we would wish, in one easy go. So we are also learning that this is how you make things on networks. They are pieces loosely joined. RSS from here, into feedburner there, some other client from over here. Location is no longer location, it is all information moving around, between and through. Finding a solution, making it happen (using free software all the way – fugu, textwrangler, and WordPress), testing it and then finding things to subscribe to, and so on. It is probably a harder and bigger step to then get your head into the space where you can see what you might do with this.
Tags:
hypertext,
Network Literacy,
teaching,
tools