On Tuesday, June 25, 2019 at 2:07:28 PM UTC+2, TonyM wrote: ... > I agree authentication and authorisation is critical but once someone is > entitled to update content there is a lot we can do in trusted > environments. Solutions should cater for both open and locked down cases.
That's why I do like the dat-project [1] a lot. DAT is a protocol, to share data between computers. DAT is also a storage mechanism, where you have write access, if you own the "private key". You do have read access, if you know the "public key". .. The public key is unique and part of the URL address. eg: dat://32d225818f3928d4f17ed4893108f630d59023ccbbda196262ecd936e4033421/ Which is also reachable as: dat://beakerbrowser.com with the beaker browser or https://beakerbrowser.com/ with every other browser. If we define the dat-address as a "namespace" in your terms, or a "bag" in my terms, we do have the ability to define multi user writeable "spaces", with a simple configuration. In this scenario everyone has the right to write to their own namespace. As you can see, the wiki is now scattered all over the network. ... That's a problem, if you don't have a connection. ... but ... DAT is a distributed system [2], which relies on the fact that other users also store the content. If you host someone elses content, the mechanism is called "seeding". For seeded content, you only have read access, since you don't know the write key. So as an author you can be sure, that others only seed / host your content, but they can't modify it. The advantage now is, the more often some content is seeded, the more accessible it is. Everyone that seeds some content, has offline access, which makes it a perfect fit for "low connectivity". If you want to modify my content, you need to "make a copy". The copy gets a new and unique dat-address. Now you own it. ... A different version of it. If you only copy single tiddlers from my namespace to yours, it's the same mechanism as a overwritten shadow tiddler in TW terms. ... So every bag, where I have read access contains shadow tiddlers. .... The only thing we need to do is, make it more visible. DAT storage is an "append only log". That means, there is automatic version history built into the system. The storage can be mapped into the real OS file system. So we still have our beloved files, we can deal with. If we modify the local files, we can create diffs between the dat-storage and the actual version in the file system. ... If the local version is ready to be published, we can write it to the store and it is redistributed to everyone, which seeds the content [3]. ... That's just the tip of the iceberg. If you follow the links, you'll get more info. The "problem" with DAT is, that it is relatively new [6]. The storage back-end seems to be stable, but the rest of the ecosystem is still in flux. Especially the beaker browser, which changes it's face with every major version. ... :/ TiddlyWiki already includes a dat-saver [4] since V5.1.15, which can handle single file wikis. The saver still works with 5.1.19 and the latest beaker browser. ... I do have an outdated dat-adaptor prototype [5], to work with single tiddlers. The videos are about 1 year old and I did stop development, since the API used in the video was experimental and deprecated at that time already. ... I would have to have a new look. have fun! mario [1] https://docs.datproject.org/docs/intro [2] https://docs.datproject.org/docs/terms#distributed-web [3] https://docs.datproject.org/docs/concepts#distributed-network [4] https://www.youtube.com/watch?v=YZxWZ0LAHWI [5] https://www.youtube.com/watch?v=G9fDICizGIM [6] https://en.wikipedia.org/wiki/Dat_(software) -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/a47f396e-605d-4185-b5a2-8317734d262e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
