<?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: Microblogging: Making improbable Communication probable</title>
	<atom:link href="http://ubimic.org/en/2010/01/microblogging-making-improbable-communication-probable/feed/" rel="self" type="application/rss+xml" />
	<link>http://ubimic.org/en/2010/01/microblogging-making-improbable-communication-probable/</link>
	<description></description>
	<lastBuildDate>Thu, 03 Jun 2010 02:26:11 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stefan Hauptmann</title>
		<link>http://ubimic.org/en/2010/01/microblogging-making-improbable-communication-probable/comment-page-1/#comment-13</link>
		<dc:creator>Stefan Hauptmann</dc:creator>
		<pubDate>Thu, 09 Sep 2010 15:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://ubimic.org/?p=350#comment-13</guid>
		<description>Thanks, Dirk, for your comment. Your numbers are interesting. We, too, think that restrictions like limited characters are a problem - therefore our recommendation to introduce &#039;light&#039; restrictions like a colour-change.
Your 2nd point, informal vs. formal communication: Microblogging is a tool. And as all tools can be used very differently (think of knifes), so an microblogging environment can be used differently, too. I think organization sciences that deal with formal vs. informal communication can help us to shape the right tools for the future. Contributing here is one part of our agenda. 
Regards Stefan</description>
		<content:encoded><![CDATA[<p>Thanks, Dirk, for your comment. Your numbers are interesting. We, too, think that restrictions like limited characters are a problem &#8211; therefore our recommendation to introduce &#8216;light&#8217; restrictions like a colour-change.<br />
Your 2nd point, informal vs. formal communication: Microblogging is a tool. And as all tools can be used very differently (think of knifes), so an microblogging environment can be used differently, too. I think organization sciences that deal with formal vs. informal communication can help us to shape the right tools for the future. Contributing here is one part of our agenda.<br />
Regards Stefan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Röhrborn</title>
		<link>http://ubimic.org/en/2010/01/microblogging-making-improbable-communication-probable/comment-page-1/#comment-12</link>
		<dc:creator>Dirk Röhrborn</dc:creator>
		<pubDate>Thu, 09 Sep 2010 11:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://ubimic.org/?p=350#comment-12</guid>
		<description>Thank you, Stefan, for this interesting insight. We have analysed out internal Communote system and found that more than 57 % of all microblog post have less than 300 characters, 67 % less than 400 and about 75 % less than 500. So 400 chars might be a pragmatic size. From my experience it is not really helpful to restrict this number and rather make sure that long posts do not disturb the readability of others. We will blog soon in more detail on this issue.
I have long been of the opinion that microblogging is mainly informal communication and thus, &quot;microblogging-posts can be ignored without having negative consequences&quot; as you state. However, I have to admit that we are more and more using our Communote system for formal team communication, too. More and more messages that would have been transmitted via email before are now distributed via the microblog. This also includes formal messages, e.g. project status updates, problem escalations, communication rules etc. Once a microblog serves as the main communications medium for a project team members cannot ignore these messages.</description>
		<content:encoded><![CDATA[<p>Thank you, Stefan, for this interesting insight. We have analysed out internal Communote system and found that more than 57 % of all microblog post have less than 300 characters, 67 % less than 400 and about 75 % less than 500. So 400 chars might be a pragmatic size. From my experience it is not really helpful to restrict this number and rather make sure that long posts do not disturb the readability of others. We will blog soon in more detail on this issue.<br />
I have long been of the opinion that microblogging is mainly informal communication and thus, &#8220;microblogging-posts can be ignored without having negative consequences&#8221; as you state. However, I have to admit that we are more and more using our Communote system for formal team communication, too. More and more messages that would have been transmitted via email before are now distributed via the microblog. This also includes formal messages, e.g. project status updates, problem escalations, communication rules etc. Once a microblog serves as the main communications medium for a project team members cannot ignore these messages.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
