The autotldr-bot only summarized the first page, so here are some more quotes. Basically, the performance was almost identical, with two notable exceptions.
Across a variety of demanding GPU benchmarks the NVIDIA R550 open kernel driver continued to perform on-par with the proprietary driver for these GeForce RTX 40 graphics cards.
While running Blender 4.0 the proprietary kernel driver seemed to yield slightly better performance. It was just fractions of a second but was rather consistently showing the proprietary driver having that slight advantage here, unlike in other workloads.
There was the small advantage too that during periods of brief downtime using the open kernel driver appeared to deliver slightly lower GPU power consumption than the proprietary driver.
Does anyone have an idea what's the point with the proprietary driver now? Does it have any features missing in the open driver?
I'm not convinced that a pile of old HDDs is a good fit for your homeserver.
Many small disks will consume more energy than fewer large disks. Currently, the best capacity per price seems to be in the 20TB segment. A similar argument can be made for noise.
The HDDs you have might not be perfect for 20/7 usage. I personally would recommend using disks that are made for continuous usage.
Start with what you have, but if you outgrow your setup, buy proper hardware. And make backups.
I'm unsure about the end-to-end encryption aspect. While this feature is great for a cloud service like ente.io, it doesn't really help much in a selfhosted scenario - and might make backups more complicated. Any other opinions on this?
Looks like NACS will be the new standard for north america:
It has been used on all North American market Tesla vehicles since 2021 and was opened for use to other manufacturers in November 2022. Between May and December 2023, many other vehicle manufacturers have announced that starting from 2025, their electric vehicles in North America will be equipped with the NACS charge port.
Setting up a reverse proxy with nginx proxy manager is pretty simple and comes with letsencrypt support.
For letsencrypt to work, a software needs to write a confirmation code to a special path in your domain. When letsencrypt verifies that you can write to this path (and therefore control the domain), you get the certificate.
The autotldr-bot only summarized the first page, so here are some more quotes. Basically, the performance was almost identical, with two notable exceptions.
Does anyone have an idea what's the point with the proprietary driver now? Does it have any features missing in the open driver?