Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Last item (blog/site) could run afoul of ISP terms. I would double check before hosting anything public.


I have Spectrum and I just checked, it is Prohibited to:

> Running any type of server on the system that is not consistent with personal, residential use. This includes but is not limited to FTP, IRC, SMTP, POP, HTTP, SOCS, SQUID, NTP, DNS or any multi-user forums.

That said, I run a small stack of personal stuff, including a public resume-style site, and I've never heard a peep from them. Because there's nothing commercial I feel like I could make an argument my site is "residential".

I did have my server pwned once though (I came home and it was very clear from the fan intensity that it was mining bitcoin) so I'm not sure I'd recommend it to anyone.


My Synology luckily was never pwned, but there were millions of attempts. Noticed higher than usual traffic one day, opened the access logs and found someone attempting to brute-force the SSH credentials... unfortunately for them I don't use passwords, only certs for authentication.


I'm actually doing this right now, and it should be fine as long as you use a service that offers dynamic DNS. If your ISP changes your IP, the dynamic DNS service will automatically point to the new IP.

Namecheap offers this when you buy a domain through them.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: