<?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/"
		>
<channel>
	<title>Comments on: LinkedIn should launch LinkedIn Connect</title>
	<atom:link href="http://slowbrand.com/2010/05/14/linkedin-should-launch-linkedin-connect/feed/" rel="self" type="application/rss+xml" />
	<link>http://slowbrand.com/2010/05/14/linkedin-should-launch-linkedin-connect/</link>
	<description>taking a slow approach to brands</description>
	<lastBuildDate>Thu, 15 Mar 2012 00:26:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Dave Bergschneider</title>
		<link>http://slowbrand.com/2010/05/14/linkedin-should-launch-linkedin-connect/comment-page-1/#comment-5651</link>
		<dc:creator>Dave Bergschneider</dc:creator>
		<pubDate>Sun, 13 Jun 2010 19:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://slowbrand.com/?p=115#comment-5651</guid>
		<description>In complete agreement with a LinkedIn identity sign-on however I prefer the twitter Oauth more forthan the facebook one. Reason being, is facebook application approval simply looks intimidating and as if the &quot;application&quot; will have full access even though it states public information. The whole wording of application is scary too because the end-user often things of applications as being like a browser toolbar or some other useless app on their computer they don&#039;t need or want. Same applies to facebook.</description>
		<content:encoded><![CDATA[<p>In complete agreement with a LinkedIn identity sign-on however I prefer the twitter Oauth more forthan the facebook one. Reason being, is facebook application approval simply looks intimidating and as if the &#8220;application&#8221; will have full access even though it states public information. The whole wording of application is scary too because the end-user often things of applications as being like a browser toolbar or some other useless app on their computer they don&#8217;t need or want. Same applies to facebook.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shannon Clark</title>
		<link>http://slowbrand.com/2010/05/14/linkedin-should-launch-linkedin-connect/comment-page-1/#comment-4836</link>
		<dc:creator>Shannon Clark</dc:creator>
		<pubDate>Sat, 15 May 2010 05:58:17 +0000</pubDate>
		<guid isPermaLink="false">http://slowbrand.com/?p=115#comment-4836</guid>
		<description>Chris,

My thought is that LinkedIn should launch this as an identity service &amp; by default and in most cases only share what is already PUBLIC on LinkedIn when LinkedIn would be used as an Oauth authentication. 

But I would also really like LinkedIn to then also look at offering, with the user&#039;s consent, to allow some services deeper integration &amp; data access. This could, for example, enable real serious syncing across social networks &amp; devices - allowing me to have my LinkedIn contacts (what they share with me already) synced to my mobile phone &amp; into whatever CRM system I might choose to use (which could be Salesforce, could be another SaaS service, could be an iPhone/iPad application or an Android app)

The point is that I think Facebook isn&#039;t the only game in town - or doesn&#039;t have to be and that LinkedIn is a more natural fit - but they would have to act quickly as they have very few developer relationships (and have soured many via past slowness to work with outside developers). At the moment Facebook is adding literally over 100,000 and counting sites external to Facebook who are integrating with Facebook via a wide range of facebook widgets (Like buttons, authentication and more). Twitter has a a number of sites and applications that use Twitter authentication but mostly directly for Twitter related purposes (less often to find folks who follow you/whom you follow on Twitter on some new service) and Yahoo &amp; Google who both have very solid OpenID services have somewhat diminished momentum at the moment (and there are dozens of other options).  Plus &quot;Oauth&quot; and &quot;OpenID&quot; while related aren&#039;t precisely the same thing. 

Anyway as I said, it was a fairly simple thought this afternoon - if I get a chance to talk with folks at LinkedIn sometime I&#039;ll ask them about it...</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>My thought is that LinkedIn should launch this as an identity service &amp; by default and in most cases only share what is already PUBLIC on LinkedIn when LinkedIn would be used as an Oauth authentication. </p>
<p>But I would also really like LinkedIn to then also look at offering, with the user&#8217;s consent, to allow some services deeper integration &amp; data access. This could, for example, enable real serious syncing across social networks &amp; devices &#8211; allowing me to have my LinkedIn contacts (what they share with me already) synced to my mobile phone &amp; into whatever CRM system I might choose to use (which could be Salesforce, could be another SaaS service, could be an iPhone/iPad application or an Android app)</p>
<p>The point is that I think Facebook isn&#8217;t the only game in town &#8211; or doesn&#8217;t have to be and that LinkedIn is a more natural fit &#8211; but they would have to act quickly as they have very few developer relationships (and have soured many via past slowness to work with outside developers). At the moment Facebook is adding literally over 100,000 and counting sites external to Facebook who are integrating with Facebook via a wide range of facebook widgets (Like buttons, authentication and more). Twitter has a a number of sites and applications that use Twitter authentication but mostly directly for Twitter related purposes (less often to find folks who follow you/whom you follow on Twitter on some new service) and Yahoo &amp; Google who both have very solid OpenID services have somewhat diminished momentum at the moment (and there are dozens of other options).  Plus &#8220;Oauth&#8221; and &#8220;OpenID&#8221; while related aren&#8217;t precisely the same thing. </p>
<p>Anyway as I said, it was a fairly simple thought this afternoon &#8211; if I get a chance to talk with folks at LinkedIn sometime I&#8217;ll ask them about it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher S. Rollyson</title>
		<link>http://slowbrand.com/2010/05/14/linkedin-should-launch-linkedin-connect/comment-page-1/#comment-4834</link>
		<dc:creator>Christopher S. Rollyson</dc:creator>
		<pubDate>Sat, 15 May 2010 02:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://slowbrand.com/?p=115#comment-4834</guid>
		<description>Shannon, intriguing idea, and a totally natural one. I&#039;ll qualify my remarks by saying that I work with very conservative enterprise execs, not startup leaders so much. The former are pretty uncomfortable with perceived loss of privacy or control, and they usually don&#039;t understand the nuances of single sign-on, inheritance, etc. LinkedIn is struggling to get them to have more value-added interaction ON the site, so it would IMO be a potential distraction to enable off-site interaction. That said, I could see them enabling a quasi-private network of trusted partners, but it would have to smell *very* different than, say, Facebook Connect or Google FriendConnect. I&#039;d be surprised if it weren&#039;t in the pipeline somewhere.</description>
		<content:encoded><![CDATA[<p>Shannon, intriguing idea, and a totally natural one. I&#8217;ll qualify my remarks by saying that I work with very conservative enterprise execs, not startup leaders so much. The former are pretty uncomfortable with perceived loss of privacy or control, and they usually don&#8217;t understand the nuances of single sign-on, inheritance, etc. LinkedIn is struggling to get them to have more value-added interaction ON the site, so it would IMO be a potential distraction to enable off-site interaction. That said, I could see them enabling a quasi-private network of trusted partners, but it would have to smell *very* different than, say, Facebook Connect or Google FriendConnect. I&#8217;d be surprised if it weren&#8217;t in the pipeline somewhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

