Tags: GoBlog

Today’s Homebrew Website Club inspired me to implement two new GoBlog features:

1. Support for OpenSearch: I can now use my blogs and diary as a search engine in Firefox.
2. An easter egg. Do you remember Konami Code? 😉

I refactored GoBlog to avoid global variables wherever possible (with the goal to make it easier to create unit tests) and I hope I didn’t introduce any new bugs. 🤞

My evening project today was to develop a feature to display post locations in GoBlog, for which I created a custom Go module (100% test coverage!) that roughly parses geo-URIs according to RFC 5870. Nice feature for when the location should be relevant for the post context or I want to save where I shared a photo. An example in this post. 😉

I have already written about my blogroll several times. After I automated it with Hugo and was also able to implement the automatic creation with GoBlog, I have now significantly improved the integration in GoBlog. Blogroll support is now directly in the application, hopefully supports other services besides Miniflux and there is an OPML download now. Blogrolls rock!

Something stupid happened to me yesterday. On my post with the cake photo I got a few responses and comments that I wanted to look at. But on the smartphone display, I seem to have slightly mis-clicked and accidentally pressed “Delete”. That’s a button that only shows up when I’m logged in.

The post was then deleted and I had to use the hourly database dump to find the entry again and add it back into the database by hand.

To counteract this in the future, I have now created a second deletion step. Now the deletion must be confirmed a second time.

I also now use the European cloud provider Scaleway to store the Docker image (instead of Quay.io). I already use Scaleway for object storage for my backups, unfortunately Hetzner does not offer such features yet.

This evening I had a little fun with SQL and JavaScript. Now it is possible to see the number of posts without date in my blog statistics (en/de), but also the number of posts in each month of each year. By clicking on the year, the months are displayed.

It would not have needed JavaScript in the frontend, would there be something like summary/details for tables. But at least it’s less than 1 KB of JavaScript.