[flagged]

In some countries (e.g. Singapore, China, Israel), when you buy a house, on paper you get something like a 99-year renewable lease on land — different from a domain name in scale, but not so much in substance.

So I guess the aptness of the analogy is unevenly distributed geographically. :)

Note that there is a section about self hosting: https://landchad.net/selfhosting/

How are you a landlord if you're paying property taxes?

Once you have everything else set up, you can migrate to a server hosted on your own internet connection. Running your own data center is one of the more tricky parts of the equation, compared to almost-free web hosting for a 10MB site.

You're also just renting a domain name.

this is why i love Tor. you can simply host a site from any pc without certificate, domain, proxy, vps.

A few nitpicks:

* landlords aren't a good thing.

* "setup" is a noun.

* It'd be helpful to offer some context. For instance, talking about ufw without even mentioning that we're talking about Linux, or even a specific Linux distro, would make most people confused. Same with apt.

These are good guides, but it should be kept in mind that they don't try to teach you anything - they're more guides to simply follow, and if you happen to learn something along the way, great.

But it makes sense to have guides that just tell you how to do a thing and don't explain it, because that represents a good chunk of the people out there. It wouldn't be bad to have links to stuff for those who want to understand what they're doing, though.

Overall, we need more sites like these.

I would even suggest apache. It is ubiquitous, config samples are easy to find, it can act like a file server and certbot --apache easily sets up your https.

Yep. Caddy is so easy to use.

[dead]

> What is the point of setting up your own email server if all of your sent messages go to spam for the majority of gmail/o365 users?

I set up a new mailserver a few years ago and have had no delivery problems whatsoever. All messages get through to gmail and outlook/o365 inboxes I've sent to. Didn't even have to register the IP with O365, it's just worked flawlessly from day one. That was from an IP address/netblock not associated with cloud or VPS providers, so initial reputation may have been higher.

A few months ago I set up a mail server on a VM in Digital Ocean, and have had no delivery problems to gmail/Google Apps recipients.

More recently, for new IPs sending mail into O365, they appear to be blocked by default but the rejection message gives you a URL to go to where you can register your IP(s). After doing that, we haven't seen any problems.

If you end up getting an IP that has been associated with previous spam or abuse, I assume your experience will be different. But in my experience, my handful of servers have not had delivery problems. This is all, of course, with proper reverse DNS records that match what the server advertises in its HELO/EHLO, SPF and DKIM all set up, etc.

So that your domain could one day expire and someone could host their email server completely impersonating you

I personally use my server to have people contact me mostly ( it also helps to flag, which stores sell what emails to who ). Although, by now, I likely have enough 'karma' equivalent to not be considered spam by other providers.

honestly I wouldn't mind an email server just to have temp throwaway emails for services that require email signup. Not sure how those that detect temp mail services would work with this though

[dead]

Not really true. You can largely ignore foreign governments as you are not in their jurisdiction.

It also does not apply to everything listed there. Build your own platform is doing things governments will not even notice if you do it for yourself and people you know rather than as a public service.

The practical difference is you're using someone else's resources (hardware, utilities, etc.) or your own.