You still haven't told us anything about your set-up. What browser are you using? What operating system? Is node.js running on the same machine or a different machine than the machine where you are working?
You say that you've lost 14 hours worth of work. But from your description, it sounds like only the current draft tiddler was lost. That would suggest that you're putting massive amounts of writing into a single tiddler. We have been told that using a single tiddler for a large document is not "the tiddlywiki way." I would worry that a large tiddler might get dropped by the node.js server, which I don't think was really ever meant for intensive server loading. Mark On Monday, December 12, 2016 at 2:56:34 AM UTC-8, Bruno Loff wrote: > > Sorry for the angry vent, that was uncalled for. I was really upset. > > The bug, wherever it lies, is hard to reproduce. > > I am running a node.js instance, and accessing it via the browser > (actually via a custom-made electron app which I had eventually planned to > release publicly). > > When I usually write a draft and close the app, the draft will still be > there when I return, provided that I wait enough for the "save" button to > turn from red to gray. So I became used to this feature. It seemed very > clever since TW will autosave very often while in the middle of editing, so > I had a false sense of security: "even if the latest edit I've made is > lost, that's at most one or two sentences, so no big deal". > > But at some point, maybe the application was closed in some abnormal way, > maybe it was killed, maybe it was closed before the red "save" button > turned back to gray, something like that, I couldn't reproduce the problem, > so I'm not sure when it occurs. Upon opening the wiki again, the draft > tiddler still exists, but it is no longer in "editing" mode when I return, > and, worst of all, its contents are completely empty. So I didn't just lose > the last few sentences I had written since the last successful autosave, I > lost all the changes that I had made since last clicking the "confirm > changes to this tiddler" button. When searching through the .tid files in > the wikifolder, indeed the "Draft of ... .tid" file was there, but it was > also empty. > > The behavior I expected was that, even if the changes I last made were not > properly saved, the draft should be at whichever state it was since the > last autosave happened. So for example, when the Sync machinery is working > to auto-save the contents of a draft, it should ensure that the operations > are "atomic", in some way, i.e., that the promise holds that it should > either overwrite the draft with the new edits, or preserve the draft's > contents since the last time it autosaved. *Never* should it happen that > the entire draft just disappears. > > The feeling of insecurity I get from having this basic assumption broken > makes me very uncomfortable in using TW for work, as if the ground beneath > my feet wasn't solid. > > Respectfully, Jeremy, your statement that TW gives enough power to shoot > oneself in the foot is not convincing, because while I do see that TW is > extremely powerful and versatile, I honestly don't think that a reliable > saving mechanism gets in the way of that. > > The reason I chose TW in the first place was out of admiration for its > highly self-reflective design. That admiration has not abated in the > slightest. > > Yours truly, > Bruno > -- 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/73cba906-0772-49ba-9820-60ebfd1ebc4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
