Some info about TiddlyWeb.
Terms:
*tiddler* ... contains the minimal useful content to work with
*bag* ... A bag is a container of uniquely named tiddlers. A bag can have
*rules
*for who can *edit, delete or read* the tiddlers in the bag. These rules
are defined in a *policy*.
*policy *... A policy is the TiddlyWeb *concept for controlling access* to
resources on the system. That is: it is the mechanism by which
authorization is managed. There are policies associated with each *bag *and
each *recipe*.
*recipes* ... A recipe is an ordered list of *bags *and *filters *that
generates a list of tiddlers.
/bags/system/tiddlers?select=tag:systemConfig;sort=-modified
/bags/{{ user }}/tiddlers
*space* ... A user friendly name for a 2 recipes. A space was bound to 1
user (by default). It did contain a "private" and a "public" recipe. If you
where authenticated and the owner, you could see the "private" space. If
you where a guest, you could only see the "public" space.
More info can be found at tiddlyweb.com .. Info from above can be found at
the Abstract Overview
<https://tank.peermore.com/tanks/tiddlyweb/Abstract%20Overview>.
On Tuesday, April 9, 2019 at 11:26:43 PM UTC+2, Yakov wrote:
....
> Syncing is the easier to explain of the two: TWC has plugins that let it
>> sync changes to TiddlyWeb, a venerable Python-based TiddlyWiki serverside
>> we developed at Osmosoft. I’ve not tested it recently, but those plugins
>> should also enable TWC to save back to a TW5 server.
>>
>
> Sounds interesting. This is namely two-way syncing or one-way saving of
> separate tiddlers?
>
2 way syncing was possible, but (I think) it wasn't implemented in the
client UI. Every tiddler had it's own history. The UI had a simple
mechanism to compare 2 version. So there was an easy fix.
The "Space" philosophy worked with "stacked" recipes.
eg:
/bags/system/tiddlers?select=tag:systemConfig;sort=-modified /bags/{{
userBBB }}/tiddlers
/bags/{{ userME }}/tiddlers
All bags are combined into 1 TW, which was served to the client.
While content of userBBB can be seen, it can't be changed. ... If I want to
change a tiddler, I had to clone and publish them in my userME bag.
The last bag in the recipe list WINS! This concept is unprecedented and it
is extremely powerful. Our future goals shouldn't be less than that!
> In other words, can it be used for simultaneous editing of different
> tiddlers by different users so that they see the changes made by others
> without reloading TW?
>
Would have been possible, but I think the sync-adaptor pulled a "skinny
list" of all tiddlers and
> Is syncing tiddler-wise?
>
yes
> Meaning that it can be used for what I've just described but cannot be
> used for simulteneous editing one same tiddler by different users?
>
With TiddlyWeb, we had so-called *spaces*. A space was bound to a user.
Users only have write access to their own spaces.
Personal Note!
Nobody except me, has the right to write to a space that I own. .. period!
If you want to change my content, clone it, modify it and distribute it on
your own space. (Assumed the right license is in place.)
> By the way, why saving the whole HTML is not easier to explain: is it very
> different from what TWC uses for ordinary saving?
>
TW savers are much, much simpler than adaptors.
have fun!
mario
--
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/c409b05d-3f19-4ebc-b8ea-5dcc8990986b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
