<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A social networking operating system</title>
	<atom:link href="http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/</link>
	<description>IT mixology and other thoughts about tech, life the universe and everything</description>
	<lastBuildDate>Thu, 11 Mar 2010 08:53:55 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Social Network Operating System &#171; Placebo Faith [GOD.000.000.00I]</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-158</link>
		<dc:creator>Social Network Operating System &#171; Placebo Faith [GOD.000.000.00I]</dc:creator>
		<pubDate>Fri, 17 Apr 2009 18:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-158</guid>
		<description>[...] OS) . I was so excited that i came up with something cool idea, when i happened to google for info, http://thestateofme.wordpress.com/2008/12/16/a-social-networking-operating-system/ Well i dont know how google is venturing (Once again dissapointed that, its already thought by the [...]</description>
		<content:encoded><![CDATA[<p>[...] OS) . I was so excited that i came up with something cool idea, when i happened to google for info, <a href="http://thestateofme.wordpress.com/2008/12/16/a-social-networking-operating-system/" rel="nofollow">http://thestateofme.wordpress.com/2008/12/16/a-social-networking-operating-system/</a> Well i dont know how google is venturing (Once again dissapointed that, its already thought by the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk Wylie</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-100</link>
		<dc:creator>Kirk Wylie</dc:creator>
		<pubDate>Wed, 31 Dec 2008 17:04:19 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-100</guid>
		<description>I&#039;d pipe in here that perhaps another reason why XMPP has started to work here is because people have spent time working on the content problem (which is one of the things that kills ESBs in their Consultant-Driven form): in order to consume, you have to be able to consume everything that&#039;s coming out; publishers all though seem to want to publish in their own form.

You very quickly get into the MxN problem: M consumer applications, N publishers. Each of them decides &quot;I&#039;m the best at modelling this problem for my particular domain&quot; and does their data modelling, and then you end up with a whole bunch of individual point connections and some really REALLY fugly glue to get similar consumption.

You really need some people to sit down and hammer out what the content of these messages (no matter how they&#039;re delivered) are going to look, and that&#039;s pretty hard, because every system is slightly different. Some people have started to do a reasonable job at this, but I&#039;d say that&#039;s as big a problem as any of the technical challenges of getting the messages from A to B: getting general agreement on what precisely is supposed to go into them in the first place.

Also, Chris, are you imagining something like Yahoo Pipes writ large?</description>
		<content:encoded><![CDATA[<p>I&#8217;d pipe in here that perhaps another reason why XMPP has started to work here is because people have spent time working on the content problem (which is one of the things that kills ESBs in their Consultant-Driven form): in order to consume, you have to be able to consume everything that&#8217;s coming out; publishers all though seem to want to publish in their own form.</p>
<p>You very quickly get into the MxN problem: M consumer applications, N publishers. Each of them decides &#8220;I&#8217;m the best at modelling this problem for my particular domain&#8221; and does their data modelling, and then you end up with a whole bunch of individual point connections and some really REALLY fugly glue to get similar consumption.</p>
<p>You really need some people to sit down and hammer out what the content of these messages (no matter how they&#8217;re delivered) are going to look, and that&#8217;s pretty hard, because every system is slightly different. Some people have started to do a reasonable job at this, but I&#8217;d say that&#8217;s as big a problem as any of the technical challenges of getting the messages from A to B: getting general agreement on what precisely is supposed to go into them in the first place.</p>
<p>Also, Chris, are you imagining something like Yahoo Pipes writ large?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexis</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-98</link>
		<dc:creator>alexis</dc:creator>
		<pubDate>Wed, 31 Dec 2008 12:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-98</guid>
		<description>Oh - PS - it is really important that whatever technology is used for micro-integration, to achieve genuine social integration it has to be decentralised and not require submission to a single authority.  This is why things like browzmi, friendfeed, gnip and twitter are intermediate solutions, however cool or useful they may otherwise be.  Federated social networks have to be *federated*.  XMPP is great for this because it has a workable model for federated identity, independent of physical addressing.</description>
		<content:encoded><![CDATA[<p>Oh &#8211; PS &#8211; it is really important that whatever technology is used for micro-integration, to achieve genuine social integration it has to be decentralised and not require submission to a single authority.  This is why things like browzmi, friendfeed, gnip and twitter are intermediate solutions, however cool or useful they may otherwise be.  Federated social networks have to be *federated*.  XMPP is great for this because it has a workable model for federated identity, independent of physical addressing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexis</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-97</link>
		<dc:creator>alexis</dc:creator>
		<pubDate>Wed, 31 Dec 2008 11:51:50 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-97</guid>
		<description>The term I prefer is &#039;micro-integration&#039; because we are talking about correlating streams of microcontent - eg. a blog comment, a tweet, a tag, an annotation to a document.  An internet of &#039;things about things&#039;.  As with normal integration the main operations are: route, transform and filter.  Chris is right to mention ESB as involving the same aysnchronous integration patterns (see also Gregor Hohpe&#039;s book).

In this context, &#039;social&#039; means sharing updates on &#039;social objects&#039; by multicast pubsub filtered by roster; now fashionably called &#039;assymetric follow&#039;.  This is just messaging - so why not seek to reapply successful integration patterns from enterprise messaging, to social applications.

I think it is useful to then ask:

* what social utilities or shared services would enable the messaging for micro-integration between social applications - eg. relays, firehose services, stream query services ...
* what standards are needed?  http, xmpp, amqp, app, ...
* what microcontent adaptors are needed at the endpoints and for transformations
* what is the pingback model (if any) and/or push pubsub model, for defining updates on web content, and subscriptions to ad hoc microcontent feeds

To address the problem Chris describes in his post above, all this needs to allow for (but not mandate) consumer driven feed creation (&quot;tell me about updates to this microcontent given by this URI that only I care about&quot;).</description>
		<content:encoded><![CDATA[<p>The term I prefer is &#8216;micro-integration&#8217; because we are talking about correlating streams of microcontent &#8211; eg. a blog comment, a tweet, a tag, an annotation to a document.  An internet of &#8216;things about things&#8217;.  As with normal integration the main operations are: route, transform and filter.  Chris is right to mention ESB as involving the same aysnchronous integration patterns (see also Gregor Hohpe&#8217;s book).</p>
<p>In this context, &#8217;social&#8217; means sharing updates on &#8217;social objects&#8217; by multicast pubsub filtered by roster; now fashionably called &#8216;assymetric follow&#8217;.  This is just messaging &#8211; so why not seek to reapply successful integration patterns from enterprise messaging, to social applications.</p>
<p>I think it is useful to then ask:</p>
<p>* what social utilities or shared services would enable the messaging for micro-integration between social applications &#8211; eg. relays, firehose services, stream query services &#8230;<br />
* what standards are needed?  http, xmpp, amqp, app, &#8230;<br />
* what microcontent adaptors are needed at the endpoints and for transformations<br />
* what is the pingback model (if any) and/or push pubsub model, for defining updates on web content, and subscriptions to ad hoc microcontent feeds</p>
<p>To address the problem Chris describes in his post above, all this needs to allow for (but not mandate) consumer driven feed creation (&#8220;tell me about updates to this microcontent given by this URI that only I care about&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Swan</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-96</link>
		<dc:creator>Chris Swan</dc:creator>
		<pubDate>Wed, 31 Dec 2008 09:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-96</guid>
		<description>Alexis knows a lot about the background to this, as we&#039;ve been talking for some months about the underlying issues before I got around to the blog post.

Once again I agree that OS is a clumsy term. I&#039;m not however that convinced by application execution environment in this context, as it stretches my own interpretation of what an &#039;application&#039; is.

My sense of what this would look like if it ever works properly is some point and click plumbing stuff over the top of some pretty fugly scripting. Clearly the average user won&#039;t be creating their own social applications (= writing fugly scripts), they&#039;ll be specifying how they want things to be joined together and configuring what&#039;s important and what&#039;s not (JP&#039;s &#039;graphic equaliser&#039;). For that to happen firstly needs some standards for the interfaces, so that one piece of equivalent functionality can be swapped for another. I doubt that the existing service providers will be that inclined to break down the walls around their gardens, so somebody else will probably have to get involved in wrapping and mashing.

This is all starting to remind me of the enterprise service bus concept (not that I&#039;ve ever really seen it work properly), though clearly stuff like OpenAdaptor was useful and successful.</description>
		<content:encoded><![CDATA[<p>Alexis knows a lot about the background to this, as we&#8217;ve been talking for some months about the underlying issues before I got around to the blog post.</p>
<p>Once again I agree that OS is a clumsy term. I&#8217;m not however that convinced by application execution environment in this context, as it stretches my own interpretation of what an &#8216;application&#8217; is.</p>
<p>My sense of what this would look like if it ever works properly is some point and click plumbing stuff over the top of some pretty fugly scripting. Clearly the average user won&#8217;t be creating their own social applications (= writing fugly scripts), they&#8217;ll be specifying how they want things to be joined together and configuring what&#8217;s important and what&#8217;s not (JP&#8217;s &#8216;graphic equaliser&#8217;). For that to happen firstly needs some standards for the interfaces, so that one piece of equivalent functionality can be swapped for another. I doubt that the existing service providers will be that inclined to break down the walls around their gardens, so somebody else will probably have to get involved in wrapping and mashing.</p>
<p>This is all starting to remind me of the enterprise service bus concept (not that I&#8217;ve ever really seen it work properly), though clearly stuff like OpenAdaptor was useful and successful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk Wylie</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-95</link>
		<dc:creator>Kirk Wylie</dc:creator>
		<pubDate>Tue, 30 Dec 2008 23:28:21 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-95</guid>
		<description>Alexis Richardson in a meatspace conversation today hit on an excellent name for this type of thing: Application Execution Environment. Hits on all of the points in your evolutionary discussion perfectly (UNIX, J2EE, and &quot;Something In The Browser&quot; all point to Application Execution Environment to me).

For those of us drilled into a rigorous CS background every time we see &quot;Operating System&quot; used wrongly (see: Cloud OS, Google OS, Social Network OS) we cringe. :-)</description>
		<content:encoded><![CDATA[<p>Alexis Richardson in a meatspace conversation today hit on an excellent name for this type of thing: Application Execution Environment. Hits on all of the points in your evolutionary discussion perfectly (UNIX, J2EE, and &#8220;Something In The Browser&#8221; all point to Application Execution Environment to me).</p>
<p>For those of us drilled into a rigorous CS background every time we see &#8220;Operating System&#8221; used wrongly (see: Cloud OS, Google OS, Social Network OS) we cringe. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Swan</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-94</link>
		<dc:creator>Chris Swan</dc:creator>
		<pubDate>Tue, 30 Dec 2008 11:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-94</guid>
		<description>Thanks Kirk,

I realised from the outset that the operating system label was likely to cause offense. To be honest I don&#039;t like it myself, and it wasn&#039;t even my label as it came up in a workshop with one of our research partners (I won&#039;t call out the guilty party by name). I used it anyway as I haven&#039;t yet thought of a better label for &#039;something in the browser&#039; that lets you do all this user side social network combination stuff.

Perhaps if we can agree to David&#039;s &#039;snopsys&#039; (even if it does have the broken term operating system buried in there) then we can move on from the symantics (which are always important in these early days) and on to a richer discussion on how this might be made to work (and who will write it)?</description>
		<content:encoded><![CDATA[<p>Thanks Kirk,</p>
<p>I realised from the outset that the operating system label was likely to cause offense. To be honest I don&#8217;t like it myself, and it wasn&#8217;t even my label as it came up in a workshop with one of our research partners (I won&#8217;t call out the guilty party by name). I used it anyway as I haven&#8217;t yet thought of a better label for &#8217;something in the browser&#8217; that lets you do all this user side social network combination stuff.</p>
<p>Perhaps if we can agree to David&#8217;s &#8217;snopsys&#8217; (even if it does have the broken term operating system buried in there) then we can move on from the symantics (which are always important in these early days) and on to a richer discussion on how this might be made to work (and who will write it)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk Wylie</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-93</link>
		<dc:creator>Kirk Wylie</dc:creator>
		<pubDate>Tue, 30 Dec 2008 10:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-93</guid>
		<description>Hey, Chris,

While I appreciate that you&#039;re trying to promote something that would be useful, you&#039;re really not talking about an Operating System. An OS is there to manage hardware resources and potentially provide a primary interface to the user. What you&#039;re talking about is services to be consumed to make doing social applications easier.

http://kirkwylie.blogspot.com/2008/12/snos-quit-angering-andrew-tanenbaum.html

Thanks a lot,

Kirk</description>
		<content:encoded><![CDATA[<p>Hey, Chris,</p>
<p>While I appreciate that you&#8217;re trying to promote something that would be useful, you&#8217;re really not talking about an Operating System. An OS is there to manage hardware resources and potentially provide a primary interface to the user. What you&#8217;re talking about is services to be consumed to make doing social applications easier.</p>
<p><a href="http://kirkwylie.blogspot.com/2008/12/snos-quit-angering-andrew-tanenbaum.html" rel="nofollow">http://kirkwylie.blogspot.com/2008/12/snos-quit-angering-andrew-tanenbaum.html</a></p>
<p>Thanks a lot,</p>
<p>Kirk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Swan</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-92</link>
		<dc:creator>Chris Swan</dc:creator>
		<pubDate>Tue, 30 Dec 2008 08:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-92</guid>
		<description>Thanks David, snopsys certainly sounds better than the geeky SNOS that I&#039;d been using so far.

Hopefully a vanity search subscription will bring Adriana along shortly. The pointer to her stuff quickly led me to http://themineproject.org/, which looks like a good attempt to by a &#039;snopsys&#039;, though clearly it&#039;s still early days.</description>
		<content:encoded><![CDATA[<p>Thanks David, snopsys certainly sounds better than the geeky SNOS that I&#8217;d been using so far.</p>
<p>Hopefully a vanity search subscription will bring Adriana along shortly. The pointer to her stuff quickly led me to <a href="http://themineproject.org/" rel="nofollow">http://themineproject.org/</a>, which looks like a good attempt to by a &#8217;snopsys&#8217;, though clearly it&#8217;s still early days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Tebbutt</title>
		<link>http://blog.thestateofme.com/2008/12/16/a-social-networking-operating-system/#comment-91</link>
		<dc:creator>David Tebbutt</dc:creator>
		<pubDate>Mon, 29 Dec 2008 23:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://thestateofme.wordpress.com/?p=59#comment-91</guid>
		<description>May I offer the name snopsys if a social networking operating system comes into being?

I too arrived here via @jobsworth / JP Rangaswami

And, by the way, it makes a lot of sense. Is Adriana Lukas part of this conversation?</description>
		<content:encoded><![CDATA[<p>May I offer the name snopsys if a social networking operating system comes into being?</p>
<p>I too arrived here via @jobsworth / JP Rangaswami</p>
<p>And, by the way, it makes a lot of sense. Is Adriana Lukas part of this conversation?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
