<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>James Slater &#187; Social Media</title>
	<atom:link href="http://james.slaterspage.com/category/social-media/feed/" rel="self" type="application/rss+xml" />
	<link>http://james.slaterspage.com</link>
	<description>If that&#039;s what you were looking for, you&#039;ve found it.</description>
	<lastBuildDate>Wed, 24 Aug 2011 13:06:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Twitter Exploit Still Not Fixed</title>
		<link>http://james.slaterspage.com/twitter-exploit-still-not-fixed/</link>
		<comments>http://james.slaterspage.com/twitter-exploit-still-not-fixed/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 12:15:58 +0000</pubDate>
		<dc:creator>James</dc:creator>
				<category><![CDATA[Social Media]]></category>

		<guid isPermaLink="false">http://james.slaterspage.com/?p=33</guid>
		<description><![CDATA[<a href="http://james.slaterspage.com/twitter-exploit-still-not-fixed/" title="Twitter Exploit Still Not Fixed"></a>Sigh. I wrote another article on Dave Naylor&#8217;s blog about the XSS exploit I found yesterday. It seems they&#8217;ve made a pretty amateurish attempt to fix the issue, completely missing the massive problem staring them in the face. It seems &#8230;<p class="read-more"><a href="http://james.slaterspage.com/twitter-exploit-still-not-fixed/">Read more &#187;</a></p>]]></description>
		<wfw:commentRss>http://james.slaterspage.com/twitter-exploit-still-not-fixed/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Taking down Twitter</title>
		<link>http://james.slaterspage.com/taking-down-twitter/</link>
		<comments>http://james.slaterspage.com/taking-down-twitter/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 16:51:35 +0000</pubDate>
		<dc:creator>James</dc:creator>
				<category><![CDATA[Social Media]]></category>

		<guid isPermaLink="false">http://james.slaterspage.com/?p=25</guid>
		<description><![CDATA[<a href="http://james.slaterspage.com/taking-down-twitter/" title="Taking down Twitter"></a>I had the opportunity (probably) to take down Twitter today. Or at least stir up a whole lot of trouble. I really can&#8217;t believe I&#8217;m the first person to think of it, but I&#8217;m pretty sure it would have worked! &#8230;<p class="read-more"><a href="http://james.slaterspage.com/taking-down-twitter/">Read more &#187;</a></p>]]></description>
		<wfw:commentRss>http://james.slaterspage.com/taking-down-twitter/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc (Feed is rejected)
Page Caching using apc (User agent is rejected)
Database Caching 1/14 queries in 0.006 seconds using apc
Object Caching 382/399 objects using apc

Served from: james.slaterspage.com @ 2012-02-05 21:35:19 -->
