<?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 &#187; Twitter Status</title>
	<atom:link href="http://socialsnipe.com/category/twitter-status/feed/" rel="self" type="application/rss+xml" />
	<link>http://socialsnipe.com</link>
	<description>Leveraging the Potential of Social Marketing</description>
	<lastBuildDate>Sat, 04 Sep 2010 00:45:01 +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>Working on stale search results</title>
		<link>http://socialsnipe.com/working-on-stale-search-results/</link>
		<comments>http://socialsnipe.com/working-on-stale-search-results/#comments</comments>
		<pubDate>Sat, 04 Sep 2010 00:45:01 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/working-on-stale-search-results/</guid>
		<description><![CDATA[ Results from tweet search are delayed several hours and we are working on the underlying problem. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Results from tweet search are delayed several hours and we are working on the underlying problem.</p>
</p>
<p>The rest is here:
<p />
<a target="_blank" href="http://status.twitter.com/post/1060850803" title="Working on stale search results">Working on stale search results</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/working-on-stale-search-results/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Investigating invalid responses from the API</title>
		<link>http://socialsnipe.com/investigating-invalid-responses-from-the-api/</link>
		<comments>http://socialsnipe.com/investigating-invalid-responses-from-the-api/#comments</comments>
		<pubDate>Fri, 03 Sep 2010 17:10:29 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/investigating-invalid-responses-from-the-api/</guid>
		<description><![CDATA[ We are investigating reports of users receiving invalid responses from the API ]]></description>
			<content:encoded><![CDATA[<p>
<p>We are investigating reports of users receiving invalid responses from the API</p>
</p>
<p>Visit link:<br />
<a target="_blank" href="http://status.twitter.com/post/1058895068" title="Investigating invalid responses from the API">Investigating invalid responses from the API</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/investigating-invalid-responses-from-the-api/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Log-in issues for users of some mobile clients</title>
		<link>http://socialsnipe.com/log-in-issues-for-users-of-some-mobile-clients/</link>
		<comments>http://socialsnipe.com/log-in-issues-for-users-of-some-mobile-clients/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 23:12:48 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/log-in-issues-for-users-of-some-mobile-clients/</guid>
		<description><![CDATA[ Users using certain Twitter clients are unable to Log in. These clients include - HTC Peep - Moto BLUR - Nokia Twitter apps - Samsung devices (except for phones running Android OS) - Huawei phones  We are working to resolve this issue. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Users using certain Twitter clients are unable to Log in.</p>
<p>These clients include</p>
<p>- HTC Peep</p>
<p>- Moto BLUR</p>
<p>- Nokia Twitter apps</p>
<p>- Samsung devices (except for phones running Android OS)</p>
<p>- Huawei phones </p>
<p>We are working to resolve this issue.</p>
</p>
<p>Follow this link:
<p />
<a target="_blank" href="http://status.twitter.com/post/1050106371" title="Log-in issues for users of some mobile clients">Log-in issues for users of some mobile clients</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/log-in-issues-for-users-of-some-mobile-clients/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Potential Errors Due to Maintenance</title>
		<link>http://socialsnipe.com/potential-errors-due-to-maintenance/</link>
		<comments>http://socialsnipe.com/potential-errors-due-to-maintenance/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 04:13:13 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/potential-errors-due-to-maintenance/</guid>
		<description><![CDATA[ We are performing some scheduled maintenance on the site; you may experience periods of elevated errors. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We are performing some scheduled maintenance on the site; you may experience periods of elevated errors.</p>
</p>
<p>See original here:
<p />
<a target="_blank" href="http://status.twitter.com/post/1045402781" title="Potential Errors Due to Maintenance">Potential Errors Due to Maintenance</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/potential-errors-due-to-maintenance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Temporarily Disabling &quot;Who to Follow&quot;</title>
		<link>http://socialsnipe.com/temporarily-disabling-who-to-follow/</link>
		<comments>http://socialsnipe.com/temporarily-disabling-who-to-follow/#comments</comments>
		<pubDate>Tue, 31 Aug 2010 22:01:52 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/temporarily-disabling-who-to-follow/</guid>
		<description><![CDATA[ We’ve temporarily turned off the “Who To Follow” feature and will be restoring it as soon as possible. We were including people you already follow - we are investigating this issue. Update at 2:15PM : This issue has been resolved. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We’ve temporarily turned off the “Who To Follow” feature and will be restoring it as soon as possible. We were including people you already follow &#8211; we are investigating this issue.</p>
<p><span><strong>Update at 2:15PM</strong>: This issue has been resolved.</span></p>
</p>
<p>Continue reading here:<br />
<a target="_blank" href="http://status.twitter.com/post/1043244719" title="Temporarily Disabling &quot;Who to Follow&quot;">Temporarily Disabling &quot;Who to Follow&quot;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/temporarily-disabling-who-to-follow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A known API issue is causing some clients to crash</title>
		<link>http://socialsnipe.com/a-known-api-issue-is-causing-some-clients-to-crash/</link>
		<comments>http://socialsnipe.com/a-known-api-issue-is-causing-some-clients-to-crash/#comments</comments>
		<pubDate>Tue, 24 Aug 2010 21:01:33 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/a-known-api-issue-is-causing-some-clients-to-crash/</guid>
		<description><![CDATA[ There is an issue with the API that is causing some clients to crash. ]]></description>
			<content:encoded><![CDATA[<p>
<p>There is an issue with the API that is causing some clients to crash. A fix is being deployed now</p>
</p>
<p>See the original post:
<p />
<a target="_blank" href="http://status.twitter.com/post/1004400550" title="A known API issue is causing some clients to crash">A known API issue is causing some clients to crash</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/a-known-api-issue-is-causing-some-clients-to-crash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mentions Timeline Frozen (@ replies)</title>
		<link>http://socialsnipe.com/mentions-timeline-frozen-replies/</link>
		<comments>http://socialsnipe.com/mentions-timeline-frozen-replies/#comments</comments>
		<pubDate>Sat, 21 Aug 2010 02:34:27 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/mentions-timeline-frozen-replies/</guid>
		<description><![CDATA[ The mentions timeline is frozen; engineers are working on the issue now. Update: this issue has been resolved. ]]></description>
			<content:encoded><![CDATA[<p>
<p>The mentions timeline is frozen; engineers are working on the issue now. </p>
<p>Update: this issue has been resolved.</p>
</p>
<p>Link:<br />
<a target="_blank" href="http://status.twitter.com/post/984754570" title="Mentions Timeline Frozen (@ replies)">Mentions Timeline Frozen (@ replies)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/mentions-timeline-frozen-replies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Follow, Follower Counts and DMs Intermittently inaccessible</title>
		<link>http://socialsnipe.com/follow-follower-counts-and-dms-intermittently-inaccessible/</link>
		<comments>http://socialsnipe.com/follow-follower-counts-and-dms-intermittently-inaccessible/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 19:36:14 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/follow-follower-counts-and-dms-intermittently-inaccessible/</guid>
		<description><![CDATA[ Some features are intermittently not available on Twitter at this time.  - Ability to Follow a user - Follow counts - Sending DMs Twitter is working to resolve this issue in full. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Some features are intermittently not available on Twitter at this time. </p>
<p>- Ability to Follow a user</p>
<p>- Follow counts</p>
<p>- Sending DMs</p>
<p>Twitter is working to resolve this issue in full.</p>
</p>
<p>Read the rest here:
<p />
<a target="_blank" href="http://status.twitter.com/post/978071082" title="Follow, Follower Counts and DMs Intermittently inaccessible">Follow, Follower Counts and DMs Intermittently inaccessible</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/follow-follower-counts-and-dms-intermittently-inaccessible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lists and Tweet Counts are Currently Disabled</title>
		<link>http://socialsnipe.com/lists-and-tweet-counts-are-currently-disabled/</link>
		<comments>http://socialsnipe.com/lists-and-tweet-counts-are-currently-disabled/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 09:14:23 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/lists-and-tweet-counts-are-currently-disabled/</guid>
		<description><![CDATA[ Lists and Tweet counts on the home page are currently disabled; we’re working toward restoring them. You can still see your total number of Tweets on your profile page. UPDATE : Lists and Tweet counts on homepage is estimated to be restored by 6AM PDT. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Lists and Tweet counts on the home page are currently disabled; we’re working toward restoring them. You can still see your total number of Tweets on your profile page.</p>
<p><strong>UPDATE</strong>: Lists and Tweet counts on homepage is estimated to be restored by 6AM PDT.</p>
</p>
<p>Continue reading here:<br />
<a target="_blank" href="http://status.twitter.com/post/976182075" title="Lists and Tweet Counts are Currently Disabled">Lists and Tweet Counts are Currently Disabled</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/lists-and-tweet-counts-are-currently-disabled/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>We&#8217;re currently experiencing a high error rate on Twitter.</title>
		<link>http://socialsnipe.com/were-currently-experiencing-a-high-error-rate-on-twitter/</link>
		<comments>http://socialsnipe.com/were-currently-experiencing-a-high-error-rate-on-twitter/#comments</comments>
		<pubDate>Fri, 06 Aug 2010 01:39:42 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/were-currently-experiencing-a-high-error-rate-on-twitter/</guid>
		<description><![CDATA[ We’re currently experiencing a high error rate on Twitter. Our infrastructure and operations engineers are responding to the incident. Update:  Thu Aug  5 22:39:04 UTC 2010: Twitter is currently recovering, Tweets are are flowing again. We expect a full recovery in the next hour]]></description>
			<content:encoded><![CDATA[<p>
<p>We’re currently experiencing a high error rate on Twitter. Our infrastructure and operations engineers are responding to the incident.</p>
<p><strong>Update:  Thu Aug  5 22:39:04 UTC 2010:</strong> Twitter is currently recovering, Tweets are are flowing again. We expect a full recovery in the next hour.</p>
<p><strong>Update: Thu Aug  5 23:46:11 UTC 2010</strong>: Twitter is fully recovered.</p>
</p>
<p>Link:
<p />
<a target="_blank" href="http://status.twitter.com/post/909630059" title="We're currently experiencing a high error rate on Twitter.">We&#8217;re currently experiencing a high error rate on Twitter.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/were-currently-experiencing-a-high-error-rate-on-twitter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
