<?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: Recommended: Jeremy Keith&#8217;s &#8220;Lock up your data&#8221;</title>
	<atom:link href="http://tiffanybbrown.com/2007/10/05/recommended-jeremy-keiths-lock-up-your-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://tiffanybbrown.com/2007/10/05/recommended-jeremy-keiths-lock-up-your-data/</link>
	<description>A web log about web development and internet culture with frequent detours into other stuff.</description>
	<lastBuildDate>Sun, 14 Mar 2010 19:03:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Can an API Steal Data?</title>
		<link>http://tiffanybbrown.com/2007/10/05/recommended-jeremy-keiths-lock-up-your-data/comment-page-1/#comment-87387</link>
		<dc:creator>Can an API Steal Data?</dc:creator>
		<pubDate>Tue, 09 Oct 2007 04:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://tiffanybbrown.com/2007/10/05/recommended-jeremy-keiths-lock-up-your-data/#comment-87387</guid>
		<description>[...] Flickr has a good track record of supporting both their developers and their passionate community. They&#8217;re paying attention to this issue. Flickr&#8217;s Paul Hammond noted that &#8220;There&#8217;s a healthy debate going on at Flickr HQ as to what our response should be&#8230;Our hands are also tied slightly by the huge number of applications that rely on the existing behaviour of the API. If we make changes too quickly, we&#8217;d break a lot of things (like, say, fd&#8217;s flickr toys) that a lot of flickr users love&#8230;We&#8217;re interested in hearing everyone&#8217;s point of view.&#8221; [via] [...]</description>
		<content:encoded><![CDATA[<p>[...] Flickr has a good track record of supporting both their developers and their passionate community. They&#8217;re paying attention to this issue. Flickr&#8217;s Paul Hammond noted that &#8220;There&#8217;s a healthy debate going on at Flickr HQ as to what our response should be&#8230;Our hands are also tied slightly by the huge number of applications that rely on the existing behaviour of the API. If we make changes too quickly, we&#8217;d break a lot of things (like, say, fd&#8217;s flickr toys) that a lot of flickr users love&#8230;We&#8217;re interested in hearing everyone&#8217;s point of view.&#8221; [via] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason W.</title>
		<link>http://tiffanybbrown.com/2007/10/05/recommended-jeremy-keiths-lock-up-your-data/comment-page-1/#comment-87282</link>
		<dc:creator>Jason W.</dc:creator>
		<pubDate>Sat, 06 Oct 2007 10:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://tiffanybbrown.com/2007/10/05/recommended-jeremy-keiths-lock-up-your-data/#comment-87282</guid>
		<description>You know I wasn&#039;t paying attention to this post, but then I started paying a lot of attention to this post.  What&#039;s always gotten me about the whole &quot;don&#039;t mess with my flickr image&quot; argument is the whole tin-foil hat attitude ... as that Pisco Bandito person said the only true way to protect your image is to mark it as private or not post it at all.  Anything that can be viewed online can be stolen, API&#039;s be damned.

Unless everyone wants to start watermarking their images, I suppose.  Still could be taken, obviously.

People get very snippy over their cat pictures.</description>
		<content:encoded><![CDATA[<p>You know I wasn&#8217;t paying attention to this post, but then I started paying a lot of attention to this post.  What&#8217;s always gotten me about the whole &#8220;don&#8217;t mess with my flickr image&#8221; argument is the whole tin-foil hat attitude &#8230; as that Pisco Bandito person said the only true way to protect your image is to mark it as private or not post it at all.  Anything that can be viewed online can be stolen, API&#8217;s be damned.</p>
<p>Unless everyone wants to start watermarking their images, I suppose.  Still could be taken, obviously.</p>
<p>People get very snippy over their cat pictures.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
