TIDDLYDESKTOP IMPORT PLUGINS CODE

So, the initial default TiddlyWiki app should be a sort of launch pad. “more scalable” for me really was all about future features – multi-user, private encrypted and public mixed, and so on. There is something interesting in this direction, but it shouldn’t be where we start. Looking at this again, this is more complex. With Fission, where we have a user account and both private file storage as well as public storage, I was thinking that one could take advantage of that to seamlessly have both private, encrypted tiddlers – in a user’s /private/Apps/Jermolene/TiddlyWiki space, as well as public tiddlers in /public/SomePath/TiddlyWiki. I think this might even be able to be mixed and matched, which could be interesting. The individual tiddler mode is most often used in various server configurations: each tiddler is an actual file.

TIDDLYDESKTOP IMPORT PLUGINS CODE

The default mode of TiddlyWiki is working in single file mode, where code + content is all in one html file. I used the fake phrase “would be more scalable”, and I really should explain myself Rather than single file, storing tiddlers as individual files would be more scalable, relying on Fission’s user / encryption to keep things private.Įxpanding on this. Fission’s key based system can communicate directly to the backend to sign requests. This can work very similarly to the existing “Git Savers” – see pesho’s tutorial, and the general Git saving service description on TW – which has setups for Gitea and Gitlab as well.Ĭurrently the info is stored in user storage for the personal access token to connect to these systems. Should initially start as a single user “Fission Saver”. Note taking is seeing a lot of attention recently, with both Notion and Roam Research bringing a lot of attention.įor those looking for similar systems, that however have the data under their control, TiddlyWiki on top of Fission would be an option. Direct link to the GitHub “savers” core file TiddlyWiki5/github.js at 3eacdc19fdb4ed7ce864a04dd87a5e1c6492daac.GitHub - jimpick/dat-tiddlywiki: Multiwriter Dat + TiddlyWiki.Jim Pick implemented a multi-user TiddlyWiki on top of DAT The kind of “Roam clones” are TiddlyBlink / Stroll or Drift. Recently, it has a number of different “Savers”, including Git savers It started off as a single page HTML / JS file that would save back to itself. Content is composed of “tiddlers”, and tiddlers, tags, and custom fields can be added, as well as many plugins.

TiddlyWiki is a fascinating note taking / wiki project with a long history. We’re moving ahead with TiddlyWiki on Fission, so have moved this post to the dedicated App category for it Description The plugin.Note: this was originally written as an “App Idea”. It can also optionally identify files external to the plugin folder that should be loaded as tiddlers. Plugin folders must contain a file that contains the metadata for the plugin. On the server, plugins can be stored as ordinary JSON tiddlers but it is often more convenient to store them as separate tiddler files within folders. Do not add the PluginFolders under a specific namespace: TiddlyWiki will attempt to include every subfolder as a plugin.

Place the PluginFolders containing the plugins in a plugins folder within the wiki folder.

The plugins can be referenced in by their name (e.g.

Use environment variables to tell TiddlyWiki to search those folders.

Arrange the PluginFolders containing the plugins in a convenient shared location.

Tiddlydesktop import plugins