What I have in mind is pretty simple, and it is about resolving issues that completely break TiddlyWiki or break an application built upon TiddlyWiki in a node.js farm of TiddlyWikis.
On Mon, Sep 6, 2021 at 3:57 PM Hans Wobbe <[email protected]> wrote: > Charlie: > > Perhaps some of the protection you are looking for can be had via the > frequent saves of a tiddler file to Dropbox? > Unless things have changed since I last used it, that would provide a > rolling 30 day cache that could be used to recover losses. > > Cheers, > Hans > > > On Monday, September 6, 2021 at 11:24:00 AM UTC-4 [email protected] wrote: > >> Well, by obfuscation, I see that as a catch-all word to also mean >> abstraction, encapsulation, and whatever other little design thingies so >> that the end result doesn't look anything like TiddlyWiki any more. >> >> So a user will have to work very hard to get into trouble. >> >> Your Plan B is my Plan A, and your Plan A is my plan Z. In my mind, folk >> who are busy with their missions don't need to be distracted by technical >> stuff needed to be kept in mind. The best kind of software is the kind >> that doesn't need any user guide other than, maybe, something concise that >> lets them know how the software supports them, their goals, their >> processes. I prefer that users trust that software they work with is >> robust/resilient/etc. and doesn't ever waste their time by allowing >> something to happen that can waste their time. Well, within reason. That >> find balance of cost/benefit. >> >> But I do suffer easily from both sensory and cognitive overload, and so >> heavily do these influence my design philosophies. >> >> >> >> >> On Monday, September 6, 2021 at 6:07:42 AM UTC-3 PMario wrote: >> >>> On Monday, September 6, 2021 at 3:01:25 AM UTC+2 [email protected] >>> wrote: >>> >>> No worries. I'll train my thoughts on obfuscation, risk-mitigation >>>> design/strategies, and automated monitoring/repairing processes. >>>> >>> >>> IMO obfuscation is wasting time, other than removing the buttons, that >>> are not needed. Which I would define as "modifying the UI according to the >>> usecase" ;) >>> >>> With nodejs you should be able to establish a "batch process" that runs >>> once a day and checks, if some important shadow tiddlers have been >>> overwritten. I would consider this as "Plan B". >>> >>> Plan A - IMO the easiest way would be to trust your users and tell them >>> what's going on, and what's important. Having Plan B will then only be >>> needed if someone changes something by accident. >>> >>> just a thought >>> mario >>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWiki" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywiki/3mowY9WMyhU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/32d6206c-085b-4f5a-a0ea-1e0269e9eda9n%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/32d6206c-085b-4f5a-a0ea-1e0269e9eda9n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAMu8EfMvRkMCCwb51PoVqjkFe7accBN_Ud_2%3DXkRf%2BLk12jjxA%40mail.gmail.com.
