the door and doorframe swelling from humidity is literally like certain body parts swelling from additional liquids

doorframe edema

Many e-mail providers such as mailbox also provide calendar synchronization via CalDAV.

AntennaPod supports Android Auto: https://antennapod.org/documentation/playback/android-auto

Honestly, it felt more like https://xkcd.com/386/.

Scheintore klingt gut.

Use [text](url) instead of (text)[url] to create a link:

Pedalos

As others mentioned, running a minecraft server by itself is pretty easy. If you want additional features like a Web UI, multiple servers at the same time etc. you might take a look at Crafty Controller.

This, but Forgejo instead of Gitea.

https://github.com/andyholmes/valent/

It’s the other way around. 0.1 kWh means 0.1 kW times 1 h. So if your device draws 0.1 kW (100 W) of power for an hour, it consumes 0.1 kWh of energy. If your device factory draws 360 000 W for a second, it consumes the same amount of 0.1 kWh of energy.

I’m likely to rebuild the backend in Go

Why bother with another language? Rust offers multiple great backend options. Using the same language for both ends might allow reusing some parts.

I’ll look into it if I find the time.

It uses the browser preference for light/dark theme by default

This doesn’t work for me. It seems like you are using leptos_use::use_preferred_dark with server-side rendering which unfortunately uses the experimental Sec-CH-Prefers-Color-Scheme header which isn’t supported by all browsers, e.g. Firefox.

In my opinion, it is way better to implement theme switching on the client side. The prefers-color-scheme media query is better supported across browsers and allows reacting to a change of the user’s system preferences.

This project sounds like a great idea!

Dark mode, so that you can write articles from the beach or from your basement

It would be great if it respected my browser’s prefers-color-scheme setting.

Pistachios aren’t actually nuts. They’re drupes

To get a TLS certificate from Let’s Encrypt, they need to verify that you are in control of your domain. For regular domains, this can be done via HTTP, for wildcard certificates they require you to create a DNS record with a special token to verify ownership of the domain.

This means that in order to automatically obtain a TLS certificate, caddy needs to interact with the API of your domain registrar to set up this record. Since there are many different providers, this isn’t built into caddy itself and you require a version that includes the corresponding caddy-dns module. Caddy modules need to compiled into the binary, so it’s not always trivial to set up (in my case I have a systemd timer that rebuilds a local container image whenever a new version of the docker.io/caddy:builder image is available).

Caddy automatically sets up certificates for you. Since I don’t want my subdomain to appear in certificate transparency logs, I use a wildcard certificate which requires using a plugin for my DNS provider.

A reverse proxy, in my case Caddy.

I never heard of Cozy, but it looks quite nice. The Self-Hosting Documentation ist a bit lacking, but https://github.com/cozy/cozy-stack-compose contains all required information to set it it up yourself.

I originally used Nextcloud, but it has a lot of features not related to file hosting

Cozy seems to be in a similar situation, where file storage is just one of many features that it provides. If you want just files, it might be the best idea to just use any WebDAV Server or something like File Browser.

phyphox has an Audio Amplitude feature.