<?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>Skitzzo.com &#187; Twitter</title>
	<atom:link href="http://skitzzo.com/archives/category/twitter/feed" rel="self" type="application/rss+xml" />
	<link>http://skitzzo.com</link>
	<description>SEO &#38; WordPress Addict</description>
	<lastBuildDate>Sat, 10 Jul 2010 18:38:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Twitter Blocking Glitch?</title>
		<link>http://skitzzo.com/archives/twitter-blocking-glitch.php</link>
		<comments>http://skitzzo.com/archives/twitter-blocking-glitch.php#comments</comments>
		<pubDate>Wed, 28 Apr 2010 08:10:32 +0000</pubDate>
		<dc:creator>Ben Cook</dc:creator>
				<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://skitzzo.com/?p=285</guid>
		<description><![CDATA[As I was playing around on Twitter tonight instead of sleeping (long story &#38; it starts in Israel, no seriously) I saw my buddy Olivier [...]]]></description>
			<content:encoded><![CDATA[<p><a class="post_image_link" href="http://skitzzo.com/archives/twitter-blocking-glitch.php" title="Permanent link to Twitter Blocking Glitch?"><img class="post_image aligncenter" src="http://skitzzo.com/wp-content/uploads/twitter-blocked.jpg" width="500" height="279" alt="Post image for Twitter Blocking Glitch?" /></a>
</p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a target="_blank" href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Ftwitter-blocking-glitch.php"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Ftwitter-blocking-glitch.php&amp;source=Skitzzo&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>As I was playing around on Twitter tonight instead of sleeping (long story &amp; it starts in Israel, no seriously) I saw my buddy Olivier mention that Rand Fishkin had blocked him.</p>
<p>Now, Olivier was being a bit belligerent with Rand sure, but I&#8217;ve never known Rand to be thin skinned and trust me, I&#8217;ve tested that theory time &amp; time again. <img src='http://skitzzo.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>So I jumped over to Rand&#8217;s twitter page only to see this somewhat shocking image you see above.</p>
<p>Now that&#8217;s odd, I thought. I can&#8217;t believe Rand would really lock his Tweets down. I mean attention whores like us want anyone and everyone hearing what we have to say.</p>
<p>Naturally, I clicked the send request button.</p>
<p><a href="http://skitzzo.com/wp-content/uploads/twitter-blocked-glitch.jpg"><img class="alignnone size-full wp-image-287" title="twitter-blocked-glitch" src="http://skitzzo.com/wp-content/uploads/twitter-blocked-glitch.jpg" alt="" width="500" height="267" /></a></p>
<p>After clicking I&#8217;m then informed that Rand has blocked me (a possibility I suppose) but I&#8217;m allowed to see the stream that had just been labeled private.</p>
<p>So um.. which is it Twitter&#8230; did Rand make his Twitter stream private, or did he block me?</p>
]]></content:encoded>
			<wfw:commentRss>http://skitzzo.com/archives/twitter-blocking-glitch.php/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Join Team Bacon &amp; Send Me to Search &amp; Social Spring Summit #SSSS</title>
		<link>http://skitzzo.com/archives/search-social-spring-summit.php</link>
		<comments>http://skitzzo.com/archives/search-social-spring-summit.php#comments</comments>
		<pubDate>Wed, 17 Mar 2010 16:20:31 +0000</pubDate>
		<dc:creator>Ben Cook</dc:creator>
				<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://skitzzo.com/?p=229</guid>
		<description><![CDATA[Update: The contest is over. The winner will be announced at the end of the week. Thanks for all the support! Come on folks, what [...]]]></description>
			<content:encoded><![CDATA[<p><a class="post_image_link" href="http://skitzzo.com/archives/search-social-spring-summit.php" title="Permanent link to Join Team Bacon &#038; Send Me to Search &#038; Social Spring Summit #SSSS"><img class="post_image aligncenter" src="http://skitzzo.com/wp-content/uploads/bacon-vs-tofu.jpg" width="500" height="462" alt="Post image for Join Team Bacon &#038; Send Me to Search &#038; Social Spring Summit #SSSS" /></a>
</p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a target="_blank" href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Fsearch-social-spring-summit.php"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Fsearch-social-spring-summit.php&amp;source=Skitzzo&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p><span style="color: #ff0000;"><strong>Update:</strong></span> The contest is over. The winner will be announced at the end of the week. Thanks for all the support!</p>
<p>Come on folks, what better team is there than Team Bacon?</p>
<p>What the hell is this about you might ask? Well if you a) love bacon &amp; b) want to help me go to <a target="_blank" href="http://www.searchenginejournal.com/twitter-contest-pick-a-team/18981/">Search &amp; Social Spring Summit</a> all you have to do is retweet this on Twitter:</p>
<p>Join @skitzzo on Team Bacon &amp; send him to #SSSS! (Please RT)</p>
<p>It really is that easy!</p>
<h6>image source: <a target="_blank" href="http://www.flickr.com/photos/zoomar/2217922878/" target="_blank">zoomar</a></h6>
]]></content:encoded>
			<wfw:commentRss>http://skitzzo.com/archives/search-social-spring-summit.php/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>John Reese &amp; Mike Filsaime Perform Twitter Bait &amp; Switch</title>
		<link>http://skitzzo.com/archives/john-reese-mike-filsaime-twitter-bait-switch.php</link>
		<comments>http://skitzzo.com/archives/john-reese-mike-filsaime-twitter-bait-switch.php#comments</comments>
		<pubDate>Fri, 10 Jul 2009 03:27:36 +0000</pubDate>
		<dc:creator>Ben Cook</dc:creator>
				<category><![CDATA[Twitter]]></category>
		<category><![CDATA[Autofollow]]></category>
		<category><![CDATA[John Reese]]></category>
		<category><![CDATA[Mike Filsaime]]></category>

		<guid isPermaLink="false">http://skitzzo.com/?p=140</guid>
		<description><![CDATA[In the internet marketing industry names don&#8217;t get much bigger than John Reese and Mike Filsaime. So, when both John and Mike make the same [...]]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a target="_blank" href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Fjohn-reese-mike-filsaime-twitter-bait-switch.php"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Fjohn-reese-mike-filsaime-twitter-bait-switch.php&amp;source=Skitzzo&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>In the internet marketing industry names don&#8217;t get much bigger than <a target="_blank" href="http://twitter.com/johnreese" target="_blank">John Reese</a> and <a target="_blank" href="http://twitter.com/mikefilsaime" target="_blank">Mike Filsaime</a>. So, when both John and Mike make the same splash on the same day, it&#8217;s going to draw some attention.</p>
<p>The splash I&#8217;m talking about is abandoning the practice of autofollowing on Twitter. For those of you who don&#8217;t know what auto-follow is, why are you reading this blog?</p>
<p>I keeed I keeed!</p>
<p>Autofollow is quite simply Twitter&#8217;s version of &#8220;you scratch my back I&#8217;ll scratch yours.&#8221; For every person that follows you, you automatically follow them back.</p>
<p>Obviously the goal of many people on Twitter, especially marketers, is to accumulate as many followers as possible. As a result, lists have sprung up containing the names of hundreds if not thousands of accounts that use autofollow. Follow a few thousand of the people on that list, and BOOM&#8230; a few thousand almost instant followers!</p>
<p>If this whole thing sounds kind of pointless and shallow, especially on a site that&#8217;s all about actually connecting with others, you&#8217;re absolutely right. As John <a target="_blank" href="http://www.income.com/blog/2009/07/09/5-reasons-why-twitter-auto-follow-is-bad-marketing/" target="_blank">points out in his post</a>, a bunch of automated followers probably aren&#8217;t going to be as high in quality as followers that CHOOSE to follow you.</p>
<p>As a result, John (and subsequently Mike) have both disavowed the practice of auto-follow, and purged the list of people they follow, citing the desire to now have <em>genuine</em> interactions on Twitter.</p>
<p>And, for the most part the move has been praised across Twitter. John&#8217;s post has been retweeted by thousands of his followers and&#8230;.</p>
<p>Wait, what? Oh yeah! That&#8217;s right! John and Mike, despite no longer following thousands of people, are STILL followed by all those thousands of people who jumped aboard the autofollow Twitter train. Who knows, maybe John and Mike made use of those autofollow lists themselves.</p>
<p>The point is, by making this noble and bold decision, John and Mike have essentially done one big bait &amp; switch on thousands of their followers.</p>
<p>If anyone else followed thousands of people, and then unfollowed them once they&#8217;d triggered the autofollow mechanism, they&#8217;d be call a spammer.</p>
<p>In fact, Twitter itself <a target="_blank" href="http://www.techcrunch.com/2009/03/31/twitter-to-kill-off-the-auto-follow/" target="_blank">stated in March</a> that they&#8217;re going to kill off the &#8220;feature&#8221; because</p>
<blockquote><p>&#8221; this behavior sends the wrong message. Namely, it is unlikely that anyone can actually read tweets from thousands of accounts which makes this activity disingenuous.&#8221;</p></blockquote>
<p>So, no, John Reese and Mike Filsaime are no longer participating in the &#8220;disingenuous&#8221; activity of autofollow, but before we all go praising them for their brilliant insight and sudden desire to make legitimate connections, realize that they still have 66 thousand followers between them.</p>
<p>They&#8217;re not giving ANYTHING up, they&#8217;re simply clearing out the feed that they read and limiting the level of access those 66k followers have to contact them.</p>
<p>I&#8217;m sure that was a really difficult decision. I mean, as Mike said, John had to &#8220;push him over the edge&#8221; after all&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://skitzzo.com/archives/john-reese-mike-filsaime-twitter-bait-switch.php/feed</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Twitter to #FixReplies Users: We Can&#8217;t But Please Be Quiet</title>
		<link>http://skitzzo.com/archives/twitter-covering-up-incompetence.php</link>
		<comments>http://skitzzo.com/archives/twitter-covering-up-incompetence.php#comments</comments>
		<pubDate>Wed, 13 May 2009 18:24:46 +0000</pubDate>
		<dc:creator>Ben Cook</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://skitzzo.com/?p=123</guid>
		<description><![CDATA[Update 2: Twitter says they've learned a lot and responded with another blog post saying:

    The problem with the setting was that it didn't scale and even if we rebuilt it, the feature was blunt. It was confusing and caused a sense of inconsistency. We felt we could do much better.

I still don't understand where they're getting that the feature was confusing or caused a sense of inconsistency from. If you used it, you saw every tweet from the people you follow. That seems pretty simple to me.
<strong>Update:</strong> Due to the uproar over the "small settings update" Twitter has published a <a href="http://blog.twitter.com/2009/05/whoa-feedback.html" target="_blank">new blog post</a> saying:
<p style="padding-left: 30px;">The engineering team reminded me that there were serious technical reasons why that setting had to go or be entirely rebuilt—it wouldn't have lasted long even if we thought it was the best thing ever.</p>

In other words, , "Remember how we told you we killed the option because it was undesirable and confusing"? Well really we had to kill it off because we don't have enough resources to run our service."

Bottom line: Twitter lied.]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a target="_blank" href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Ftwitter-covering-up-incompetence.php"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fskitzzo.com%2Farchives%2Ftwitter-covering-up-incompetence.php&amp;source=Skitzzo&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p><strong>Update 2:</strong> Twitter says they&#8217;ve learned a lot and responded with another blog post saying:</p>
<blockquote><p>The problem with the setting was that it didn&#8217;t scale and even if we rebuilt it, the feature was blunt. It was confusing and caused a sense of inconsistency. We felt we could do much better.</p></blockquote>
<p>I still don&#8217;t understand where they&#8217;re getting that the feature was confusing or caused a sense of inconsistency from. If you used it, you saw every tweet from the people you follow. That seems pretty simple to me.</p>
<p>The post continues:</p>
<blockquote><p>So here&#8217;s what we&#8217;re planning to do. First, we&#8217;re making a change such that any updates beginning with @username (that are not explicitly created by clicking on the reply icon) will be seen by everyone following that account. This will bring back some serendipity and discovery and we can do this very soon.</p></blockquote>
<p>So wait, only @replies that <em>aren&#8217;t</em> generated by clicking the reply button will be shown? Meaning users now have to choose whether they want all of their followers to see a reply, or whether they want to link the reply to the tweet they&#8217;re actually replying to?</p>
<p>And that&#8217;s supposed to be making things LESS confusing? Riiiight.</p>
<p>@Biz concludes by saying</p>
<blockquote><p>Second, we&#8217;ve started designing a new feature which will give folks far more control over what they see from the accounts they follow. This will be a per-user setting and it will take a bit longer to put together but not too long and we&#8217;re already working on it. Thanks for all the great feedback and thanks for helping us discover what&#8217;s important!</p></blockquote>
<p>And wait a minute, did you just call this an important issue? I thought the feature wasn&#8217;t used by anyone and too confusing.</p>
<p>Putting that issue aside, this <strong>actually does </strong>sound like an improvement. What makes Twitter great is the ability of users to turn it into whatever they want it to be.</p>
<p>Of course, given Twitter&#8217;s history of down time, problems with scaling, and their recent pathetic attempt at a cover-up, I&#8217;m not going to be holding my breath on these new features.</p>
<p>@Biz says that Twitter learned a lot from this flap.</p>
<p>Judging from their continuing unwillingness to simply admit they lied about the reason initially and are simply unable to continue to support the feature, I&#8217;m not sure they learned anything at all.</p>
<p>====================</p>
<p><strong>Update:</strong> Due to the uproar over the &#8220;small settings update&#8221; Twitter has published a <a target="_blank" href="http://blog.twitter.com/2009/05/whoa-feedback.html" target="_blank">new blog post</a> saying:</p>
<p style="padding-left: 30px;">The engineering team reminded me that there were serious technical reasons why that setting had to go or be entirely rebuilt—it wouldn&#8217;t have lasted long even if we thought it was the best thing ever.</p>
<p>In other words, &#8220;Remember how we told you we killed the option because it was &#8216;undesirable and confusing&#8217;? Well really we had to kill it off because we don&#8217;t have enough resources to run our service.&#8221;</p>
<p>Bottom line: <span style="text-decoration: underline;"><strong>Twitter lied</strong></span>. (&amp; I&#8217;ll now be using the #TwitterLied hashtag)</p>
<p>Rather than admitting that despite taking on millions in venture capital, they still don&#8217;t have the resources needed to continue running their service properly.</p>
<p>As experienced as the Twitter founders are in social media, I&#8217;m a bit surprised they&#8217;d try and then admit to a cover-up of this magnitude. As always, their failure is now an even bigger story than it would have been if they&#8217;d have been open and honest with their users from the start.</p>
<p>====================</p>
<p>As many Twitter users will notice this morning, #fixreplies, #TwitterFail, &amp; Goodbye People I are all trending topics.</p>
<p>For those of you wondering what this is all about, I&#8217;d point you over to Twitter&#8217;s blog post announcing the &#8220;small settings update&#8221; but in reality that wouldn&#8217;t help much.</p>
<p>Why? Because Twitter apparently doesn&#8217;t explain things very well.</p>
<p>Maybe it&#8217;s because they&#8217;re used to only using 140 characters, but whatever the reason, the result has been a mass of confusion in the Twitterverse.</p>
<h3>Your Reply Tab Hasn&#8217;t Changed</h3>
<p>Despite the many panicked tweets you may have seen on the subject,  you&#8217;re STILL able to see every message that mentions your Twitter name.</p>
<p>Whether you follow that person or not, if they @reply or drop your Twitter handle in a tweet, it will show up in your @replies tab.</p>
<h3>What Twitter Broke</h3>
<p>What Twitter actually changed, was a setting that they say many users didn&#8217;t use or understand in the first place. If you <a target="_blank" href="http://twitter.com/Skitzzo" target="_blank">follow me on Twitter</a>, and I @reply to someone that you don&#8217;t follow, you will no longer see my tweet.</p>
<p>Judging from my debate with <a target="_blank" href="http://twitter.com/danzarella" target="_blank">@DanZarella</a> (who by the way is a good guy to follow for Social Media info) this morning, it seems that some people may not understand why you would even WANT to see a one sided conversation.</p>
<h3>Who Cares?</h3>
<p>Personally, I find it&#8217;s the best way to discover new users that I would like to follow. If I see several people in my Twitter stream responding to a person I don&#8217;t know, chances are I&#8217;ve just found someone else useful to follow.</p>
<p>Also, there are a lot of questions being asked and answered on Twitter. And just like in grade school, even if I wasn&#8217;t the one asking the question, the response might be quite useful to me.</p>
<p>By eliminating the option, Twitter has essentially forced you to only be exposed to people you&#8217;re already following. Rather than frequently being introduced to new people to follow, Twitter has moved us into our own exclusive cliques.</p>
<h3>Why Remove the Option?</h3>
<p>The only reasoning for this change that <a target="_blank" href="http://blog.twitter.com/2009/05/small-settings-update.html" target="_blank">Twitter gave</a> was that:</p>
<p style="padding-left: 30px;">&#8221; receiving one-sided fragments via replies sent to folks you don&#8217;t follow in your timeline is undesirable. Today&#8217;s update removes this undesirable and confusing option.&#8221;</p>
<p>You know what was cool about options? They&#8217;re optional. As in if you don&#8217;t like the feature you can turn it off. If you do like it, great, use it!</p>
<p>So, rather than allowing users to determine whether the option was &#8220;undesireable&#8221; on their own, they&#8217;ve made the decision for you.</p>
<p>Rather than doing a better job of explaining the supposedly &#8220;confusing option&#8221; they just disabled it, pissing off the users who <em>liked </em>the option.</p>
<p>Heaven forbid Twitter would actually educate their users on the option, possibly allowing them to get even more value out of their service.</p>
<h3>New Features!</h3>
<p>But don&#8217;t worry! Twitter will</p>
<p style="padding-left: 30px;">&#8220;be introducing better ways to discover and follow interesting accounts as we release more features in this space.&#8221;</p>
<p>Now, I&#8217;m no expert but if you have to create a new feature to replace the one you just killed off, maybe the old one had some value after all.</p>
<p>But just to get ahead of the curve, I&#8217;d like to put in a request to Twitter for a new feature. I&#8217;d really like to be able to follow ALL of the tweets of people I follow, not just the ones directed at people I already follow.</p>
<p>In other words, give us back the option you just took away.</p>
]]></content:encoded>
			<wfw:commentRss>http://skitzzo.com/archives/twitter-covering-up-incompetence.php/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
