3 ms·

I've looked into it a few times now, each time I get a little closer to actually using it. Currently I've moved from the "What? I have to install a browser plug

I've looked into it a few times now, each time I get a little closer to actually using it. Currently I've moved from the "What? I have to install a browser plugin to save changes?" phase to "I guess I'm going to have to sit down one weekend and find a hosting setup I like for this tool" I'm definitely interested in tiddlywiki, but there's so many options it's a little overwhelming on first glance. What does your implementation look like?

AlphaWeaver 7y ago
Actually, I started out by just using the simplest saving method possible, which is downloading a new version of the HTML file on every save. It seems clunky but isn't that difficult to do. I branched out to using the Tiddloid Lite [0] Android client, (Tiddloid and Tiddloid Lite are both free and open source, the Lite version just has a different feature set,) and I just uploaded my previous wiki into Google Drive and the app just worked... saving became completely automatic and it syncs to Drive without a hitch. I'm looking into standing up a TiddlyServer [1] soon for my upcoming project, and I'm planning on eventually doing some modifications to do data storage in a database instead of on disk. One thing's for sure: it's got a great gradual way to "get into" using it... it just isn't great at communicating those options in a way that isn't overwhelming. [0]: https://github.com/donmor/TiddloidLite https://github.com/donmor/TiddloidLite [1]: https://github.com/Arlen22/TiddlyServer https://github.com/Arlen22/TiddlyServer