<?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: Fixing security issues for Twitter</title>
	<atom:link href="http://blog.nullvariable.com/2009/11/fixing-security-issues-for-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nullvariable.com/2009/11/fixing-security-issues-for-twitter/#utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=fixing-security-issues-for-twitter</link>
	<description>The musings of the Nullvariable Web Consulting Team.</description>
	<lastBuildDate>Thu, 04 Mar 2010 02:42:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: nullvariable</title>
		<link>http://blog.nullvariable.com/2009/11/fixing-security-issues-for-twitter/comment-page-1/#comment-368</link>
		<dc:creator>nullvariable</dc:creator>
		<pubDate>Sun, 08 Nov 2009 09:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nullvariable.com/?p=517#comment-368</guid>
		<description>I&#039;d agree but the horsepower to check links would have to be pretty high. I suppose that they could use a service like Google and FireFox are using and check the URLs against that but it seems like it takes too long for a site to get picked up by those filters. I don&#039;t know what the solution is but seems like both Facebook and Twitter need to really get on the ball or they&#039;re going to start losing people.</description>
		<content:encoded><![CDATA[<p>I&#39;d agree but the horsepower to check links would have to be pretty high. I suppose that they could use a service like Google and FireFox are using and check the URLs against that but it seems like it takes too long for a site to get picked up by those filters. I don&#39;t know what the solution is but seems like both Facebook and Twitter need to really get on the ball or they&#39;re going to start losing people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nullvariable</title>
		<link>http://blog.nullvariable.com/2009/11/fixing-security-issues-for-twitter/comment-page-1/#comment-357</link>
		<dc:creator>nullvariable</dc:creator>
		<pubDate>Sun, 08 Nov 2009 01:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nullvariable.com/?p=517#comment-357</guid>
		<description>I&#039;d agree but the horsepower to check links would have to be pretty high. I suppose that they could use a service like Google and FireFox are using and check the URLs against that but it seems like it takes too long for a site to get picked up by those filters. I don&#039;t know what the solution is but seems like both Facebook and Twitter need to really get on the ball or they&#039;re going to start losing people.</description>
		<content:encoded><![CDATA[<p>I&#39;d agree but the horsepower to check links would have to be pretty high. I suppose that they could use a service like Google and FireFox are using and check the URLs against that but it seems like it takes too long for a site to get picked up by those filters. I don&#39;t know what the solution is but seems like both Facebook and Twitter need to really get on the ball or they&#39;re going to start losing people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Dodd</title>
		<link>http://blog.nullvariable.com/2009/11/fixing-security-issues-for-twitter/comment-page-1/#comment-356</link>
		<dc:creator>Steve Dodd</dc:creator>
		<pubDate>Fri, 06 Nov 2009 20:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nullvariable.com/?p=517#comment-356</guid>
		<description>Doug, this is a great start and Twitter really does need to get this right, quickly.  But, in addition to password protection, it also needs to implement site validation so that every link that is submitted and shortened goes through a virus and phishing filter to stop anything from being distributed that can cause damage.  I know users should have this capability but so many just don&#039;t.</description>
		<content:encoded><![CDATA[<p>Doug, this is a great start and Twitter really does need to get this right, quickly.  But, in addition to password protection, it also needs to implement site validation so that every link that is submitted and shortened goes through a virus and phishing filter to stop anything from being distributed that can cause damage.  I know users should have this capability but so many just don&#39;t.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
