archive.org link

Note: archive.today kinda sucks.

I think it’s kinda better using quadlets, because I wrote some custom scripts, and quadlets made the process better. But podman compose is probably file too.

Rootless. The docker containers were rootful, hence the permission struggles.

Yes of course. Had to spend a couple of hours fixing permission related issues.

Just did that last weekend. Nothing to do anymore. 😢

Damn, I guess I’ll stick to the older release for now. Hopefully a viable alternative/fork comes around.

The error is ~1/log(x), for anyone interested.

Paradox of tolerance type shi

It’s DoW now, baby. And apparently, it’s over 50,000!

Username checks out.

I just did uv tool install yt-dlp[default] --with mutagen. Updates are handled automatically.

I’ve always been kinda technically motivated. The only reason I didn’t actually study computer science is that I had a great math teacher who made me fall in love with math. But I had it for a minor, and like to read stuff up from time to time. So, I guess I’m kinda in the grey area in regards to being a person in tech.

Anyway, I love tinkering with stuff, so I inevitably got into self hosting. Nowadays, I’ve even started maintaining some self hosted software.

Things break. More than upgrades, Framework laptops are great for repairability.

Not surprised. From what I’ve heard from pretty much every German person I’ve talked to, Bavaria is basically their Texas (read UP if you’re Indian, not sure about analogies for other countries).

touch: cannot touch 'your': Permission denied
touch: cannot touch 'mother': Permission denied

Exactly. I never see people actually liking Cinnamon as a DE, but everyone keeps recommending Mint. It’s so frustrating, and perplexing.

The idea is that someone is checking the code. And by building it yourself, you can at least ensure that you’re getting what’s built from the code. It is possible that some malicious stuff was inserted while building the binary that doesn’t show up in the source code. Building from source solves that problem.

Reproducible builds try to solve that problem by generating some provenance from a third party. A middle ground can be building the binary using something like GitHub Actions, since that can be audited by others. That comes with its own can of worms since GH is owned by M$, but I digress.

So it is technically sane to do it, just not very practical in my view. But for lesser known apps, I do sometimes build from source.

I mean, that’s not a Rust issue per se. It’s only noticeable because cargo is much better than most build systems, and hence is an actual option for distribution of software. But there should ideally always be a binary distribution. I know some people like to build everything by themselves, but I get it, it’s annoying.

Tempus: An open source and lightweight subsonic client.

It’s a fork of Tempo.