5 ms·

If you like this idea, but prefer something more self-contained, Tiddlywiki is an excellent option, as it runs in-browser from a single HTML file. Its core appr

If you like this idea, but prefer something more self-contained, Tiddlywiki is an excellent option, as it runs in-browser from a single HTML file. Its core approach is to treat notes as a queryable database, and its markup supports dynamic content based on queries of that DB. Because its UI is constructed from the same DB, the same techniques that allow you to construct a dynamic view from the DB also allow you to construct custom UIs for that view, including changing properties/attributes of items in the DB. That's all pretty abstract. A simple example: it allows you to construct a tabbed view of several todo lists based on tags and fields and adjust priority and status from that single UI. It's been available for many years, but has never been trendy, despite its unique design and strengths. I recommend giving it a spin!

pqs 4y ago
Can Tiddlywiki be used by a team with simultaneous edits?
- rpdillon 4y ago
  Not at all, AFAIK. Completely single-user in my experience.
- RyEgswuCsn 4y ago
  You can. But you need to host it with a nodejs server.
lr1970 4y ago
> It's been available for many years, but has never been trendy, despite its unique design and strengths. I recommend giving it a spin! I was a heavy TiddlyWiki user in the past but moved away from it precisely because of its singe-HTML file design. Modern browsers like chrome made it virtually impossible to save an edited page. Not TW's fault per se, but ruined my experience with it. There is a way to install TW-5 with node.js as a directory tree but my ship has sailed. Now I am a happy obsidian user.
- rpdillon 4y ago
  Yes, that aspect of the design makes it feel like a toy, which is a shame. I've written my own tooling for saving to bridge this gap. It's a Python script that provides a response to an OPTIONS call so Tiddlywiki's native WebDAV support allows seamless saving. It also provides automatic backups and an index page to serve multiple wikis. I've used it for my last two jobs and in my personal life and I'm really happy with it. I hope to make it available publicly in case others find it useful, just haven't gotten around to it.
RyEgswuCsn 4y ago
I use tiddlywiki (with the nodejs setup) regularly. It's great until your wiki grows too large, at which point you need to wait ~10s for it to load even with modern hardware.
- rpdillon 4y ago
  I'd be very curious to hear about the sizes and use cases where you're seeing this. My understanding was that single file wikis could scale to a hundred megabytes and beyond, and I thought the nodejs version was more scalable than that due to lazy loading tiddlers. My wikis tend to be less than 20mb since I mostly use plain text for everything.
  - RyEgswuCsn 4y ago
    I do make use of the `backlinks` query extensively, and I use saqimtiaz's wonderful `streams` [1] plugin to recreate a Roam-like experience. This setup leads to a large amount of small-sized tiddlers (2.5k and counting), which might add to the overhead. Not to mention downloading and parsing 20mb-worth of html+js each time you open up the wiki can be quite slow. As for lazy loading --- when enabled, it breaks the indexing (e.g. finding backlinks) and searching because these are done by the js inside the browser too. I only lazy-load images and binaries because they are not indexable anyway. [1]: https://github.com/saqimtiaz/streams https://github.com/saqimtiaz/streams

pqs 4y ago

Can Tiddlywiki be used by a team with simultaneous edits?

rpdillon 4y ago
Not at all, AFAIK. Completely single-user in my experience.
RyEgswuCsn 4y ago
You can. But you need to host it with a nodejs server.

lr1970 4y ago

> It's been available for many years, but has never been trendy, despite its unique design and strengths. I recommend giving it a spin! I was a heavy TiddlyWiki user in the past but moved away from it precisely because of its singe-HTML file design. Modern browsers like chrome made it virtually impossible to save an edited page. Not TW's fault per se, but ruined my experience with it. There is a way to install TW-5 with node.js as a directory tree but my ship has sailed. Now I am a happy obsidian user.

rpdillon 4y ago
Yes, that aspect of the design makes it feel like a toy, which is a shame. I've written my own tooling for saving to bridge this gap. It's a Python script that provides a response to an OPTIONS call so Tiddlywiki's native WebDAV support allows seamless saving. It also provides automatic backups and an index page to serve multiple wikis. I've used it for my last two jobs and in my personal life and I'm really happy with it. I hope to make it available publicly in case others find it useful, just haven't gotten around to it.

RyEgswuCsn 4y ago

I use tiddlywiki (with the nodejs setup) regularly. It's great until your wiki grows too large, at which point you need to wait ~10s for it to load even with modern hardware.

rpdillon 4y ago
I'd be very curious to hear about the sizes and use cases where you're seeing this. My understanding was that single file wikis could scale to a hundred megabytes and beyond, and I thought the nodejs version was more scalable than that due to lazy loading tiddlers. My wikis tend to be less than 20mb since I mostly use plain text for everything.
- RyEgswuCsn 4y ago
  I do make use of the `backlinks` query extensively, and I use saqimtiaz's wonderful `streams` [1] plugin to recreate a Roam-like experience. This setup leads to a large amount of small-sized tiddlers (2.5k and counting), which might add to the overhead. Not to mention downloading and parsing 20mb-worth of html+js each time you open up the wiki can be quite slow. As for lazy loading --- when enabled, it breaks the indexing (e.g. finding backlinks) and searching because these are done by the js inside the browser too. I only lazy-load images and binaries because they are not indexable anyway. [1]: https://github.com/saqimtiaz/streams https://github.com/saqimtiaz/streams