Multi-user collaboration currently on Node

52 views
Skip to first unread message

TonyM

unread,
Sep 2, 2020, 1:59:21 AM9/2/20
to TiddlyWikiDev
Folks,

I recently installed a new node tiddlywiki, and accessed it at the same time from two browsers. 

Background
  • I note there is a little contention and complexity however I believe we have a layer on which to could build tools that allow a multi-user wiki.
    • What I mean is building a software interface on top of TiddlyWiki which helps stop damaging contention occurring.
      • Eg don't allow edit if a draft.of exists in someone else's name.
  • I am aware than Bob does this and quite well through a messaging system, but as I understand it on vanilla node on edit of a tiddler if autosave is set on it will save that tiddler and the other user will see the change.
  • I believe The contention is ONLY on the edits and changes of tiddlers simultaneously
Request for your thoughts
  • I am interested in investigating the ability to turn such a wiki into a multi-user multi-access environment by forcing user login and develop-ways to reduce the possibility of contention and resolve it when it occurs.
  • Am I correct in assuming the contention is primarily at a tiddler level, and of course some processes can impact a large umber of tiddler at once?

I have a whole kit bag of ideas and methods to achieve this. But I post here to solicit your thoughts on this. My preference is for any limitation to be followed by a possible work-around.
  • What gets saved can be varied by user, eg; they can only save tiddlers they own
    • Eg never save passing details like history and story etc...
    • Local storage can hold these tiddlers
  • Tiddlers can be save under a user namespace but appear as if they have not
  • A Serial editing process could be applied to the whole wiki or only tiddlers.
    • A Conditional edit button would manage this.
    • A request to edit and a release for edit process behind the scenes
  • etc...
Is this achievable or am I just barking up the wrong tree because node implementations are hard to safely publish on the internet?
  • Does this even matter for LAN based teams of trusted collaborators?
Please separate ideas for a future version TWX from what we can achieve now (which is my focus)

Regards
Tones

TonyM

unread,
Sep 4, 2020, 1:39:17 AM9/4/20
to TiddlyWikiDev
Post Script,

I also believe this approach may lend itself to implementation on single files wikis with a lock mechanism for serial edits and a way to save select tiddlers to an alternative file name, and reload them on change of user.

Regards
Tony
Reply all
Reply to author
Forward
0 new messages