This is only for the node version of tiddlywiki and it is less polished than I would like, but it may be a week before I get back to working on it so I wanted to share it now.
For a while I have been using websockets with tiddlywiki to control my robot and as an interface between tiddlywiki and git. I finally got around to packaging the websockets portion up nicely into a plugin. Unfortunately I don't have a good demo application for this yet. I am working on setting up a git plugin as a demo but it isn't ready yet.
What this plugin lets you do is send messages between the browser and the node process.
This gives a framework for doing a few things that people have been asking for and discussing, including triggering bash or other scripts from a wiki, allowing edits to tiddler files (or adding tiddler files) outside of the wiki to affect the wiki without having to restart the node server, to search through folders of images or pdf files and create the .meta files to add them to a wiki, and, like I was doing with my robot, stream real time data into a wiki and use the wiki to control other systems on the computer. This can hopefully be used to make multi-user wikis by allowing the server to let each wiki know when a tiddler is being edited.
Now I just need to make some of it. It uses a two npm modules, websockets (the ws module) and it gets information it needs using the ip module. If you don't know what that means than this is probably not developed enough for you to play with yet.
<$button>
Test
<$action-websocketmessage $type='test'/>
</$button>
and when you click the button the window with the node process should display
in the console where the node process is running.
With this base worked out creating things that use this is relatively straight forward and as soon as I get a demo application set up I am going to write documentation for it. Hopefully this is something we can add into the node version of tiddlywiki after a bit of polishing.