I think with all these shared / collaboration concepts one thing is key:
separating "the wiki(s)" from "the store(s)"
For collaboration around TiddlyWiki, the single-file paradigm is
essentially untenable,
not just for the simple reason that to currently push 1 byte of "changed
tiddler"
you my need to push +2mb of "changed wiki"... unless you're using a pretty
vulnerable node server.
So, imho, we're looking for solutions with "prebuild" / "cooked" / "baked"
TiddlyWiki *wikis* that are configured to CRUD individual tiddlers to
whichever *stores* said wiki is configured to talk to.
So, making TiddlyWiki use Seafile or BTSync, you have two problems...
1. reading, writing individual tiddlers to stores
- perhaps different adapters / syncer modules to talk to either
- it should be possible to tell TiddlyWiki to which store out of x to
add tiddler y
- perhaps even to which subfolder
2. reading, writing the wiki (application) itself
- which could be the same as 1. if there was
- some skelleton TiddlyWiki with a basic configuration for some
"wiki-store"
- all customizations to the wiki written to said store
- in other words, separating content from presentation / the
application
- insofar that's needed for a proper startup
- the point being, that the wiki file itself is only modified when
absolutely necessary
- so as make use of caching and not clogging communication with
reading and writing an entire wiki rather than tiddlers
- of course, you don't want to make a bazillion requests per
tiddler either,
- so, talk to stores and read "bags", e.g. meaningful
collections of tiddlers
- while writing tiddlers back to it individually
Best wishes, Tobias.
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
