<?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: Protected Updates on Twitter are not so Protected</title>
	<atom:link href="http://threefourteendesign.com/blog/2009/05/protected-updates-on-twitter-are-not-so-protected/feed/" rel="self" type="application/rss+xml" />
	<link>http://threefourteendesign.com/blog/2009/05/protected-updates-on-twitter-are-not-so-protected/</link>
	<description></description>
	<lastBuildDate>Thu, 13 Oct 2011 07:06:33 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: freriepails</title>
		<link>http://threefourteendesign.com/blog/2009/05/protected-updates-on-twitter-are-not-so-protected/comment-page-1/#comment-290</link>
		<dc:creator>freriepails</dc:creator>
		<pubDate>Fri, 11 Dec 2009 23:46:17 +0000</pubDate>
		<guid isPermaLink="false">http://threefourteendesign.com/blog/uncategorized/protected-updates-on-twitter-are-not-so-protected/#comment-290</guid>
		<description>Various of folks talk about this subject but you wrote down really true words!</description>
		<content:encoded><![CDATA[<p>Various of folks talk about this subject but you wrote down really true words!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://threefourteendesign.com/blog/2009/05/protected-updates-on-twitter-are-not-so-protected/comment-page-1/#comment-175</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 13 May 2009 17:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://threefourteendesign.com/blog/uncategorized/protected-updates-on-twitter-are-not-so-protected/#comment-175</guid>
		<description>I&#039;d wager that this is related to users who have recently protected their updates and google has a pre-protection copy in its cache.</description>
		<content:encoded><![CDATA[<p>I&#8217;d wager that this is related to users who have recently protected their updates and google has a pre-protection copy in its cache.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

