My Komoot export script has become quite popular. It was shared on a subreddit a few months ago, and I received many requests and comments about it. This morning, I decided to do some “guided vibe-coding” (I told Copilot what to implement, then checked and modified the result) and extend the export script. I replaced the static variables with CLI options for the credential file and download directory, added new flags to add the title to the file name and download planned tours. I also improved the readme to better explain how to acquire the necessary credentials and run the code.

See my original post about the script, the last update, and the source code.

My email server works perfectly for almost everyone. I’ve got all the security measures: SPF, DKIM, DMARC, MTA-STS, DNSSEC etc. My IP isn’t on any blocklist. Yet, with giants like Outlook and iCloud.com, my emails consistently hit spam or get outright rejected. The fix? An AWS SES relay, just for them. Suddenly, mail from Amazon gets through. This is pure tech oligopoly garbage, forcing us through their gatekeepers! /rant

A small update to my post from yesterday:

I did one final (really, the last one!) optimization to my network (luckily without new hardware). Instead of letting the new ASUS router do all the networking and QoS, I repurposed one of my GL.iNet Beryl AX routers with vanilla OpenWRT as the main router, doing SQM, DHCP, DNS proxying, and all the other stuff. Now the ASUS is running in Access Point Mode, handling just the mesh WiFi and partly acting as a LAN switch (because the Beryl AX has just one WAN and one LAN port). My bufferbloat is much better (or non-existent), and the Cloudflare Speedtest is showing me “Great” in all categories, even when connected with WiFi to the repeater.

I think I will stay without cake-autorate, but try to tweak the optimal SQM bandwidth limits a bit over the following days.

My laptop was always becoming hot when charging, and the fan speed increased to 100%. After applying new thermal paste, that problem is gone. The fan is still running, but at a much lower level. And the temperature of the CPU is also a bit lower. Fun fact on the side: I figured out that the ARCTIC headquarters are just about 2 km away from me.

Walking in the sunny park is like balm for the soul. 😌

Same spot as always. 📸

Hello, little deer! 👋

Before going to sleep, a quick walk around the block. 🌔

It took me so long to find the cause of a memory leak in GoBlog. I thought it was smart to use a cache for prepared database statements. But I didn’t read the documentation and didn’t know that prepared statements need to be closed when they are no longer needed to free up the allocated resources. 🤦‍♂️ I finally fixed it by removing the prepared statement cache altogether. Less code, fewer problems in the future, and the cache wasn’t much of an improvement anyway. I also learned about the usefulness of memory profiling.

I have a question for the IndieWeb community: What can we do against Webmention spam, except filter it out, when it fails validation? I receive hundreds of invalid Webmentions a day, and even using a filtering DNS server doesn’t seem to help much. But I also don’t want to waste network traffic to access all those spam sites. Is there any good block list I can check first before doing the request for validation? I thought about Akismet, but the API has no such option to only check the submitted URL.