The era of cloud computing

So again it is a special-use loan shell primarily accessed through a web browser or specialty software

this
also the fact that VPS have the ability to keep multiple images of your server alive if you so choose for higher availability and failback, in addition to the fact they get to treat their servers like cattle vs yours as a pet

until you can scale up into something like a Cassandra/Hadoop/etc. cluster of nonlocal disks (in which case, you have become the datacenter) you have to do your own backups to somewhere off site as well, in case your house bursts into flame, which means accepting some sort of off-site SaaS solution (Backblaze or w/e) or make tapes/discs/cold copies and mail them to people you can trust (who do you trust with your data?)

I am running a Dell r710 at home as a domain controller and despite doing my own backups to cold copy disks I still feel at risk for the housefire or lightning strike meme. I keep a VPS for shitposting purposes specifically to host forum software for friends, but like hell do I trust my host not to rat me out or snoop around.

Attached: 992ca103f4168185bf0feab70cbeca2da8e5576fda4060516b9376d0d294909c.png (181x194, 8.73K)

It IS the peple going out and getting a server to host content on, what's the difference?

I want self hosted email (no-one I know encrypts, cock.li is a perv but still a top 3 provider) but I don't want to get my outgoing mail dropped because that shit can get me fired if I miss 20 emails.
Advice?

Host with a reputable business provider. Cheap, residential, and bulletproof providers are often blocked.
Get a .com domain, because retard admins will block whole top level domains.
Setup your mail server according to the guidelines provided by blacklist and anti-spam services. These fuckers are anal about mail headers should look.

This. It's all a mean for oppression. Not saying you are oppressed now but you might get into such a situation and then it's too late.

I noticed that I couldn't even receive emails from my college through a cock.li email.

You could use your employer's mail infrastructure for business e-mail and your own server for personal e-mail. That said, the number of MTAs that silently fail when your message cannot be delivered is minuscule. Usually, the worst case scenario is a delay between sending and getting a bounce. I've come across exactly one report of a silently undeliverable message in 4 or 5 years of helping run a self-hosted Exchange instance for 40-ish users where all IT complaints end up on my desk. I also have never had any trouble with my personal self-hosted mail when I used Postfix and later OpenSMTPD on a VPS. In any case, beyond the one fluke I mentioned, delivery failures have always caused my MTAs to warn the sender. Any diverging behavior is likely unintended by the remote postmaster.

Also:

This is true, and I would add that you should query spam blacklists from your server every now and then to see whether it got added, e.g. on mxtoolbox.com/blacklists.aspx (maybe cron a mail sent to the ping@ address listed, if you're going to use their service which I will shill for free; they've been real good to me over the last decade).

The main problem, all this aside, in my opinion, is incoming spam. Using one or more of the blacklists mentioned in the above link (or others) could help but might result in erroneously blocked or spam-filtered messages. I don't know what the state of FOSS anti-spam sieves like SpamAssassin or whatever is like now so you're on your own. Also think about how you'll mitigate DoS attacks, e.g. someone spamming you with huge e-mails.

Define that term please.

Opinions on Freedombone?
freedombone.net/