Stev.. First and foremost if you can host a bob or bob.exe server you can have contention on tiddlers controlled. When one person is editing it another cant. However after that they can edit it and "replace" the tiddler.
Bob is at present the only way to have simultaneous access to one wiki for edit. I am working on the larger picture of logins and tracking changes, but I do not have a finished product to share. The key for both node and single file, is I believe, the ability to checkin and out tiddlers Or whole wiki, so only one editor at a time will save disaster, next is a software layer within the wiki that managers the interaction of multiple users over time. Regards Tony On Monday, 21 September 2020 at 20:01:50 UTC+10 [email protected] wrote: > (Relative newby #question) - > Is there a way to ensure #import of a group of tiddlers from one TW into > your TW does not overwrite existing tiddlers that happen to have the same > name? > > I'm trying to prevent problems I foresee years from now that could come > from extensive shared TW use by a group or family. > > Thank you for the help! > > Probably irrelevant, currently using: > Stroll with all empty TW5 tiddlers imported > (Ideally, I want to incorporate #TiddlyMap or #TiddlyRoam) > json import/exports of tiddlers > ON > Windows 10 Enterprise 10.0.18363 Build 18363 > Edge Version 85.0.564.51 (Official build) (64-bit) > Chrome Version 85.0.4183.102 (Official Build) (64-bit) > OR > Safari 14.0 > macOS 10.14 Mojave > > > > -- 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/9b9bce6a-0dc1-46d9-b516-a3493936dfc0n%40googlegroups.com.
