<?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: Blowback from Fauxlowers Hits Fauxlowers.com</title>
	<atom:link href="http://fauxlowers.com/blog/blowback-from-fauxlowers-hits-fauxlowers-com/feed/" rel="self" type="application/rss+xml" />
	<link>http://fauxlowers.com/blog/blowback-from-fauxlowers-hits-fauxlowers-com/</link>
	<description>Liars, Damn Liars &#38; Twitter Followers</description>
	<lastBuildDate>Tue, 19 Apr 2011 08:24:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Antone Roundy</title>
		<link>http://fauxlowers.com/blog/blowback-from-fauxlowers-hits-fauxlowers-com/#comment-71</link>
		<dc:creator>Antone Roundy</dc:creator>
		<pubDate>Fri, 05 Feb 2010 21:02:19 +0000</pubDate>
		<guid isPermaLink="false">http://fauxlowers.com/blog/?p=66#comment-71</guid>
		<description>We&#039;ve been reactivated (whew!) Apparently my response to Twitter support never got attached to the ticket for some reason, which is why it took this long. Good to be back online!</description>
		<content:encoded><![CDATA[<p>We&#8217;ve been reactivated (whew!) Apparently my response to Twitter support never got attached to the ticket for some reason, which is why it took this long. Good to be back online!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antone Roundy</title>
		<link>http://fauxlowers.com/blog/blowback-from-fauxlowers-hits-fauxlowers-com/#comment-70</link>
		<dc:creator>Antone Roundy</dc:creator>
		<pubDate>Tue, 02 Feb 2010 15:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://fauxlowers.com/blog/?p=66#comment-70</guid>
		<description>In case my response to the French blog post linked to above doesn&#039;t get approved, here it is:

----------------------------

A few parts of this post didn’t come through clearly in Google Translate, so I’m not quite sure whether you suspect that my app was doing something malicious, or whether somebody else who was doing something malicious was trying to make it look as if Fauxlowers was responsible. I can tell you, my app never did anything that wasn’t clearly explained in advance to everyone who joined. The only thing Fauxlowers did after someone granted it access to their Twitter account was:

1) Send out ONE tweet with the person’s stats and linking to their profile on Fauxlowers.com. (This was recently made optional.)

2) Send ONE welcome DM to each NEW follower with pretty much the same information (stats and profile link). This has been optional almost since Fauxlowers was launched (but I think some people didn’t bother glancing at the form they were submitting, so they didn’t realize this, even though I tried to make it as clear as possible, and it was easy to disable). This feature has now been removed from the site to avoid future complaints from people who don’t read the forms they submit.

“As a reminder, you should be extraordinarily suspicious of any third party that offers to artificially inflate your follower count.”

Fauxlowers has absolutely nothing to do with inflating your follow count, so this statement is clearly not aimed at my site. Also, since Fauxlowers uses OAuth to access Twitter accounts (NOT passwords), resetting one’s password doesn’t affect it. So if the alert Twitter sent out had anything to do with Fauxlowers, it wouldn’t have been talking about passwords, it would have been talking about your Connections control panel. And there would have been no need for them to tell users, because they could have simply deleted all of Fauxlowers’ connections — or, as they did, they could just deactivate the Fauxlowers app.

In short, Fauxlowers has absolutely nothing to do with any phishing attack. Anyone who thought they’d been phished must not have read the clear and detailed explanation on the Fauxlowers.com homepage of what Fauxlowers was going to do before they gave it authorization to access their account.</description>
		<content:encoded><![CDATA[<p>In case my response to the French blog post linked to above doesn&#8217;t get approved, here it is:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>A few parts of this post didn’t come through clearly in Google Translate, so I’m not quite sure whether you suspect that my app was doing something malicious, or whether somebody else who was doing something malicious was trying to make it look as if Fauxlowers was responsible. I can tell you, my app never did anything that wasn’t clearly explained in advance to everyone who joined. The only thing Fauxlowers did after someone granted it access to their Twitter account was:</p>
<p>1) Send out ONE tweet with the person’s stats and linking to their profile on Fauxlowers.com. (This was recently made optional.)</p>
<p>2) Send ONE welcome DM to each NEW follower with pretty much the same information (stats and profile link). This has been optional almost since Fauxlowers was launched (but I think some people didn’t bother glancing at the form they were submitting, so they didn’t realize this, even though I tried to make it as clear as possible, and it was easy to disable). This feature has now been removed from the site to avoid future complaints from people who don’t read the forms they submit.</p>
<p>“As a reminder, you should be extraordinarily suspicious of any third party that offers to artificially inflate your follower count.”</p>
<p>Fauxlowers has absolutely nothing to do with inflating your follow count, so this statement is clearly not aimed at my site. Also, since Fauxlowers uses OAuth to access Twitter accounts (NOT passwords), resetting one’s password doesn’t affect it. So if the alert Twitter sent out had anything to do with Fauxlowers, it wouldn’t have been talking about passwords, it would have been talking about your Connections control panel. And there would have been no need for them to tell users, because they could have simply deleted all of Fauxlowers’ connections — or, as they did, they could just deactivate the Fauxlowers app.</p>
<p>In short, Fauxlowers has absolutely nothing to do with any phishing attack. Anyone who thought they’d been phished must not have read the clear and detailed explanation on the Fauxlowers.com homepage of what Fauxlowers was going to do before they gave it authorization to access their account.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Attack Alert Sur Twitter, Fauxlowers Dans Notre Viseur &#124; TwitteRadar</title>
		<link>http://fauxlowers.com/blog/blowback-from-fauxlowers-hits-fauxlowers-com/#comment-69</link>
		<dc:creator>Attack Alert Sur Twitter, Fauxlowers Dans Notre Viseur &#124; TwitteRadar</dc:creator>
		<pubDate>Tue, 02 Feb 2010 12:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://fauxlowers.com/blog/?p=66#comment-69</guid>
		<description>[...] xavierv on 2 février 2010   Le 27 Janvier, le fondateur de l&#8217;application Fauxlowers a annoncé sur son blog que Twitter venait de suspendre son application. Effectivement, si l&#8217;on cherche [...]</description>
		<content:encoded><![CDATA[<p>[...] xavierv on 2 février 2010   Le 27 Janvier, le fondateur de l&#8217;application Fauxlowers a annoncé sur son blog que Twitter venait de suspendre son application. Effectivement, si l&#8217;on cherche [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antone Roundy</title>
		<link>http://fauxlowers.com/blog/blowback-from-fauxlowers-hits-fauxlowers-com/#comment-68</link>
		<dc:creator>Antone Roundy</dc:creator>
		<pubDate>Thu, 28 Jan 2010 22:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://fauxlowers.com/blog/?p=66#comment-68</guid>
		<description>Twitter has replied to my inquiry, verifying that it was complaints about welcome DMs that got us suspended. They asked for confirmation of what I&#039;ve written above about the changes to welcome DMs. It sounds like we&#039;ll get reactivated once they get to my my response to their response.</description>
		<content:encoded><![CDATA[<p>Twitter has replied to my inquiry, verifying that it was complaints about welcome DMs that got us suspended. They asked for confirmation of what I&#8217;ve written above about the changes to welcome DMs. It sounds like we&#8217;ll get reactivated once they get to my my response to their response.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rendy</title>
		<link>http://fauxlowers.com/blog/blowback-from-fauxlowers-hits-fauxlowers-com/#comment-67</link>
		<dc:creator>Rendy</dc:creator>
		<pubDate>Thu, 28 Jan 2010 10:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://fauxlowers.com/blog/?p=66#comment-67</guid>
		<description>Automated tweaks and dms are not the way to go. Only the serious tweeters can succeed on this playing field.</description>
		<content:encoded><![CDATA[<p>Automated tweaks and dms are not the way to go. Only the serious tweeters can succeed on this playing field.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

