Folks,
Just a little more. This discussion
<https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/NQB7F4Z4z7w> is
what triggered this idea, trying to use cardio as a multi-user solution.
- An important point here is my proposed solution would allow existing
TiddlyWiki's to be quickly converted to multi-user solutions.
- I would also add this would be a candidate for a plugin, if it can
work on top of the core, rather than needing to be in it. Thus it could be
in a 5.1.X version rather than TWX
- Although using such a namespace method would help with multiple users,
it could also be redeployed for other interesting applications, where by
users can change namespace on the fly.
- For example change namespace and you are looking at one edition,
change and you can see another edition and download the custom edition
you
want. ie an editions name space, that only contains the delta between
editions.
- This may overcome performance issues by being able to load only the
required namespace, so you could have a database for each team, you
select
the team namespace and only that is contained in memory, yet you still
remain in the same tiddlywiki. You could load a minimal wiki, then on
selecting the namespace, load the balance *ONLY*
- Under node we could publish namespace tiddlers at
\namespacefolder\tiddlername making them visible (if desired) to all
(authenticated) users. Ideally the user can control what is published using
a filter. This could effectively treat such tiddlers as external tiddlers,
and could even exist on another server
"other.com\namespacefolder\tiddlername". These could be published as static
tiddlers or as actual tid files that the server can render.
Perhaps another flight of fantasy?
Regards
Tony
On Monday, June 24, 2019 at 9:47:10 AM UTC+10, TonyM wrote:
>
> Folks,
>
> Please take this suggestion seriously. I think it could resolve some
> serious multi-user requirements. Please also forgive me for my speculation
> and dreams.
>
> *Given a number of multi-user scenarios and the ability to selectively
> save tiddlers to a server;*
>
> I was wondering if it may be practical to have a namespace eg
> $:/username/tiddlername such the the active user creating or saving
> tiddlers will actually write to their namespace only. When the wiki loads
> the tiddlers in the namespace are loaded/reloaded rather than the
> tiddlernames they replace. For all intents and purposes it would look like
> they are using "tiddlername" however this will actually be saved as
> S:/username/tiddlername
>
> The save mechanism can then be set to only save their name space tiddlers
> to the server, meaning they can not overwrite the servers shared, core or
> system tiddlers (but they can overide them with a replacement version). It
> is a bit like how the local-storage plugin works loading over the existing
> tiddlers, loading the users modified tiddlers from local-storage.
>
> A version of this for single file wikis could permit the users namespace
> tiddlers to operate in local storage, and be saved/exported out for
> re-import so that they may be loaded back into local-storage. Well designed
> this would permit an independant save process (an alternate filename such
> as username.html) making this a possible feature of single file wikis as
> well.
>
> In both server and singlefile configurations username.html could also be
> imported into a master server wiki to enable a loosely coupled multi-user
> environment. Tw-Receiver or other save mechanisms php or auth could then
> control access to the username.html, so only the authorised user can
> load/save or export the whole wiki with there namespace tiddlers applied or
> stored independently.
>
> Additional features could be introduced so the owner of the server can
> import the user name space tiddlers, review and selectively replace the
> server versions of the tiddlers. Thus users can submit proposed changes in
> their own name space for selective inclusion in the master namespace.
> Tiddlers in the user namespace could be tagged "pull request" so they
> appear as change requests to the master namespace.
>
> I have no certainty what complexity is involved in what I propose but
> given how the local storage plugin now works my guess is the ability and
> features are only a small step away.
>
> PS I know some may say that TW-Federation or similar already does this. If
> it is the case please publish it, whenever I look at tw federation and
> similar solutions, I get lost in developer discussions and can't find an
> actual solution, or go beyond some betas.
>
> Thanks for considering this seriously
> Tony
>
>
>
--
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/516af398-8ca2-4128-a42b-d8f918e9717b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
