I don’t want to self-host, and even worse: I think most individuals shouldn’t host services for others. Yet, I am self-hosting services and I even teach people how to do it.
They’re not wrong in that most people aren’t suited to or should be running what is effectively public services for other people from some surplus Dell R410 they found on eBay for $40.
That said, it’s all a matter of degree: I don’t host critical infra for people (password managers, file sharing, etc.) where the data loss is catastrophic, but more things that if it explodes for an afternoon, everyone can just deal with it. I absolutely do not want to be The Guy who lost important data through an oversight on an upgrade or just plain bad luck.
But, on the other hand, the SLA on my Plex server is ‘if it works, cool, if not I’ll fix it when I can’ and that’s been wildly popular I haven’t had any real issues, because my friends and family aren’t utter dicks about it and overly entitled, but YMMV.
TL;DR: self-hosting for others is fine, as long as the other people understand that it’s not always going to be incredibly reliable, and you don’t ever present something that puts them at risk of catastrophic loss, unless you’ve got actual experience in providing those service and can do proper backups, HA, and are willing to sacrifice your Friday evening for no money.
I only share my services with two groups of people: my girlfriend and my technical friends. These services do include critical ones like password managers. I’m ok doing this because a.) the services i choose to use won’t prevent access to the data even if my server goes down and b.) my girlfriend understands its a one man band and my technical friends also self host so there’s an expectation of down time. I wouldn’t be comfortable with sharing what I host with anyone else though.
They’re not wrong in that most people aren’t suited to or should be running what is effectively public services for other people from some surplus Dell R410 they found on eBay for $40.
That said, it’s all a matter of degree: I don’t host critical infra for people (password managers, file sharing, etc.) where the data loss is catastrophic, but more things that if it explodes for an afternoon, everyone can just deal with it. I absolutely do not want to be The Guy who lost important data through an oversight on an upgrade or just plain bad luck.
But, on the other hand, the SLA on my Plex server is ‘if it works, cool, if not I’ll fix it when I can’ and that’s been wildly popular I haven’t had any real issues, because my friends and family aren’t utter dicks about it and overly entitled, but YMMV.
TL;DR: self-hosting for others is fine, as long as the other people understand that it’s not always going to be incredibly reliable, and you don’t ever present something that puts them at risk of catastrophic loss, unless you’ve got actual experience in providing those service and can do proper backups, HA, and are willing to sacrifice your Friday evening for no money.
I found out my Plex went down when I got a call from a family member I didn’t give a login to.
My brother-in-
christ-law,I do not fix things on your schedule.
Now everyone is getting individual authentications, so who knows how many other leechers you just cut off.
I only share my services with two groups of people: my girlfriend and my technical friends. These services do include critical ones like password managers. I’m ok doing this because a.) the services i choose to use won’t prevent access to the data even if my server goes down and b.) my girlfriend understands its a one man band and my technical friends also self host so there’s an expectation of down time. I wouldn’t be comfortable with sharing what I host with anyone else though.
That’s what I love about Vaultwarden. Even if the Database were to explode, everyone could still access their own passwords and export them.