Trying to achieve a robust architecture for a farm of node.js TiddlyWikis that together form a distributed database, with end-user level (and private) TiddlyWikis that have certain types of tiddlers that are automagically shared (and the rest private), and system-level TiddlyWikis that tie all of the architecture together along with user-interface stuff, etc. etc. etc.
Sure, not very likely end-user folk could muck things up, but a robust system really should never allow an end-user to break their TiddlyWiki (in this farm idea of mine) by somehow replacing any key component tiddler. No worries. I'll train my thoughts on obfuscation, risk-mitigation design/strategies, and automated monitoring/repairing processes. All part of a big idea that ties together, in part: - A brewing idea: TiddlyWiki on node.js: check for changes <https://groups.google.com/g/tiddlywiki/c/GMagvXTOxLI/m/POV20R69AwAJ> - More playing around with TiddlyWiki on node.js: the makings of a distributed database <https://groups.google.com/g/tiddlywiki/c/OuYwkSgPBDo/m/egsk9fhoAwAJ> On Sunday, September 5, 2021 at 8:18:19 PM UTC-3 PMario wrote: > On Sunday, September 5, 2021 at 8:36:26 PM UTC+2 [email protected] wrote: > ... > >> Is there an easy way to protect such a tiddler? >> > > No. In TW you can overwrite every core tiddler if you like. So there is no > way to write-protect a tiddler. > What do you want to achieve? > -m > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c43f9b8f-a004-41a2-8dd9-c222426f9499n%40googlegroups.com.
