It’s a VGA connection and, yes, my primary concern is resource usage. I’m running 2-3 VMs on it so that I can easily migrate the VM around.

I had plain old top and it was boring. I did not know how many alternatives there were.

I’ll also have to check out cmatrix.

This is an excellent idea!

Generally, no. On some cases where I’m extending the code or compiling it for some special case that I have, I will read the code. For example, I modified a web project to use LDAP instead of a local user file. In that case, I had to read the code to understand it. In cases where I’m recompiling the code, my pipeline will run some basic vulnerability scans automatically.

I would not consider either of these a comprehensive audit, but it’s something.

Additionally, on any of my server deployments, I have firewall rules which would catch “calls to home”. I’ve seen a few apps calling home, getting blocked but no adverse effects. The only one I can remember is Traefik, which I flipped a config value to not do that.

This smells a little funny, as others have suggested. I read an article a while ago that suggested that we’re not running out of raw materials; we’re thinking about the problem wrong:

Chachra proposes that we could – we must – treat material as scarce, and that one way to do this is to recognize that energy is not. We can trade energy for material, opting for more energy intensive manufacturing processes that make materials easier to recover when the good reaches its end of life. We can also opt for energy intensive material recovery processes. If we put our focus on designing objects that decompose gracefully back into the material stream, we can build the energy infrastructure to make energy truly abundant and truly clean.

This is all outlined in the book How Infrastructure Works from Deb Chachra.

I read recently that the lidar on many self driving cars can wreck the CCD on most phones. I don’t know how it works, but maybe parking one of the cars by your front door will solve your problem.

The issue does not exist with the version installed from F-Droid. I think the Play Store version is a different build with the feature disabled as a condition of hosting it on the Play Sore.

The Android app itself still works with the permission, and we released new versions on the external F-Droid store. So the limit is a “purely” Google Play Store-related problem.