Hi Dmitry,

Without getting into too much detail atm, thank you for your very well 
thought out response which quite put your motivation(s) into perspective.

You are indeed quite ambitious and I now see that you are rather good at 
communicating a clear perspective, perhaps leading to workable future 
frameworks, in terms of organisation as well as technological focus.

Of course, you can imagine that *multi-user* is a buzzword that probably 
popped up as early as the first year of TiddlyWiki being around.

With the end of TiddlySpace and plenty silence around TiddlyWeb, the most 
advanced collaborative technology for TiddlyWiki didn't quite manage to 
sprout, if only for its gardeners having gone and focus on other fruits to 
harvest.

So, at this point, it seems, we've gone back to square 1 for now in terms 
coming to new forms of TiddlyWiki-driven collaboration. You can still see a 
remnant of previous collaborative efforts involving inclusion of bags of 
tiddlers in the context where needed in something like: 
http://mbtf.tiddlyspace.com, knowing that local centers were able to 
include the master documentation and branch of from there, extend it as 
needed... while the master documentation would be able to list and display 
local variations of itself.

I am in no position to say wheter TWederation has the potential of filling 
the collaboration gap or not.

Possibly, a node.js & GitHub driven workflow, especially for a developer 
community seems to make for a splendid TiddlyWiki based collaboration 
platform, including versioning, and conflict resolution via merges, etc... 
with the master being publicly accessible for consumption, for example... 
somewhat similar to TiddlyWiki.com. But, of course, this type of workflow 
is hardly apt for the general public, or so it seems, for now. but perhaps 
it actually isn't. There once were some tests regarding a GitStore 
implementation... you know, storing tiddlers in GitHub directly, from 
within TiddlyWiki. But you can imagine the complexities of resolving 
merge-conflicts, should they arise.

As for a P2P web of tiddlers, it appears we've only just started exploring 
this kind of technology, e.g. via BeakerBrowser <https://beakerbrowser.com/>. 
How this helps advance multi-user applications, at this point, is more or 
less unknown.

Anyway, there's solving all the little challenges which I think is what 
this group is doing, mostly, every day. But perhaps it's time to consider 
the more long term challenges a bit more frequently and a bit more 
strategically, not just from a development point of view, in terms of 
code-base that is. How and possibly where that may unfold, we have yet to 
see.

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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/399b97e9-2217-456f-a97a-b636d892f4de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to