Over the holidays I finally took my time to dig into Masodon. It has been a bit of a journey, both to understand how it works, and how to use it. From the start it feels like twitter, but as you use it you see the differences and realise how different they are. Regardless I do now feel at home on Mastodon, and the lack of an algorithm feeding posts it thinks I will like is most refreshing. ...
After getting tiered of the shortcomings of commercial network equipment I decided to invest in some professional devices. However, investigating the different brands are even more difficult than for commercial products. In the end I decided to go for MikroTik, due to their small office offerings. The devices are great and when first connecting to them you realise their potential through the sheer volume of configuration. As expected you need to design and configure you network to get it to work at all. This made me realise that I have not touched professional network equipment since university, and that was Cisco equipment. To my dread I could not find a good guide on how to configure a simple network with my equipment, so after finishing this is my guide. ...
It has now come to an end of an era. The time has come to move on from from my previous way of building this blog (with Jekyll) to something new. For a while now I’ve been looking for a reason to dig some more into golang, so when i began looking for a new theme for my blog the choice to migrate to Hugo came quite easy. At first glance it does exactly the same thing as Jekyll, but for someone who from time to time make changes to the theme it makes more sense (my personal opinion). ...
In a previous post I shared my experience with moving my page from Github pages to Cloudflare. It is now time to follow up that post and comment on my experiences after approximately a quarter. The experience of publishing new posts is about the same as when hosting on Github, you just push an update to the specified branch and then a build is triggered that will be published upon completion. The main difference is that the build process is somewhat slower in Cloudflare than on Github. This means that a build can take about 5 minutes, instead of the previous 1. This is most likely due to the fact that Cloudflare pulls everything and builds locally, instead of using Jekyll remote themes. ...
I’ve been looking around on how to get some statistics from my blog, especially regarding the number of visitors. Sadly the current solution (GitHub pages) does not seem to natively support this kind of statistics without adding third party tracking. After looking around for different solutions Cloudflare caught my attention. I know that among others, Troy Hunt writes about and uses Cloudflare, so I decided to give it a try. Migrating from GitHub pages to Cloudflare pages was as easy as configuring what GitHub repo to use in Cloudflare, picking Jekyll and then it just worked. Right after the page was built you see some basic statistics, such as the amount of request grouped by country. Below the first hours of traffic is shown in a map, as presented by Cloudflare. ...