HC Thanks for sharing, its importiantfor the community. I use a large wiki on top of sharepoint and use the same method. I think it can apply in many cases. Keeping the save button that goes red visible, when automatic saving is off can be important.
Another thing to consider in similar circumstances is the local storage plugin, at least on browser accessed wikis (I am not sure about the apps). Saving takes place in the browser continuously and the manual save commits it to the server/file system. If you did accidently close the tab returning to the same url should reload the temp storage items, from which you have another opportunity to save (in this case I think of the word "commit" the changes) I am working on a Local storage helper icon to make this clearer to the user but the combinations make it a small challenge. Regards Tony On Saturday, March 7, 2020 at 3:35:25 AM UTC+11, HC Haase wrote: > > Sharing my discovery > > In retrospect, it is obvious, but it didn't occur to me for a long time. > > when I use TW on mobile it is always encrypted because the risk of loss or > other compromising is higher than my pc, so unencrypted wiki is not an > option IMO. This led to the wiki being very slow on save and therefore hard > to use. > > The obvious solution. > > If you use an encrypted wiki on mobile: > > > Turn off automatic saving, and save manually when you need to. > > This is simple, but it made my wiki workable again on mobile, so a big > impact. > -- 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/3719a9b9-3bd9-436c-8dc5-a4729fe1652a%40googlegroups.com.
