Access Control to predefined areas

[Fred Aerique]

Hi,

I am using TiddlyWiki mainly as a repository for my own thoughts,
product ideas, etc.
My Desktop-wiki synchronizes with that on Tiddlyspot, which is
password protected.
I was wondering these days whether it was possible to give friends
access to just a
single tiddler, but I cannot find information on that anywhere...

Where could I start looking for this, or: does anyone know how to do
it?

Regards,
Fred

[Eric Shulman]

> I was wondering these days whether it was possible to give friends
> access to just a
> single tiddler, but I cannot find information on that anywhere...

As long as there is password-protection on the file, your friends
would require that password in order to access that file... and any
tiddlers it contains.

Perhaps you could set up a second, non-password-protected, tiddlyspot
account to which you could post your 'public' tiddlers. Then just
give your friends a permalink to a tiddler in THAT document.

They can then use:
http://www.TiddlyTools.com/#ExternalTiddlersPlugin
to "pull" the tiddler content into their own documents (either as a
'temporary' tiddler, or 'import-on-demand'), like this:
<<tiddler TiddlerName|http://foo.tiddlyspot.com/#TiddlerName>>

or... they could use:
http://www.TiddlyTools.com/#LoadTiddlersPlugin
to automatically *import* the published tiddler into their document
whenever that tiddler has been updated on the server.

HTH,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

[FND]

> I was wondering these days whether it was possible to give friends
> access to just a single tiddler

Generally speaking, TiddlyWiki is not geared towards multi-user
collaboration. That's mainly because user management generally requires
some sort of server-side mediation (e.g. resolving conflicts arising
from simultaneous editing) - TiddlyWiki's code is executed on the client
side (i.e. in the user's browser) though.

Take a look at this (still incomplete) article on the community wiki:
http://tinyurl.com/26zhvg
(http://www.tiddlywiki.org/wiki/Can_I_use_TiddlyWiki_as_a_multi-user/collaborative/server_based_wiki%3F)

Eric's idea for using separate a TW document would work though, provided
that you don't need elaborate access control with permissions for a
large number of different user groups.

-- F.

[Fred Aerique]

Very nice, many thanks for the quick responses!

Can't have those pages non-pw-protected, as the
content contains IP that I only want to leave to
trusted peers for review.

I don't need to define many user groups, I just
need one additional password for the group "friends".

Ideally, for every page I could check a tickbox called
"share with friends" or sth...

I wasn't able to find out whether the above plugins
can load pw-protected tiddlers, but if they can and
this is the current state of affairs re multi-user
collaboration, I will simply export every tiddler that
I want to share to a second, password-protected wiki.

Really hope that there will be some advances
in the near future though...

Fred

On Jan 5, 2:31 pm, FND <Ace_No...@gmx.net> wrote:
> > I was wondering these days whether it was possible to give friends
> > access to just a single tiddler
>
> Generally speaking, TiddlyWiki is not geared towards multi-user
> collaboration. That's mainly because user management generally requires
> some sort of server-side mediation (e.g. resolving conflicts arising
> from simultaneous editing) - TiddlyWiki's code is executed on the client
> side (i.e. in the user's browser) though.
>
> Take a look at this (still incomplete) article on the community wiki:
> http://tinyurl.com/26zhvg

> (http://www.tiddlywiki.org/wiki/Can_I_use_TiddlyWiki_as_a_multi-user/c...)

[Eric Shulman]

> I wasn't able to find out whether the above plugins
> can load pw-protected tiddlers, but if they can and

Yes, they can. Depending upon your browser configuration, you should
be prompted with the usual username/password dialog box when access
password-protected content via the <<loadTiddlers>> or plugin-enhanced
<<tiddler>> macros. If you don't get prompted by your browser, you
can also enter local, cookie-based option values:
<<option txtRemoteUsername>>
and
<<option txtRemotePassword>>
which, if defined, will be automatically sent to the server when
retrieving remote content.

enjoy,

[FND]

> Really hope that there will be some advances
> in the near future though...

An enhanced server-side solution is in the works (I believe there will
also be access control - not sure to what extent though). No ETA yet.

-- F.

[Fred Aerique]

> An enhanced server-side solution is in the works (I believe there will
> also be access control - not sure to what extent though). No ETA yet.

That is good to know! Really looking forward.

Thanks again, I appreciate your dedication.