Dominic Sayers

Social Data Flow minor update

I'll probably write some more about Social Data Flow shortly, but for now I just wanted to talk about extending the canonical data flow with bespoke updates flowing through my own site. In a perfect world, my syndicator (which happens to be ping.fm) would take care of all my syndication needs. It would take my micro-blogs and status updates and send them to all known social sites where I have an account. Unfortunately while ping.fm appears to have the best coverage, it's not complete. Posterous, for example, is a significant omission (any site where Stephen Fry is active has to be considered a significant site, or anyway it soon will be). As it happens, it's very easy for me to update Posterous with my ping.fm outpourings since I've already implemented a ping.fm Custom URL for my own site - it updates the dynamic sections in the left-hand column. All I had to do was arrange for the PHP page that receives the ping.fm updates to then mail the same update to Posterous. Job done. Not sure why ping.fm haven't done it themselves, except that pressure of other feature request probably prevents them doing everything they want to straight away. More to come on my struggle to get an acceptable flow of location data in place.

Social data flow in action

OK, I've seen a few things online recently that amused me and I'd like to share them. I don't want to add them to delicious.com because that's what I use for links I need to find again someday. These are things I've seen and enjoyed but they are gone. For me they are yesterday's newspaper. But you may not have seen them and I think you should. So I've decided to add them to Tumblr. Easy. Tumblr is a great tool for doing this, it makes it easy to add videos, links, pictures, anything. I am very happy with this choice. But this has now repurposed Tumblr in my social data flow from an output device to a content provider. Before, it just used to receive my status updates and micro blogs. Now it is the place where I link to things that have amused me. Here's how I needed to reconfigure my social data flow: 1. Add Tumblr to my aggregators. Now my Tumblr posts will appear in my All Activity feed. 2. Remove Tumblr from my syndication list. Now Tumblr will not receive my status updates or micro blogs. This is important because otherwise these updates would appear twice in my All Activity feed. 3. Er... 4. That's it. Simple.

Revised social data flow

In an attempt to remove the latency problem from my social data flow, I've rearchitected it a bit. Unfortunately the reworked flow is not quite as elegant as the original but then it had more sophisticated design goals so that's not terribly surprising. Here's the revised flow with notes below:

(Click on the image for a bigger version)

Notes:

1. Now I can allow ping.fm to update Twitter and identi.ca immediately so I have removed the latency problem from the previous configuration. Once again I can use Twitter in a conversational way instead of it being a mere receptacle for RSS updates every half hour.
2. You'll note also that Twitterfeed can now update identi.ca and other Laconica-based micro-blogging sites. Thanks, Mario. This means I can promote identi.ca to be a peer with Twitter and receive all my updates including real-time micro-blogs (tweets).
3. The three subscription points are the same: Writing, Status Updates and All Activity. The URIs for those resources have not changed.
4. I have distinguished between blog posts such as this and the notification of those posts. To subscribe to the full post stream use the Writing feed. If you subscribe to the All Activity feed you will be notified about posts but only see the title not the whole article. Unfortunately if you subscribe to both you will see both the blog post and a separate notification of its existence - I can't do anything about this yet.

So there's an emerging gap between those select sites that I use to do stuff and those sites that merely receive notification of that activity. My strategy will be to keep to a minimum the sites I use for doing things, and maximise the number of sites that are notified about it. This way I can keep all my pictures, links, writing etc. in one place but all my disparate multiple friend communities will get equal notification of new activity in one of those upstream sites. I think the new slightly less elegant social data flow is functionally better and I'll try to stick with it for a while to see how it performs in practice.

Initial thoughts on my new social data flow

Firstly, apologies to anybody who couldn't see the social data flow diagram in my earlier post - I've now hosted it on my own server so it shouldn't disappear quite so often.

(Click on the image for a bigger version)

The new data flow, using ping.fm to syndicate my status updates and micro-blogs and FriendFeed to aggregate my other activity and consolidate everything into a coherent set of feeds, is working quite well. I would like to be able to have more control over the format of what both ping.fm and FriendFeed do for each target system, but the defaults are adequate for now. Here are the issues I'm experiencing: 1. Using Twitterfeed to take my FriendFeed RSS and pipe it into Twitter introduces a degree of latency that's a bit inappropriate for Twitter. Twitter should be near real-time and conversational (whilst not being an instant messaging system), but Twitterfeed only reads my FriendFeed every half an hour. If I get ping.fm to update Twitter directly then I'm going to get some updates twice, which is exactly what I'm trying to avoid. 2. Some of the connected systems (identi.ca for example) are Twitter-like, and I'd like to treat them the same way as Twitter: as an output device for all my activity. But Twitterfeed is Twitter-specific and I haven't found an equivalent for identi.ca etc. yet. In any case I don't want a different Social ETL tool for each output system; I want Twitterfeed (or something) to do this for a number of target systems. 3. There's no class solution for location-based systems yet. Obviously I'd like to be able to update my location and travel plans in one place and have it propagate to TripIt, Dopplr, BrightKite etc. I think FireEagle may be trying to do this but it's short of two things at the moment: co-operation from the other systems and an invitation for me. If anybody has access to FireEagle I would appreciate a way in. 4. Now I need to do the other thing - deduplicate my profligate friends' updates. When Myrto uploads a picture to Flickr, for instance, I get notified about it four times. I can rationalise this a bit but I can't ignore her FriendFeed or Twitter because I would miss some of her updates, so I'm condemned to hearing about her new pictures multiple times unless (a) she adopts a version of my social data flow or (b) I find a solution to deduplicating the same update coming through multiple channels. This duplicate filter is necessary until everybody adopts my architecture, i.e. for ever. Does anybody know of a solution out there? This all seems quite difficult to manage and well beyond anybody who is either busy or technically challenged. There's no real way of developing a packaged solution until all the social systems adopt a single sign-on technology like OpenID, and many of them have sound technical reasons for not doing so (OpenIDs can be created by anybody anywhere so it's a bit like expecting system owners to trust a digital certificate that has no trusted root certification authority). Anyway, that's the state of play at the moment. More to come I'm sure.