[tw5] Re: The penultimate words on saving - multi access and multi user

Thanks Thomas, It is amazing how many alternate implementations and delivery mechanisms are available for tiddlyWiki. I will look behind the scenes of Glitch. I suppose what you are raising here is providing TiddlyWiki as a service TWaaS which has being hinted at a few times. Lets prepare a

[tw5] Re: The penultimate words on saving - multi access and multi user

Hi, I just mentioned Glitch in the other thread , as it was *relatively* simple to set up and I could imagine using it in a starter course for the first lesson(s) or steps, before people download their single file wiki and

[tw5] Re: The penultimate words on saving - multi access and multi user

TT, Go ahead. Please post a reply here with the details, If you think it will have a long thread of its own perhaps start a new one and link back here and from here to there. In "The Last Word In Saving" I raised an example Of a wiki to handle the Sustainable Development Goals, this is

[tw5] Re: The penultimate words on saving - multi access and multi user

Ciao TonyM I have been thinking about this discussion, as well as "The Last Word In Saving". I concluded I might be interesting to request specific usage/app. need in their details. Why? Because I think real needed app./service specs will help clarify parts of the puzzle. I can post a

[tw5] Re: The penultimate words on saving - multi access and multi user

Ste Wilson wrote: > > Noteself does have a multi user thing. You can grab it from somewhere in > this here group. I think ibm changing it's couchdb offering to something > less nice to use stalled noteself before it really got going. Getting > another couchdb seems tricky. I agree. Part of

[tw5] Re: The penultimate words on saving - multi access and multi user

Noteself does have a multi user thing. You can grab it from somewhere in this here group. I think ibm changing it's couchdb offering to something less nice to use stalled noteself before it really got going. Getting another couchdb seems tricky. Twederarion for single file wikis by the

[tw5] Re: The penultimate words on saving - multi access and multi user

Original post updated with Alternative thread Title: *"TiddlyWiki Encounters of the Third Kind"* - *First = Initial single file wiki on internet* - *Second = Single File or read only wiki published on a server* - *Third = Delivered on a platform that permits multi-access or

[tw5] Re: The penultimate words on saving - multi access and multi user

Just some thoughts; Tw-Receiver is one of my favorite extensions that allows a Single File tiddlywiki online to save to the server via php. It is somewhat secure because the passcode to save can be stored only in local storage and you can't save without it, Using a server such as an apache

Re: [tw5] Re: The penultimate words on saving - multi access and multi user

Folks, This is a penultimate question in so far as it is not the last Question we need to answer *How do we enable saving tiddlywikis for **naive and casual users? in *The last word in Saving? Ok perhaps it is not the

Re: [tw5] Re: The penultimate words on saving - multi access and multi user

With Bob you can have one wiki open in multiple tabs with no trouble. And it supports multiple editing at the same time, just not the same tiddler. For security I made a secure server that has logins and fine grained access control. -- You received this message because you are subscribed to

Re: [tw5] Re: The penultimate words on saving - multi access and multi user

> I thought you already had had "*The last word in Saving?*" So I will take your "*penultimate*" as evidence you have time travel :-) You have made me seriously question my understanding of EVERY use of this word I have ever seen! Google: define penultimate. last but one in a series of things;

Re: [tw5] Re: The penultimate words on saving - multi access and multi user

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).

[tw5] Re: The penultimate words on saving - multi access and multi user

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

[tw5] Re: The penultimate words on saving - multi access and multi user

On Sunday, 24 November 2019 22:41:02 UTC, 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

[tw5] Re: The penultimate words on saving - multi access and multi user

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