Folks, This post is seeking input from the community to overcome what I perceive to be the last big issue in saving. It may seem only suited to experienced users but perhaps you know something we don't, so please be brave and contribute.
I may have an opportunity in coming months to work with a team of videographers in their off season. They do "things for good" and my thought was to build a nice application (on tiddlywiki) for people to explore how they or their business can participate in reaching the *Sustainable Development Goals (SDG's)*. This will promote the SDG's, their work, my work and the power of TiddlyWiki, but there seems to me, to still be an elephant in the room - saving. *How do we enable saving tiddlywikis for naive and casual users?* To be sure, I am across most saving mechanisms, and some are very good and quite easy to set up a very sophisticated solution, I use Timimi, TiddlyServer, TiddlyDesktop and Bob.exe Imagine someone visits my SDG app online - They could use it and apply changes but not save it - With local storage and save some changes in the browser but they may be lost later - They Can download it easily enough, even with their in browser or local storage content - But if they wish to open it again, make changes and save they then need to consider this https://tiddlywiki.com/#GettingStarted - scary for many. Basically I think tiddlywiki is brilliant and we have lots of wonderful options for saving, once someone gets involved with the ecosystem, I believe any nodeJS solution is hard to secure on the internet and like NoteSelf we have to manage the server, but it seems we are so close to a better single file solution (My Opinion). I know some saving mechanisms come close to helping *naive and casual users* however their remains a need to take unfamiliar steps, that can be quite fragile, especially to those not overly computer literate. Saving under downloads folders, running batches and installing local apps are all impediments to *naive and casual users* in my view, as this becomes Operating system dependant, demands more trust, will not work in many locked down cases and more. I am starting this thread to try and inspire some serious creativity to overcome this barrier. Here are some ideas floating in my head but I am keen to hear from you. - Any idea is a good idea - A diversity of ideas in needed - We may need to "think outside the box" - Can an existing solution be better engineered to meet these goals? Some of my own musings - One approach may be to never download the whole wiki, but store the changes in a separate file that is automatically loaded over the in browser one, and saved only by saving changes back to the nominated file. - Building all the necessary content to install Timimi or another saver from the single wiki (No other document or external info required) Not yet chrome and IE - A Form of bob.exe/TiddlyDesktop that can be loaded with a custom tiddlywiki that shows only that wiki unless some settings are changed in the control panel. Ie a single local installable. - A Way of packaging a TiddlyWiki with Node.exe and hosting on a port that will not clash with other server hosts, perhaps an packaged extension of TiddlySaver. - I was inspired to open this up to the community after playing with bookmarklets and Jeremy's solution <https://groups.google.com/forum/#!searchin/tiddlywiki/bookmarklets%7Csort:date/tiddlywiki/pTInT6T4gMs/iJV5P-RPAgAJ> because javascript can be loaded into bookmarks I wonder if it could be used to save changes to local tiddlywiki files and reimport on click. - I also looked at solutions such as https://en.wikipedia.org/wiki/IMacros which suggests there may be other ways to achieve the desired results. - IPFS, BeakerBrowser, CouchDB or saving to a MYSQL or even a wordpress database? All I want for Christmas is a simple way for *naive and casual users *to save their tiddlywiki (again and again) Yours Sincerely Tony -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/4567ad22-1709-4373-b75d-a40812fed942%40googlegroups.com.
