I have to admit I find myself grabbing a copy from tiddlywiki.com or tiddlywiki.com/prerelease for quick note taking, or experimenting, and using the default “download saver” often, but not as often as I’m starting or restarting the local node server.
But I think Offray puts it well in their new thread:
As usual, we try to simplify infrastructure to amplify/diversify participation.
Some people are more used to an experience where the data-storage is handled “in the background”, and even juggling multiple standalone wiki files (and their backups) can be overwhelming. I think single file wikis are one of the key features of tiddlywiki. But it has taken me a while to understand how tiddlywiki renders an HTML page from-itself-in-active-memory (standalone download saver, or when you first hit that page load request on the node server), and that this process of filtered-transclution-template-rendering can be used to render OTHER static HTML content. Now I want TWaaS, because exporting standalone “published” wikis with a subset of content, or as deep-storage backups is a great idea.
More thoughts after my job interview. 