<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Open Connections</title>
	<atom:link href="http://openconnections.net/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://openconnections.net/blog</link>
	<description>A new standard for the open social web</description>
	<lastBuildDate>Mon, 21 Jun 2010 08:03:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New Project on Codeplex</title>
		<link>http://openconnections.net/blog/2010/06/new-project-on-codeplex/</link>
		<comments>http://openconnections.net/blog/2010/06/new-project-on-codeplex/#comments</comments>
		<pubDate>Mon, 21 Jun 2010 08:02:51 +0000</pubDate>
		<dc:creator>Todd</dc:creator>
				<category><![CDATA[Open Connections]]></category>

		<guid isPermaLink="false">http://openconnections.net/blog/?p=22</guid>
		<description><![CDATA[An early version of the initial profile provider has been uploaded to Codeplex. This is what we hope will be the first of many implementations.
This is a very early release. It is primarily serving as a protocol test bed right now. As the protocol nears completion, we will begin running it as a live profile [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>An early version of the initial profile provider has been uploaded to Codeplex. This is what we hope will be the first of many implementations.</p>
<p>This is a very early release. It is primarily serving as a protocol test bed right now. As the protocol nears completion, we will begin running it as a live profile provider.</p>
<p>This provider is comprised of two main pieces. The first piece is a WCF web service and the second is an ASP.NET MVC 2 web app. They are both written in C# on .NET 4.0. We would like to port this to Mono when time permits.</p>
<p>The system requires PostgreSQL 8.4 and uses a database abstraction framework called <a href="http://mnemo.codeplex.com/">Mnemo</a>. This framework currently only supports Postgres, though it will eventually support multiple databases. This requires, among other things, writing new templates for the code generator.</p>
<p>A final set of components are back-end services. These are written as Windows services and function like daemons. The first service is responsible for message handling. There will eventually be others for handling status streams, etc.</p>
<p>There is very little documentation right now, primarily in the interest of development speed. Please contact us if you have any questions.</p>
]]></content:encoded>
			<wfw:commentRss>http://openconnections.net/blog/2010/06/new-project-on-codeplex/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Friend Invites</title>
		<link>http://openconnections.net/blog/2010/06/friend-invites/</link>
		<comments>http://openconnections.net/blog/2010/06/friend-invites/#comments</comments>
		<pubDate>Sun, 20 Jun 2010 22:47:38 +0000</pubDate>
		<dc:creator>Todd</dc:creator>
				<category><![CDATA[Open Connections]]></category>

		<guid isPermaLink="false">http://openconnections.net/blog/?p=20</guid>
		<description><![CDATA[The initial version of the friend invite and accept protocol is complete. It has undergone five revisions but we&#8217;ve finally settled on a version that works well with OAuth 2.0.
One of the challenges in working with the OAuth 2 protocol is that it has been designed with large services in mind. When a third party [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>The initial version of the friend invite and accept protocol is complete. It has undergone five revisions but we&#8217;ve finally settled on a version that works well with OAuth 2.0.</p>
<p>One of the challenges in working with the OAuth 2 protocol is that it has been designed with large services in mind. When a third party wants to interact with users on such a service, they first need to register with the service to get a client ID and client secret. This, then, becomes their identity when dealing with the service and its users.</p>
<p>The difficulty with OC is that it&#8217;s a distributed system. If profile A is on one provider and they want to add a friend (profile B) on another provider, these two providers have to interact with each other. Not only do the providers have to cooperate, but their users will be using OAuth 2  to invite friends and accept or decline friend invites. This means that each provider has to have a client ID/secret issued by the other provider.</p>
<p>This is the interaction that the friend invite portion of the OC protocol facilitates. Once the client IDs and secrets are exchanged, then the normal OAuth 2 mechanism is used to invite and accept.</p>
<p>We&#8217;ll be publishing the details of the protocol, along with sequence diagrams, etc. to help illustrate it once we&#8217;re a little further along.</p>
]]></content:encoded>
			<wfw:commentRss>http://openconnections.net/blog/2010/06/friend-invites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open Connections Introduction</title>
		<link>http://openconnections.net/blog/2010/05/open-connections-introduction/</link>
		<comments>http://openconnections.net/blog/2010/05/open-connections-introduction/#comments</comments>
		<pubDate>Mon, 10 May 2010 02:00:31 +0000</pubDate>
		<dc:creator>Todd</dc:creator>
				<category><![CDATA[Open Connections]]></category>

		<guid isPermaLink="false">http://openconnections.net/blog/?p=4</guid>
		<description><![CDATA[Open Connections (OConn) is a way of connecting profiles in an open and secure fashion. The goals of the project are to develop a REST protocol that will be submitted to a standards body and to develop an open source implementation of that protocol. OConn itself is built around open standards such as OAuth and [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Open Connections (OConn) is a way of connecting profiles in an open and secure fashion. The goals of the project are to develop a REST protocol that will be submitted to a standards body and to develop an open source implementation of that protocol. OConn itself is built around open standards such as <a title="OAuth" href="http://oauth.net/">OAuth</a> and <a title="OpenID" href="http://openid.net">OpenID</a>.</p>
<p>The evolution of social networks during the last decade has followed that of content in the 1990s. Service providers such as America Online™, CompuServe™, and Prodigy™ built online communities around content and attempted to keep their communities inside so-called <em>walled gardens</em>. The big social networks of the past decade have followed the same path.</p>
<p>Initially, the walled garden has a strong appeal. Rich content and new features keep people coming back. Over time, the enthusiasm fades and people begin to notice cracks in the masonry.</p>
<p>Some problems with the current social networks are data privacy and the related sharing or selling of profile data to 3rd parties. These problems stem from a root cause: all your data belongs to a single company. We have a situation today in which nearly 6% of the world&#8217;s population keep their private profile information stored with <a href="http://www.facebook.com/">one corporation</a>. A corporation with a poor track record of being entrusted with it.</p>
<p>In the same way that HTTP and HTML allowed people to connect their pages together with hyperlinks, OConn will allow people to connect their profiles by relationships. The Web&#8217;s basic protocol and data format allowed an infinite variety of content, applications, and services to be developed. In the same way OConn will provide a solid and secure foundation for a new class of content and services.</p>
<p>It is time for people to take control of their own profiles and data. It&#8217;s time to move beyond the walled gardens.</p>
]]></content:encoded>
			<wfw:commentRss>http://openconnections.net/blog/2010/05/open-connections-introduction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

