Mark/Jed, On Tuesday, April 28, 2020 at 7:53:34 AM UTC-7, Jed Carty wrote: >> >> being lost without warning, the wiki is only available in that browser on >> that computer, it isn't sharable unless you use some other saver, like the >> built-in download saver, to get a copy that you can then move around or >> share. >> > > But in terms of an initial user experience, there's only one easy > extension to install, and they're good to go. Yes, down the road they'll > have to learn how to save or export the file, but it would give an easy > first step. And for people who never move around, it may be the only step > they need. >
Of course when it comes to single file wikis once loaded even without Local storage they continue to operate and accept changes even if the the save mechanism fails. The browser download option remains and changes could be exported as JSON files. To me this is already a degree of local first, perhaps which we have not fully made use of. For example; Load a wiki from a URL on your mobile and make changes, disconnect from the network and keep using the wiki indefinitely (don't close the window and don't let the phone restart). Now return to a stable internet connection and save the wiki at its original address. If we had a invisible save changes only on our mobile we could restore only if necessary we are a long way there. Jed, I mentioned you here, because I wonder if there is a way that a bob/node served wiki could wholey move into browser memory pending reconnection, as is the case for single file wikis, not withstanding this could render the wiki single user. Regards 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/a0847dfc-2c14-4732-830b-5ae41199d708%40googlegroups.com.
