XD. Always a pleasure to you see on these here innanets, sir. `/salute`. Family and I were talkin' about you the other night during Family Gathering. What's your plans for what you got left on this rock?
It's simply not the best thing since sliced bread. I'm not here to sell it to you. I'm still planning and prototyping a replacement for my own (which is much more difficult than you might guess [for comparison, I've found building TW "correctly" from scratch {for my usecase} about as difficult as creating a full-blown `micro`-esque text editor written in a high-portability Forth-like composable system disciplined by a Rust VM {a tiny, self-describing, scriptable terminal computing environment: part editor, part language runtime, part automation surface, built so humans and aigents can inspect, replay, and safely modify work with ergonomic precision}, but that's, in part, because ChatGPT cloudtainers have historically been somewhat more suited to this task]). You'll note that many tools have been built in virtue of Tiddlywiki, quietly. The community is fabulous (and it needs to be because the documentation and updateability have always been lacking), and that matters when you get stuck, imho. I am indebted to these people.
I've been an extreme user every day for a decade, and I no longer recommend it in most cases. I've even moved my family off TW. I maintain mine, in part, because I have a public deliverable, and an offline-first, kitchensink, batteries-included single html file is exactly what I need within my technical constraints. If you don't need hackable unified portability meant to serve others (I happen to value sharing the pilot's seat with my audience as well), I think you should consider looking elsewhere.
I also don't have time to design interfaces from scratch, and TW's is acceptable enough that I don't have a cheap substitute to migrate to. AI has also lowered the friction for customization to the point where I don't think TW's way of doing things is the best way for most people. Here's my advice: if you're not building something meant for others to navigate, then just organize your files on your own machine, and when you can't do it on your own, interface with and shape your data with the assistance of the noble wireborn sandpeople (LLMs). Don't go down a useless toolpr0n rabbithole (that goes for all the tools you listed). Make things that matter.
Very cool project. I would like to caution against confidence in the claim that a ton of games wouldn't be necessary for plausible data. I also am not convinced that anyone but human experts in particular matchups are really in an appropriate epistemic position to say much in sufficiently complex magic formats. Game wins are probably a better indicator on average.
I can appreciate this desire. Printing my website is basically out of the question at this point. I rely upon people thinking it worthwhile to keep a copy, and I make it fairly easy for people to do so. I distribute on a number of networks, I offer a number of snapshot archives (e.g. https://web.archive.org/web/*/philosopher.life), and I make it easy to download a complete copy of the entire site (https://philosopher.life/#Readme), as it's just a single html file. I do ask family and friends to see it as a book they will keep in their libraries, and I keep it very small, almost pure text (I don't want it to be any further a burden than it already is). Some store it on a thumbdrive or even keep it as an e-mail attachment. And, that it is nearly pure text is something that I think is exceptionally useful for this problem, as even if there aren't browsers that will be able to render it (that would be sad), there may be tools that can at least read the source (and, in a way, the site is meant to be somewhat readable from source, though it requires some motivation). I also enjoy the knowledge that there are random copies out there sitting on hard drives. I think it's gonna take some luck too.