<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Aggregating Organizational Tweets</title>
	<atom:link href="http://wiredpen.com/2010/02/20/aggregating-organizational-tweets/feed/" rel="self" type="application/rss+xml" />
	<link>http://wiredpen.com/2010/02/20/aggregating-organizational-tweets/</link>
	<description></description>
	<lastBuildDate>Tue, 14 Feb 2012 06:59:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: luisantezana</title>
		<link>http://wiredpen.com/2010/02/20/aggregating-organizational-tweets/#comment-21252</link>
		<dc:creator><![CDATA[luisantezana]]></dc:creator>
		<pubDate>Thu, 04 Mar 2010 08:31:32 +0000</pubDate>
		<guid isPermaLink="false">http://wiredpen.com/?p=2663#comment-21252</guid>
		<description><![CDATA[I&#039;d love to fill you in on how we did the Yahoo Pipes part (actually it was one man&#039;s work, http://twitter.com/royalbacon), but it turns out we&#039;re not using that anymore. We&#039;ve gone with handcoding a way to give attributions to the tweets that link to the employee&#039;s page on the corporate website, while linking to the tweet in Twitter via the date stamp.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;d love to fill you in on how we did the Yahoo Pipes part (actually it was one man&#8217;s work, <a href="http://twitter.com/royalbacon" rel="nofollow">http://twitter.com/royalbacon</a>), but it turns out we&#8217;re not using that anymore. We&#8217;ve gone with handcoding a way to give attributions to the tweets that link to the employee&#8217;s page on the corporate website, while linking to the tweet in Twitter via the date stamp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kegill</title>
		<link>http://wiredpen.com/2010/02/20/aggregating-organizational-tweets/#comment-21237</link>
		<dc:creator><![CDATA[kegill]]></dc:creator>
		<pubDate>Sun, 21 Feb 2010 22:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://wiredpen.com/?p=2663#comment-21237</guid>
		<description><![CDATA[I agree that there could easily be a lot of &#039;noise&#039; on a ComTweets channel. I know CoTweet but was not familiar with (nope, I had forgotten about!) ConnectTweet - thanks! Remembering the hashtag is a barrier, however.

Your comment about lists is also valid: these tools were birthed before Twitter launched lists. I don&#039;t understand why Twitter isn&#039;t providing the RSS link for lists. I&#039;ve used http://twiterlist2rss.appspot.com/ to create RSS feeds for lists where I have an interest.

Do you have a tutorial on how you did that with Yahoo Pipes? ;-)]]></description>
		<content:encoded><![CDATA[<p>I agree that there could easily be a lot of &#8216;noise&#8217; on a ComTweets channel. I know CoTweet but was not familiar with (nope, I had forgotten about!) ConnectTweet &#8211; thanks! Remembering the hashtag is a barrier, however.</p>
<p>Your comment about lists is also valid: these tools were birthed before Twitter launched lists. I don&#8217;t understand why Twitter isn&#8217;t providing the RSS link for lists. I&#8217;ve used <a href="http://twiterlist2rss.appspot.com/" rel="nofollow">http://twiterlist2rss.appspot.com/</a> to create RSS feeds for lists where I have an interest.</p>
<p>Do you have a tutorial on how you did that with Yahoo Pipes? ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aggregating Organizational Tweets — UW Twitter Book</title>
		<link>http://wiredpen.com/2010/02/20/aggregating-organizational-tweets/#comment-21236</link>
		<dc:creator><![CDATA[Aggregating Organizational Tweets — UW Twitter Book]]></dc:creator>
		<pubDate>Sun, 21 Feb 2010 22:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://wiredpen.com/?p=2663#comment-21236</guid>
		<description><![CDATA[[...] This post first appeared at WiredPen. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This post first appeared at WiredPen. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: luisantezana</title>
		<link>http://wiredpen.com/2010/02/20/aggregating-organizational-tweets/#comment-21233</link>
		<dc:creator><![CDATA[luisantezana]]></dc:creator>
		<pubDate>Sun, 21 Feb 2010 21:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://wiredpen.com/?p=2663#comment-21233</guid>
		<description><![CDATA[I do see usefulness for large organizations as a way to for employees to discover each other&#039;s accounts, if your employees actually use Twitter accounts under their work addresses.

Another of ComTweet&#039;s uses is to serve as a voice of the company. This would work if employees tweet under work e-mail-aligned accounts and all/most of their tweets are relevant, but I think that&#039;s a fringe case in practice, if I understand the service correctly. 

I&#039;ll write from the perspective of using a tool for company visibility. The obvious goal then is to have a visible and accessible voice of the business, and I&#039;d add that the voice should be intentional and relevant.

We use a service called ConnectTweet (it&#039;s like CoTweet but was available earlier and we&#039;ve stuck with it), which allows a central admin to add select Twitter accounts to a list of approved contributors as the voice for a single company Twitter account. The individual tweeters designate specific tweets to appear in the company Twitter feed by ending tweets with a self-defined hashtag, in our case #mstrm. ConnectTweet knows to publish all those tweets from the company Twitter account and to add a self-defined attribution, in our case &quot;via @username.&quot; That stream becomes the hive mind of our employees but only the tweets they wish to share for that purpose. This reduces noise and increases focus. We then take that stream and process it through a Yahoo Pipe for additional formatting and republish it on a page on our company website. This increases visibility/niftiness. You can see our stream at http://twitter.com/m_stream. (That said, I do often forget to use the #mstrm tag :)

The other way to get visibility for company tweeters is to use the company Twitter account to create a Twitter list of the company&#039;s employees. This list is publicly subscribable/RSS-enabled, so it&#039;s easy to access after the initial discovery.

Neither of these exactly duplicates ComTweets, they&#039;re just different ways to get similar exposure for company tweeters.


Luis Antezana

http://methodologie.com
http://twitter.com/luckylou]]></description>
		<content:encoded><![CDATA[<p>I do see usefulness for large organizations as a way to for employees to discover each other&#8217;s accounts, if your employees actually use Twitter accounts under their work addresses.</p>
<p>Another of ComTweet&#8217;s uses is to serve as a voice of the company. This would work if employees tweet under work e-mail-aligned accounts and all/most of their tweets are relevant, but I think that&#8217;s a fringe case in practice, if I understand the service correctly. </p>
<p>I&#8217;ll write from the perspective of using a tool for company visibility. The obvious goal then is to have a visible and accessible voice of the business, and I&#8217;d add that the voice should be intentional and relevant.</p>
<p>We use a service called ConnectTweet (it&#8217;s like CoTweet but was available earlier and we&#8217;ve stuck with it), which allows a central admin to add select Twitter accounts to a list of approved contributors as the voice for a single company Twitter account. The individual tweeters designate specific tweets to appear in the company Twitter feed by ending tweets with a self-defined hashtag, in our case #mstrm. ConnectTweet knows to publish all those tweets from the company Twitter account and to add a self-defined attribution, in our case &#8220;via @username.&#8221; That stream becomes the hive mind of our employees but only the tweets they wish to share for that purpose. This reduces noise and increases focus. We then take that stream and process it through a Yahoo Pipe for additional formatting and republish it on a page on our company website. This increases visibility/niftiness. You can see our stream at <a href="http://twitter.com/m_stream" rel="nofollow">http://twitter.com/m_stream</a>. (That said, I do often forget to use the #mstrm tag :)</p>
<p>The other way to get visibility for company tweeters is to use the company Twitter account to create a Twitter list of the company&#8217;s employees. This list is publicly subscribable/RSS-enabled, so it&#8217;s easy to access after the initial discovery.</p>
<p>Neither of these exactly duplicates ComTweets, they&#8217;re just different ways to get similar exposure for company tweeters.</p>
<p>Luis Antezana</p>
<p><a href="http://methodologie.com" rel="nofollow">http://methodologie.com</a><br />
<a href="http://twitter.com/luckylou" rel="nofollow">http://twitter.com/luckylou</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

