In the very short period of time I've used it, the last month or so, I have come to very much enjoy TiddlyWiki. The take it provides on the concept of a non-linear notebook is one that resonates with the way my brain operates and has stuck unlike apps like Obsidian, Logseq, Roam, Notion and the other apps in the slew that have emerged in the past couple of years. I think it is TiddlyWiki's approach that every piece of information can fit on a card (or 'tiddler' using their language) and that pieces of information should be as small as possible from which they can be linked and related that has made it click for me.
I feel as this system is the digital manifestation for my love of notecards and sticky notes. I only wish I learned of this tool many years earlier so I could have started to amass such a notebook as part of my work for my Master degree. But, like they say about trees— "the second best time to plant a tree is today."
So planting my notebook of a tree has begun.
—
The biggest frustration I have come across with TiddlyWiki is the saving of the file. TiddlyDesktop is the best option, but when working on two different devices (one being corporate issued) the syncing of the files isn't as streamlined as it should be. Then there is the issue of file access and editing on an iPad. Everything is harder on an iPad, and while Quine 2 exists it's buggy when it comes to syncing and saving files. Not all of the blame falls on the app, much of it has to do with the iPad platform itself.
Most of all, accessing the wiki file when you're not on your normal device, or sharing it with others publicly so it can be linked to is next to impossible with any of the aforementioned options. This leads to hosting the wiki online for easy access. Adding a file to a custom domain is easy; making it editable and sayable is a bit trickier.
To work through this challenge I've used tw-receiver: TiddlyWiki Plugin - save to PHP server in combination with my shared hosting. The setup was easy enough, and the saving works most of the time, but I've run into a couple of issues. The connection to the saving modules fails, the backups are created in such a way that aren't all that useful, or that a fresh copy of the wiki isn't always served by default when the wiki is loaded— a refresh seems to be needed sometimes.
All of this is to say— I'm in love with TiddlyWiki, but like any relationship based on love it isn't without its frustrations. I had a bit of a saving scare today where I thought I lost a full day's worth of heavy work. Thanks to a server-side auto backup, the scare wasn't as bad as I initially thought, but it was a scare nonetheless. Moving forward I'll continue to monitor the saving process and change up my plan if I run into any ongoing issues.