On Jan 24, 8:48 am, HansBKK <
hans...@gmail.com> wrote:
> Sorry if I wasn't clear - for these particular use cases the data itself
> cannot be stored on a machine out of the group's control.
>
> Even if there were a service that had end-to-end encryption using
> transparent FOSS tools where the sysadmin at the data center and Justice
> Department storm troopers couldn't ever read the data on disk without
> direct application of rubber hoses to my cranium - not allowed.
TiddlyWeb is specifically architected to allow these kinds of
solutions. As far as I know there's no implementation that does all
the things you say, but the structure of the system is such that you
could:
* run the whole thing over ssl
* write a StorageInterface that saves to DCVS
* establish what are called "validators" that inspect cryptographic
signatures on submitted tiddlers to protect against man in the middle
attacks
* write a SerializationInterface which a) presents useful diffs of a
tiddler's history b) accepts patches as input
People moan a bit about TiddlyWeb's apparent complexity but it's
important to keep in mind what its goals were: To demonstrate what
really could be done if you had a well architected web api and server
for tiddlers. Thus, it has quite a number of configurable and
extendable abstractions that are initially a bit overwhelming. It's
the cost of power, I guess.
The existing implementations and installations have barely scratched
the surface of what's possible.