Mario, Thanks for your comments.
Because I never understood TiddlyWeb I can't say weather my proposal is like it or not. However in some ways what I propose it is quite simple. *In fact I now believe I can make a working prototype.* - What I propose here is not about a cloud based server, or service online, it is about a multi-user configuration. - It is Just like the local storage plugin saves tiddlers to local storage and on reload it applies them on top of what was loaded from the server. - This idea would save the users modified tiddler under a prefix or compacted into a json tiddler. The save to server process will be configured to only save the current users "prefixed" tiddlers back to the server. - I am simply suggesting a similar mechanism that rather than save to local storage, renames the modified tiddlers with a username based prefixes and saves them in the wiki. At reload it determines the users prefix and "restores" the tiddlers over those loaded from the server. However the reason I raise it here is such a mechanism provided in a plugin, a saver or parts in the core would allow the normal save filters and methods to work. Not to mention may be needed to facilitate it for single file wikis. *Single File Wikis* For Single file wikis a similar mechanism would save the users modified tiddlers to a seperate file of tiddlers. When the single file wiki is loaded, it will at the very last step load the users modified tiddlers over the ones loaded from the file. In this model the only thing that changes is the content of the users tiddlers which are saved separately. *Advanced security* In the "single file Wiki" configuration that saves users modified tiddlers into a separate file, implementations such as on PHP with tw-receiver, we will gain the ability to read or write the users modified tiddlers file, and these files could have user and password security applied. Unless I am logged in as fred I can not save to wikiname-fred.json or read from it. Regards Tony On Tuesday, June 25, 2019 at 1:44:57 AM UTC+10, PMario wrote: > > Hi Tony, > > What you describe, is basically the concept of TiddlyWeb, with different > names. ... TiddlyWeb had more security related options. > > The "namespace" you describe is named "bags" in TWeb. A bag is a tiddler > field, so it doesn't interfere with the title namespace. ... User read / > write access was configured "per bag". > > In TiddlySpace (TS) several filtered bags could be combined into a > "space", which is similar to your "filtered namespaces". > > ... BUT TiddlySpace is dead. ... > > It suffered from the "centralisation problem" that we have in the net of > today. The users data doesn't belong to the user any-more, because it's > stored in data-silos, that are controlled by 3rd parties. If a centralized > server is shut down the whole "community" is destroyed. ... That's exactly, > what happened to TS. > > > At the moment I'm having a closer look at the DAT-project [1] and the > beaker-browser [2], which I think is a very promising peer-to-peer (p2p) > platform. Also for multi user configurations. ... I think TW is a perfect > match here. > > have fun! > mario > > [1] https://dat.foundation/ > [2] https://beakerbrowser.com/ > > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/c5918eaa-b03c-4ee4-bacc-6ca5a8658b70%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
