Live data from Hacker News

Start Self Hosting

rohanrd.xyz

361–370 of 625 posts

Re: Start Self Hosting

#361

Earlier quoted context omitted.

>It's extremely unlikely that github or cloudflare will ever choose to censor any content I care to share are you absolutely certain that in 5, 10, 15 years, _all_ things you do and views you express that are widely acceptable today will continue to be so?

In 15 years I may be dead, and yes I'm pretty much certain. Life is too short to worry about these things. I'll say controversial things in private or anonymously.

Cloudflare blocks readers running Tor or VPNs and GitHub has been down every day this week. I don't think your plan is bullet proof.

Re: Start Self Hosting

#362
post #132

This is why I'm building Timelinize [1]. It's a follow-up to my open source Timeliner project [2], which has the potential to download all your digital life onto your own computer locally, and projects it all onto a single timeline, across all data sources (text messages, social media sites, photos, location history, and more). It's a little different from "self hosting" but it does have a similar effect of bringing…

Wow; I love this idea. Thanks for writing it! Also, I love how pluggable it is!

Re: Start Self Hosting

#363

Lots of good points about the challenges of self-hosting throughout this thread, especially maintenance, security, and time-investment. Here's my solution to all of them: Invest in your common infra. Docker provides stable images configured primarily with env vars. I have a docker-compose host with logging/monitoring/alerting. All service-specific files are mounted from a NAS that has backups. All network access is c…

How'd you go getting docker + IPv6 going? I spent hours trying to get docker containers to get native IPv6 IPs and eventually gave up because it was to painful.

Why? All you have to do is add a prefix to both the docker daemon and individual networks configured by compose. I do it and it's painless, never hit a bug. Just ensure the prefixes are at least /112.

Re: Start Self Hosting

#364
post #98

Self-hosting is something that we should be constantly iterating on making easier; it's really the path forward for privacy centric folks. The main challenges are managing workload scheduling (SystemD is complicated for a layperson). Networking is another challenge; for instance, if you wanted all or part of these services to remain offline or on a Mesh VPN there's a lot of knowledge required. There's some projects t…

> SystemD is complicated for a layperson Is it? It has clean and logical abstractions, and consistency. Services depending in each other isn‘t complex or difficult to understand. I suspect that a nice GUI would make systemd quite usable for non-expert users. BTW: It‘s called ”systemd“: > Yes, it is written systemd, not system D or System D, or even SystemD. And it isn't system d either. [0] [0]: https://www.freedeskt…

If someone says it’s complicated, then yes it’s complicated. It may not be complicated for you, but by definition someone finding it complicated makes it complicated.

Re: Start Self Hosting

#365
Hosting a server from my house is a violation of the TOS from my ISP. My choices are them or DSL. I don't live in a rural area. I'm well inside a metro area of 5 million people in the USA.

Re: Start Self Hosting

#366
post #98

Self-hosting is something that we should be constantly iterating on making easier; it's really the path forward for privacy centric folks. The main challenges are managing workload scheduling (SystemD is complicated for a layperson). Networking is another challenge; for instance, if you wanted all or part of these services to remain offline or on a Mesh VPN there's a lot of knowledge required. There's some projects t…

It's pretty easy to write a unit file for a service and install/use it. A layperson could easily follow a guide with just a few of the most common cases.

This thread is sad. You don't need to create a unit file to install Fortnite. Why set your sights so low?

Re: Start Self Hosting

#368

Hosting a server from my house is a violation of the TOS from my ISP. My choices are them or DSL. I don't live in a rural area. I'm well inside a metro area of 5 million people in the USA.

So get a VPS.

Re: Start Self Hosting

#369
post #98

Self-hosting is something that we should be constantly iterating on making easier; it's really the path forward for privacy centric folks. The main challenges are managing workload scheduling (SystemD is complicated for a layperson). Networking is another challenge; for instance, if you wanted all or part of these services to remain offline or on a Mesh VPN there's a lot of knowledge required. There's some projects t…

Most consumer platforms don't have functional automatic backups, so this is a pie in the sky at the moment. Even for a proffesionsl, self hosting is kind of time consuming

Re: Start Self Hosting

#370

One problem with "self-hosting" is you're usually still hosting in the cloud – say, on a DigitalOcean droplet or something. That means you're spending $5-10 every month or whatever, plus you're still vulnerable to some amount of cloud-provider fickleness (though much less than a SaaS provider). Much better would be a physical device in your own home. Lately I've been dreaming about a home wifi router that doubles as…

Given the choice between $5/month and, say, $300 upfront most people will choose monthly. I think both options should be available but realistically not many people are going to buy the box. There have been a bunch like FreedomBox, IndieBox, Helm, etc. but they don't seem to take off.
Post reply on HN