<?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: The Future of Microblogging</title>
	<atom:link href="http://www.stubbornmule.net/2008/08/microblogging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stubbornmule.net/2008/08/microblogging/</link>
	<description>The things that exercise my mind</description>
	<pubDate>Tue, 06 Jan 2009 11:49:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Molly</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1987</link>
		<dc:creator>Molly</dc:creator>
		<pubDate>Tue, 18 Nov 2008 09:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1987</guid>
		<description>@ Stubbornmule 
You're right.  In the end it is a microblogger in the sense that the technical workings behind the service is a twitter clone, but by customizing it and making the messages almost always private, it desocializes the microblog.  

The communication is site owner -&#62; user/ user -&#62;site owner, but never user  -&#62; user. I was afraid if we made user comments public, the service would turn into a sort-of trip advisor where everyone gives their two cents about the establishment (these reviews could be phony or vulgar and would need moderation). 

Instead, all user comments are either private notes for themself or direct questions/requests to the hotel (only the hotel owner sees these requests, they are not public). 

As far as using the structure of a discussion forum, I was thinking that since the comments are taggable, the entries will be organized into subjects in this way. I thought this would be better than setting up a mini-forum for each hotel structure in which the users have to respond to a particular thread.  (though they could also create a new thread...) I like the freedom of the microblogger better. Do you think more structure would be better? 

It will also be possible to rank comments according to their importance so users can remember which comments are  more important.

Perhaps we could add some suggestions about what to write/ask the hotels so that users have some focus. 

I am considering expanding the service so that it can be used on any site, not just for hotels, and so at first didn't want to limit the scope. But maybe you're right, users need some direction (like there is in a forum). 

Thanks again for sharing your thoughts!</description>
		<content:encoded><![CDATA[<p>@ Stubbornmule<br />
You&#8217;re right.  In the end it is a microblogger in the sense that the technical workings behind the service is a twitter clone, but by customizing it and making the messages almost always private, it desocializes the microblog.  </p>
<p>The communication is site owner -&gt; user/ user -&gt;site owner, but never user  -&gt; user. I was afraid if we made user comments public, the service would turn into a sort-of trip advisor where everyone gives their two cents about the establishment (these reviews could be phony or vulgar and would need moderation). </p>
<p>Instead, all user comments are either private notes for themself or direct questions/requests to the hotel (only the hotel owner sees these requests, they are not public). </p>
<p>As far as using the structure of a discussion forum, I was thinking that since the comments are taggable, the entries will be organized into subjects in this way. I thought this would be better than setting up a mini-forum for each hotel structure in which the users have to respond to a particular thread.  (though they could also create a new thread&#8230;) I like the freedom of the microblogger better. Do you think more structure would be better? </p>
<p>It will also be possible to rank comments according to their importance so users can remember which comments are  more important.</p>
<p>Perhaps we could add some suggestions about what to write/ask the hotels so that users have some focus. </p>
<p>I am considering expanding the service so that it can be used on any site, not just for hotels, and so at first didn&#8217;t want to limit the scope. But maybe you&#8217;re right, users need some direction (like there is in a forum). </p>
<p>Thanks again for sharing your thoughts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stubbornmule</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1980</link>
		<dc:creator>stubbornmule</dc:creator>
		<pubDate>Mon, 17 Nov 2008 12:05:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1980</guid>
		<description>@Molly: In that case, it sounds like you'd be using it more like a discussion forum. While a microblog can certainly work like that, you may want to consider whether you want some of the other features that a more traditional forum would offer, such as thread topics. In a forum, people can zero in on the particular topics of interest to them, while a microblog is a less structured conversation. If you don't feel that you need the structure, microblogs do have the advantage of being flexible for users: they can dip in and out, subscribe to rss feeds, search etc.</description>
		<content:encoded><![CDATA[<p>@Molly: In that case, it sounds like you&#8217;d be using it more like a discussion forum. While a microblog can certainly work like that, you may want to consider whether you want some of the other features that a more traditional forum would offer, such as thread topics. In a forum, people can zero in on the particular topics of interest to them, while a microblog is a less structured conversation. If you don&#8217;t feel that you need the structure, microblogs do have the advantage of being flexible for users: they can dip in and out, subscribe to rss feeds, search etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Molly</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1979</link>
		<dc:creator>Molly</dc:creator>
		<pubDate>Mon, 17 Nov 2008 11:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1979</guid>
		<description>@ stubbornmule Thanks for your input!  Good points about having a strong community to base the new venture on.  I hadn't considered the community aspect from that perspective. And now that I think about it, the service I'm planning isn't really meant to be community based.  In the sense that each hotel sees only responses/comments they've made and comments users have sent directly to them.  Every user will see only the comments they sent to hotels and all the comments they received from hotels.  (In reality it's the same microblog that everyone is using, but the comments are private so that only the two people involved in the communication see them.  There is also the option to make a post public, but I think the majority of the dialog will be private).  Do you think this type of microblog could perhaps be too individualized/too niche?)</description>
		<content:encoded><![CDATA[<p>@ stubbornmule Thanks for your input!  Good points about having a strong community to base the new venture on.  I hadn&#8217;t considered the community aspect from that perspective. And now that I think about it, the service I&#8217;m planning isn&#8217;t really meant to be community based.  In the sense that each hotel sees only responses/comments they&#8217;ve made and comments users have sent directly to them.  Every user will see only the comments they sent to hotels and all the comments they received from hotels.  (In reality it&#8217;s the same microblog that everyone is using, but the comments are private so that only the two people involved in the communication see them.  There is also the option to make a post public, but I think the majority of the dialog will be private).  Do you think this type of microblog could perhaps be too individualized/too niche?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stubbornmule</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1962</link>
		<dc:creator>stubbornmule</dc:creator>
		<pubDate>Sat, 15 Nov 2008 01:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1962</guid>
		<description>@Molly: I certainly think that niche microblogs have a lot of potential and the &lt;a href="http://army.twit.tv/" rel="nofollow"&gt;TWiT Army&lt;/a&gt; microblog is a good example. Of course, the key to success is to have a core group of people who are enthusiastic, motivated contributors who feel some sense of belonging to the community in question. To maximise the chances of this happening, it would help if there is already a community in some form (e.g. in the TWiT case these were regular listeners to the TWiT podcast) and then the microblog becomes a natural forum for these people to begin communication with one another.</description>
		<content:encoded><![CDATA[<p>@Molly: I certainly think that niche microblogs have a lot of potential and the <a href="http://army.twit.tv/">TWiT Army</a> microblog is a good example. Of course, the key to success is to have a core group of people who are enthusiastic, motivated contributors who feel some sense of belonging to the community in question. To maximise the chances of this happening, it would help if there is already a community in some form (e.g. in the TWiT case these were regular listeners to the TWiT podcast) and then the microblog becomes a natural forum for these people to begin communication with one another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Molly</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1961</link>
		<dc:creator>Molly</dc:creator>
		<pubDate>Fri, 14 Nov 2008 12:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1961</guid>
		<description>I enjoyed reading your article, especially because I'm thinking about starting an OpenMicroBlog especially designed for hotels.  You say that you think open microblogs are the way of the future, but do you think an open micro blog specifically geared towards a particular genre of people (mine would be used by hotels &#38; their clients) could work?  Or that it could stand a chance of being as successful as the more generic (unselective) microblogs?  My service would be free (using publicity to pay for the relatively small amount of money put into making the service).  I'd love to hear your opinion/thoughts on such a project!  Thanks</description>
		<content:encoded><![CDATA[<p>I enjoyed reading your article, especially because I&#8217;m thinking about starting an OpenMicroBlog especially designed for hotels.  You say that you think open microblogs are the way of the future, but do you think an open micro blog specifically geared towards a particular genre of people (mine would be used by hotels &amp; their clients) could work?  Or that it could stand a chance of being as successful as the more generic (unselective) microblogs?  My service would be free (using publicity to pay for the relatively small amount of money put into making the service).  I&#8217;d love to hear your opinion/thoughts on such a project!  Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deeta</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1774</link>
		<dc:creator>Deeta</dc:creator>
		<pubDate>Wed, 08 Oct 2008 12:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1774</guid>
		<description>You mentioned that IM never succeeded to move beyond its initial fragmentation. An attempt was made though. The jabber project released a federation-able IM server in 2000. (which lead to the XMPP standard). But since then user awareness of freedom issues have increased. So let us hope identi.ca and jabber subscriptions increase in the future and eclipse their closed counterparts ^-^</description>
		<content:encoded><![CDATA[<p>You mentioned that IM never succeeded to move beyond its initial fragmentation. An attempt was made though. The jabber project released a federation-able IM server in 2000. (which lead to the XMPP standard). But since then user awareness of freedom issues have increased. So let us hope identi.ca and jabber subscriptions increase in the future and eclipse their closed counterparts ^-^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riflessioni sul futuro di Twitter &#124; Microblogging.it</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1578</link>
		<dc:creator>Riflessioni sul futuro di Twitter &#124; Microblogging.it</dc:creator>
		<pubDate>Thu, 25 Sep 2008 12:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1578</guid>
		<description>[...] spunti di discussione li offre stubbornmule.net soffermandosi sul perché un modello chiuso come Twitter pagherà alla lunga la diffusione di un [...]</description>
		<content:encoded><![CDATA[<p>[...] spunti di discussione li offre stubbornmule.net soffermandosi sul perché un modello chiuso come Twitter pagherà alla lunga la diffusione di un [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randal L. Schwartz</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1458</link>
		<dc:creator>Randal L. Schwartz</dc:creator>
		<pubDate>Tue, 16 Sep 2008 14:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1458</guid>
		<description>Thanks for mentioning FLOSS Weekly!  And http://army.twit.tv/ is alive and well and being used by many people.</description>
		<content:encoded><![CDATA[<p>Thanks for mentioning FLOSS Weekly!  And <a href="http://army.twit.tv/">http://army.twit.tv/</a> is alive and well and being used by many people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aktueller Trend: Mikro-Blogging &#124; enterprise2null</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1417</link>
		<dc:creator>Aktueller Trend: Mikro-Blogging &#124; enterprise2null</dc:creator>
		<pubDate>Thu, 11 Sep 2008 20:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1417</guid>
		<description>[...] Carmody gibt einen kleinen Einblick in die Zukunft des Mikro-Bloggings und kommt auch zu der Einsicht, dass es über kurz oder lang [...]</description>
		<content:encoded><![CDATA[<p>[...] Carmody gibt einen kleinen Einblick in die Zukunft des Mikro-Bloggings und kommt auch zu der Einsicht, dass es über kurz oder lang [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Monetising Microblogs with Music? &#124; A Stubborn Mule's Perspective</title>
		<link>http://www.stubbornmule.net/2008/08/microblogging/comment-page-1/#comment-1343</link>
		<dc:creator>Monetising Microblogs with Music? &#124; A Stubborn Mule's Perspective</dc:creator>
		<pubDate>Thu, 04 Sep 2008 00:14:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornmule.net/?p=1087#comment-1343</guid>
		<description>[...] my recent post on the future of Microblogging, I expressed concerns about the viability of twitter given that they are yet to find a business [...]</description>
		<content:encoded><![CDATA[<p>[...] my recent post on the future of Microblogging, I expressed concerns about the viability of twitter given that they are yet to find a business [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
