Let me first preface this by saying that Paul Stamatiou (aka “stammy“) has done a great job delving into the slideshow for flickr users and enabling them to easily use it on their blog or site through his new assistive-application flickrSLiDR. That said, it is not without limitations, and while not due to Paul I do believe that the way it works should have been explained.
Flickr Slideshow
The lovely ladies and gents at Flickr (my favourite photo community) created the slideshow a few years back in September 2004 (Introducing Slideshows - September 10, 2004) and it was of course a great success. In spite of this there existed a major limitation, and that was in getting it to show anywhere but at flickr. Enter Paul Stamatiou.
Embedded Flickr Slideshow
In November of 2005 Stamatiou managed to determine a quick technique to embed slideshows in pages beyond flickr (see HOW TO Quickie: Embedded Flickr Slideshows - November 19, 2005), allowing flickr users to have the swish slideshow visible on their site with relevant tags, sets, groups and/or users acting as filters for the photos shown. I used this technique in a post showing the photos from my sisters high school graduation (see Eliza Graduates, November 2006).
Use of the Quick Embedding of Flickr Slideshows courtesy of Paul Stamatiou
The biggest issue is the use of iframes to embed the slideshow. Due to security restrictions on many free blogs and social sites iframes are prevented from being used. Despite the attention at the time, this was not a wide issue, since the uptake in the social sites was not as widespread as it is now, nor for that matter was flickr as popular.
flickrSLiDR
Enter Stamatiou’s new assistive-application flickrSLiDR - a tool to assist the creation of the code needed to embed the slideshow from flickr. Despite the upgrade to flickr’s slideshow (see flickr.com/photos/jufemaiz/show/), Stamatiou has not yet been able to move to the new slideshow flash file. The same issues also remain regarding embedding options of the iframe with free blog software and many social sites (of which the main one that springs to mind would be the security-as-swiss-cheese MySpace). Additionally, due to a wider audience than ever before, Stamatiou failed in his article to fully articulate what he was using and why these methods might fail (and the comments on his post reflect that).
Unfortunately the misinformation goes further, with people not understanding that this is an implementation of flickr’s own slideshow tool. With requests including: the ability to play mp3’s; add titles and other information; change the colours; change the order of the slides; and randomisation, it is obvious that a disclaimer would be exceedingly useful to be displayed to ensure that people who read the article were not misled over the potential that the flash file may have.
Thanks Stamatiou
While this might seem a little rough on Stamatiou, I hope he doesn’t take it as such. I was simply attempting to ensure that people were informed as to how the tool that he had worked on won’t get negative publicity for limitations outside of his control. I also believe it would have been wise to ensure that the post included the information on the technical aspect, so it could be referred back to directly to show why the limitations exist (and help prevent rather silly feature requests).

Your sis is a bit of all right!
Thanks for the feedback. I know what you mean.. people are asking for mp3 support and I’m like waht?! heh. As for the new slideshows, I have written a ton of code trying to get them to work and they do.. for about 5 hours. Flickr took a different strategy with the new slideshows which makes it a bit more complex to embed properly. If I do offer the new slideshows, which I do actually like, it would likely have to rely on a script hosted on my server that updated every few hours as flickr uses a unique token which changes every so often.
@tate: Trust you to get sidetracked there!
@Paul: I guess flickr might be actively attempting to discourage the use of their slideshow “software” (mini-app?) outside of their own site (that’d be the primary reason to use a token wouldn’t it?). A bit sad, though in line with their ToS. I suppose the alternative would be to DIY and use an RSS feed of image information (or perhaps something more in depth like direct queries) - though this would put a large strain on the API key (methinks). Cheers for the response though!