Every week or two, I backup my data to an 8T drive. Every year or so, I take the 8T drive off site.
Screw it, I’ll host it myself
281–290 of 495 posts
Re: Screw it, I’ll host it myself
#282Earlier quoted context omitted.
So I agree with your sentiment, your details are a little off. “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.” It would be difficult because you’d have to have host access. VM disk encryption is now tied into an HSM or TPM these days, host access wouldn’t help. As for memory, that is now us…
> Encryption tied to TPM Common on laptops, but I wouldn’t assume that for systems/SANs in a data center, much less their virtual disks. Would love to be corrected.
Google builds its own solution into all servers... And to show that branding brilliance, uses the same name as for all things security: https://www.datacenterdynamics.com/en/news/google-reveals-de...
Re: Screw it, I’ll host it myself
#283Earlier quoted context omitted.
Like Sandstorm?
Yup, the sibling comments mention a few alternatives (FreedomBox and Yunohost) but Sandstorm is really the only one I've ever used that makes me confident in the state of the system long-term. Let me elaborate on that. FreedomBox and Yunohost use more traditional software installation mechanisms; they'll install packages, run scripts, etc. They just add (sometimes very nice) UI around it. While that's great for some…
FreedomBox is the only one that security updates from Debian. And for more than five years. Without breaking changes.
Re: Screw it, I’ll host it myself
#284Earlier quoted context omitted.
Regarding email, I spent some tens of hours setting it up, including implementing DKIM, DMARC, SPF and getting my mail delivered to Gmail and O365. That was over a year ago and things mostly just work with the occasional upgrade or configuration change. You could also save a lot of time by going with a pre-packaged solution. I understand if you don't have time for that, but at least in my experience, self-hosting ema…
It is near impossible. I did all the same things, totally valid and secure setup, gmail would never deliver. YMMV.
I've got the same problem. Using a Hetzner VPS and can't find my IP on any blacklists but it's all sent straight to spam...
Re: Screw it, I’ll host it myself
#285Earlier quoted context omitted.
Hardware sales. People will pay for the convenience of a device that works out of the box with minimal setup. On the software side, integrate tightly with your own subscription services (offsite backups, VPS, etc) to upsell to those who want that, and win over the enthusiast crowd by making it possible to host your own alternatives to those services with a little technical know-how. Open source most components to app…
this is Helm - check us out at thehelm.com
See I see this and it's $349 for the hardware plus $99/year.
At that point, I might as well just go with a paid ProtonMail or similar solution.
My expectations for self hosted isn't to have annual or monthly fees.
Re: Screw it, I’ll host it myself
#286Earlier quoted context omitted.
In 2021, HN doesn't make that much traffic. Any decently built website should be able to handle it, if the owner cares about the user experience.
"HN doesn't make that much traffic" Cite your sources, that claim sounds made up. Your inference that if somebody doesn't use a CDN or have acceptable load times for you, that they don't care about user experience, and so their opinion on self hosting is not worth listening to is absurd.
Well here is a link about someone who made the front page in January: https://nicklafferty.com/blog/what-happens-when-you-re-on-th...
They said they got 18,000 hits in one day. That's a tiny amount of traffic for any decent static website (which this one that we are talking about is). Even assuming they got all that traffic in one hour, that's only 5 requests per second.
Re: Screw it, I’ll host it myself
#287The diagram alone is more than enough of an argument to dissuade me from giving this a shot right now - it's simply too complicated and too much to manage for the amount of time I can dedicate to it. BUT - I'm really thankful for people who keep posting and sharing these sorts of projects; they're the ones iterating the process for the rest of us who need something a bit more turn-key. I'm excited to see this eventua…
After reading through it all, I think this is more a condemnation of the author's diagram (or at least their decision to put that particular one up-front), than of their process in general, nor the challenge. Breakdown of (my) issues with the diagram: - author's interaction with each device is explicitly included, adding unnecessary noise - "partial" and "full" real-time sync are shown as separate processes, whereas…
Nice, maybe I can stop being gravedigger now.
Re: Screw it, I’ll host it myself
#288Earlier quoted context omitted.
> It would be difficult because you’d have to have host access. Which AWS has, by definition. > VM disk encryption is now tied into an HSM or TPM these days, host access wouldn’t help. Are you passing all of the data through the TPM? If no: you still need to keep the key in memory somewhere, the TPM is just used for offline storage. If yes: the TPM, and the communication with it, is still under AWS' control. > As for…
"Good to know that AWS employees are either clueless about their own offerings, or deliberately spreading misinformation." ::shrugs:: I don't work for that part of AWS. My opinion came from other experience. You're not only wrong, but you managed to insult me while being wrong. That's the worst kind of wrong. If you want some further reading, there is some cool work being done in this space. https://docs.aws.amazon.c…
Happy to be corrected if something is actually wrong, but somehow perpetual motion machine peddlers always seem to forget that part.
Re: Screw it, I’ll host it myself
#289I fully support this as long as you can click a button and deploy a new instance when one dies.
Wow, what a disgusting indulgent statement. Period. Much love. Ugh.
Re: Screw it, I’ll host it myself
#290Earlier quoted context omitted.
These systems cruise along for years, and when something finally does go belly-up, I can't remember how I set it up in the first place. This happened a few times to me over the years and then I was lucky enough to go on a packer/terraform course. Now everything is scripted and stored in git. A Gitlab job rebuilds the VMs from scratch every two weeks to include the latest bugfixes and updates. It was a lot of work at…
Now you have N problems... What happens when those images are not available, terraform/packer change APIs, etc?
My solution is Kubernetes. Everything's configured in YAML files. The solution to all those problems is... change fields in YAML files.
Of course, you need to figure out what you need to change and why, but you'll never not need to do this, if you're rolling your own infra. K8s allows you to roll a lot more of the contextual stuff into the system.