<?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: CCText catches my attention.</title>
	<atom:link href="http://www.gilyehuda.com/2009/10/12/cctext/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gilyehuda.com/2009/10/12/cctext/</link>
	<description>A blog about collaboration, trust, open source, workplace, and community behaviors.</description>
	<lastBuildDate>Thu, 02 Feb 2012 15:35:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Gil Yehuda</title>
		<link>http://www.gilyehuda.com/2009/10/12/cctext/comment-page-1/#comment-2761</link>
		<dc:creator>Gil Yehuda</dc:creator>
		<pubDate>Tue, 13 Oct 2009 02:22:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.gilyehuda.com/?p=814#comment-2761</guid>
		<description>Thanks for the comment Steven.  I guess I try to look for the positive, so that&#039;s why I commented that UI comes across pretty cleanly and I found the interaction to be fast.  Yet, at the end of the day, this product did not seem destined for mass-success in its current go-to-market strategy. Hence my best suggestion would be to sell the technology, not to try to go retail - or package the technology with some other process (that has more market appeal).  I did not comment in the blog post that the pricing strategy did not excite me either.  And yes, the markup thing is a problem, one they try to cover with with the nifty preview.  Had this been around 6 years ago, I think people would have loved it (since it is so much better than most of the available options that were around at that time).  It seemed like they needed to really think through what options are out there and how they can stand out above the rest.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Steven.  I guess I try to look for the positive, so that&#8217;s why I commented that UI comes across pretty cleanly and I found the interaction to be fast.  Yet, at the end of the day, this product did not seem destined for mass-success in its current go-to-market strategy. Hence my best suggestion would be to sell the technology, not to try to go retail &#8211; or package the technology with some other process (that has more market appeal).  I did not comment in the blog post that the pricing strategy did not excite me either.  And yes, the markup thing is a problem, one they try to cover with with the nifty preview.  Had this been around 6 years ago, I think people would have loved it (since it is so much better than most of the available options that were around at that time).  It seemed like they needed to really think through what options are out there and how they can stand out above the rest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Walling</title>
		<link>http://www.gilyehuda.com/2009/10/12/cctext/comment-page-1/#comment-2760</link>
		<dc:creator>Steven Walling</dc:creator>
		<pubDate>Tue, 13 Oct 2009 01:58:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.gilyehuda.com/?p=814#comment-2760</guid>
		<description>I first took a look at CCText a couple months ago, and was not impressed either as a wiki geek or a business user. 

When I tested it out I didn&#039;t find it to be faster &lt;em&gt;at all&lt;/em&gt; than good WYSIWYG wikis (i.e. not the systems slapped on top of legacy MediaWiki), though admittedly this may have improved in couple of months that have passed since then.

More importantly, markup is an impediment to use by non-geeks. I asked the people behind CCText directly about it, and apparently they really think markup is in the best interest of the average joe. 

On the up side for CCText, I thought it was had great design and overall user experience, which is more than some of the enterprise wikis out there can easily claim. I think things like the markup are huge barriers to overcome, but there&#039;s still plenty of room in the wiki market for a smart newcomer.</description>
		<content:encoded><![CDATA[<p>I first took a look at CCText a couple months ago, and was not impressed either as a wiki geek or a business user. </p>
<p>When I tested it out I didn&#8217;t find it to be faster <em>at all</em> than good WYSIWYG wikis (i.e. not the systems slapped on top of legacy MediaWiki), though admittedly this may have improved in couple of months that have passed since then.</p>
<p>More importantly, markup is an impediment to use by non-geeks. I asked the people behind CCText directly about it, and apparently they really think markup is in the best interest of the average joe. </p>
<p>On the up side for CCText, I thought it was had great design and overall user experience, which is more than some of the enterprise wikis out there can easily claim. I think things like the markup are huge barriers to overcome, but there&#8217;s still plenty of room in the wiki market for a smart newcomer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention CCText catches my attention. -- Topsy.com</title>
		<link>http://www.gilyehuda.com/2009/10/12/cctext/comment-page-1/#comment-2758</link>
		<dc:creator>Tweets that mention CCText catches my attention. -- Topsy.com</dc:creator>
		<pubDate>Tue, 13 Oct 2009 01:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.gilyehuda.com/?p=814#comment-2758</guid>
		<description>[...] This post was mentioned on Twitter by C.A.M.. C.A.M. said: another one of those apps... RT @gyehuda: Blog post #e20 CCText catches my attention. I recently had a briefing by... http://ow.ly/15Uw5U [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by C.A.M.. C.A.M. said: another one of those apps&#8230; RT @gyehuda: Blog post #e20 CCText catches my attention. I recently had a briefing by&#8230; <a href="http://ow.ly/15Uw5U" rel="nofollow">http://ow.ly/15Uw5U</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

