Feedify will make Atom feeds out of your Flickr and Instagram contacts’ photos, so you can see new uploads in your RSS reader.
I built another thing. Feedify will make Atom feeds out of things that don’t have feeds, because I like having feeds. Basically, I got bored of having to jab at 5 icons on my phone every time I wanted to do a sweep of “what my friends are doing” – I’d much rather just subscribe to feeds and my RSS reader can tell me about things.
Right now it’ll make feeds out of Flickr and Instagram photo uploads of your friends. These were easy – they map directly to single API calls to the respective services (in the case of flickr, this leads to unavoidable disadvantages with the feed. But that’s life). As and when I think of more things that are easy, I’ll add them.
So yes. Feedify. Play with it.
Timezones are hard. I’ve personally spent way too much time dealing with date and time formatting issues and stupidity. But in this case I want to mount a defence of XML–RPC, because I really quite like it. I feel the kung-foo blog gets its complaint wrong:
The Atom publishing protocol gets this right. It requires that dates sent and received specify the timezone. There’s no need to configure ecto as it knows Atom is a good boy. The problem is with XML–RPC. It does not have that requirement, and each blog system interprets dates differently.
The XML–RPC spec is really small. It’s very easy to implement from scratch if you need it, but you don’t normally need to do so, because sensible languages already have clients. And you don’t need to know about the XML side of things – it’s just RPC, you’re calling a named method on a specific endpoint with ordered parameters. Not very RESTful, I’ll grant you. But I like things that map well to the underlying realities.
One of the data types it knows how to encapsulate is a ‘date’, and it does this sensibly, serializing the date using ISO8601. If ‘not specifying timezones’ is an error, then it’s an error in the ISO8601 spec, because the spec allows a time without a timezone. XML–RPC isn’t judgemental. But ‘floating’ times do exist. And I can send them with XML–RPC.
Granted, they make little sense in the context of a blog entry. So the error is with the metaweblog (and associated) apis, which merely use XML–RPC as their transport. I will happily agree that the awful mess that is the metaweblog api is a pain. But don’t equate a cruddy API and buggy implementations with the underlying transport.