Dave.2 wrote: > > Yes, I forgot to mention that the entire file will be for a single > patient. >
(I was surprised at this. If you have 100 patients you'll need to update 100 wikis, install each new pluign on 100 wikis, modify on 100 wikis etc etc... Or maybe I misunderstand. Or maybe multi-updates etc is possible via TiddlyDesktop or sth..) > The concept of separating [...] > With the node.js version, and Bob, you'd have separate tiddlerfiles but for the same wiki. > As for privacy, I'd thought that the best way would be to possibly encrypt > the hard drive its on and use syncthing (also encrypted) to keep current > copies sync'd between the treatment rooms and my office computers. I guess > I'd have to see if there are Tiddlywiki ways to encrypt a single TW file in > case a patient wanted a copy. > There is the native full wiki encryption and Danielo just revamped the single-tiddler encryption. > * and what about updating TW version? Currently I drag my TW file onto a > thing at tiddlywiki.com/updates, but that can't be a secure enough method > as far as privacy legislation, can it? > As is stated on the updates site, the data doesn't leave your computer. It is not uploaded. Instead, what you see (just as for any webpage) is a local copy of the updates file. So you drag'n drop your old wiki onto it and the core replaced with the new one and you save this locally. So nothing leaves your browser so, yeah, that should be secure. <:-) -- 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/8b84d02f-6230-4f42-b8d7-cd9a74dcc164%40googlegroups.com.
