Hi Mat,

Your suggestions are certainly interesting, but far beyond my pay grade I'm afraid! For example, the iframe trick with JavaScript is beyond my level of expertise, to give you an idea.

I can see how my "community search wiki" can give the illusion of some form of dynamic sharing of tiddlers between different wikis, but it's actually not the case I'm afraid: behind it there is a program (not a TW program, an independent script) which applies a very crude treatment to the wikis; it is just a standard text file manipulation process, using the TW node.js version precisely because tiddlers are simple text files in this version.

This means that it is not dynamic, because there is an intermediate "worker" which does all the menial work between the source wikis and the aggregator wiki. I don't know whether the kind of dynamic sharing that you envision is technically possible with TW, Jeremy or the other developers are certainly more in a position to answer than I am.

About the blacklist/whitelist marking at the level of tiddlers: it was also my first idea, but I think doing it as a a list in a special tiddler gives more freedom to the author: this way instead of having to mark each tiddler with a specific tag or field, they can use their own filter; for instance if you already have some categories IdeasForTW, TipsForTW, MyGroceryList and MySecretDiary, you can do a whitelist filter "[tag[IdeasForTW]] [tag[IdeasForTW]]" or a blacklist filter "[tag[MyGroceryList]] [tag[MySecretDiary]]".

Regards
Erwan


On 08/01/15 21:36, Mat wrote:
@Erwan

    You are probably the only one who has so many wikis so I don't
    know if the approach is generalizable, but I had vaguely started
    thinking about doing something similar at the level of tidders:
    https://github.com/erwanm/tw-aggregator/issues/6
    <https://github.com/erwanm/tw-aggregator/issues/6>


In addition to the two ideas you mention there, here's a third. I hope it's not pie in the sky, in not a programmer, so FIWW:

Note that permalinks can contain filters in TW. This could perhaps be used for some kind of "matching mechanism" so that in the call for the source TW you not only specify which tiddlers you would like to index but also send some kind of identifier for who you are. The source TW can read this and use the identifier as an allow/dismiss criteria.

In another context, (iframes), here's a description <http://mattsnider.com/hash-hack-for-cross-domain-iframe-communication/> of using hash based 'additions' to urls for communication between domains.


Another idea: One of your ideas in your issue brings up haveing whitelists/blacklists in a tiddler. Maybe it would be desirable to allow /individual/ tiddlers to specify this. I.e having the individual tiddler accept or reject when someone attempts to include it.
Perhaps fields
"whilelist: exclusively if domain as tiddler foo"
"blacklist: username=bar OR domain=frotz.com"

This latter idea would be particularly useful in collaboration situations where you want to give different persmissions to different people.


Do I make sense at all?


<:-)

<:-)
--
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 tiddlywiki+unsubscr...@googlegroups.com <mailto:tiddlywiki+unsubscr...@googlegroups.com>. To post to this group, send email to tiddlywiki@googlegroups.com <mailto:tiddlywiki@googlegroups.com>.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

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

Reply via email to