If we’re talking about breaking compatibility, then the first suggestion from me is either shifting to Markdown as the default markup language, or adding support for Markdown as an fully functional alternative to WikiText.
2 Likes
I think this is a topic where TW’s flexibility is both a boon and a bane; which user-base should the future be geared towards?
Developers, from what I can glean as a non-programmer, want something that is more similar to other software solutions.
Product Users who want a mostly ready to use product would benefit from a more modern UI and a little more “linearity” but I think the problem with both is that they can mean different things to different users.
Tinkerers are the most likely to roll with TW’s quirks regardless. My biased view as a tinkerer is that this is the only tool that exists for those without full on developer skills but are still interested in building and not just using, so keeping things open to non-developers is important.
I was alive in the 90’s when the internet came about and remember the chatter about what it could be used for, and then seeing what it turned out to be. I hear the chatter about AI now and I see how the early usage by the general public (non-tech people) is already veering from what the tech people think AI is going to be used like. Your average person isn’t going to be integrating AI with TW for their needs, they’re going to grab a premade fully finished product, possibly one made with TW, but at that point the tinkering and flexibility of TW isn’t what they were looking for in the first place.
My day job is in metal fabrication. I work with everything from modern machining to processes that are fundamentally the same as they were when discovered in The Bronze Age. Even as a non-programmer, I can see that AI in programming is yet another tool and not a means to an end.
Your average person can’t be bothered to run a home 3D printer despite technology being as cheap and easy as it is nowadays, but they will use Amazon Alexa to do shopping. They’re not going to bother with AI beyond finished consumer applications. I think hypothesizing about that potential user-base to attract misses the point of what makes TW unique.
9 Likes
100% agreed to this.
My first TW usage was 2009 with TW Classic, and the doubleclick-to-edit made for a very low barrier (at the time) to move between reading/editing.
In the last few years, my note taking has mainly been in tomboy/gnote, which does as you describe - provide a richly formatted visual output in the window which is editable at any time. There is no distinction between a reading and editing mode.
Returning to TW in the last year and picking up TW5, the loss of doubleclick-to-edit I was originally disappointed with, though there is a plugin which implements it and I’ve only set it on one of the several TW I have. The problem being that sometimes I want to doubleclick-to-select, so adds frustration in another direction. (“doubleclick = edit only if no text is selected” is an idea I’ve thought of, but I need to learn JS coding before seeing if I can tweak the existing for that)
Anyway, for my taste, tomboy/gnote style “the viewer IS the editor at all times” distinction would be wonderful - and keep a dedicated “edit the markup directly” mode for the power user gurus who want to get their hands that little bit dirtier!
(I do think an always-an-editor mode needs a more powerful undo/view-old-revisions history though, since the chance of accidentally “I typed in the wrong window and didn’t realise it till later” is much higher. I use TW via node so I get tiddlers as individual files, and shovel the whole thing into local git, but a more integrated solution would be great (and indeed, some of David Bovill’s demonstration (on the "Hitchhikers TiddlyWiki All-Nighter) of running local shell code via TW feels like a potential great step in that direction)
2 Likes
That’s how my TWs work, for the most part.
Edit your tiddlers through another tiddler[1] – call it your “master editor”. Let it navigate through your tiddlers, selecting them for editing. Viewing them in the story, they update “live” as you type in your editor.
Whoever it was that said, “the only limit is your imagination,” was dead right. Stop looking at the way TW is presented on tiddlywiki .com as “the only way”. TW is not hardware – it was built to be modified. TiddlyWiki puts the soft back in software.
[1] Take great care modifying macros and css live. And by "great care" I mean don't do it.
2 Likes
Correct me if I’m wrong, but what you describe sounds like the editor is still separate to the display though, but instead of needing a preview pane to the editor, the edits are reflected live instantly? It definitely sounds neat and I’m interested to know how you did that, but it’s not what I imagine as the ideal.
Many of the comments here make good points. Things I’d like to see TiddlyWiki improve on going forward:
- Live WYSIWIG editing like @linonetwo’s slate-write. This is “table stakes” for apps in this category today.
- A more official shared / community plugin repository system. The TiddlyWiki plugin repository could point to CPL, Relink, Kookma, Fibbles, EvidentlyCube, etc. - the plugin repositories that contain so many handy utilities. Maybe some of these could become “Recommended” by the core (Relink or TW-Commander, for instance).
- Document and extend the
tiddlywikicommand line interface. Give examples, and simplify common operations (for example, rendering a tiddler or filter for a single-line wiki should be as simple astiddlywiki my_wiki.html --render "Index"and write tostdout).- Blur the line between single file and NodeJS wikis. It’d be great if I could trivially “explode” a single file wiki, edit the files, and then “implode” it back.
I’d also like many of the features that have open PRs - dark mode customization, AI integration, AST node serialization - to land, but I know that this takes time.
To import a single file wiki into a NodeJS one, you can do
$ tiddlywiki newwiki --load path/to/file.html
It works even if the single file wiki is password protected:
$ tiddlywiki newwiki --password 123 --load path/to/file.html
I have created an older thread regarding this months ago, expressing my concern that this leaves the plain text password in the shell history file though.
To export it back, after editing the files, you can do
$ tiddlywiki newwiki --build index
Am I misunderstanding this part and you mean something else?
1 Like
My Viewpoint on TiddlyWiki
TiddlyWiki is a scalable framework that adapts not only to the user’s skill level but also to a wide range of use cases. Hear me out.
Let’s say I want a simple journal. TiddlyWiki handles that effortlessly. As I get more comfortable, I can explore fields and transclusions ({{||}}, {{!!}}, etc.), learning in small increments or keeping things relatively unchanged. If I’m more technically inclined—like I am—I can experiment with HTML, CSS, and even bits of JavaScript.
What I love most is pushing TiddlyWiki beyond its typical use case. Is been turned it into a PC desktop clone, an Excel-style spreadsheet, and even a desktop application framework. It scales with both the user’s knowledge and creativity.
The few limits I’ve encountered are minor and often feel like gaps in my own knowledge rather than flaws in TiddlyWiki itself. I refer to it as a framework because it doesn’t function like any other tool I know. With plugin support, I genuinely can’t think of any major constraints—it operates much like game engines or other frameworks, except it’s built on HTML, CSS, and JavaScript.
What sets TiddlyWiki apart is its unique scalability. Whether you’re my grandmother or a JavaScript cyber-god, both can use it comfortably without a steep learning curve. While some features could be more user-friendly, its progress and stability are mind-blowing 
. Most frameworks break old plugins with every minor update, but TiddlyWiki remains impressively robust.
If a few suggestions could be made, a more robust editing, highlighting is problematic, the “”" function isn’t by default a button, text scale and font are not available on a per tiddler basis without knowing @@values or css, canonical_uri is a “hidden feature” many fields are not easily understood at a glance things like caption & description. Documentation is very lacking, it takes a long time for docs to catch-up with features or user’s end up making wikis to further explain syntax.
3 Likes
Jeremy
Can this thread be “pinned”.
I find it important. And needs highlighting for a few months, IMO, to get maximal feedback.
Best, TT
4 Likes
As this thread became a general TW feedback thread, I’d like to note that in this forum all feedback will come from TW enthusiasts. That is, if a person looks at TW, finds it to be complex, and moves on to use some other tool, then chances of them stumbling into this thread are extremely slim.
Maybe worth submitting a message in the Obsidian forum to get some of those users’ feedback (that is, users that looked at TW but ended up using Obsidian)
7 Likes
First, you know, others don’t, I am not code literate.
But, readers, keep that in mind.
TW is more than bare coding. It is a kind of philosophy too.
In the past I have praised it for being “agnostic”–that still works.
Most everything else is not agnostic in it’s application.
The agnosticism of TW on uses is a WINNER.
TW let’s users (albeit experts already) MAKE what they desire without limits.
A comment, TT.
4 Likes
Probably a topic for another thread, but this doesn’t work as I’d expect:
tiddlywiki --verbose newwiki --load somewhere/some_wiki.html
doesn’t make newwiki in my directory. Creating and loading also doesn’t make files for any of the tiddlers:
tiddlywiki --verbose newwiki --init
tiddlywiki --verbose newwiki --load somewhere/some_wiki.html
(for any folks reading - I think you need to import the wiki)
This is where I think the command line interface could be improved for TiddlyWiki. Having one-liners to “explode” and “implode” a wiki would go a long way.
I would just say there are good thoughts on this topic: TW5+TW6 informal discussion - including my own.
Vision
I have some thoughts and experience that from an organisational and values perspective, which I have DM’d you about.
I will comment on the product’s vision. I think of TiddlyWiki as one of the closest realisations of the concept of hypertext, all the way through the application’s design.
Ward Cunningham’s Wiki Design Principles combine with the Tiddler Philosophy for a working and reading environment that enables and encourages the use of hypertext at every turn.
Distribution (more related to TWX)
I also think having some more ‘batteries included’ would help, perhaps having a few core extensions that are very limited in scope, where they won’t be extended further and create ecosystems of their own. I am thinking of GNU Emacs here. In Emacs, is the ‘vanilla’ toolkit that has to be turned on & customised to be better (e.g. icomplete), with competing third-party suites that have their own extension ecosystem (helm, ivy, vertico) that are at varying levels of integration with the core. Emacs very conservatively expands its core offering, while never breaking compatibility.
Unfortunately, this leaves the user with an uncomfortable uncertainty on if they’re truly getting ‘the best’. It also means that if you are heavily invested in one of those toolkits, you’d have to rework your entire stack of Emacs packages* if you want a specific new feature.
*very similar to TW plugins, with updaters and all.
I would encourage you to look into the world of Emacs as I think the way it splits off and has its own ecosystems of packages around a fairly consistent core is very similar to TiddlyWiki. Emacs also has popular distributions like Doom Emacs, which introduce users to the Emacs ecosystem, while still relying on the same core code.
You could also take some notes from Linux distributions in this regard. There is a full graphical desktop that’s the default, most prominent link, but also a minimal release that is often ‘headless’ and intended for servers. Most of the packages are the same, with a last 300 or so totally optional packages. As long as you have a good idea of how large the core should be, shipping some high-quality packages alongside would be reasonable to get more users through the proverbial door.
Let TW be like Fedora, which offers:
- A standard ‘semi-skimmed’ release
- A ‘skimmed’ release for special cases (Server, CoreOS)
- Distributions downstream of it can be more akin to ‘whole milk’ (Nobara, Ultramarine, Universal Blue/Bazzite).
There has been talk over and over about how different distributions of TW could work and I think there is more yet to happen. For me, I would encourage you to consider keeping the core in a similar scope as it is now, while officially supporting and shipping some quality-of-life extensions by default. As some examples, I believe Relink, Favourites, Context Search (though it needs an update) and possibly Tiddler Commander would be good candidates for inclusion in a standard distribution of TW.
TWX interface & markup language in particular
Beyond what I suggested in the older topic:
If you are prepared to do breaking changes, you should probably move to a Markdown-like syntax. It is far my favourite LML (that is between Asciidoc 2.0+ and Textile), and TW’s Wikitext is a good markup language. But for whatever reason, it is a serious stopping point for many users. I switch between Markdown, TW Wikitext and Confluence/Jira markup every single day and don’t have a problem. Still, you have to go with what’s popular.
Base Markdown is not sufficient and needs extensions.
I also think it’s important to be close to HTML, and let us use raw HTML in tiddlers like we can now. This means you should probably be closer to the original implementation of Markdown in some ways, for example in having a single linebreak still be treated as part of the same <p>, without inserting a <br> like Discourse does.
On that note, Outline Wiki has finally managed to integrate Markdown and WYSIWYG in a compelling way, which should be considered as part of my suggestion in the older topic to have viewing and editing modes be closer to each other.
5 Likes
This post resonated a lot with me, and the fact that TWs versatility is both its biggest strength and its biggest weakness has come up before in several discussions.
Abandoning its very powerful but rather technical root would be a mistake, I think, we can’t really live and build all we have now without it; but without appealing to the masses who need a simple note taking or tasks tool, it is also hard to grow in popularity.
Jeremy is probably stretched thin, a single person can’t possibly attend alone to the core, desktop, mobile, MWS, end users, UI and still be able to significantly advance all simultaneously.
Maybe a potential solution is for Jeremy to focus solely on the core, a powerful unified, backwards-compatibility-breaking core, versatile enough for all the programmer, power users, and wonderful plugins we have amassed.
Then on top of that solid foundation, leverage the community, let all the contributors build the variety of plugins, flexible mobile UIs, WYSWYG, and all the end-user friendly ready-made solutions for the less technical masses. The larger community is also more likely or able to be able to cover and refine all the different variations and myriad of particular requirements the public will naturally have.
We’d “just” need a friendly way for the users to access the various “flavours”, which the current plugin library already does acceptably well.
2 Likes
In 11 years from now, I would like TW to be the no-brainer ecosystem to go to when designing data driven applications.
Not being a developer myself I looked at others with this “magical powers” and wished I had the tools and skills to materialize my ideas, TW in its current state allows me to create wikis and demos in an interface that does not require to have to write code (but does not limit you if you have the skills to create custom plugins) however, I wish for a deeper customization.
I would like to trespass the wiki realm, therefore I specially like the efforts of @poc2go with Tw5-node-red continued to lower the barriers to materialize projects for non-tech folks like me and opens the door to make our wikis to talk with IOT devices, Telegram bots, mail servers, and whatever you imagine by using Node-Red.
I guess In the coming years I want TW to be so standardized and interoperable that allows you to not just create wikis but whatever custom software solution you need.
1 Like
I’d love to see a list of what these TiddlyDesktop on macOS capabilities are.
[ext[the caption|the file path]] lets you do two things. If the path is a folder, it opens the Finder to that folder. If the path is a file, it opens the file in whatever app that you have set (with the Finder’s Info panel). As my work on a show progresses, I use one tiddler to take notes on a piece I’m composing that includes many different files, the scoring file, the original audio files from workshops which are the source material for the lyrics, the lyrics as they progress are written directly in the tiddler, the pdf files of the score that I send out to the performers with their input and transposition needs attached to each, the DAW files I record the different versions into, rehearsal recordings, and finally videos of performances. All these files are in different places. I used to make aliases and then put the aliases into folders along with text snippets, or a descriptive text file. TiddlyDesktop makes this so much easier and more flexible.
The other tool is the iframe: <iframe width="100%" height="600" src="/path-to-folder"></iframe> for example. I see the contents of a folder directly in the tiddler without having to switch to the Finder and then open the right folder to list the contents. As an example, a single tiddler can group any number of such “open folders” together to give a bird’s eye view of work that has been done with or for a given person. And because it’s TiddlyWiki, you can write explanatory notes, include links to other tiddlers, or use transclusion all in the same place where the open FInder windows are.
My main wiki runs under node.js on an old mac mini and broadcasts itself on a port I’ve opened in my internet box/router so that I can work with it from anywhere on any device. But the TiddlyDesktop wiki is all about keeping track of local files. Hope this helps.
1 Like
Thank you for this.
I am currently considering what my next main desktop working environment should be what with my seven year old Windows box going out of fashion and having acquired a Mac Mini slightly unintentionally. As such I am also interested in tiddlers containing
- message: URLs. I know Mail.app kind of does this right less so Thunderbird (cb_thunderlink and derivatives)
- Page references for PDFs which should be done by adding #page=n to the URL
- References to source files possibly handled by emacsclient in my case
Re: Thunderbird email links:
The cb_thunderlink plugin apparently only works with older versions of Thunderbird.
What works for me is saving the message you want to link to as an .eml file. For example, without the user defined caption for the sake of clarity, [ext[/Users/m/Desktop/email with TD/[Talk TW] Project 2036_ the future of TiddlyWiki - Jon Schneider via Talk TW <noreply@talk.tiddlywiki.org> - 2025-04-09 1125.eml]] opens the email in a fresh (undistracted) Thunderbird window. To do the save I used right click Save As… on the message; and then opened the “Format: All FIles” dropdown menu to get to choose “Mail Files”. Your message takes 10 KB. Once it’s path is referenced in TiddlyWiki, it will be so much easier to find (and to take notes on) than lost in the endless meanders of the mail app itself.
Re: Page refs for PDFs
“#page=n” works fine for me. Long pdfs where page references are useful don’t go into my local TiddlyDesktop wiki because I don’t write anything that long that needs to be shared as a pdf. I have them on my main node.js wiki. Since I want to access them from anywhere, I put them on a CDN server; but they could just as well be on the old mac mini which serves my wiki. The code which is of type “application/pdf” in a field called “_canonical_uri:” is like this (for example):
https://TWpull.b-cdn.net/101%20Montunos.pdf#page=41
Re: source files
If you set the finder’s info panel to open the file with emacs, and copy the path, the ext syntax as explained previously will open the file with emacs.
1 Like