The toilet then sends the data it collects to a cloud server.

What could go wrong.

Just one more line bro. One more line will fix it.

I just think they don’t understand how copyright and licenses work. If you create a work, you own the copyright. If you license it to someone (even when using a restrictive CC license) you are granting them rights that they hadn’t before. It doesn’t get more restrictive than just not licensing your comment.

There are some local differences in math notation, e.g. . vs. , as a decimal separator, • vs. × for multiplication, : vs ÷ for division et cetera.

https://github.com/michidk/rost

Aren’t you müde from writing Rust programs in English? Do you like saying “scheiße” a lot? Would you like to try something different, in an exotic and funny-sounding language? Would you want to bring some German touch to your programs?

rost (German for Rust) is here to save your day, as it allows you to write Rust programs in German, using German keywords, German function names, German idioms.

This, but Forgejo instead of Gitea.

deleted by creator

FIY, this appeared as a post on !linuxmemes@lemmy.world. I assume that this wasn’t your intention. Maybe this happened because you mentionend lemmy.world/c/linuxmemes?

See https://lemmy.world/post/24972437

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

https://nostalebots.xyz/

There is not much of a difference

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.

# apt apt install
E: Invalid operation apt

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 would prefer manually writing each software using butterflies over having snapd installed on my system.

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.