In mastodon technology Shutdown, Ash Furrow writes:

I have sad news that I have decided to shut down the mastodon.technology instance. In accordance with the Mastodon Server Covenant, the server will be shut down no earlier than December 1, 2022.

Ash Furrow

I’ve been on the Mastodon.technology instance for nearly 5 years. It’s been great, but given the coming shutdown I needed to find a new instance.

I almost gave up on the whole Fediverse. After all, I’ve been on Twitter for nearly 20 years already. Never had to move or change anything. That’s of course no guarantee, but you know. Plus, it’s Twitter.

Last week I decided that I’d like to write with a bit more discipline than what I’d been doing in the journal entries, so I fired up a new Ghost instance at RudimentaryLathe.org.

As much as I, ehem, LoveIt, the theme’s very theme-specific magic felt like trouble waiting to happen. And honestly, I was bored with it, so I went looking for something new.

I was struggling with some recent tweaks to this blog’s theme, and while poking around I discovered that the LoveIt theme was once again being developed. I had moved to the CodeIt theme after LoveIt looked to be abandoned back in 2020. The author had simply seemed to disappear. And then, a month ago, there was this post.

Since CodeIt was archived recently and development stopped, I took the opportunity to kill my fork and switch back to LoveIt. I cleaned up a bunch of unnecessary CSS while I was in there. I’m trying to stick as close as I can to the defaults for now.

UPDATE June 09, 2022: This post was copied and pasted from the original WordPress post. Meta! :)

I’m typing this post in the WordPress editor. I don’t enjoy writing here unless I’m adding an image gallery or some other fancy embedded content. It just feels off. “So write in MarsEdit or Ulysses or something instead,” you implore.

Now that I’ve moved my blog back to a static site generated with Hugo, I noticed that I was writing both my Daily notes and my blog posts in side-by-side Emacs buffers. It got me thinking about consolidating my sites even further.

TiddlyWiki is a single static HTML file. It does not generate an RSS feed of new entries. It doesn’t generate anything.

I treat my wiki at wiki.baty.net more like a blog than a wiki, so not having an RSS feed feels like an omission. Most of the time I consider this to be a feature. I like that I can write any old nonsense and it doesn’t actively go out and bother anyone. It’s my little secret, that you can read if you want.

TL;DR: daily.baty.net.

You see, I have a nice wiki, and for a couple of years, I have written a new entry in it (nearly) every day. These “daily notes” have been interspersed and interlinked with the rest of the wiki’s content. It works, but I don’t love it.

Writing in TiddlyWiki is fine. It’s super easy, but it’s also a little clunky, which quickly becomes friction. And the experience for visitors is weird if you’re not familiar with TiddlyWiki. Also, there’s no RSS feed. I sometimes consider this a feature, because it’s nice writing freely and knowing it’s not “going anywhere”. On the other hand, if I were someone wanting to follow along with me, I’d want a damn RSS feed.