<?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: Four Lessons From Twitter&#8217;s Spam/Customer-Busting Episode</title>
	<atom:link href="http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/feed/" rel="self" type="application/rss+xml" />
	<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/</link>
	<description>Exploring the intersection of communications, marketing and social media</description>
	<lastBuildDate>Wed, 23 May 2012 09:47:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: PR Cliches (and Other PR Blog Jots) &#171; Media Bullseye &#8211; A New Media and Communications Magazine</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-81455</link>
		<dc:creator>PR Cliches (and Other PR Blog Jots) &#171; Media Bullseye &#8211; A New Media and Communications Magazine</dc:creator>
		<pubDate>Fri, 19 Feb 2010 21:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-81455</guid>
		<description>[...] why Internal Comms should stay a separate and equally senior part of the management team.&#8221;  Learning from Disaster Dave Fleet I know, I know, more complaining about Twitter. At least this one takes the usual [...]</description>
		<content:encoded><![CDATA[<p>[...] why Internal Comms should stay a separate and equally senior part of the management team.&#8221;  Learning from Disaster Dave Fleet I know, I know, more complaining about Twitter. At least this one takes the usual [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Fisher</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-14547</link>
		<dc:creator>David Fisher</dc:creator>
		<pubDate>Tue, 21 Oct 2008 16:18:48 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-14547</guid>
		<description>Thanks for noticing and having this great writeup of what happened. I think the main less is fast response, which I know is difficult. I didn&#039;t realize that at the time Twitter was only 16 employees. For some reason I figured that in raising 15M that they&#039;d hired a bit more. 

I&#039;m glad that they fixed the problems, but it was a disturbing 24 hours. I felt as if my voice on the internet was taken away.</description>
		<content:encoded><![CDATA[<p>Thanks for noticing and having this great writeup of what happened. I think the main less is fast response, which I know is difficult. I didn&#8217;t realize that at the time Twitter was only 16 employees. For some reason I figured that in raising 15M that they&#8217;d hired a bit more. </p>
<p>I&#8217;m glad that they fixed the problems, but it was a disturbing 24 hours. I felt as if my voice on the internet was taken away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PF Anderson</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-5408</link>
		<dc:creator>PF Anderson</dc:creator>
		<pubDate>Wed, 06 Aug 2008 13:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-5408</guid>
		<description>Connie is so on target mentioning the impact on the followers. You also have to remember that to get a response we used other social networks, beyond Twitter, and there is a broader public watching. Most important in my mind is the possibility of there being other victims who have not yet discovered the problem, have not realized that it isn&#039;t a temporary fluke (which is what I thought for the first several hours) or who don&#039;t know how to report it. 

As I said on the GetSatistfaction page: &quot;So far most of the people who have found this page are fairly high-end Twitter users, savvy folk who know their way around troubleshooting. I am concerned that there may be effected users who are not so savvy, may not know how to get help, may not realize the scope of the problem, or may not have even thought to check their accounts yet. It would be nice if Twitter looked out for any other as-yet-undiscovered victims of this problem and took a proactive role in communicating with their community, creating a variety of communication paths to the necessary support information.&quot;</description>
		<content:encoded><![CDATA[<p>Connie is so on target mentioning the impact on the followers. You also have to remember that to get a response we used other social networks, beyond Twitter, and there is a broader public watching. Most important in my mind is the possibility of there being other victims who have not yet discovered the problem, have not realized that it isn&#8217;t a temporary fluke (which is what I thought for the first several hours) or who don&#8217;t know how to report it. </p>
<p>As I said on the GetSatistfaction page: &#8220;So far most of the people who have found this page are fairly high-end Twitter users, savvy folk who know their way around troubleshooting. I am concerned that there may be effected users who are not so savvy, may not know how to get help, may not realize the scope of the problem, or may not have even thought to check their accounts yet. It would be nice if Twitter looked out for any other as-yet-undiscovered victims of this problem and took a proactive role in communicating with their community, creating a variety of communication paths to the necessary support information.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Connie Crosby</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-5282</link>
		<dc:creator>Connie Crosby</dc:creator>
		<pubDate>Tue, 05 Aug 2008 04:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-5282</guid>
		<description>LOL! I wasn&#039;t challenging you. I have just been thinking a lot about it since we last talked. I agree if only 8 people are affected it might not be a good move to blog it. But, all 8 of us had 1500+ followers, many of whom expressed concern about the situation. Many of my followers were far more concerned about it than I was, and they needed some comfort from Twitter, too. There was no real way to quietly fix things in this case I think.</description>
		<content:encoded><![CDATA[<p>LOL! I wasn&#8217;t challenging you. I have just been thinking a lot about it since we last talked. I agree if only 8 people are affected it might not be a good move to blog it. But, all 8 of us had 1500+ followers, many of whom expressed concern about the situation. Many of my followers were far more concerned about it than I was, and they needed some comfort from Twitter, too. There was no real way to quietly fix things in this case I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eden Spodek</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-5281</link>
		<dc:creator>Eden Spodek</dc:creator>
		<pubDate>Tue, 05 Aug 2008 04:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-5281</guid>
		<description>I&#039;m not defending twitter in their decision about whether or not to blog about the problem but sometimes you have to make a judgement call. If only 8 people were affected that&#039;s a tiny percentage of the total number of customers. Addressing the entire customer base may not be the right approach as it may have made a mountain out of a mole hill.

We discussed this on our upcoming podcast and you didn&#039;t challenge me on that comment. ;-)</description>
		<content:encoded><![CDATA[<p>I&#8217;m not defending twitter in their decision about whether or not to blog about the problem but sometimes you have to make a judgement call. If only 8 people were affected that&#8217;s a tiny percentage of the total number of customers. Addressing the entire customer base may not be the right approach as it may have made a mountain out of a mole hill.</p>
<p>We discussed this on our upcoming podcast and you didn&#8217;t challenge me on that comment. <img src='http://davefleet.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Connie Crosby</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-5279</link>
		<dc:creator>Connie Crosby</dc:creator>
		<pubDate>Tue, 05 Aug 2008 03:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-5279</guid>
		<description>Why I think the blog should have been used in this case:

On the Twitter blog I was actively participating in their discussion about efforts being taken to clean up spam. They should have mentioned there that they were deleting suspected spam accounts. @biz tweeted that they had made mistake, why not post that in the blog? After all, if I can&#039;t get into my account and if I am not following @biz (I didn&#039;t know he existed before this!) how would I see this tweet? http://twitter.com/biz/statuses/875773303

Eventually I discovered the discussion in the &quot;Get Satisfaction&quot; forum. Again, I had to hunt for that. The blog would have been a more central place to communicate with those of us with problems.

They keep saying 8 of us had the problem. How do we know there weren&#039;t more? I am concerned there are others out there who just gave up, not knowing they were deactivated accidentally. Maybe they have been off-line all weekend?

Finally, I have a lot of followers who expressed concern that they were not seeing enough evidence of Twitter communicating with me. They were concerned not just about me, but about their own accounts and especially about advocating the use of Twitter for others. They could also have benefitted from seeing communication on the blog.

Ultimately, I think it is good Twitter is working to clean out spam accounts. I wish they had sent each of us an email message telling us the accounts had been deleted and why. Then we would have had better recourse from the beginning.</description>
		<content:encoded><![CDATA[<p>Why I think the blog should have been used in this case:</p>
<p>On the Twitter blog I was actively participating in their discussion about efforts being taken to clean up spam. They should have mentioned there that they were deleting suspected spam accounts. @biz tweeted that they had made mistake, why not post that in the blog? After all, if I can&#8217;t get into my account and if I am not following @biz (I didn&#8217;t know he existed before this!) how would I see this tweet? <a href="http://twitter.com/biz/statuses/875773303" rel="nofollow">http://twitter.com/biz/statuses/875773303</a></p>
<p>Eventually I discovered the discussion in the &#8220;Get Satisfaction&#8221; forum. Again, I had to hunt for that. The blog would have been a more central place to communicate with those of us with problems.</p>
<p>They keep saying 8 of us had the problem. How do we know there weren&#8217;t more? I am concerned there are others out there who just gave up, not knowing they were deactivated accidentally. Maybe they have been off-line all weekend?</p>
<p>Finally, I have a lot of followers who expressed concern that they were not seeing enough evidence of Twitter communicating with me. They were concerned not just about me, but about their own accounts and especially about advocating the use of Twitter for others. They could also have benefitted from seeing communication on the blog.</p>
<p>Ultimately, I think it is good Twitter is working to clean out spam accounts. I wish they had sent each of us an email message telling us the accounts had been deleted and why. Then we would have had better recourse from the beginning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eden Spodek</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-5278</link>
		<dc:creator>Eden Spodek</dc:creator>
		<pubDate>Tue, 05 Aug 2008 03:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-5278</guid>
		<description>I&#039;m also friends with Connie Crosby and Dave Delaney. They are two of the last people I&#039;d ever expect to be accused of twitter spamming.  

I agree, twitter could have done a better job of communicating with the eight individuals involved. I&#039;m not sure twitter needed to announce the problem on their blog as some people suggested but they could have have done a better job of contacting the eight individuals.

As for the role of a PR professional on the twitter team, I couldn&#039;t agree with you more. I&#039;m seeing more examples every day where the need for public relations professionals, especially those with an understanding of digital communications, has grown.</description>
		<content:encoded><![CDATA[<p>I&#8217;m also friends with Connie Crosby and Dave Delaney. They are two of the last people I&#8217;d ever expect to be accused of twitter spamming.  </p>
<p>I agree, twitter could have done a better job of communicating with the eight individuals involved. I&#8217;m not sure twitter needed to announce the problem on their blog as some people suggested but they could have have done a better job of contacting the eight individuals.</p>
<p>As for the role of a PR professional on the twitter team, I couldn&#8217;t agree with you more. I&#8217;m seeing more examples every day where the need for public relations professionals, especially those with an understanding of digital communications, has grown.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Connie Crosby</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-5274</link>
		<dc:creator>Connie Crosby</dc:creator>
		<pubDate>Tue, 05 Aug 2008 03:13:59 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-5274</guid>
		<description>Hi Dave:

You make a good point, that a PR specialist would have known better how to handle this. Crystal from Twitter has now been in more personal contact with me and Dave Delaney. And Jason Goldman has been stellar in trouble-shooting in the help forum. Took them a while to figure out how to deal with us, but I think they have learned albeit the hard way!

I have posted my take on the whole thing over on my blog: &quot;Connie Crosby&#039;s Day Off, Or How Twitter Decided We Needed a Break&quot; http://tinyurl.com/5hrznx

Enjoy!
Connie</description>
		<content:encoded><![CDATA[<p>Hi Dave:</p>
<p>You make a good point, that a PR specialist would have known better how to handle this. Crystal from Twitter has now been in more personal contact with me and Dave Delaney. And Jason Goldman has been stellar in trouble-shooting in the help forum. Took them a while to figure out how to deal with us, but I think they have learned albeit the hard way!</p>
<p>I have posted my take on the whole thing over on my blog: &#8220;Connie Crosby&#8217;s Day Off, Or How Twitter Decided We Needed a Break&#8221; <a href="http://tinyurl.com/5hrznx" rel="nofollow">http://tinyurl.com/5hrznx</a></p>
<p>Enjoy!<br />
Connie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amrita Chandra</title>
		<link>http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/comment-page-1/#comment-5273</link>
		<dc:creator>Amrita Chandra</dc:creator>
		<pubDate>Tue, 05 Aug 2008 03:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://davefleet.com/2008/08/four-lessons-from-twitters-spamcustomer-busting-episode/#comment-5273</guid>
		<description>Good synopsis of lessons learned.  The personalization one in particular is something that seems so simple but is often overlooked.  There is no worse feeling that thinking your email/Tweet/inquiry to a company has gone into a black hole which is what you feel when you get a cut and paste response.

The Twitter situation can happen at any company, to different degrees.  Nice reminder of how to make the best of a bad situation when it is happening to you.</description>
		<content:encoded><![CDATA[<p>Good synopsis of lessons learned.  The personalization one in particular is something that seems so simple but is often overlooked.  There is no worse feeling that thinking your email/Tweet/inquiry to a company has gone into a black hole which is what you feel when you get a cut and paste response.</p>
<p>The Twitter situation can happen at any company, to different degrees.  Nice reminder of how to make the best of a bad situation when it is happening to you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

