created 23 September 2009 in links tagged api, flickr and scaling.
Paul speaks Truth.
..while adding more “extras” would reduce the number of API calls needed for a specific application, it doesn’t reduce the load on flickr’s back end systems. We’ve found it actually increases the load, as developers are more likely to request extra data they don’t need, and one heavy API request ties up more of our system resources than multiple lighter API requests.
Also, developer time. But that’s more obvious. What I like is the point that, yes, it’s annoying making n+1 calls, but putting that into one call is still going to end up as n+1 database calls at some point. Joins are Bad. Keep them explicit.
created 16 October 2008 in stream tagged flickr and whine.
created 03 October 2008 in links tagged explore, flickr, interesting and panda.
The Panda. Slightly horrifying. But fascinating.
created 30 September 2008 in links tagged flickr, photos, pixelpipe and upload.
It’s like Shozu, basically. Except the iPhone client is nicer and the website provides a little more feedback. Oh, and the iPhone client actually uploads usefully metadata-rich images - see http://jerakeen.org/photos/2008/09/2901776022/ for an ugly example. There’s also a free iPhoto export plugin. Won’t talk to the jerakeen.org metaweblog interface yet, though. Must look into that.
created 09 September 2008 in notes tagged flickr, georss and meta and is geotagged
Maybe I talk to Aaron too much, but I’m obsessed with geodata this week. So today the crazy mess of code that is jerakeen.org understands lat/longs on pages, and presents little ‘has a location’ links next to the tags (I’ve tagged this one with ‘where I’m sitting’ as an example). When I syndicate flickr photos, I’m pulling any geotagging data across as well, so you’ll be able to see lots of geotagged photos as well.
In the same vein, I’ve added georss to the Dopplr journal feeds. Items are tagged with the lat/long of the tip or city that they’re about. Trip items get their location from the city the trip is to. Not every item will have a geotag, but everything that I can tie to a location will do.
Feedparser (which I use to pull my Dopplr feed into jerakeen.org) needs a patch to be able to parse the GML properly (that patch doesn’t apply clean to the 4.1 release on code.google.com, but can be bullied into working pretty easily). So I also pull the lat/longs of my Dopplr updates into jerakeen.org.
I have no idea what I’m going to do with this data. It just seemed a shame to leave it lying around unexposed. I’ve put it into my RSS feeds as well (I love django), so the stream feed can be dropped into Google Maps for prettiness. And eventually I’ll make the ‘has a location’ links do something more interesting, I guess.
created 01 August 2008 in notes tagged flickr.
On the whole, building the Science is a lot more fun than the eclipse itself.
Also, I can now blog from flickr into jerakeen.org! Yay XMLRPC.
(Partial Solar Eclipse-7 by blackbeltjones)
created 10 April 2007 in links tagged design, flickr, patterns and screenshots.
Screenshots of common operations.
http://www.flickr.com/photos/factoryjoe/collections/72157...
created 07 December 2004 in blog tagged flickr and photos.
flickr is annoyingly slick. I messed around for a few hours trying to learn enough php to parse the RSS feed or use their API or something to get a list of recent photos on the page here, then I realised that there’s a page that just does all the work for you. You need to mess with javascript, but I can cope with that. Don’t I look silly now?
Also, I can get (atom? rssd+? Who cares?) feeds of anyone’s photostream, I can upload from my mobile via email from anywhere (leading to silly photos), I can just link to anything without having to explicitly share it… As has been said to me, these aren’t necessarily very clever features from a technical point of view, but it’s all about the workflow, innit? It’s so easy to use.