TW5-Bob

Erlang backend process. # Bayesian & TF-IDF auto-tagging If Wikis are going to talk to each other, they need a shared ontology (understanding of words). Joe wrote code to analyze Tiddlers and predict tags based on content. The presentation showed that Bayesian inference worked well for predicting existing tags (85% accuracy) but TF-IDF provided tags that felt more "human." Similar functionality exists via modern plugins (like the TiddlyWiki Natural Language Processing plugins), though not the specific Erlang implementation Joe built. # Provenance tracking To track exactly where a Tiddler they borrowed the idea from Ted Nelson’s Project Xanadu). TiddlyWiki today has fields for source and creator, but the deep, automated chain-of-custody tracking across the web (Xanadu style) was a theoretical goal rather than a concrete feature. -- In time TiddlyWiki has developed other methods to achieve similar goals of "Inter-tiddler" communication. TiddlyWiki 5 uses an internal messaging system that mirrors the Actor model slightly. Widgets (UI elements) send messages up the DOM tree (eg. tm-navigate, tm-save-tiddler). It is event-based, but it is strictly local to the browser session and hierarchical, whereas the Erlang prototype was distributed and peer-to-peer. TiddlyWiki standardized on Node.js for its server-side implementation. This allows TiddlyWiki to run as a server, load tiddlers from the file system, and serve them to multiple clients. As it was simpler I preferred using the 1 TiddlyWiki html file solution. https://talk.tiddlywiki.org/t/how-to-tiddlywiki-on-nodejs-ng... You can HTTP fetch tiddlers from other TiddlyWikis, but it is a pull model (importing), not the asynchronous push/mailbox model Joe Armstrong envisioned. If you wanted to build a "Federation" of wikis today without using complex custom backends, you would indeed use tm-http-request to poll other wikis for updates. https://tiddlywiki.com/#WidgetMessage%3A%20tm-http-request A community version of TiddlyWiki called Bob (by OokTech) implements real-time, two-way communication between the server and the browser, and between different wikis managed by the same server. This is the closest functional equivalent to what Joe and Jeremy discussed, but it's built on WebSockets and Node.js. https://github.com/OokTech/TW5-Bob

b.com/OokTech/TW5-Bob is being built to serve one or more Wikis for multiple people, but I don't know that they have revision history (I could be mistaken).

dlyWiki to online publishing is built-in for http://tiddlyspot.com. And more I can't list. See main site for info. It has its own scripting language that includes string matching, maths and complex filters. In particular its "filter" mechanisms, that are largely list oreientated, allow complex interrogation and presentation of content. It supports JavaScript modules allowing full integration of good existing tools. There are libraries of plugins--both official (https://tiddlywiki.com/#%24%3A%2Fcore%2Fui%2FControlPanel%2F...) and unofficial (https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM -- hundreds) that extend function in many ways. There are also other versions of TW that are node based. Of the more interesting branches are "Bob" (https://github.com/OokTech/TW5-Bob) that provides all of TW's base functionality plus interaction with the OS on all major desktop platforms. Another is TiddlyServer (https://github.com/Arlen22/TiddlyServer). IMO its a very sophisticated and very effective tool for recording unstructured data in any form. The real plus in it is that you can then, if you need, begin to structure that data in innumerable ways. An upside is you can learn the basics very quickly. A downside is that it can take some time to fully understand all you can do in it and how to do it. For developers its Github gives insight into how it works and current developoments (https://github.com/Jermolene/TiddlyWiki5). It has a useful, friendly, discussion group (https://groups.google.com/forum/#!forum/tiddlywiki). Its a kind of "Swiss Army Knife" of information tools.