<?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: Searching for a Perfect Notetaking Solution: TiddlyWiki</title>
	<atom:link href="http://redmonk.com/sogrady/2006/03/14/searching-for-a-perfect-notetaking-solution-tiddlywiki/feed/" rel="self" type="application/rss+xml" />
	<link>http://redmonk.com/sogrady/2006/03/14/searching-for-a-perfect-notetaking-solution-tiddlywiki/</link>
	<description>because technology is just another ecosystem</description>
	<lastBuildDate>Wed, 25 Jan 2012 16:19:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: didier</title>
		<link>http://redmonk.com/sogrady/2006/03/14/searching-for-a-perfect-notetaking-solution-tiddlywiki/comment-page-1/#comment-1770</link>
		<dc:creator>didier</dc:creator>
		<pubDate>Sat, 18 Mar 2006 06:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/wp/?p=763#comment-1770</guid>
		<description>Hey Stephen, I&#039;ve been using TW for taking notes and scalability is a concern too. Here are a couple of links that might be relevant for this issue:

* A TW thread (http://groups.google.com/group/TiddlyWiki/browse_thread/thread/e0a36719941c340c/cc6c9cc8065566a9?q=scalability&amp;rnum=2#cc6c9cc8065566a9) on Google Groups mentions some interesting facts about how TW scales. It seems that things get bad around 600kb of text. There are also some ideas of how to get around that.

* There&#039;s a server-side, non-DB dependant version of TW called MyWiki (http://aasted.org/wiki/). It uses PHP and flat files to store content. I have a feeling it should be slightly more efficient than TW.  

</description>
		<content:encoded><![CDATA[<p>Hey Stephen, I&#8217;ve been using TW for taking notes and scalability is a concern too. Here are a couple of links that might be relevant for this issue:</p>
<p>* A TW thread (<a href="http://groups.google.com/group/TiddlyWiki/browse_thread/thread/e0a36719941c340c/cc6c9cc8065566a9?q=scalability&#038;rnum=2#cc6c9cc8065566a9" >http://groups.google.com/group/TiddlyWiki/browse_thread/thread/e0a36719941c340c/cc6c9cc8065566a9?q=scalability&#038;rnum=2#cc6c9cc8065566a9</a>) on Google Groups mentions some interesting facts about how TW scales. It seems that things get bad around 600kb of text. There are also some ideas of how to get around that.</p>
<p>* There&#8217;s a server-side, non-DB dependant version of TW called MyWiki (<a href="http://aasted.org/wiki/" >http://aasted.org/wiki/</a>). It uses PHP and flat files to store content. I have a feeling it should be slightly more efficient than TW.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephen o'grady</title>
		<link>http://redmonk.com/sogrady/2006/03/14/searching-for-a-perfect-notetaking-solution-tiddlywiki/comment-page-1/#comment-1769</link>
		<dc:creator>stephen o'grady</dc:creator>
		<pubDate>Thu, 16 Mar 2006 19:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/wp/?p=763#comment-1769</guid>
		<description>Luis: i guess it&#039;s using the mechanism that Jack describes, but TiddlyWiki does indeed have autosave capability. it&#039;s great. re: the cron job option, i&#039;m agreed; what can&#039;t be done easily, i think, is handling a scenario where you&#039;re *editing* the different files and then synicing them. that&#039;d be harder. 

Jack: thanks for dropping the knowledge, much appreciated. just added you, so will be tracking your efforts to make TW more scalable. 

Cote: always happy to be your tester ;)</description>
		<content:encoded><![CDATA[<p>Luis: i guess it&#8217;s using the mechanism that Jack describes, but TiddlyWiki does indeed have autosave capability. it&#8217;s great. re: the cron job option, i&#8217;m agreed; what can&#8217;t be done easily, i think, is handling a scenario where you&#8217;re *editing* the different files and then synicing them. that&#8217;d be harder. </p>
<p>Jack: thanks for dropping the knowledge, much appreciated. just added you, so will be tracking your efforts to make TW more scalable. </p>
<p>Cote: always happy to be your tester <img src='http://redmonk.com/sogrady/wp/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cote'</title>
		<link>http://redmonk.com/sogrady/2006/03/14/searching-for-a-perfect-notetaking-solution-tiddlywiki/comment-page-1/#comment-1768</link>
		<dc:creator>Cote'</dc:creator>
		<pubDate>Wed, 15 Mar 2006 22:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/wp/?p=763#comment-1768</guid>
		<description>I&#039;ve thought of using TiddlyWiki, but I didn&#039;t want to guinea pig the scalability problem...so, I&#039;m glad someone else took that on ;)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve thought of using TiddlyWiki, but I didn&#8217;t want to guinea pig the scalability problem&#8230;so, I&#8217;m glad someone else took that on <img src='http://redmonk.com/sogrady/wp/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://redmonk.com/sogrady/2006/03/14/searching-for-a-perfect-notetaking-solution-tiddlywiki/comment-page-1/#comment-1767</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Wed, 15 Mar 2006 12:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/wp/?p=763#comment-1767</guid>
		<description>Luis: TiddlyWiki&#039;s save uses ActiveX in IE and a similar mechanism in FireFox. Both require you to approve the save. Firefox however has a permissions model and you only need to do this once. TW is best used with FireFox.

sogrady: I am also a big TW Fan and use it daily. Scalability is an issue however but Wiki&#039;s can be surprisingly large before it really kicks in because you are just working with text. However, I am working on a project to provide a server side engine for TW where all tiddlers are stored in a DB. The idea is to improve scalability as well as enjoy some of the integration advantages a database brings. One of these is of course the seperation of code and data which in TW is in one file.
Jack
http://ajaxwiki.blogsome.com/</description>
		<content:encoded><![CDATA[<p>Luis: TiddlyWiki&#8217;s save uses ActiveX in IE and a similar mechanism in FireFox. Both require you to approve the save. Firefox however has a permissions model and you only need to do this once. TW is best used with FireFox.</p>
<p>sogrady: I am also a big TW Fan and use it daily. Scalability is an issue however but Wiki&#8217;s can be surprisingly large before it really kicks in because you are just working with text. However, I am working on a project to provide a server side engine for TW where all tiddlers are stored in a DB. The idea is to improve scalability as well as enjoy some of the integration advantages a database brings. One of these is of course the seperation of code and data which in TW is in one file.<br />
Jack<br />
<a href="http://ajaxwiki.blogsome.com/" >http://ajaxwiki.blogsome.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://redmonk.com/sogrady/2006/03/14/searching-for-a-perfect-notetaking-solution-tiddlywiki/comment-page-1/#comment-1766</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Wed, 15 Mar 2006 01:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/wp/?p=763#comment-1766</guid>
		<description>I had looked at it, but dismissed it because (as I understood it) you had to use the browser&#039;s file-&gt;save function to save the content, which struck me as actually more dangerous than not auto-saving, because I&#039;d get into bad habits of not saving regularly and then be totally hosed if my laptop lost battery life or my browser crashed. If it has somehow managed to add actual autosave-to-disk functionality (which I have no idea how it would do, and I&#039;d frankly be troubled if there are ways for javascript to do it), I&#039;d have to look again.

[In support of tiddlywiki and accessing it in multiple locations, I&#039;m sure you could whip something up with cron and rsync that would throw the tiddlywiki up on your website regularly.]</description>
		<content:encoded><![CDATA[<p>I had looked at it, but dismissed it because (as I understood it) you had to use the browser&#8217;s file-&gt;save function to save the content, which struck me as actually more dangerous than not auto-saving, because I&#8217;d get into bad habits of not saving regularly and then be totally hosed if my laptop lost battery life or my browser crashed. If it has somehow managed to add actual autosave-to-disk functionality (which I have no idea how it would do, and I&#8217;d frankly be troubled if there are ways for javascript to do it), I&#8217;d have to look again.</p>
<p>[In support of tiddlywiki and accessing it in multiple locations, I'm sure you could whip something up with cron and rsync that would throw the tiddlywiki up on your website regularly.]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Object Caching 296/298 objects using xcache

Served from: redmonk.com @ 2012-02-14 10:27:22 -->
