First-step with Yahoo! Pipes

I’ve been reading a lot recently about Yahoo! Pipes so I thought I’d give it a try myself. I created a simple feed aggregator by merging the RSS feeds for my Google reader starred items,, and the RSS feed for this together and output as a new feed. I had to do some minor manipulation, for example to remove duplicates (which you get when you star, bookmark or link-blog the same item) and to sort the merged feeds into descending order of publication date. Then I took the output of the resulting feed and added it to my iGoogle page. The result is a nice summary of my recent activities.

This was a very quick experiment, and I’m sure there’s a lot more that you can do: for example, only the link title and URL is captured, not the text, nor any multimedia content. But it’s very easy to use and worthy of further experimentation.

We ignore digital media at OUr peril: the movie

In a follow-up to his blog article on Digital Media (reported in my article about serendipity), OU Educational Technologist Tony Hirst has used the web 2.0 site SplashCast to mash up a presentation with the cited videos. Here’s Tony’s blog article, and here is the presentation. The end result serves both as an interesting introduction to the educational possibilities of digital media and an interesting case study of what can be done with access to video sharing sites and the web.

The view from here

Seen in today’s Guardian is news of the impending July 27th release of the BBC’s new content-on-demand iPlayer. Unfortunately, acording to the article and Guardian blogger Bobbie Johnson, it won’t run on Vista which adds it to a growing list of essential software (which includes Quicktime and iTunes) which won’t run on my newly upgraded laptop. Still, we still have XP on the computer at home so next time we miss an episode of Dalziel and Pascoe because of a recording clash on the Sky+ box, all will not be lost!

Mr Brown’s Arrival

It’s not technology related, but the arrival of new Gordon Brown as new PM, ought to be marked somehow, even if a day late! My personal Brown story: I was once within three feet of Gordon in the ticket hall of the Paddington Station underground. He was in the opposition then, so got around using public transport. I don’t suppose he’d remember me.

(image originally published on the BBC news web site.)

Social Software: Scary Monsters?

So we’re all agreed. Blogs: good; email: bad. Wikis: good; sending round attachments to a dozen people and then having to merge all the changes by hand afterwards: bad.

This one goes out to all my colleagues who really do want to send out attachments by email and merge changes manually. (No, I tell a lie, they want to send out printouts of documents and merge red-lined versions back into the electronic documents manually!) Here’s a presentation by Suw Charman (note no Powerpoint!!) recorded at Google HQ and released in the Google TechTalks series that spells out the barriers to social tools and why it might be good to embrace change. This is why I live my life on the web: welcome to my world!
(Note: video is 55 minutes long, so lock the door, take the phone off the hook and grab a coffee before hitting play.)

Also discovered

New blog entry on the Learning Lab is a related item about using Google docs for collaborative writing. This might actually work for us!

Next Big Language (NBL)

Following a link in Stefan Tilkov’s blog to another blog entry by John Lam which claims that Rails has been ported to JavaScript by Steve Yegge of Google, I came across this intriguing article by Mr Yegge published back in February. He gives a lot of hints but doesn’t actually name the NBL: but from the speculation in the comments and now this announcement, it looks like it might have been JavaScript!


InfoQ has published an article on the blogosphere’s buzz around Steve Yegge‘s presentation of the JavaScript (Rhino) port of rails at FooCamp. The article quotes heavily from Steve’s own posted response to all of the interest. But I find Steve’s work interesting mainly because it reveals the unexpected power of the Rhino JavaScript interpreter which of course is built in to Java SE 6 and runs on the JVM on the server.