<?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>Social Snipe</title>
	<atom:link href="http://socialsnipe.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://socialsnipe.com</link>
	<description>Leveraging the Potential of Social Marketing</description>
	<lastBuildDate>Tue, 27 Jul 2010 20:46:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>SSL Certificate Errors</title>
		<link>http://socialsnipe.com/ssl-certificate-errors/</link>
		<comments>http://socialsnipe.com/ssl-certificate-errors/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 20:46:08 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/ssl-certificate-errors/</guid>
		<description><![CDATA[ We’re looking into expired SSL certificate errors now and working quickly to resolve it. The problem affects a small portion of TweetDeck API requests. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We’re looking into expired SSL certificate errors now and working quickly to resolve it. The problem affects a small portion of TweetDeck API requests.</p>
</p>
<p>See more here:<br />
<a target="_blank" href="http://status.twitter.com/post/867427356" title="SSL Certificate Errors">SSL Certificate Errors</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/ssl-certificate-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Avatar Upload Temporarily Disabled</title>
		<link>http://socialsnipe.com/avatar-upload-temporarily-disabled/</link>
		<comments>http://socialsnipe.com/avatar-upload-temporarily-disabled/#comments</comments>
		<pubDate>Mon, 26 Jul 2010 03:05:04 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/avatar-upload-temporarily-disabled/</guid>
		<description><![CDATA[ We’ve temporarily disabled avatar upload as we do some work; we’ll update again when it’s reenabled. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We’ve temporarily disabled avatar upload as we do some work; we’ll update again when it’s reenabled.</p>
<p><strong>Update (18:10 PST, 01:10 UTC)</strong>: Avatar uploading is reenabled.</p>
</p>
<p>Read more from the original source:<br />
<a target="_blank" href="http://status.twitter.com/post/858808188" title="Avatar Upload Temporarily Disabled">Avatar Upload Temporarily Disabled</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/avatar-upload-temporarily-disabled/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twitter Help Center Temporarily Down</title>
		<link>http://socialsnipe.com/twitter-help-center-temporarily-down/</link>
		<comments>http://socialsnipe.com/twitter-help-center-temporarily-down/#comments</comments>
		<pubDate>Mon, 19 Jul 2010 22:28:47 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/twitter-help-center-temporarily-down/</guid>
		<description><![CDATA[ In a related issue (that is also being worked on), our help center is currently down; we’re working to bring it back up. ]]></description>
			<content:encoded><![CDATA[<p>
<p>In a related issue (that is also being worked on), our help center is currently down; we’re working to bring it back up.</p>
</p>
<p>See the rest here:<br />
<a target="_blank" href="http://status.twitter.com/post/833075034" title="Twitter Help Center Temporarily Down">Twitter Help Center Temporarily Down</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/twitter-help-center-temporarily-down/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Users Cannot Update Profiles</title>
		<link>http://socialsnipe.com/users-cannot-update-profiles/</link>
		<comments>http://socialsnipe.com/users-cannot-update-profiles/#comments</comments>
		<pubDate>Mon, 19 Jul 2010 17:30:27 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/users-cannot-update-profiles/</guid>
		<description><![CDATA[ We’re currently working on remedying the issue blocking users from updating their profiles. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We’re currently working on remedying the issue blocking users from updating their profiles.</p>
</p>
<p>Here is the original post:
<p />
<a target="_blank" href="http://status.twitter.com/post/832539693" title="Users Cannot Update Profiles">Users Cannot Update Profiles</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/users-cannot-update-profiles/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Had trouble following people?</title>
		<link>http://socialsnipe.com/had-trouble-following-people/</link>
		<comments>http://socialsnipe.com/had-trouble-following-people/#comments</comments>
		<pubDate>Mon, 19 Jul 2010 03:34:44 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/had-trouble-following-people/</guid>
		<description><![CDATA[ It’s a  known issue that is now resolved. All followings and unfollowings are now real-time and up to date]]></description>
			<content:encoded><![CDATA[<p>
<p><span><span> It’s a  known issue that is now resolved. All followings and unfollowings are now real-time and up to date.<br/></span></span></p>
</p>
<p>Read more:
<p />
<a target="_blank" href="http://status.twitter.com/post/830058364" title="Had trouble following people?">Had trouble following people?</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/had-trouble-following-people/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SSL Issue</title>
		<link>http://socialsnipe.com/ssl-issue/</link>
		<comments>http://socialsnipe.com/ssl-issue/#comments</comments>
		<pubDate>Wed, 14 Jul 2010 02:01:03 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/ssl-issue/</guid>
		<description><![CDATA[ We are aware of an SSL issue on our API and are in the process of fixing it. This issue does not pose a threat to account security. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We are aware of an SSL issue on our API and are in the process of fixing it. This issue does not pose a threat to account security.</p>
</p>
<p>Here is the original post:
<p />
<a target="_blank" href="http://status.twitter.com/post/808469968" title="SSL Issue">SSL Issue</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/ssl-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Investigating &quot;Rate Limit Exceeded&quot; issues</title>
		<link>http://socialsnipe.com/investigating-rate-limit-exceeded-issues/</link>
		<comments>http://socialsnipe.com/investigating-rate-limit-exceeded-issues/#comments</comments>
		<pubDate>Wed, 07 Jul 2010 18:32:11 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/investigating-rate-limit-exceeded-issues/</guid>
		<description><![CDATA[ Many users are receiving incorrect “Rate Limit Exceeded” errors through the Twitter API. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Many users are receiving incorrect “Rate Limit Exceeded” errors through the Twitter API. We are investigating the cause and will update when it is resolved.</p>
</p>
<p>Read this article:
<p />
<a target="_blank" href="http://status.twitter.com/post/781763549" title="Investigating &quot;Rate Limit Exceeded&quot; issues">Investigating &quot;Rate Limit Exceeded&quot; issues</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/investigating-rate-limit-exceeded-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Incorrect Rate-Limiting</title>
		<link>http://socialsnipe.com/incorrect-rate-limiting/</link>
		<comments>http://socialsnipe.com/incorrect-rate-limiting/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 16:24:09 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/incorrect-rate-limiting/</guid>
		<description><![CDATA[ We’re hearing reports from developers that they’re running into some incorrect rate limits; we’re looking into it. ]]></description>
			<content:encoded><![CDATA[<p>
<p><span><span><span>We’re hearing reports from developers that they’re running into some incorrect rate limits; we’re looking into it.</span></span></span></p>
</p>
<p>Go here to read the rest:<br />
<a target="_blank" href="http://status.twitter.com/post/777268689" title="Incorrect Rate-Limiting">Incorrect Rate-Limiting</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/incorrect-rate-limiting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mobile Website</title>
		<link>http://socialsnipe.com/mobile-website/</link>
		<comments>http://socialsnipe.com/mobile-website/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 18:27:14 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/mobile-website/</guid>
		<description><![CDATA[ We’re working to resolve an issue with the mobile website, http://mobile.twitter.com . UPDATE: Resolved at 15:31 UTC / 8:31 PDT. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We’re working to resolve an issue with the mobile website, <a href="http://mobile.twitter.com">http://mobile.twitter.com</a>.</p>
<p>UPDATE: Resolved at 15:31 UTC / 8:31 PDT.</p>
</p>
<p>Go here to read the rest:
<p />
<a target="_blank" href="http://status.twitter.com/post/773077785" title="Mobile Website">Mobile Website</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/mobile-website/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Missing @ Replies</title>
		<link>http://socialsnipe.com/missing-replies/</link>
		<comments>http://socialsnipe.com/missing-replies/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 18:27:13 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/missing-replies/</guid>
		<description><![CDATA[ Some users are experiencing an issue in which they’re not receiving all of their @ replies; we’re working on a fix. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Some users are experiencing an issue in which they’re not receiving all of their @ replies; we’re working on a fix.</p>
</p>
<p>Visit link:
<p />
<a target="_blank" href="http://status.twitter.com/post/773257081" title="Missing @ Replies">Missing @ Replies</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/missing-replies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
