Unfortunately TLS encryption is only from client to server.

Server to server encryption is optional. Thats where the issue lies.

Who the hell keeps buying nvidia? Stop it.

Check out SyncThing, which can sync a folder of your choice across all 3 devices

[edit] oops, just saw you don’t plan on using it

In that case, if you use KDE, you can use Dolphin to set up network drives to your local network machines through SSH

Wait until they sue Mississippi

You’re missing some security updates, it seems.

Release notes for your newer BIOS/UEFI updates:

4.80 -
Improve GPU compatibility for GeForce RTX 40 series.

4.90 -
Enhance S3/S4 mode.

8.01 -
Update AMD AM4 AGESA Combo V2 PI 1.2.0.8

10.01 -
Update AMD AM4 AGESA Combo V2 PI 1.2.0.A

10.08 -

1. Update AMD AM4 AGESA Combo V2 PI 1.2.0.B\
2. Patch UEFI LogoFail vulnerabilities.

10.11 -
Update AMD AM4 AGESA Combo V2 PI 1.2.0.C

10.31 -
Update AMD AM4 AGESA Combo V2 PI 1.2.0.Cc to patch SMM Lock Bypass security issue.

10.41 -
Update AMD AM4 AGESA Combo V2 PI 1.2.0.E

It honestly just depends on how many steps you want. You’re going to have to figure out the logistics of taking them, first of all. Do you want to take a premade set of steps or would you rather mold/cast them onsite?

Obviously concrete is heavy af, so if you are going to precast them, you might consider using less steps. The more steps you add, the heavier its going to be. Of course, this isn’t an issue if you have a heavy duty vehicle with a lift.

Also, do you want rails on them? That will take extra time to set them in place.

Some examples i would recommend would be something like these.

Or maybe this

Local, county, state government employee salaries are public, and they still seems to be running fine for hundreds of years.

I get you want to keep the data, but I dont. We’re at odds. Thats all. Simple. Agree to disagree.

We don’t have to align on this.

Exactly. Just do that then.

Meanwhile, let me manage data on my instance as I see fit. If i want to delete it from my instance, then thats up to me.

The unfortunate reality is obscuring the post by unlinking the account serves no purpose. There are ways to tie the posts to accounts even after they would have been unlinked. Post style, metadata, and residual data leftover by the instance is probably enough to recreate that link.

It sucks that the whole post disappears once someone deletes it, instead of just a single user’s part of it, but that’s preferable versus leaving data behind IMO.

Even so, I would rather have the option to eliminate data pollution at my convenience. If someone else wants to replicate my data, they have their window to do it. Once Ive deleted it, that window is closed. I want to be able to decide that window of time, not others decide it for me.

We should all be proactive on cleaning up our data footprint imo. This is more than social media posts. It should be images, documents, videos, and any other data that is sprawling out uncontrolled. Gotta clean things up occasionally.

I appreciate having control over my own data though. I would like to keep an option to delete all my posts/likes/dislikes/accounts as I desire. If someone wants to save a copy of my data, they have an option to do so before I delete my data, but not after.

I wish all the firmware for every motherboard was made public and open sourced. Even if a company has proprietary firmware/drivers, I would hope that once that product reaches end of life that they do in fact open source that code so that someone else can pick up where they left off.

I 100% agree that they should not brick their hardware once it reaches end of life. There might be someone out there who would take on the task of maintaining it, which is better than nobody maintaining it.

No.

You want it, build it yourself. Or pay devs to do it.

Some vendors still have a red flag on their support page discouraging uefi updates unless you’re actively experiencing problems.

I dont know which vendor you are referring to, but that is a horrible practice. There should be active support and release notes stating that “This release is a security fix” at a bare minimum. If your motherboard manufacturer does not offer that, then I could never recommend them to someone. They need to be held to a higher standard.

At least from my experience, ASUS, Dell, and Apple will publish that information.

Even if the code is there, you will need someone to maintain that code. Easier or not, even in a git repository, those individual components will eventually not have the support necessary to patch it.

If an eight year old usb controller has flaws, and the manufacturer is not maintaining that git repository anymore because they cannot possibly afford to hire someone to look at that code after so long, then it is going to keep those flaws. It wont matter if that code is proprietary or open source and included in coreboot. Its just simply not feasible to support hardware properly once most of the world has moved on to other products.

Generally, motherboard manufacturers source their components from other companies. They do not manufacture the entire board themselves. This includes CPUs, Wifi cards, USB controllers, bluetooth, audio, display controllers, etc. Each and every one of them create new products, maintain their own firmware for all those new products, and push updates to the motherboard manufacturers when there are updates.

Coreboot/libreboot do not update those components themselves. They also must be provided that source code.

Just for coreboot alone, the last release had more than 120 contributors push over 900 commits. One person is not able to maintain that piece of software, as it is an enormous task.

No idea. You can use something like jackett to generate an RSS feed for you if they dont have one.

Maybe they have a newsletter for updates, or a registration card, social media account, or maybe a security team that announces security updates.

All im suggesting is look into how your manufacturer announces these updates and actively listen to that communication.

IMO, keep an rss feed of your vendors firmware updates being released on their website or periodically check it yourself. As soon as its released, go ahead and install it. If you want to be cautious, maybe give it a week or two to make sure they dont pull the update due to issues with that particular release.

Even better, if the manufacturer offers a utility to keep updates installed, just run that periodically.

As much as I would like to agree with that, each piece of hardware is going to have its own niche set of problems that the coreboot/libreboot team is not going to research and maintain. It wont be because they dont want to. They just dont have the resources and source code from the vendors. You will get your standardized updates, but it will not cover a lot of the proprietary blobs necessary for the hardware to operate.

Once the vendor stops supporting it, thats it. Its a ticking time bomb. Its how we get articles like the one in the OP. The vendor and user are not going to put in work to keep this updated. Even if they had coreboot/libreboot, it wont get updated.

Its a shitty thing that isn’t easy to solve except by tying in hardware and software into single, unified products that are written in perfect code. Its not possible.