First, it is a not a good idea to have multiple people using Bob to access 
the same wiki at the same time. They would fight over file changes and you 
would get a lot of phantom tiddlers that you can't properly delete and 
infinite loops of different instances making changes to the same tiddler 
again and again.

Unfortunately the security components that Jeremy is working on probably 
won't play well with Bob. Supporting multiple wikis simultaneously makes 
reusing the single wiki server components difficult at best and I don't 
think that the normal server anything for the websockets.

I am currently polishing up my online version of Bob. It has better 
security than most online services, but given the horrific state of online 
security that is a pretty low bar. I wouldn't trust it with plans to 
overthrow a national government, but I think it is secure enough for most 
things short of that.

We have been using it for OokTech things for a few weeks now and it hasn't 
given us any trouble. It is on our server and accessible online and we 
haven't had any trouble yet.

It is Bob with secure logins and proper access controls so you can 
configure who can see or edit wikis individually and I have fine grained 
controls over what each person can do in each wiki.

We were hoping to have the public demo up this weekend but progress is slow 
because I have very spotty internet access at my home right now. Also the 
rest of OokTech is insisting that I make it a bit polished before I open 
the public demo.

-- 
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/ce45a2b3-454c-4584-a292-f1c785f60eee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to