<?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: Flickr Services</title>
	<atom:link href="http://jeffnolan.com/wp/2006/05/01/flickr-services/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffnolan.com/wp/2006/05/01/flickr-services/</link>
	<description>Jeff Nolan&#039;s take on investment, innovation, entrepreneurship and the technology industry</description>
	<lastBuildDate>Mon, 06 Feb 2012 06:44:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brian Keairns</title>
		<link>http://jeffnolan.com/wp/2006/05/01/flickr-services/comment-page-1/#comment-1747</link>
		<dc:creator>Brian Keairns</dc:creator>
		<pubDate>Mon, 01 May 2006 17:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://jeffnolan.com/wp/2006/05/01/flickr-services/#comment-1747</guid>
		<description>Thanks for the excellent post. I think youâ€™ve focused in on a very important example. People often like to discuss innovation at the 30,000 foot level but in my experience something as seemingly small as getting user authentication right can make all the difference in whether a new innovation succeeds or not. And in reality doing user access well with a web based application is a BIG deal. One of the biggest issues my company deals with, even in simple implementations, in the Enterprise Wiki space is making it easy for the right people to get what they want and hard for the wrong people. If itâ€™s too hard you shut down participation. If itâ€™s not effective in providing security people wonâ€™t trust it. This becomes an even more important issue when (as in your Flickr example) we start to deal with integration with third party applications.</description>
		<content:encoded><![CDATA[<p>Thanks for the excellent post. I think youâ€™ve focused in on a very important example. People often like to discuss innovation at the 30,000 foot level but in my experience something as seemingly small as getting user authentication right can make all the difference in whether a new innovation succeeds or not. And in reality doing user access well with a web based application is a BIG deal. One of the biggest issues my company deals with, even in simple implementations, in the Enterprise Wiki space is making it easy for the right people to get what they want and hard for the wrong people. If itâ€™s too hard you shut down participation. If itâ€™s not effective in providing security people wonâ€™t trust it. This becomes an even more important issue when (as in your Flickr example) we start to deal with integration with third party applications.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

