Tag Archives: hosting

Setting up a new web site

so I’ve been looking for a new programming project to work on in my spare time. I know, Cybrinth isn’t finished and Mines-Perfect-Linux never really got started, and AcrylicPaint could always use my help. I’ve just temporarily lost interest in those projects. It happens – I can go several months between commits on Cybrinth, for example, but I’ll never forget it. The same is true for the others.

The other day, I decided on a whim to buy a new domain. Something involving dragons, because dragons. I initially thought I’d just use it for music streaming and file synchronization between my own devices. I am still going to do those things. But I want to do other stuff too.

Recently, the gang over at alt.fan.dragons have been the disappearance of documentation regarding the Dragon Code, a method by which dragons can be described using a minimal number of text characters. That’s what I’ll do with the new domain: set up a simple, low-bandwidth site serving up whatever info I can find about the DC. I’ll code all the pages by hand, and I’ll serve them up from my home server (which I’m in the process of setting up now). That way I can avoid paying hosting costs – even the electricity is essentially free because the physical server I’m using is my router, an essential part of my home network which stays online regardless of whether it’s serving up web pages. Other services, such as NNTP or MUCK servers, can be added later if I feel like they won’t interfere with my neighbors’ internet connections. Or I might set up subdomains with paid hosting.

The downside of hosting at home is that it is a violation of Comcast’s Acceptable Use Policy. Comcast could rate-limit, or even shut down completely, my internet connection. It’s risky, I’ll admit that. But I don’t think they’re going to. For one thing, I’ve been violating their AUP in another way for over a decade and never even received so much as a warning letter: file sharing. BitTorrent, specifically, is what I use now but I’ve used other protocols in the past. Comcast’s network is more than capable of handling all the traffic my family generates now, and I really don’t expect much traffic going to my new HTTPS server. The impression I get from reading various forum posts is that Comcast doesn’t care about small little servers generating virtually undetectable levels of traffic; it’s only when the traffic is enough to cause problems that they step in.