As far as I can tell, TiddlyWiki 5 has no feature or plugin to have revision history integrated into the UI, although one might come in the future [1]. According to [1], there used to be "TiddlyWeb/TiddlySpace, a robust serverside that supports revision history", but TiddlySpace (a hosted service) is dead, and TiddlyWeb (an open source codebase that I guess was the backend for TiddlySpace?) seems to be no longer maintained and mainly targeted the 'old' (pre-5.x) TiddlyWiki.
That's too bad for me, because I have a use case where I'd otherwise be very interested in using TiddlyWiki. I love that links load instantly, I love that forking a TiddlyWiki is trivial, I'm interested in the idea of dividing information into smaller-than-a-normal-wiki-page 'tiddlers', and I like the UI design. Overall, I can't find any other software that quite matches TiddlyWiki's capabilities.
But my use case is for a publicly editable wiki, so it's critical that revision history not only exist but be integrated into the UI. Right now, as far as I can tell, the closest approximation would be to use TiddlyWiki's feature of auto-saving to a Git hosting service (which for some reason supports only specific hosting services, not arbitrary remotes?). Then you could browse the history on that service. But that would be a totally separate site from the wiki itself, which would create an awkward user experience.
It's hard to find a good solution since the main Tiddlywiki is built as a single-user rather than multi-user solution. But these two tools may help now or in the future since they are being developed. (I can't definitively answer since I'm not super familiar with either).
There's a Noteself setup of Tiddlywiki (https://noteself.org/) that syncs with a database and has revision history. You click on the upper right corner of a tiddler to access revision history. The revision UI's not very intuitive to start and I'm not sure how making a public site with revision history available would work though. It also is on version 5.1.21 rather than 5.1.23 of Tiddlywiki, though maybe the maker plans to upgrade in the future. You could ask here https://forum.noteself.org. I just started using it so I'm not super familiar with it.
TW5 Bob https://github.com/OokTech/TW5-Bob is being built to serve one or more Wikis for multiple people, but I don't know that they have revision history (I could be mistaken).
You could use the node tiddlywiki which saves the tiddlers in separate files, you could also use the markdown plugin and the tiddlers are saved in seperate markdown files. Perhaps as service could do a git commit with each file change in the background, perhaps saving the browserstring and ip address with it. You could make a seperate page - for example Gitlab with the commit history.
Try checking the file into GitLab (or GitHub) pages. It’s just an HTML5 file. Use pull requests to manage changes. Use the git repo as your history.
In the 2005-2009 timeframe I served a TiddlyWiki from PTC Windchill as a project website for my team. Windchill provided the access, change history & configuration management layer.
That's too bad for me, because I have a use case where I'd otherwise be very interested in using TiddlyWiki. I love that links load instantly, I love that forking a TiddlyWiki is trivial, I'm interested in the idea of dividing information into smaller-than-a-normal-wiki-page 'tiddlers', and I like the UI design. Overall, I can't find any other software that quite matches TiddlyWiki's capabilities.
But my use case is for a publicly editable wiki, so it's critical that revision history not only exist but be integrated into the UI. Right now, as far as I can tell, the closest approximation would be to use TiddlyWiki's feature of auto-saving to a Git hosting service (which for some reason supports only specific hosting services, not arbitrary remotes?). Then you could browse the history on that service. But that would be a totally separate site from the wiki itself, which would create an awkward user experience.
[1] https://github.com/Jermolene/TiddlyWiki5/issues/436#issuecom...