Invidious. It got so bad that I just gave up and switched to piped which has been... well, not perfect, but definitely far more consistent.

I don't, because I switch it with something better if something like that happens.

It is fine, but then again I update it often too late which is actually pretty bad. The problem is Nextcloud pushes new features and a high frequency schedule of releases with those at an alarming rate of speed. Perhaps for corporate environments it is not as big of a deal as a professional team can fix obscure bugs with their knowledge and experience on their mirrored test servers, but home users don't have these resources available and public community knowledge and bug fixes need time which that release schedule hinders.

I still wouldn't say it is bad by default, simply because somehow it runs pretty stable for me since a decade. Updates are a pain though with many breaking changes and little bugs.

My wonderful MongoDB powered, old as fuck mFi vm. It's running on Ubuntu 14 because that's the last supported version and Ubiquiti abandoned this shit decades ago. It's set to restore and reboot once a month. That usually keeps shit working lol

The simple fix is to not use nextcloud

Bad stories about nextcloud scare me 😂 I hope Im not gonna jinx myself, but my nextcloud runs super stable for almost a year. I get some errors while updating, but service doesnt stop working and its usually simple fix by following the message it shows.

I removed apps that I dont use (most of them) and web ui became super fast on my budget server

Actually all services are so smooth and almost no issues, maybe beginner luck 😉

What we need is something that is a) Private (not saying nc isn't) b) Independent of any judicial government c) P2P and ultra redundant d) Run by a true non-profit (not like openAI) e) Massively distributed, process wise and storage wise f) OS independent, written in pure C or Rust.

Open media vault on pi4 is shitting the bed constantly

Yep. Got such a service as well. I've got this one docker container that's supposed to connect to a VPN and provide access from the outside to another one. The bitch keeps just crashing to a point where even "restart policy: always" will give up on it. Doesn't matter too much usually, since I can start the container before I need it, and it will usually run for half a day or so, yet still

I run a k3s Kubernetes cluster on a single KVM host(multiple VMs). Honestly I do not care a single f*ck about that machine nor k3s itself. I update once a year, do not have any documentation written nor IaC somewhere. I always forget how I configured the networking stuff for example. But that machine runs my critical services flawlessly without a single crash in like 3 years. So no I cannot relate.