For the 3rd party templates, there should be more info, where they actually come from. Users should have more control over the template links.
In browsers the browser vendors take care to block links to potentially dangerous sites. That’s not the case for stand alone apps. So we need to take care, that users have control. – Just a thought.
Currently, external-js is used to startup tiddlywiki (I remember that it seems to start faster), but the ctrl+s save under nodejs will automatically upload after the tiddlywiki saver is configured. If there is no configuration, it will try to save the HTML locally. Therefore, the current measure taken by the tiddlywiki app is to intercept the ctrl+s shortcut key that comes with tiddlywiki and use the default export operation.
This is the button you should see on the nodejs wiki.
Of course this configuration can be supported。 However, for better compatibility, I have cancelled the external-js startup method. I currently think that for some small wikis, the speed improvement perceived by users is minimal.
Note the use of {{$:/config/SaveWikiButton/Filename}} and {{$:/config/SaveWikiButton/Template}}
These are TWCore “hidden” configuration settings that determine the filename and template used for saving.
If $:/config/SaveWikiButton/Filename is missing (or empty), the TWCore code defaults to using the filename of the currently loaded wiki URI.
The default (shadow) definition of $:/config/SaveWikiButton/Template contains $:/core/save/all, which creates a full stand-alone single-file HTML wiki. To save tiddlers for use with an external-js core, this value should be changed to $:/core/save/all-external-js