Dear Jeremy,
Well, that's a bit of good news!
Apropos of a minor and and a major couple of other things that you might consider, if they aren't already in the pipeline.
The minor thing is: To the right of the "river" (i.e. on the right side), it would be nice to have the tools not scroll, along with the headers at the top and left of the scrolling list of tiddlers. I find that I have to do a lot more scrolling to get to the tools on the right (whatever their proper name) than I would like.
The major thing is to consider making a version of TiddlyWiki that would act as an email client. I have, by hand, put a considerable number of emails of a long correspondence into TW and find that it is possible to do all sorts of things with it that you simply cannot do with any usual email program.
Even though I use gmail, which has a pretty good UI, at least for filing emails, it pales by comparison with TW. In fact, Goggle would be doing all Firefox users a giant favor to integrate gmail with TW, which I should think would not be an insuperable task (and they would certainly have the resources to do so).
On the other hand, it may well be impossible to have the open source TW mixed up with the Google empire at all, and the modifications to make this sort of magic happen may have to be in the plugin or add-on or whatever it is that enables TW to run within Firefox, which would talk to the gmail (or Verizon's or Juno's or whoever's on-line email) API and get a similar result on different email systems in TW.
My approach, really a first stab, is to simply to label the tiddlies that are each discrete email message with the Subject of the email. Duplicates are numbered in date/time order, the Then From: and To and Date (I have neglected Time) are realized as tags, and each tag (e.g. From= name> To= >name, (although, at least on a Mac, «name and »name for From and To might be better so as to have them grouped together in a list of tags, and always have them together in the message tiddly, rather than being on either side of the date) and then the Date, in ISO YYYY.MM.DD numeric format (and Time, if realized as tags and there is no reason not to). It may make more sense to just store the entire email header and display its contents by parsing according to the user's desires, and also be able to look at the original. The body of the message of course is in the contents field.
I have run into my own ignorance (as often happens) in that in-line pictures and, even worse, attached web pages, which TW is capable of displaying, I have had to be handled manually, and as links to separate tiddlies. Then there is the question of how to display "conversations" in a meaningful stream, ideally exportable at least into fold-able HTML or even as LaTex files with which to make PDF records of correspondences. (It should be noted that gmail handles in-line dragged/dropped pictures fairly gracefully).