<?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: How CoTweet is helping the Spyder Trap Team with collaboration</title>
	<atom:link href="http://www.spydertrap.com/blog/2009/07/how-cotweet-is-helping-the-spyder-trap-team-with-collaboration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spydertrap.com/blog/2009/07/how-cotweet-is-helping-the-spyder-trap-team-with-collaboration/</link>
	<description>Minneapois online marketing blog covering search engine optimization (SEO), social media, online public relations, online marketing strategy, website development, sponsored search, web analytics and more</description>
	<lastBuildDate>Fri, 18 Jun 2010 14:52:57 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brad Wellman</title>
		<link>http://www.spydertrap.com/blog/2009/07/how-cotweet-is-helping-the-spyder-trap-team-with-collaboration/comment-page-1/#comment-3144</link>
		<dc:creator>Brad Wellman</dc:creator>
		<pubDate>Fri, 10 Jul 2009 14:12:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.spydertrap.com/blog/?p=667#comment-3144</guid>
		<description>Thanks for the comment Paul. 

I agree with you completely that it might be a little too much of an overload if there were dozens of assigned users to it for one brand.  That&#039;s why its good to find a nice balance where you have more than one person (to get different ideas, viewpoints, and personalities) but not too many people so your followers are struggling to figure out who said what...

From what I&#039;ve seen, a lot of the companies using it are keeping the number of people assigned to it relatively low, like &lt;a href=&quot;http://www.twitter.com/mswindows&quot; rel=&quot;nofollow&quot;&gt;@MSWindows&lt;/a&gt;, &lt;a href=&quot;http://www.twitter.com/cotweet&quot; rel=&quot;nofollow&quot;&gt;@CoTweet&lt;/a&gt;, and &lt;a href=&quot;http://www.twitter.com/twitterapi&quot; rel=&quot;nofollow&quot;&gt;@TwitterAPI&lt;/a&gt; to name a few. I like how they (and us) are showing who sends each tweet. Larger organizations such as &lt;a href=&quot;http://www.twitter.com/ford&quot; rel=&quot;nofollow&quot;&gt;@ford,&lt;/a&gt; &lt;a href=&quot;http://www.twitter.com/cocacola&quot; rel=&quot;nofollow&quot;&gt;@cocacola&lt;/a&gt; and &lt;a href=&quot;http://www.twitter.com/pepsi&quot; rel=&quot;nofollow&quot;&gt;@pepsi&lt;/a&gt; aren&#039;t using CoTags (CoTweet signatures) to identify a particular tweeter, but obviously use it for collaboration in managing the Twitter account.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Paul. </p>
<p>I agree with you completely that it might be a little too much of an overload if there were dozens of assigned users to it for one brand.  That&#8217;s why its good to find a nice balance where you have more than one person (to get different ideas, viewpoints, and personalities) but not too many people so your followers are struggling to figure out who said what&#8230;</p>
<p>From what I&#8217;ve seen, a lot of the companies using it are keeping the number of people assigned to it relatively low, like <a href="http://www.twitter.com/mswindows" rel="nofollow">@MSWindows</a>, <a href="http://www.twitter.com/cotweet" rel="nofollow">@CoTweet</a>, and <a href="http://www.twitter.com/twitterapi" rel="nofollow">@TwitterAPI</a> to name a few. I like how they (and us) are showing who sends each tweet. Larger organizations such as <a href="http://www.twitter.com/ford" rel="nofollow">@ford,</a> <a href="http://www.twitter.com/cocacola" rel="nofollow">@cocacola</a> and <a href="http://www.twitter.com/pepsi" rel="nofollow">@pepsi</a> aren&#8217;t using CoTags (CoTweet signatures) to identify a particular tweeter, but obviously use it for collaboration in managing the Twitter account.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul jahn</title>
		<link>http://www.spydertrap.com/blog/2009/07/how-cotweet-is-helping-the-spyder-trap-team-with-collaboration/comment-page-1/#comment-3142</link>
		<dc:creator>paul jahn</dc:creator>
		<pubDate>Fri, 10 Jul 2009 01:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.spydertrap.com/blog/?p=667#comment-3142</guid>
		<description>Good stuff Brad. I haven&#039;t even heard of CoTweet until I read this post. You and I probably had the same initial thoughts with &quot;why would I use this when I can just share login info&quot;.

I like how you guys are using it. It&#039;s easy to tell when the messages are coming from you, Mike, Jason or Glenn and can see the different personalities. If a company used it with 50 assigned users, it would be too much of an overload for me. My two cents.</description>
		<content:encoded><![CDATA[<p>Good stuff Brad. I haven&#8217;t even heard of CoTweet until I read this post. You and I probably had the same initial thoughts with &#8220;why would I use this when I can just share login info&#8221;.</p>
<p>I like how you guys are using it. It&#8217;s easy to tell when the messages are coming from you, Mike, Jason or Glenn and can see the different personalities. If a company used it with 50 assigned users, it would be too much of an overload for me. My two cents.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
