Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
You're not wrong. And the line between evil and laziness here is too messy for me to sort out. We got into this mess because the internet was originally designed as a communication tool between business, university, and government. Specifically, Bell Labs connecting universities as part of the military project DARPA. Since they were connecting dozens of sites, the 4 billion addresses (2^32) seemed like plenty.
Skipping over dialup and forward to early broadband, the issue of the number of addresses problem was 'solved' by a clever firewall technique network address translation (NAT). It was adversited as a security feature, but it allowed ISPs to give one public IP per customer. This standardized things for them - they give you one IP and you multiplex it as you wish. However, since the average customer wanted a turnkey solution, the ISPs would then toss in the modem as a rental. (Also, as enshitification hit this rental modem started getting more user hostile.)
But at this point ISPs are engorged and lazy and redoing everything is a chore, so they got one IPv6 space for everyone, and set up their IPv6 servers to assign chucks of that space based on your assigned IPv4 address. Easy-peasy! Now none of their other management or billing systems have to change! Of course, now your v6 space moves anytime your v4 space does but -they always have those business accounts to sell you …
A diamond in the rough: When I was younger, working at a data center and IPv6 was new, I found this gem coupled with IPv6 world day (via Reddit): https://tunnelbroker.net/
Hurricane Electric was/is happy to give you a free static IPv6 /48 prefix, and you could tunnel your home connection directly to this (like a site to site VPN). Their catch is if you start pushing significant traffic you'll have to pay market rates. But if your goal is to add a free static IPv6 frontend to your home network, this has been here the whole time.
Similarly, I've read Cloudflare's Terms of Service [privacy policy, et al.] and they're fairly tame compared to many. I'm also partial to their WARP technology. The idea is the end user's traffic is encrypted and sent to any of Cloudflare's servers and from there they can then bounce to anywhere in the world (a handy trick if you need to get around a great firewall or other tools of censorship). If your home lab uses Cloudflare's tunnel, and your phones use WARP, the only thing a third party can see it that you're using the largest CDN in the world - which is sorta a 'well, duh' statement. Cloudflare's schtick is they don't need limits - they can flood you home connection and it wouldn't be a blip on their radar. However, they need to run variations of these technologies to operate their primary business. So making a copy for you to use is almost trivial. (And if you go viral and suddenly need a CDN, I'm sure they can sell you some)
Tl;dr: you're not wrong, but the desert has water in it, if you know where to look.