<?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 tags changed the way we work</title>
	<atom:link href="http://blog.nodeta.fi/2009/10/28/flowdock-how-tags-changed-the-way-we-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nodeta.fi/2009/10/28/flowdock-how-tags-changed-the-way-we-work/</link>
	<description>on Rails</description>
	<lastBuildDate>Mon, 06 Sep 2010 07:01:37 +0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JAVA_MONKEY</title>
		<link>http://blog.nodeta.fi/2009/10/28/flowdock-how-tags-changed-the-way-we-work/comment-page-1/#comment-34569</link>
		<dc:creator>JAVA_MONKEY</dc:creator>
		<pubDate>Tue, 04 May 2010 03:15:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nodeta.fi/?p=283#comment-34569</guid>
		<description>P.S. I&#039;ve assigned a Flowdock (Beta) account for our company and another for an association where I am on the Board of Directors.  You&#039;ll find Java_Monkey at Flowdock&#039;s UserVoice, too.  I&#039;m interested in Flowdock&#039;s potential for our project management, using it as our &quot;War Room&quot; or &quot;Project Room&quot;.  We tested GoogleWave and still have some back-of-office functions situated there, but I hope to move everyone to Flowdock, if it tests well.  Best to everyone at Nodeta/Flowdock.  Onnea!</description>
		<content:encoded><![CDATA[<p>P.S. I&#8217;ve assigned a Flowdock (Beta) account for our company and another for an association where I am on the Board of Directors.  You&#8217;ll find Java_Monkey at Flowdock&#8217;s UserVoice, too.  I&#8217;m interested in Flowdock&#8217;s potential for our project management, using it as our &#8220;War Room&#8221; or &#8220;Project Room&#8221;.  We tested GoogleWave and still have some back-of-office functions situated there, but I hope to move everyone to Flowdock, if it tests well.  Best to everyone at Nodeta/Flowdock.  Onnea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JAVA_MONKEY</title>
		<link>http://blog.nodeta.fi/2009/10/28/flowdock-how-tags-changed-the-way-we-work/comment-page-1/#comment-34568</link>
		<dc:creator>JAVA_MONKEY</dc:creator>
		<pubDate>Tue, 04 May 2010 03:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nodeta.fi/?p=283#comment-34568</guid>
		<description>I&#039;m British, working in the US on a US-version Mac, but dealing solely in UK and European matters.  Hence, my system preferences for the keyboard are set to &quot;British&quot; and what would normally be my hashtag key (uppercase 3) is interpreted as &quot;£&quot;.  I&#039;m sure it must be glaringly obvious -- and hopefully, fast and simple, too -- but what are my tagging options to quickly yield # without having to resort to using the Character Palette (as I just had to do).

Ta!</description>
		<content:encoded><![CDATA[<p>I&#8217;m British, working in the US on a US-version Mac, but dealing solely in UK and European matters.  Hence, my system preferences for the keyboard are set to &#8220;British&#8221; and what would normally be my hashtag key (uppercase 3) is interpreted as &#8220;£&#8221;.  I&#8217;m sure it must be glaringly obvious &#8212; and hopefully, fast and simple, too &#8212; but what are my tagging options to quickly yield # without having to resort to using the Character Palette (as I just had to do).</p>
<p>Ta!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nodeta &#187; Blog Archive &#187; Track your brands with Flowdock</title>
		<link>http://blog.nodeta.fi/2009/10/28/flowdock-how-tags-changed-the-way-we-work/comment-page-1/#comment-29947</link>
		<dc:creator>Nodeta &#187; Blog Archive &#187; Track your brands with Flowdock</dc:creator>
		<pubDate>Tue, 02 Mar 2010 19:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nodeta.fi/?p=283#comment-29947</guid>
		<description>[...] the best group messenger in the world, but it can be so much more. We&#8217;ve previously covered using tags to abolish the barrier of reporting bugs, and now I&#8217;ll show how you can make your team act as a single unit in tracking, creating, [...]</description>
		<content:encoded><![CDATA[<p>[...] the best group messenger in the world, but it can be so much more. We&#8217;ve previously covered using tags to abolish the barrier of reporting bugs, and now I&#8217;ll show how you can make your team act as a single unit in tracking, creating, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antti</title>
		<link>http://blog.nodeta.fi/2009/10/28/flowdock-how-tags-changed-the-way-we-work/comment-page-1/#comment-22857</link>
		<dc:creator>Antti</dc:creator>
		<pubDate>Wed, 28 Oct 2009 12:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nodeta.fi/?p=283#comment-22857</guid>
		<description>Cool! I&#039;m currently working on my master&#039;s thesis about content annotation in Kassi service (http://kassi.sizl.org) and I have been thinking that some kind of tagging will be needed in Kassi also. What I have not yet finalized is how it should be done in the user interface, but reading this certainly made me think that just inserting tags with # in front of them (like in Twitter and apparently in Flowdock) could be a handy way of doing that. At least it could be allowed as one possible way of tagging content.

Flowdock seems very interesting, I&#039;m eager to see the beta!</description>
		<content:encoded><![CDATA[<p>Cool! I&#8217;m currently working on my master&#8217;s thesis about content annotation in Kassi service (<a href="http://kassi.sizl.org" rel="nofollow">http://kassi.sizl.org</a>) and I have been thinking that some kind of tagging will be needed in Kassi also. What I have not yet finalized is how it should be done in the user interface, but reading this certainly made me think that just inserting tags with # in front of them (like in Twitter and apparently in Flowdock) could be a handy way of doing that. At least it could be allowed as one possible way of tagging content.</p>
<p>Flowdock seems very interesting, I&#8217;m eager to see the beta!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
