Live data from Hacker News

Screw it, I’ll host it myself

markozivanovic.com

201–210 of 495 posts

Re: Screw it, I’ll host it myself

#201
Outside Vultr (oof, probably the hosting provider with the second highest amount of malicious traffic coming out of it besides OVH and on our permanent blacklist) solid setup.

I'm boring, I just use an external drive kit, hard drives, and an rsync or robocopy script depending on my flavor of the month device. Doesn't spend the money on power to have a NAS going 24/7 and is largely immune to someone oopsieing with ransomware.

Re: Screw it, I’ll host it myself

#202

Ok, I’m SUPER into self hosting, but this article? No way. 1) Duck out isn’t a thing, just stop it. 2) Half the articles cited as examples of corporate abuse were later revealed to be mistakes by the user or easily avoidable pitfalls. 3) Self hosting still requires trust (software you’re running, DNS, domains, ISP, etc...) The line of who to trust and how far is a tough one to answer, even for the informed. How I sol…

I always think of it as – how many examples of "I got locked out of all my data!" would there be if billions of people start following the author's advice? Definitely more than the ~5 they list (whether that is user error or actually Apple/Google/Amazon's fault).

Re: Screw it, I’ll host it myself

#204
post #58

Ok, I’m SUPER into self hosting, but this article? No way. 1) Duck out isn’t a thing, just stop it. 2) Half the articles cited as examples of corporate abuse were later revealed to be mistakes by the user or easily avoidable pitfalls. 3) Self hosting still requires trust (software you’re running, DNS, domains, ISP, etc...) The line of who to trust and how far is a tough one to answer, even for the informed. How I sol…

I am perpetually confused about why people think that self-hosting on a VPS solves their privacy and security problems. While I'm sure there are controls in place at reputable VPS providers, it wouldn't be too difficult for them to grab absolutely anything they want. Even disk encryption doesn't save you. You're in a VM, they can watch the memory if they need to. Using a VPS can also make you more identifiable. Your…

Vultr/Choopa specifically is like the number 2 source of malicious hosting company traffic we see (number 1 is OVH, cisco's written extensively about them).

They're blacklisted in every environment I touch along with LACNIC and the usual suspects like China and Russia. Their traffic isn't worth it.

Re: Screw it, I’ll host it myself

#205

The problem I have always had when building elaborate home server setups is the "set it and forget it" nature of the systems I've installed bites me in the ass. Since it's not my full-time job to manage these systems, I'm really not familiar with them the way I might be with the systems I manage at work. These systems cruise along for years, and when something finally does go belly-up, I can't remember how I set it u…

This right here; but even more so. Eventually, whatever platform / tool you use will need to be upgraded. Security vulnerabilities, new features, etc happen and projects like these can get abandoned within a 5-year timeframe. When you have to migrate to either a new or upgraded platform, you have to figure it all out yourself. When the config is broken by an upstream dependency, you’re on the hook too. Who knows if t…

Long term platform stability seems to be moving from relying on the OS to higher up in the stack with the advent of Docker. It feels like Docker is being used more and more in cases where I would have considered something like CentOS.

Re: Screw it, I’ll host it myself

#206
I think it's great that people are publishing their home server setups.

At the same time, the scary sounding warnings of "You're at risk if you put your trust in another company to hold your data!!" ring really hollow to me. I mean, does this person keep all of his money under his mattress, or does he put it in a bank (though I guess he could keep it all in crypto...)? Does he buy insurance, or again just keep a mountain of backup cash in a safe somewhere?

At the end of the day our entire economy is built around being able to trust other companies, and the systems in place to safeguard that trust. "I'll do it all myself" is essentially the process you see in third world countries where the systems are too fragile or corrupt to support that trust.

Re: Screw it, I’ll host it myself

#207

Theres an opportunity here for someone to build a "platform" that makes this all plug-n-play; like what the apple/google app stores have done but where the end user has control. Something along the lines of someone buys some hardware with this platform on it and gets a gui that lets me install "apps" on top of it. Personally, I've got a home setup that is on its way to what the op has; but I think there's demand from…

That's what https://yunohost.org/ is doing

Re: Screw it, I’ll host it myself

#208
post #107

Earlier quoted context omitted.

Use borg or other encrypted backup tool (Restic is also recommended by others in this thread). rsync.net is my offsite backup. Doesn't matter what anyone demands of them, all they ever see is an encrypted blob.

I have been using Duplicati, but >Backup archives are mountable as userspace filesystems for easy interactive backup examination and restores (e.g. by using a regular file manager). looks like a really nice feature of borg. Thanks.

sidenote: restic can do that too

Re: Screw it, I’ll host it myself

#209
I said "screw it" after my Oracle Cloud "always free" account was terminated with no recourse, a few days after having activity on the database building an application prototype, well under the resource limits. I'm now running a libvirt VM on my laptop to develop the prototype.

Others have complained about Oracle Cloud's draconian practices. Doesn't sound like a company that wants to build a cloud business.

Cheers

Re: Screw it, I’ll host it myself

#210

The problem I have always had when building elaborate home server setups is the "set it and forget it" nature of the systems I've installed bites me in the ass. Since it's not my full-time job to manage these systems, I'm really not familiar with them the way I might be with the systems I manage at work. These systems cruise along for years, and when something finally does go belly-up, I can't remember how I set it u…

Oh and don't forget that now maybe you make everything work, but in two years time your setup won't be reproducible, because chances are the original images are not available any more, they got deleted from Docker Hub some months after you used them. Yeah, you should update them anyway for security... but the setup itself is not reproducible, and being forced to use the latest version of something, with the new idiosyncrasies it might bring, is not a nice situation to be in when you just want to hurry up and resolve your downtime.

So I guess that's one more thing to worry about it seems, maintaining your own images repository!

Post reply on HN