201–210 of 625 posts
Bringing self hosting to lambda users is _REALLY_ hard and Big Tech won't let you do it too easily. Many corp email smtp servers will IP block your email server (big thanks to spamhaus), or won't support no-DNS email address and servers (which is RFC from the start) or won't have the decency to handle grey listing or will send all your emails to their spam boxes (gogol) even though ppl did remove your emails from the…
Earlier quoted context omitted.
> 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…
I swear, writing it as SystemD isa shibboleth of systemd haters.
Earlier quoted context omitted.
Got one of those. It is hard. Very hard. Absolutely freakin’ hard to make a bump-in-the wire dynamic 5-tuple blocking “hub”. It also does “waterfall” egress packet delaying.
I'm not sure I understand what you're describing ... A slug should not need to be dynamic nor should it be complicated in any way ... in fact, it is one of the simpler systems I have ever deployed ...
Earlier quoted context omitted.
> You need to take care of security Easiest solution is to just host stuff on a local network without access to the wider internet. E.g. running on an old laptop/raspberry pi/server in your basement. Sure, that means you can no longer access your self-hosted stuff when you're out of the house, but the tradeoff is peace of mind about your data leaking or worse.
> Sure, that means you can no longer access your self-hosted stuff when you're out of the house, but the tradeoff is peace of mind about your data leaking or worse. Lots of things I'd consider self-hosting are functionally useless if I can't access them from my phone while out and about. I could put my phone on a VPN, but that's just another layer of complexity to add to the self-hosting process.
Self hosting is hard. You need to take care of security, backups, software updates, software installation and so on. Even on something like a QNAP (which can be compared to managed hosting) this can be hard. Flip the wrong switch and you expose something to the world. Missed a security update: your device is now vulnerable. While I host a lot of things myself I can understand self hosting is not for everyone.
automation is not a thing? I'm pretty all cloud providers do it...
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…
Good for them that it is seeing traction :)
Bringing self hosting to lambda users is _REALLY_ hard and Big Tech won't let you do it too easily. Many corp email smtp servers will IP block your email server (big thanks to spamhaus), or won't support no-DNS email address and servers (which is RFC from the start) or won't have the decency to handle grey listing or will send all your emails to their spam boxes (gogol) even though ppl did remove your emails from the…
> Many corp email smtp servers will IP block your email server (big thanks to spamhaus) Nope. Spamhaus doesn't block self-hosted email servers. Spamhaus just publishes a number of lists, which postmasters can use or not, whether for filtering or just for scoring. The PBL in particular is likely to catch people self-hosting from a retail connection, because it lists most residential IP address-space. But it's the rece…
Self hosting is hard. You need to take care of security, backups, software updates, software installation and so on. Even on something like a QNAP (which can be compared to managed hosting) this can be hard. Flip the wrong switch and you expose something to the world. Missed a security update: your device is now vulnerable. While I host a lot of things myself I can understand self hosting is not for everyone.
It doesn't even require actively flipping switches, but can be from not knowing a vulnerable feature was enabled by default. My QNAP got hit with ransomware because of a vulnerability in the cloud access software that I wasn't even using. I've since locked down all non-local traffic.
This article is a bit delusional and oblivious to market dynamics. 1. Privacy: Self hosting is not necessarily more private than cloud services. The security of self hosted services is only as good as the effort put into maintaining it. Who do you think invests more in security: the giant corporation or a free open source project? Even if the project is well maintained, there are many ways your server can be compromi…
While it’s an issue you should consider, those attacks are pretty unlikely. However traditional cloud services will harvest every bit of what they get about you with a frightening efficiency but they’ll never automatically scan your server for vulnerabilities to read your mails.