Mat, It has the potential for that but it isn't there yet. Like with twederation the potential is there but adoption seems to be the problem judging by the response I have seen.
Since I haven't really gotten much feedback on this I have just been making what I want smashed into one big plugin. So I have a setup where on the local network the wikis are accessible to people I know who can edit them without restriction. The framework for a per-user list of uneditable tiddlers is in place, and for a list of tiddlers that are only given to specific people. I haven't had a use for those yet and I haven't really had feedback aside from people who seem to be using it like I do so I haven't bothered with it. It is certainly not secure in the way it should be if it were used on the open internet. I think that I am going to make this into the multiuser edition and split it into the 5 or 6 separate plugins because it is a lot of different pieces. If we added the browser part of the websockets, which is actually quite small, to twederation it wouldn't change anything about how single file wikis interact but the wikis could then connect to a node server using websockets and it could mediate updates and make the whole system much more scalable. Instead of sending the initial hello world message to a google server it could be to one of these servers. But that would only use a small part of the multiuser setup so I should probably split this into different plugins first. -- 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/7bab1883-25e5-4260-a991-195b7631be3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
