CI/CD just became a lot harder when every container needs the users age verified. Not just configured, verified.

Windows media center was really really good for live TV.

Eventually, yes

What's not funny is how old I feel now

I want to say... Some sort of self hoster with a cheap domain going for the "security through obscurity" approach...

https://crt.sh/?q=91268476.xyz

I'll let you explore, but definitely a self hoster!

At the homelab scale, proxmox is great.
Create a VM, install docker and use docker compose for various services.
Create additional VMs when you feel the need. You might never feel the need, and that's fine. Or you might want a VM per service for isolation purposes.
Have proxmox take regular snapshots of the VMs.
Every now and then, copy those backups onto an external USB harddrive.
Take snapshots before, during and after tinkering so you have checkpoints to restore to. Copy the latest snapshot onto an external USB drive once you are happy with the tinkering.

Create a private git repository (on GitHub or whatever), and use it to store your docker-compose files, related config files, and little readmes describing how to get that compose file to work.

Proxmox solves a lot of headaches. Docker solves a lot of headaches. Both are widely used, so plenty of examples and documentation about them.

That's all you really need to do.
At some point, you will run into an issue or limitation. Then you have to solve for that problem, update your VMs, compose files, config files, readmes and git repo.
Until you hit those limitations, what's the point in over engineering it? It's just going to over complicate things. I'm guilty of this.

Automating any of the above will become apparent when tinkering stops being fun.

The best thing to do to learn all these services is to comb the documentation, read GitHub issues, browse the source a bit.

I guess there is a difference between "it's known to happen" and "a nation state accuses another nation state"

It's a funny read.

IMO, the bridge example is more like joining a maintenance team looking after an old bridge. I'm sure there could be good metaphors of the old guy that hammered 300 of the original rivets, and can tell an interesting story about toilet breaks 250ft in the air. And new government regulations both about bridges and conservation of protected buildings/structures that somehow clash or whatever.
Building a bridge would be more of a startup/new project.

It does feel like it takes the most esoteric circumstances, as well.
Same could be said for "Steve that has to dig a ditch" seeing competitions of plant operators doing back flips in forestry machines meant to scale mountains.

It's just that programming is a very accessible hobby that can transition into a career (how most programmers got a career, tbh), but is also the thing that modern business/industry/entertainment all depends on.

Well, it wasn't caused by pronouns. That's for sure

Oh, I love these deep dives, identifying tech debt, then how they refactor them!
And the new way of managing wires makes a huge amount of sense.

There are 3 reasons I can see.

1:
It's a huge change, and they did a dual-implementation however long ago - where they store it in the active legacy system, and also store it in the new inactive system ready for when the switch is flipped.
Do a year of this, changeover flawlessly, and suck up the outrage over lost data.

2:
It's a maybe not such a large change, but the data processing for it is expensive. So, however long is an acceptable cost, and its balanced against user outrage

3:
There was a TOS change. So data before that date can't be sold/monetised, whereas after that date has value.
So, drop the data that costs money, keep the data that can be monetised.

Whatever, it's bullshit.
Glad I left. And glad Lemmy is cool

Yeh, but you KNOW that's next on the chopping block.
Not sure if I'd support old.reddit for premium only users. I'm really enjoying Lemmy, and the genuine conversations that are happening