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)


  1. Now I can allow to update Twitter and 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 and other Laconica-based micro-blogging sites. Thanks, Mario. This means I can promote 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.


3 Responses to “Revised social data flow”

  1. 1 Dominic Sayers August 11, 2008 at 11:25

    Yes, see note 4 on my previous post. You do not need to subscribe separately to my Facebook and feeds since they should now be synchronised.

    What you may be doing is subscribing to a general feed from Facebook and/or of all your friends’ updates. Since your friendset on Facebook is not identical to your friendset on you must continue to do this or you will lose updates from friends that are on one site but not the other. But you will get duplicate updates from friends that are on both.

    ps I am loving the word “friendset” and will try to work it into a conversation soon.

  2. 2 decster August 8, 2008 at 20:19

    Your revised social data flow, as impressive as it is, has one flaw, albeit one that you won’t notice. I now get your status updates duplicated on my Facebook and feeds.

    So now I must suffer your urbane observations multiple times.

  1. 1 Social data flow in action « Dominic Sayers Trackback on August 13, 2008 at 08:52

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


This is not a riot

RSS What Dominic is doing

  • An error has occurred; the feed is probably down. Try again later.

Share me

Add to Technorati Favorites

Dominic's photographs

RSS My stubbornly unread reading list

  • An error has occurred; the feed is probably down. Try again later.

%d bloggers like this: