Zyb is saying (I think) that the failure occurred silently. That is, it didn't announce that it wasn't saving. So your method would fail just like the DropBox method, because no new edits were being saved to disk.
Maybe TW needs to make a bigger fuss when a save fails so that the user knows to stop working. It already does this when running on node.js. -- Mark On Friday, March 9, 2018 at 11:12:37 AM UTC-8, @TiddlyTweeter wrote: > > Ciao Zyb > > To the people suggesting backups: You’re aware, right? that we are talking >> about unsaved (and unsavable), ‘dirty’ files here, for which the backup >> process (simultaneous to the save) has already failed >> > > ABSOLUTELY. That is why I run redundant backup that checks for changes > every 5 minutes. External backup is simply the reliable method with the > least hassle. > > The other writers who are talking about JSON scenarios are correct, but > overlooking breakdown scenarios. > > Best wishes > Josiah > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/f9efdf75-2387-4074-9df1-bc918713c1e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
