I think this is something we’re trying to do with TiddlyWeb / TiddlyHost, but I’m missing something about how to implement. Please help / correct.
Use case : I’d like to share notes on holography. Just sharing broadly, with the public.
I looked at TiddlyHost : I can start a public Tiddler for holography, and publish my notes there for anyone to consume. Someone who wants to use this content can drag-and-drop, or create an external tiddler by creating a blank tiddler, and setting the field value of _canonical_uri to either the whole tiddlywiki instance, or a specific tiddler by getting that tiddler’s permalink (doesn’t seem to work in testing, but should, I think) and setting the new tiddler’s content type to html.
I can even transclude external tiddlers in internal ones; so I can weave bits of content together.
TiddlyHost limitations. It doesn’t look like external tiddlers to TiddlyHost work, for some reason. I can externally link to wikipedia,
With TiddlyWeb, I can export individual or groups of tiddlers into a bag or recipe. Recipes can be versioned, and a newer version will be respected over an older one, if both are in an instance.
TiddlyWeb limit. But I still need to manually publish the new bag or recipe. I might be able to do this with npm, which is very helpful, but I can’t push out to anyone who for some stupid reason has imported my thoughts about HX200 photopolymer into their own tiddler to get the newest version. Consumers would need to discover updates manually, and bring them in manually. Not necessarily awful, if I go and publish a broken plugin
Finally, it looks like I might be able to do the same with ZeroNet using zeronet-js; and the plugin changes will be pushed to other consumers. (Haven’t determined if this is true yet). This way, I might decide to add topics : code, statistics, … or, in the case of the non-hypthetical 3D rendering plugin I have, I could add royalty-free 3D models to the bag, and everyone would get them without any work on anyone’s part.
Am I getting this right?