>
> The agreement just consists of the names of the syncfiles. The important 
> point I may have forgotten to mention explicitely is that the information 
> about the syncfile of A is told to B in a meta way.
>

We are talking of ONE wiki, are we not? So, the "agreement" you refer to 
simply is that there are different *modifier* names being used throughout 
the wiki... and possible "syncfiles" for each. Making sure that each 
modifier actually does use its own username seems a bit of an issue. What 
if two (unknowingly) use the same? Anyhow, you want each user to use their 
own username when editing that wiki in the browser. This seems to ask for 
either local storage or a good old cookie, not a tiddler to store who 
everyone is.

Which means that the name of the syncfile of A is told B per comment / chat 
> / social functionality of the sync carrier (the cloud service).
>

Considering the above, it does not mean that. Those users are hardcoded or 
merged 
into the wiki like any other content.

In a case where you have a single wiki in a directory in sync over a cloud 
> service you have to exchange this meta information only once!
>

So, the challenge is not one of exchanging some "me, too" by means of 
communication, but of successfully adding a new modifier to the group of 
modifiers of a wiki.

In theory, the meta thing might be not elegant.
>

If not into the wiki, I wonder where you want to put it.
 

> In reality it would be highly practical, because you only have to exchange 
> the meta information when your team changes or the cloud service does - 
> that would be really convenient.
>

Exchanging information is not the issue, telling TiddlyWiki about it is. :-)

Best wishes, Tobias.

-- 
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to