5 ms·

Have you tried TiddlyWiki [0] which is running the brainfck.org Zettelkasten mentioned in the article. Seems like a very similar concept. I am intrigued by the

Have you tried TiddlyWiki [0] which is running the brainfck.org Zettelkasten mentioned in the article. Seems like a very similar concept. I am intrigued by the concept and thinking about trying it out, so any input on picking one or the other would be great. [0]: https://tiddlywiki.com/ https://tiddlywiki.com/

romwell 5y ago
I've been using Tiddly Wiki for years, and can very much recommend it. To start, all you need is a template HTML file. No installation, no nothing - it's self-hosted within the HTML! You save changes by clicking the "Save" button, which generates an HTML with changes. If you really want, you can install a Node.js version which saves changes automatically. But you don't need it to start. I mostly use Tiddly Wiki to keep notes at work, but I also built this with it: http://romankogan.net/adhd/ http://romankogan.net/adhd/
- gwd 5y ago
  I started using TiddlyWiki many years ago and loved the idea, until browsers started cracking down on webpages saving files. Has that changed significantly, or do you still need some hack to work around it?
  - bachmeier 5y ago
    IMO you'll want to either run a local webserver or set up the Github/Gitlab saver. The other solutions are clumsy.
    - romwell 5y ago
      The other solutions don't require an install though, and are thus super portable :)
  - deleted 5y ago
    [deleted]
  - romwell 5y ago
    I never ran into an issue of needing a hack to save a file. It works just as downloading any file would. What was the issue that you ran into?
- japanuspus 5y ago
  Thanks. Spent half an hour playing around with it, and must admit that it seems magical. Implementation aside, the whole idea of splitting information into minimal parts _and then displaying your whole route_ on one page is a stroke of genius. The hardest part coming from the outside is grokking where the state (/database) lives: I soon found out that you could save everything in a new .html-file, and also got github sync to work, but I missed the option to use a local node-install. This is something I need to look into before comitting, as much of my workflow is centered around scripts modifying notes.
  - romwell 5y ago
    I started with a single .html file, and then moved to Node.js. You don't need to look much into it, since you can import data from the .html file. The only hiccup I've had so far was that I could reference images in the same folder with an [img[relative-path-to-file.jpg]] syntax from the HTML file, but not from the Node.JS version (you need to "import" images first). Wasn't a big deal for me, since I just had to manually update an image or two. Most of my notes in that wiki were just text.
jrm4 5y ago
I have. And where it just didn't do it for me is how everything's locked up in that file. Again, the killer part for me is that I can use basic Linux file tools on it easily; e.g. I can either use the internal search, which is good, but also grep.

romwell 5y ago

I've been using Tiddly Wiki for years, and can very much recommend it. To start, all you need is a template HTML file. No installation, no nothing - it's self-hosted within the HTML! You save changes by clicking the "Save" button, which generates an HTML with changes. If you really want, you can install a Node.js version which saves changes automatically. But you don't need it to start. I mostly use Tiddly Wiki to keep notes at work, but I also built this with it: http://romankogan.net/adhd/ http://romankogan.net/adhd/

gwd 5y ago
I started using TiddlyWiki many years ago and loved the idea, until browsers started cracking down on webpages saving files. Has that changed significantly, or do you still need some hack to work around it?
- bachmeier 5y ago
  IMO you'll want to either run a local webserver or set up the Github/Gitlab saver. The other solutions are clumsy.
  - romwell 5y ago
    The other solutions don't require an install though, and are thus super portable :)
- deleted 5y ago
  [deleted]
- romwell 5y ago
  I never ran into an issue of needing a hack to save a file. It works just as downloading any file would. What was the issue that you ran into?
japanuspus 5y ago
Thanks. Spent half an hour playing around with it, and must admit that it seems magical. Implementation aside, the whole idea of splitting information into minimal parts _and then displaying your whole route_ on one page is a stroke of genius. The hardest part coming from the outside is grokking where the state (/database) lives: I soon found out that you could save everything in a new .html-file, and also got github sync to work, but I missed the option to use a local node-install. This is something I need to look into before comitting, as much of my workflow is centered around scripts modifying notes.
- romwell 5y ago
  I started with a single .html file, and then moved to Node.js. You don't need to look much into it, since you can import data from the .html file. The only hiccup I've had so far was that I could reference images in the same folder with an [img[relative-path-to-file.jpg]] syntax from the HTML file, but not from the Node.JS version (you need to "import" images first). Wasn't a big deal for me, since I just had to manually update an image or two. Most of my notes in that wiki were just text.

jrm4 5y ago

I have. And where it just didn't do it for me is how everything's locked up in that file. Again, the killer part for me is that I can use basic Linux file tools on it easily; e.g. I can either use the internal search, which is good, but also grep.