I would say, the combination of https and strong passwords should get you a long way. Depending on your setup, you could add client IP address restrictions. And physical access would even be more secure in the cloud.
-Poul 24 Jan., 04:57, HansBKK <[email protected]> wrote: > On Tuesday, January 24, 2012 1:52:36 AM UTC+7, Poul wrote: > > > I'm not sure what you mean - you can export your pages as stand-alone > > tiddlywikis or just-the-content XML. > > But the native storage used by giewiki is the cloud-hosted App Engine > > data store documented here: > > >http://code.google.com/intl/da-DK/appengine/docs/python/datastore/ > > I am looking for a self-hosted solution, and my specific concern here is > data privacy, as several of my use cases prohibit cloud-based (or in fact > any outside-the-group-accessible) storage. Strong on-disk encryption would > of course be one approach, at a filesystem level, as ideally the tiddler > data would be stored in an easily diffed/merged format and stored > in/distributed by an arbitrary DVCS. > > Any and all suggestions welcome, but don't mean to hijack the thread, feel > free to fork this off if appropriate. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
