3 ms·
"I host my own content on my own servers, or on rented VM's (not AWS). I host my personal home-page on a VM ..." This sounds a lot like my own practices. Ther
by rsync 9y ago
"I host my own content on my own servers, or on rented VM's (not AWS). I host my personal home-page on a VM ..."
This sounds a lot like my own practices.
There is one pitfall which I find interesting and that is that you cannot host your own phone number in the same way that you host your own email/DNS.
If you own a domain and self-host your DNS and mail, you really are the provider - the requests come to you and you first and you have a good deal of "control" over that resource.
However, unless you actually become a CLEC, you cannot "own" your own phone number and become the "server" of that resource. No matter what your setup, some third party intercepts that requests and hands it to you - you are never first in line with a phone call.
One reason this is interesting is, if you run your own mail server, you can email other local users without generating any network traffic - it's just a local copy operation. This is not the case with VOIP/asterisk/anything - your calls are going over the telco network no matter what (again, unless you are a CLEC).