Widdler is a single binary that serves up TiddlyWikis
github.com
github.com
Anyway, I wouldn't count the kind of simple, focused libraries dependencies Widdler relies on as additional LOC.
As a rule of thumb, if it's something that wouldn't make me blink an eye if I found it was in the python stdlib, it gets a pass from me. Only the webdav library might not fit this.
This is subjective, of course. If anyone has a better heuristic for this, I'm all ears.
The only external dependency is OpenBSD specific and used on that operating system only.
It looks like the entire wiki implementation is copied to a new file when you create a new wiki page. It's a 2.3 MB file, which seems like a lot to download when you visit a new page.
It is, But I feel it's still better than what ever framework they're using nowadays to generate doc/wiki for APIs which hijacks Ctrl-F with a useless pop-up which rarely gets me what I need[1]. Please bring back plain HTML document pages.
Perhaps their time would be better spent thinking up some way to prevent a TiddlyWiki from becoming a wormable nightmare.
Thanks for your opinion on where my time is better spent though, I don’t know what I was thinking.. building a tool to solve a problem I had and releasing it completely free of charge! I’ll know better next time!
Editing can be done in Markdown, all version-controlled, there's user support built-in, the whole thing basically resides in a repository, which is a kind of a SQLite db. The wikis can be imported from text files too.
It may be not fancy-looking, but for "note-taking" can be good enough. I guess it may be made to run in Tmux or the likes to have a Wiki served locally to the smartphone.
Wish the Fossil was more templatable, also there's no proper wiki category tagging, but it does work for the purpose.
[1]: https://fossil-scm.org/home/doc/trunk/www/wikitheory.wiki
I've been using TiddlyDesktop, but that thing has some questionable privacy because it's based on Chromium. One time, I had it running in the background while working on something completely unrelated, and I got a Chrome-style popup/alert warning me about a network printer being disconnected. I didn't even have Chrome installed on my machine at the time and it took me a while to realize that it came from TiddlyDesktop.
But besides the privacy issues, TiddlyDesktop only serves local wikis. That's annoying when you have multiple devices.
Also, pro-tip if you're on Ubuntu: the latest golang version in the default repos isn't compatible with this. You'll need to use golang 1.16 or later, which can be installed manually from the website, or installed via apt with a custom PPA (https://github.com/golang/go/wiki/Ubuntu)
>>
Timimi is a web-extension accompanied by a native host that allows you to save and backup your standalone HTML tiddlywiki files anywhere in your hard-drive. Once installed, you can save the tiddlywiki files without any extra steps, like the original Tiddlyfox addon.
Timimi also provides users with 4 backup strategies, viz:
- Create a backup Every nth save
- Create a backup every nth minute
- Customised Tower of Hanoi
- First in First Out [3]
<<
[0] https://ibnishak.github.io/Timimi/
[1] Chrome/Edge/Brave: https://chrome.google.com/webstore/detail/timimi/mnggafnmmhd...
[2] Firefox: https://addons.mozilla.org/en-US/firefox/addon/timimi/
[3] https://tiddlywiki.com/static/Timimi%253A%2520WebExtension%2...
- https://github.com/fiatjaf/tiddlywiki-remotestorage-server
- https://github.com/fiatjaf/tiddlywiki-remotestorage
A TiddlyWiki plugin for saving tiddlers to https://remotestorage.io/ and also a server to fetch them from any public remoteStorage on demand and serve them as HTML to visitors (for sharing).
I think my server at https://tiddly.fiatjaf.com still works. You can just open it and start creating your tiddlywiki with auto-save (it will be saved on localStorage by default).
Thanks! I was about to give up
PD: Couldn't install it either with the new binaries: "package embed: unrecognized import path "embed" (import path does not begin with hostname)"
I think they should revisit this issues if really want widespread adoption.
If it's not correct, try `command -v go` to see which go binary your shell is using. If it's not "/usr/bin/go", then your PATH probably points to another one. In that case, try running `/usr/bin/go` directly instead of just `go` (assuming you installed the PPA linked above).
> I think they should revisit this issues if really want widespread adoption.
This isn't the project's fault. It requires a particular version of go, but you have the wrong version on your computer.
I wanted something that just let me open the wiki and save changes to it. Nothing else. No massive dependencies. This is what I wrote: https://github.com/bachmeil/tiddlyd You view you TW and you save changes to it, nothing else.
I've tried to address this with https://tiddlyhost.com/ (and in the past with http://tiddlyspot.com/ ).
node ..\tiddlywiki.js "my new wiki" --init server
cd "my new wiki"
node ..\..\tiddlywiki.js --listen
... is also not THAT difficult :-)
Or alternatively, an AutoHotkey shortcut, which fixes the anachronistic ctrl+s shortcut of the browser (anachronistic = doesn't remember save action for this url)
I use my TW every day like a madman (https://philosopher.life/#⧖). I'd like to submit https://github.com/OokTech/TW5-Bob as a powerful (though perhaps not as simple) alternative. That's what most of my household uses (one is aiming to switch over soon).
I am used to creating "web application" and running it on a web server of some sort: Apache / IIS /Lite.
In this perspective the web server or what not handles a lot of the complexity, thread pools, isolation, restarting, logging etc etc.
I frequently see applications like this that is "one binary" and you run it by starting it on the command line. That is easy , no worries.
But how to handle running it "in production", were I want to ensure that it is up and running all the time?
If I wanted to put this on my VPS and share it with the net, what steps do I need to take?
systemd? (k8s I really hope not)
My current use case is: running on a vps and exposing a password protected space for me to jot down various things.
At the very basic level you can SSH, and type in the command. Bobs your uncle. Then unless you something it shuts down when you end your session.
You can just set it to execute in the background with basic sh or something like tmux.
Or do you set it up in systemd to be watched and restarted if something goes wrong?
c.f. OpenBSD's unveil() https://lwn.net/Articles/767137/
> ...
> Optional TLS support.
I know it's supposed to be pretty minimal, but this is a bad combo. Great that TLS is offered but it should be mandatory if you're using the authentication.
There's two of the words you complain about in it: the name of the project itself, and TiddlyWiki - which is clear that it's a wiki, and naming it explicitly instead of just referencing a generic wiki is useful for everyone who is aware of it.