Hi Alren Thanks for starting the discussion. I’m going to respond with a few points here to keep the information together.
Firstly, TiddlyWiki under Node.js is specifically designed for multi-user scenarios, but there are some rough edges that make the experience imperfect at present: * There’s no separation between different users, so they share the same username for signing edits, and share the same state data (much of the state data isn’t synced to the server eg for popups) * There’s no instant notification of changes made by another user * There’s no feedback if the edits of another user clash with your own * There’s no support for multiple revisions None of those things present any implementation difficulties. The biggest architectural change that I can see is to separate the client wiki from the server wiki, so that they don’t need to be same (with the same plugins etc). The best approach to the problem you mention of all the tiddlers being shipped to the client is to shift some or all of the processing back to the server. For example, we can ship skinny tiddlers to the client, but handle searches on the server. Or, as you note, we can generate standalone HTML tiddlers on the server. (In that situation I would handle interactivity by swapping in revised definitions for macros like the TOC, or tabs, that use minimal JS to manipulate state in the DOM (like Bootstrap etc)). As you reflect in the Google doc, there are some security issues with sharing TiddlyWiki content on the server. On the whole, I don’t think they would be a huge problem for a community documentation project. TiddlyWiki’s strong encapsulation at the HTTP boundary makes it easy to build new and different server sides for it; a simple serverside for TiddlyWiki is a good deal less complicated than TiddlyWiki itself. So I’d always encourage such experimentation. In my day job, I’ve been doing a lot of work with getting TiddlyWiki running under Amazon Web Services. Rather than a conventional server, I stitch together services like S3, CloudFront and Lambda to build TiddlyWiki HTML files and provide an API for them to use. Personally, I’m a huge fan of not having to run a conventional server, and not having to worry about patches and intrusion attempts :) Your document strays into some questions around the design collaboration systems. My own view, which evolved before TiddlySpace, is that shared spaces do not work beyond a very small number of users. I’m still an enthusiast for the approach that TiddlySpace took — separate spaces for individual users or small, trusted groups, and space inclusion as the primary sharing mechanism. It’s the same thinking as the current TWederation work. Best wishes Jeremy > On 16 Dec 2016, at 22:06, Arlen Beiler <[email protected]> wrote: > > Hello Everyone, > After making the comment on the documentation, I started wondering exactly > what it would require to re-invent the MediaWiki juggernaut as TiddlyWiki. > Here is what I came up with. Part of this comes from my experience on > Wikipedia, and part from setting up my own MediaWiki installations on my > computer. Not that I have a lot of experience, but for what it's worth. > > https://docs.google.com/document/d/1Y8qV6I9BI1vgvve5kfThLKUOPu0aeF-FiCNpWvP62Hs/edit?usp=sharing > > <https://docs.google.com/document/d/1Y8qV6I9BI1vgvve5kfThLKUOPu0aeF-FiCNpWvP62Hs/edit?usp=sharing> > > Feel free to add comments on the document itself or here. > > Enjoy! > -Arlen > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <https://groups.google.com/group/tiddlywikidev>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSRNaznTeB1qupTmgzW4bK6%2BNaLFrOv2CUEi7MoZLaiYow%40mail.gmail.com > > <https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSRNaznTeB1qupTmgzW4bK6%2BNaLFrOv2CUEi7MoZLaiYow%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/B274027C-5B15-4603-9EB9-8C2107968AEC%40gmail.com. For more options, visit https://groups.google.com/d/optout.
