Jed Carty wrote:
>
> TWederation works between single file wikis without node or anything else, 
> and it has been functional for something like two years.
>

OK, I assumed you were referring to the system you continued with after the 
single file version. But yes, the original TWederation system could 
probably cover a lot of what the OP in this thread brings up. If I recall, 
there are a few less-than-optimal aspects - please correct if I 
mis-remember anything:

1) A http*s* hosted wiki will not fetch from a http hosted wiki, which for 
a normal collaboration projects would mean "everyone use http XOR https".
2) Both the fetching and the serving side need the plugin installed. This 
means all parts have to intentionally participate, which is a natural thing 
in a *collaboration *project - but it does mean that single individuals 
have "no" use for it because ain't nobody to call. (This is probably a 
strong reason why there isn't much interest in it.)
3) Fetching fairly quickly became slow as more collaborators (i.e wikis) 
joined. This might be because a general "fetch", fetched from *all *
collaborators. 

For a small collaboration project this may still be useful.

Regarding (2) - was is at all possible to remove this condition, i.e so 
that one can fetch from any wiki without it having the plugin? That way one 
could subscribe to wikis and just use a filter so check if anything is new.

<:-)








-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/70d2afb6-1c87-49fe-8f83-b45d605365f7o%40googlegroups.com.

Reply via email to