<?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>Fri, 05 Mar 2010 22:46:33 +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>Some users experiencing misdirected Tweets</title>
		<link>http://socialsnipe.com/some-users-experiencing-misdirected-tweets/</link>
		<comments>http://socialsnipe.com/some-users-experiencing-misdirected-tweets/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 22:46:33 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/some-users-experiencing-misdirected-tweets/</guid>
		<description><![CDATA[ We’ve received reports of users seeing Tweets from people they are not following in their timelines; we’ve isolated the issue and remedied it. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We’ve received reports of users seeing Tweets from people they are not following in their timelines; we’ve isolated the issue and remedied it.</p>
</p>
<p>Originally posted here:
<p />
<a target="_blank" href="http://status.twitter.com/post/428781525" title="Some users experiencing misdirected Tweets">Some users experiencing misdirected Tweets</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/some-users-experiencing-misdirected-tweets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>@Replies In Timeline</title>
		<link>http://socialsnipe.com/replies-in-timeline/</link>
		<comments>http://socialsnipe.com/replies-in-timeline/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 02:56:33 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/replies-in-timeline/</guid>
		<description><![CDATA[ Some users reported seeing @replies in their home timeline from folks they were not following; we’ve remedied the issue going forward. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Some users reported seeing @replies in their home timeline from folks they were not following; we’ve remedied the issue going forward.</p>
</p>
<p>View original post here:<br />
<a target="_blank" href="http://status.twitter.com/post/427175695" title="@Replies In Timeline">@Replies In Timeline</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/replies-in-timeline/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reports of Missing Tweets</title>
		<link>http://socialsnipe.com/reports-of-missing-tweets/</link>
		<comments>http://socialsnipe.com/reports-of-missing-tweets/#comments</comments>
		<pubDate>Mon, 01 Mar 2010 10:11:05 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/reports-of-missing-tweets/</guid>
		<description><![CDATA[ We’re currently hearing from users who’re missing updates on their timelines; we’re looking into the situation and working to fix it. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We’re currently hearing from users who’re missing updates on their timelines; we’re looking into the situation and working to fix it.</p>
</p>
<p>More:
<p />
<a target="_blank" href="http://status.twitter.com/post/419501875" title="Reports of Missing Tweets">Reports of Missing Tweets</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/reports-of-missing-tweets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some user&#8217;s timelines frozen</title>
		<link>http://socialsnipe.com/some-users-timelines-frozen/</link>
		<comments>http://socialsnipe.com/some-users-timelines-frozen/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 22:56:33 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/some-users-timelines-frozen/</guid>
		<description><![CDATA[ Some users are experiencing no new updates to their timeline. We are aware of the issue and investigating. Update (2/28 1:00p): We have pinpointed and resolved the issue]]></description>
			<content:encoded><![CDATA[<p>
<p>Some users are experiencing no new updates to their timeline. We are aware of the issue and investigating.</p>
<p><b>Update</b> (2/28 1:00p): We have pinpointed and resolved the issue.</p>
</p>
<p>Follow this link:
<p />
<a target="_blank" href="http://status.twitter.com/post/418019220" title="Some user's timelines frozen">Some user&#8217;s timelines frozen</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/some-users-timelines-frozen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Update Re: Phishing</title>
		<link>http://socialsnipe.com/update-re-phishing/</link>
		<comments>http://socialsnipe.com/update-re-phishing/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 23:13:20 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/update-re-phishing/</guid>
		<description><![CDATA[ Over the past few days, we’ve seen an increase in phishing attempts and are working on resetting passwords for accounts that were affected. While we’ve updated about these attacks via both @safety and @spam, we felt that it was important to post a more complete alert. ]]></description>
			<content:encoded><![CDATA[<p>
<p>Over the past few days, we’ve seen an increase in phishing attempts and are working on resetting passwords for accounts that were affected. While we’ve updated about these attacks via both @safety and @spam, we felt that it was important to post a more complete alert. If you receive a DM or see a message with a phrase like “This you??” or “LOL is this you” followed by a link, please do not click through; there’s a phishing site on the other side. While simply receiving this message does not mean your account is compromised, if you do click through and enter your username and password, you’ll want to change your password. If you’ve received this type of spam from a friend, you may want to alert them to change their password. You can read more information about keeping your account safe here: <a><a href="http://bit.ly/SecureMyAccount">http://bit.ly/SecureMyAccount</a></a>.</p>
</p>
<p>Read the rest here:
<p />
<a target="_blank" href="http://status.twitter.com/post/409689888" title="Update Re: Phishing">Update Re: Phishing</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/update-re-phishing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Name search is temporarily disabled</title>
		<link>http://socialsnipe.com/name-search-is-temporarily-disabled/</link>
		<comments>http://socialsnipe.com/name-search-is-temporarily-disabled/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 04:54:40 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/name-search-is-temporarily-disabled/</guid>
		<description><![CDATA[ We have disabled the name search feature. It will be a few days before it is re-enabled for all users. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We have disabled the name search feature. It will be a few days before it is re-enabled for all users.</p>
</p>
<p>More here:
<p />
<a target="_blank" href="http://status.twitter.com/post/408103192" title="Name search is temporarily disabled">Name search is temporarily disabled</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/name-search-is-temporarily-disabled/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Name search working as expected</title>
		<link>http://socialsnipe.com/name-search-working-as-expected/</link>
		<comments>http://socialsnipe.com/name-search-working-as-expected/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 07:56:34 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/name-search-working-as-expected/</guid>
		<description><![CDATA[ We re-enabled name search. Thanks for your patience! ]]></description>
			<content:encoded><![CDATA[<p>
<p>We re-enabled name search. Thanks for your patience!</p>
</p>
<p>More:<br />
<a target="_blank" href="http://status.twitter.com/post/394096188" title="Name search working as expected">Name search working as expected</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/name-search-working-as-expected/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Name search feature temporarily disabled</title>
		<link>http://socialsnipe.com/name-search-feature-temporarily-disabled/</link>
		<comments>http://socialsnipe.com/name-search-feature-temporarily-disabled/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 03:15:23 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/name-search-feature-temporarily-disabled/</guid>
		<description><![CDATA[ The name search feature is temporarily disabled. We’re working on getting it back online ASAP. ]]></description>
			<content:encoded><![CDATA[<p>
<p>The name search feature is temporarily disabled. We’re working on getting it back online ASAP.</p>
</p>
<p>Read more:<br />
<a target="_blank" href="http://status.twitter.com/post/393717130" title="Name search feature temporarily disabled">Name search feature temporarily disabled</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/name-search-feature-temporarily-disabled/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SMS connectivity issues on AT&amp;T</title>
		<link>http://socialsnipe.com/sms-connectivity-issues-on-att/</link>
		<comments>http://socialsnipe.com/sms-connectivity-issues-on-att/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 01:10:46 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/sms-connectivity-issues-on-att/</guid>
		<description><![CDATA[ We are currently investigating intermittent connectivity problems on the AT&#038;T network. ]]></description>
			<content:encoded><![CDATA[<p>
<p>We are currently investigating intermittent connectivity problems on the AT&#038;T network. Sending and receiving is affected.</p>
</p>
<p>Read more:
<p />
<a target="_blank" href="http://status.twitter.com/post/384493823" title="SMS connectivity issues on AT&#038;T">SMS connectivity issues on AT&#038;T</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/sms-connectivity-issues-on-att/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reason #4132 for Changing Your Password</title>
		<link>http://socialsnipe.com/reason-4132-for-changing-your-password/</link>
		<comments>http://socialsnipe.com/reason-4132-for-changing-your-password/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 01:31:33 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Twitter Status]]></category>

		<guid isPermaLink="false">http://socialsnipe.com/reason-4132-for-changing-your-password/</guid>
		<description><![CDATA[ As part of our ongoing efforts to monitor our user base for odd activity, we noticed a sudden surge in followers for a couple accounts in the last five days.  Given the circumstances surrounding this, we felt it was best to push out a password reset to  accounts that were following these suspicious users. Then we started doing some digging and, given what we found today, we felt it important to share this information.  An outline of what appears to have happened follows … Torrent sites aren’t exactly “new”; however, this is one of the first times that we’ve seen an attack that came from this vector.  It appears that for a number of years, a person has been creating torrent sites that require a login and password as well as creating forums set up for torrent site usage and then selling these purportedly well-crafted sites and forums to other people innocently looking to start a download site of their very own.  However, these sites came with a little extra — security exploits and backdoors throughout the system.  This person then waited for the forums and sites to get popular and then used those exploits to get access to the username, email address, and password of every person who had signed up.  Additional exploits to gain admin root on forums that weren’t created by this person also appear to have been utilized; in some instances, the exploit involved redirecting attempts to access the forums to another site that would request log-in information.  This information was then used to attempt to gain access to third party sites like Twitter.  We haven’t identified all of the forums involved (nor is it likely that we’ll be able to, since we don’t have any connection with them), but as a general rule, if you’ve signed up for a torrent forum or torrent site built by a third party, you should probably change your password there]]></description>
			<content:encoded><![CDATA[<p>
<p>As part of our ongoing efforts to monitor our user base for odd activity, we noticed a sudden surge in followers for a couple accounts in the last five days.  Given the circumstances surrounding this, we felt it was best to push out a password reset to  accounts that were following these suspicious users. <br/><br/> Then we started doing some digging and, given what we found today, we felt it important to share this information.  An outline of what appears to have happened follows …</p>
<p>Torrent sites aren’t exactly “new”; however, this is one of the first times that we’ve seen an attack that came from this vector.  It appears that for a number of years, a person has been creating torrent sites that require a login and password as well as creating forums set up for torrent site usage and then selling these purportedly well-crafted sites and forums to other people innocently looking to start a download site of their very own.  However, these sites came with a little extra — security exploits and backdoors throughout the system.  This person then waited for the forums and sites to get popular and then used those exploits to get access to the username, email address, and password of every person who had signed up.  Additional exploits to gain admin root on forums that weren’t created by this person also appear to have been utilized; in some instances, the exploit involved redirecting attempts to access the forums to another site that would request log-in information.  This information was then used to attempt to gain access to third party sites like Twitter.  We haven’t identified all of the forums involved (nor is it likely that we’ll be able to, since we don’t have any connection with them), but as a general rule, if you’ve signed up for a torrent forum or torrent site built by a third party, you should probably change your password there.</p>
<p>The takeaway from this is that people are continuing to use the same email address and password (or a variant) on multiple sites.  Through our discussions with affected users, we’ve discovered a high correlation between folks who have used third party forums and download sites and folks who were on our list of possibly affected accounts.  While not all users who were sent a password reset request fall into this category, we felt that it was important to put this knowledge out there so that users would know of the possibility of compromise of their data by a third party unrelated to their Twitter account.  We strongly suggest that you use different passwords for each service you sign up for; more information on how to keep your Twitter account safe can be found here: <a><a href="http://twitter.zendesk.com/forums/10711/entries/76036">http://twitter.zendesk.com/forums/10711/entries/76036</a></a>.</p>
<p>Del Harvey<br/> Director, Trust and Safety</p>
</p>
<p>The rest is here:<br />
<a target="_blank" href="http://status.twitter.com/post/367671822" title="Reason #4132 for Changing Your Password">Reason #4132 for Changing Your Password</a></p>
]]></content:encoded>
			<wfw:commentRss>http://socialsnipe.com/reason-4132-for-changing-your-password/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
