Short answer, internalFetch is made for exactly this sort of thing, there is nothing that would prevent what you want but there are some relatively minor concerns.
More detail: The internalFetch websocket message is made to fetch tiddlers from other wikis served by Bob. https://github.com/OokTech/TW5-Bob/blob/master/Documentation/WebSocketMessages/WebSocketMessage-internalFetch.tid I haven't come up with a better method of getting information from one wiki to another yet, so I would go with that. The only potential worry is that fetching from a wiki loads the tidders for that wiki on the back-end, so if you have a lot of them it may take a few seconds for them to load and for the tiddlers to be fetched. So whatever the solution is it shouldn't run often. I am not sure what the best way to ensure that this information is shared between all the wikis is. I think that adding it to the wiki settings would work but that would either mean there was a duplicate list or I have to redesign how the paths to the wikis are listed. Another concern with that is I am working on some more privacy features so that you only see the wikis you have access too instead of seeing all the wikis regardless of if you can access them or not, which would make running this once at the start and sharing that with each wiki more complex. -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8ae624b2-9983-4c68-b3e1-997adb80ec5c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
