I agree that these should be blocked for privacy, but the amount of these requests is really completely meaningless. The reason there are so many is because they are blocked, not despite it. It will keep trying over and over on failure.
Whenever I break something and can't figure it out, I just make sure anything important is backed up and do a clean reinstall. Someone else might have a better answer though
For 3D printing to work, you basically just need some standard motors to move a thing that gets hot around. Yes it needs to be pretty precise, but it's only printing at a single point that moves. Classic 2D printing not only prints across the whole sheet at once, it is also sometimes expected to do it in color (which does take multiple passes usually). As for the technological aspects of conventional printers, I really don't consider myself an expert, there are great videos online. However by my understanding, a laser is often used to trace the exact contents of the page so that the depositing material is picked up and placed. That sort of light manipulation is already more complicated than everything most 3D printers do.
Basically, you could build a new 3D printer in your garage using off the shelf parts and some knowhow, but good luck even repairing a 2D printer with a serious problem in its printing mechanism, though this difficulty is certainly not made better by companies such as HP
USB C is just a connector, you might be referring to Displayport over USB C which is basically just the same standard with a different connector at the end. That or Thunderbolt I guess
Update in case anyone is interested: I figured out what caused the problem. When I mounted the new drive I used to store my configurations onto Proxmox, I completely forgot to make the relevant /etc/fstab entry. The drive mounted successfully so I didn't realize at the time that I had forgotten to do that step. The update I ran from apt-get included a kernel update, so I restarted the machine to complete it. Since I hadn't modified fstab, my new drive was not mounted when the system started up again. Even though the drive wasn't mounted correctly, I still somehow had access to some incomplete version of the files in its directory (no idea how that works). So no fault of Docker, LXCs or Proxmox, purely PEBKAC.
Despite getting the files back I will still work towards a more resilient system and more regular backups.
The files were on a mountpoint, completely separate drive. This has also been the case for all the previous times I ran an update, though I did recently move these files to a different drive mounted the same way. I got some sort of permission wrong maybe?
Will definitely set up a better backup system as soon as I can
The question was "why," you may as well be protesting the addition of a new codec