This is not really correct. Although TW appears to be "all mixed together" on the surface, there is actually a very strict separation of concerns in the architecture. Updating of the wiki-store is done (as far as I understand it) by the syncer, employing a suitable sync-adapter. In standalone TW, the wiki-store is a dedicated DIV in the HTML but the node.js version uses a different sync adaptor to update individual files on the silesystem.
It should be possible to write a sync-adaptor to store your tiddlers anywhere - there is a link on tw.com to an indexedDB adapter implementation http://tiddlywiki.com/#IndexedDB%20Plugin%20by%20Andreas%20Abeck and I know that, last year, Danielo Rodriguez was working on a CouchDB/PouchDB adapter. https://groups.google.com/forum/#!searchin/Tiddlywiki/couchdb%7Csort:date Personally I think it would be really interesting to see how an adapter for IPFS might work. Content published onto IPFS is addressed by it's hash. If we published individual tiddlers onto it and then the 'container' TW code to assemble them, you'd have an atomised document, distributed across the internet and when someone opens it, all the content would get pulled in from whichever copy is fastest (it's like a cross between bit-torrent, git and the web). I have never seen any work/discussion about using TW as a data-source, but I bet if anyone knows, it would be Eric because I think a lot of his work with TW2 was data-driven. Regards, Richard -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0d0437cb-b3bf-459b-97ce-32f8fefb536d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
