3 ms·

Exposing your home devices to the internet is a really bad idea, because it exposes you to doxxing, DDoSing, whatever security issues your 5-year-old smartphone

by crote 3y ago

Exposing your home devices to the internet is a really bad idea, because it exposes you to doxxing, DDoSing, whatever security issues your 5-year-old smartphone may have, and a plethora of other risks. People used to do this in the 90s and early 2000s, but it turned out to be a hilariously bad idea security-wise. Even the enthusiasts these days use a dedicated server somewhere in a datacenter. Services like Github Pages and Cloudflare exist for a reason, and it isn't because anyone is trying to gatekeep web hosting.

detourdog 3y ago
Some of us have been doing this since the 90's and don't see and end in sight. The issues are not bad compared to your average customer service call. I prefer knowing what is going on with the technology I manage. Most websites are way over complicated on the backend. It's very easy to self-host.
Santosh83 3y ago
Other than DDoS, all other issues you mentioned apply equally to all internet facing apps like Whatsapp etc. A static file server can be hardened to the point where only DDoS remains a significant threat and that hardly applies to an average Joe. IF my little site of a few boring pages & pics gets DDoS'ed, then I can move to Wordpress, Cloudflare or whatever.
- shortcake27 3y ago
  There’s also a nice middleground - you can just proxy your site through Cloudflare. This masks your IP and protects against DDoS, the only caveat being you need to move your DNS to Cloudflare.
  - detourdog 3y ago
    My usual model is to configure the servers to be hosted locally and rsynced anywhere else. I'm currently going through this exercise right now. I start by making everything good local and then can publish anywhere. I love having a completely independent working local copy. My environment is perfect for my needs or I change it. Basically my deployment plans and disaster recovery are indistinguishable.

by crote 3y ago

detourdog 3y ago

Some of us have been doing this since the 90's and don't see and end in sight. The issues are not bad compared to your average customer service call. I prefer knowing what is going on with the technology I manage. Most websites are way over complicated on the backend. It's very easy to self-host.

Santosh83 3y ago

Other than DDoS, all other issues you mentioned apply equally to all internet facing apps like Whatsapp etc. A static file server can be hardened to the point where only DDoS remains a significant threat and that hardly applies to an average Joe. IF my little site of a few boring pages & pics gets DDoS'ed, then I can move to Wordpress, Cloudflare or whatever.

shortcake27 3y ago
There’s also a nice middleground - you can just proxy your site through Cloudflare. This masks your IP and protects against DDoS, the only caveat being you need to move your DNS to Cloudflare.
- detourdog 3y ago
  My usual model is to configure the servers to be hosted locally and rsynced anywhere else. I'm currently going through this exercise right now. I start by making everything good local and then can publish anywhere. I love having a completely independent working local copy. My environment is perfect for my needs or I change it. Basically my deployment plans and disaster recovery are indistinguishable.