Sounds like a long-awaited race condition finally coalescing.
The boot splash screen would expect the drivers to be ready, and will hang/timeout if it isn't ready when it tries to render the splash screen

I can say I've never glorified suicide. When I've been suicidal, suicide is literally the only logical solution my brain can arrive at. It's completely irrational in hindsight, but it makes so much sense at the time.

I don't think I have ever not-watched something due to content warnings alone. But it has alerted me that there may be issues, so it doesn't surprise me when it comes up.

It's from 2015, so its probably what you are doing anyway

Thankfully containers are open source.
Everything is "docker this" and "docker that". But podman is viable, and there are other container systems.
The container format is so ubiquitous it's FOSS. I mean, it's kubernetes.

Oh, this is on android yt app.
Pixel 8pro, so Google & Google.
There isn't any variable that they don't have control of.
Video playback after ads skips 500ms, plays 500ms, skips 500ms etc. Changing quality doesn't fixing it. Play/pause doesn't fix it, skipping doesn't fix it. I have to fully quit YT app and restart it to get playback again, and chances are it starts the ads again.
Never had an issue on FF, w10 or Linux.

I get that streaming video is expensive for bandwidth. And creators need an incentive to create.
I don't expect it for free. I don't YT enough to warrant a premium subscription.
The ads literally break the platform for me.
Makes sense to me to get into one of the alternative clients... But I don't want to not pay my dues... It's just not worth the £13 a month: there is no way I'm consuming that much content.

I've had it return from ads, make the video playback stutter. I refresh/reload or whatever, jump back in, get more ads, video playback stutter. It's annoying as fuck

Pretty sure votes are public. It's just that most (all?) the front ends only show the number.
It's kinda how the fedi spec works. Nothing is private.
I know kbin/mbin showed who voted.

A technical reason is because he has been a president before

I have 3nm ~in my pants~

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.

Bitwarden is cheap enough, and I trust them as a company enough that I have no interest in self hosting vaultwarden.

However, all these hoops you have had to jump through are excellent learning experiences that are a benefit to apply to more of your self hosted setup.

Reverse proxies are the backbone of hosting and services these days.
Learning how to inspect docker containers, source code, config files and documentation to find where critical files are stored is extremely useful.
Learning how to set up more useful/granular backups beyond a basic VM snapshot in proxmox can be applied to any install anywhere.

The most annoying thing about a lot of these is that tutorials are "minimal viable setup" sorta things.
Like "now you have it setup, make sure you tune it for production" and it just ends.
And finding other tutorials that talk about the next step, to get things production ready, often reference out dated versions, or have different core setups so doesn't quite apply.

I understand your frustrations.

It's good to document weird and creepy behaviour.
If things like this don't make the news cycle, they essentially go un-called-out. Which might make it seem like normal or acceptable behaviour.

Weird behaviour doesn't live up to scrutiny