If you host a static website the traditional way, there are four main security, privacy, and cost issues which I know: - a name, address, and email address hav

If you host a static website the traditional way, there are four main security, privacy, and cost issues which I know: - a name, address, and email address have to be registered to the domain name. Just like in porn, there are cheap services which will act as an intermediary and hide these things from the general public while ensuring that the authorities can find that name, address, and email if need be. - any way of logging in to the web host needs to be protected like any other service accessible from the Internet (so use secret usernames and long passwords with high entropy) NB. a static website (where pages are generated once and served many times) has far fewer points of attack than one powered by a content management system with all kinds of ways for people to post to it. - if you sign up to pay a flat rate for bandwidth to your site, its theoretically possible that you have to pay more if someone directs a lot of traffic there. AWS currently offers 1 TB / month of bandwidth and storage for USD 0.01 (1 cent!) and I know of small hosts which charge about 10 dollars for the same service. So bandwidth and web storage are cheap if you shop around. - anything you post to a URL may be read by anyone with a browser who knows the URL (and anything you store on a computer is accessible to whoever controls the computer). This applies to social media, content management systems, and a hand-coded myBookmarks.html I have no experience with Digital Ocean Droplets. Websites on hosting static sites include https://thoughts.melonking.net/guides/introduction-to-the-web-revival-1-what-is-the-web-revival https://thoughts.melonking.net/guides/introduction-to-the-we... and https://blog.itsnero.com/webguide https://blog.itsnero.com/webguide