Previously only a single local folder could be attached at a time. Now any number of local folders can be attached. (Local folder functionality is supported only by chrome/edge based browsers)
Previously subfolders could not be created or managed. Now subfolders can be viewed and created. This feature is available on both the Local Folder and the Browser File Storage (OPFS) flavors
The “create wiki” page now supports loading from a custom url
Tiddlystow v2 is implemented as static html + javascript. The term “static” is relative to the server. The server doesn’t need to dynamically generate anything, only serve the files.
It is implemented using a service worker which requires a web server (IOW, it won’t work from file:/// url) at initial launch. But since they are static files, there are lots of easy deploy options.
I didn’t test this exact procedure, but something like this should work:
run a web server to serve these files on your local host (i.e. python -m http.server, rclone serve, thousands of other options).
using your browser, visit the /v2 url on your local host webserver
once you confirm it is working, you can stop the webserver forever (or until you want to upgrade) since the service worker provides offline support…all the html/javascript/etc. files are cached in your browser storage.
You can perform similar procedure to deploy to your favorite static hosting service on the internet.
Unless i missread this, rather than reproduce identical static servers everywhere it would seem sensible to install it under a tiddlyverse domain and let us all use the same one?
I created a directory. The error message is:
The webpage at https://btheado.github.io/tiddlystow/v2/i/dir1/ may be temporarily unavailable, or it may have been permanently moved to a new URL.
If you’re not having any issues, it might be a VPN problem.
