This week, we launched a ‘social media widget’ on the JISC homepage (the eagle-eyed among you might have noticed it was launched last week but quickly pulled when it fell over!).
We didn’t just want to provide a link to YouTube, Slideshare etc. We wanted to surface some of the actual content JISC provides on social websites; in usability terms, to provide good ‘scent of information’. The widget needed to be accessible, scalable (as more social media channels come online) and fit within a small space on the JISC homepage.
The development itself was not always fun owing to the vagaries of working with 3rd party services and feeds. We had to build in error handling for when 3rd party feeds suddenly died or changed. As feeds came in various formats or were simply invalid, Feedburner also came to the rescue with its ability to convert feeds into other formats (we standardised on RSS 2.0). Anyone who works with feeds will know the benefits of using a service like Feedburner but I discovered another one during this development. Twitter (and probably other services) implements various methods to reduce the amount of data it is sending out. This is normally done by reducing the number of feed requests from any one source. However, certain sites like Feedburner and Yahoo Pipes are ‘whitelisted’ and allowed more requests. Another advantage is that if a 3rd party service goes down, the feed should display the content that has been cached at Feedburner. So yay for Feedburner …but hold on; it doesn’t seem to like Twitter feeds very much 🙁 Our developer managed to set it up but now we can’t change it and it seems to be a well-documented issue that Feedburner and Twitter feeds do not play nicely together.
We did also try implementing a bit of AJAX to refresh the widget if a feed updated when a user was viewing the homepage. This proved very fiddly and, on reflection, we thought ‘well how long do people spend on the homepage anyway’? Nice to have but not worth the hassle.