I am going to change the name of the multiuser plugin because it outgrew 
that name a few months ago and it is probably leading to more confusion 
about what the plugin does than anything else.

While I am doing this I am trying to decide if I should split it up into 
separate plugins or not. This is probably going to be a more involved 
process than I had hoped, and since tiddlywiki doesn't have a robust plugin 
dependency system in place it may be a bit of an annoyance to use because 
of how the  plugins would depend on each other.

So instead of just pushing forward and doing a lot of work splitting up the 
plugin I am going to ask:

Does anyone who would use the plugin not want the full functionality?

At the moment it can:

- Serve multiple wikis
- Have two-way (almost) immediate updates when a tiddler is edited either 
in a browser or on the server
- Support multiple people editing the same wiki at the same time
- Convert an html wiki into a new node-based wiki and export a node based 
wiki as an html wiki (this function is a bit rough still, but eventually it 
should let you go mostly seemlessly from a single file to node and back)

It does most of this using websockets so there is a server command that 
uses the web socket adaptor and an external server command that lets you 
use an external server (like an expressjs server) which makes 
authentication and access controls much simpler. (I am going to have a 
publicly accessible demo of the multi-user wiki setup sometime soon, shh! 
it's a secret.)

-- 
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/95cdebc3-7d10-4e2e-a059-8c95e308619e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to