On Wed, 10 Dec 2014, Mat wrote:
Probably not a coincidence - I have most likely been influenced by blog posts of yours, and specifically remember reading about your fascination with the individual tiddler rather than the whole TW. BTW how would you say your TANK <https://tank.peermore.com/> project manifests this vision? (I am not a member there).
On the surface Tank is mostly just trying to be a simple page-oriented wiki but it has a few features (beyond those already provided by straight TiddlyWeb) with which it tries to make the swarms of individual and collections of tiddlers a bit more available: * The auth model + full CORS support makes it fairly straightforward for other interfaces and web services to do CRUD operations on tiddlers. You can create named revokable keys which you can "give" to various applications or tools. * There is a thing call the policy manager[1] which makes it easier to adjust the policy settings on individual bags so that you can easily say what users can do what actions on the bags. Support for recipes is pending. * Tiddlers are easy to move between tanks. * Compositions[2] make adding additional functionality (both simple[3] and complex[4]) a matter of putting the right things in the right place. * Like tiddlyspace there are websocket notifications and atom feeds of most everything, so other systems can be easily made aware when stuff happens. Properly functioning CORS support was a bit of a struggle to get right, but it goes a very long way to making it possible to build things _elsewhere_ that happen to use tiddlers that are kept in tank. The features list is worth gazing at: https://tank.peermore.com/tanks/docs/Features [1] https://tank.peermore.com/tanks/docs/Policy%20Manager [2] https://tank.peermore.com/tanks/docs/composition [3] https://tank.peermore.com/tanks/journalizer/index https://tank.peermore.com/tanks/bookmarker/index [4] https://tank.peermore.com/tanks/tw5/index -- Chris Dent http://burningchrome.com/ [...]
