It's a broad church I think, it depends on what you're self-hosting and why. Email is more work than Nextcloud, and an hour or two of maintenance work feels different when it's a hobby you're doing on a quiet weekend than when you're busy with life and some essential service has gone down unexpectedly.
Security, as well, is a very deep rabbit hole that can be hard to really get your head around unless you have specific training in it. I "self" host some stuff on a public-facing VPS but there are a couple of services I have moved back to third-party hosting because I had persistent anxiety about unexpected downtime or data breaches.
> It's also great to have a beefy always-on computer to run compute jobs flooring all cores of the CPU for 200 hours on and not have to worry about bills later.
What do you mean not having to worry about bills? Presumably flooring your CPU for 200 hours would generate a hefty enough electricity bill or am I misunderstanding?
> What do you mean not having to worry about bills? Presumably flooring your CPU for 200 hours would generate a hefty enough electricity bill or am I misunderstanding?
Not as much as you'd think. Looking at my power bills, the difference between a month with a relatively idle server, and a month with a very busy server somewhere around 30 KWh. As a year average, the server has added about 60 KWh to my consumption.
Security, as well, is a very deep rabbit hole that can be hard to really get your head around unless you have specific training in it. I "self" host some stuff on a public-facing VPS but there are a couple of services I have moved back to third-party hosting because I had persistent anxiety about unexpected downtime or data breaches.
> It's also great to have a beefy always-on computer to run compute jobs flooring all cores of the CPU for 200 hours on and not have to worry about bills later.
What do you mean not having to worry about bills? Presumably flooring your CPU for 200 hours would generate a hefty enough electricity bill or am I misunderstanding?