https://tiddlywiki.com/ is an amazing piece of software, but it relies on saving and keeping a file on your local drive with all the data and code and markup mixed in, very nice and old-school and anti-cloud thing.
I wanted to use it, but didn’t want to keep a file, as remoteStorage was a so nice fit for the “tiddlers” model, so I wrote this plugin: https://github.com/fiatjaf/tiddlywiki-remotestorage. It saves each tiddler individually in a remoteStorage key (using the syncadaptor TiddlyWiki architecture), so it is different from other plugins out there that save your entire HTML to some cloud provider (except, I guess https://noteself.github.io/ and http://tiddlyweb.com/).
Anyway, that doesn’t matter. i believe remoteStorage is the best fit for the TiddlyWiki model.
Plus, you get the ability to more easily share your TiddlyWiki if your tiddlers are in a /public namespace (you can choose – and you can keep multiple TiddlyWikis on the same remoteStorage account, don’t worry) in a publicly-accessible remoteStorage.
To make that even easier, I made https://tiddly.alhur.es/ available. You can visit https://tiddly.alhur.es/ and authorize your remoteStorage to start editing, and you can link people to https://tiddly.alhur.es/<your remoteStorage account>/<this TiddlyWiki remoteStorage subdirectory> and they’ll be served with the tiddlers stored in the given subdir.
(Everything is under the /tiddlers namespace, so either /tiddlers/<subdir> or /public/tiddlers/<subdir>.)
