On first thought, I would ensure a "backup" with a git script with a new commit each hour. I could piece together something that worked. This would give some security against bad actors.
I wonder if anyone has mad a plugin which functions as a "Trash" can for deleted Tiddlers. Essentially deleted Tiddlers under node would be move into a folder, rather than actually be deleted. They would then be pruned on a regular basis. About your idea for an overlay, I would think setting some fields in the User Tiddler would be more persistent? And would allow settings to move between browsers and devices. Though it could make sense to add some state that is used for devices. One example is the Cardo theme doesn't work well on phones, but works well on Desktop. Some may want to change the theme on phone, instead of the Desktop. On Sunday, June 23, 2019 at 8:04:02 AM UTC-4, TonyM wrote: > > Post script > > You did explain it much better. > > I was not concerned about bad actors either. I just want to ensure > integrity, consistency etc the accidental damage is the most likely problem. > > It sounds like cardio may have already demonstrated a multiuser > architecture, this can now be enhanced by using minimal local storage to > keep track of each browser session. In effect managing user differences in > core settings with a local storage overlay. > > Regards > Tony > > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/4ff7a51b-36e6-4678-88ae-f38872f3f15b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
