My two cents, > I think multiusers with simultaneous access IS interesting.
I think there could be further breakdown of this "requirement". Because there will be completly different set of issues in each case: - one person (user) having the same wiki opened on multiple devices (clients). There will be edit conflicts because of distributed nature of this system. - multiple people (users) updating the same wiki. In addition to conflict management, there will be some work to ensure there is no security issues. Best regards, iilyak On 25 November 2019 09:05:40 GMT-08:00, TiddlyTweeter <[email protected]> wrote: >Ciao Tony > >I thought you already had had "*The last word in Saving?*" So I will >take >your "*penultimate*" as evidence you have time travel :-) > >I think multiusers with simultaneous access IS interesting. > >Bob definitely is in the right direction. What I seen looks good. > >But part of the issue is what is it for? > >In my own case I like to chat. But I don't see TW anytime soon being >able >to do more than post to Twitter & Telegram. >So the interaction you refer to is within a limited scope. What is it? > >And that is the point, I think. What are we trying to integrate? For >what? > >What I'm trying to get to is part of the issue is about fundamentals of > >tech & part (important part too) is why? > >I think we need to see more (including thought experiments) to >understand >the issue well? > >Early thoughts >TT > >On Sunday, 24 November 2019 23:41:02 UTC+1, TonyM wrote: >> >> Folks. (edited) >> >> This thread in an intentional fork of the last word in saving thread. >I am >> keen to keep the last word in saving focused on single file wikis and >a >> simple path for even new users to make it their own. Invariably this >bleeds >> into multi user and multi access implementation so please raise it >here >> instead. >> >> >> - Multi access - more than one user updating a tiddlywiki at the >same >> time >> - Multi user - more than one user updating a single wiki can be >with >> serial editing or multi access >> >> *The only multi access solution I am aware of is Jeds wonderful bob >server >> which addresses the contention when editing tiddlers. Please advise >if >> other wise, perhaps noteself can when configured for cloudDB. * >> >> >> Please share your ideas, experience and more on multi access and >multi >> user tiddlywiki such that we can develop new approaches and >documentation >> or identify gaps we can address as a community. >> >> >> Regards >> Tony >> >> >> Post Script >> >> Using multi-access and Multi-user implementations of Tiddlywiki can >also >> be extended to multi-device solutions. Such as you would like a >tiddlywiki >> on your mobile and access it on your desktop. Such solutions can make >use >> of a server based solution as needed with multi-access and multi-user >(of >> the simultaneous type) or single file based wikis stored on a cloud >> service such as Google Drive, Microsoft One Drive, Dropbox and more. >> Where possible please keep this thread focused on Node, server or >folder >> based solutions and see the discussion *the Last Word in Saving >> ><https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/98-q0H0q6bA>* >for >> single file wikis. >> >> > >-- >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/b9717441-ca4d-4768-87a6-b2b78d6acb7a%40googlegroups.com. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/740A9F6B-4C99-4D8A-9D0B-2EDCEF8D4DB9%40gmail.com.
