Comcast continue to prove that they are evil, scum-sucking bastards

[jducoeur]

This morning, with no warning or notice, they starting blocking inbound port 80 to my house. Given that I am trying to get some work done here, that's more than a little rude, especially since the inbound traffic is essentially trivial -- it's just for test purposes, not a real public website, so we're talking something on the order of tens of K. No idea whether it was an across-the-board change, or specifically targeted at me.

Fortunately, it's easy enough to work around (the nice thing about developing a Facebook app is that the layer of indirection means that I can redirect the port at the FB layer without any change at the user level), but it continues to increase my desire to quit this annoying company. Do I understand correctly from recent conversations that RCN (for a small surcharge) allows inbound port 80? That alone might get me to sign up for them for Internet, given how incompetent Comcast has been lately. (Have I mentioned that outbound email through Comcast has been consistently failing for us for the past two days?)

For now, I seem to be back up and running. I'm tentatively assuming that they simply noticed my inbound port 80 traffic and chose to shut it down. (Although, in that case, I have no idea why they were allowing it previously.) If I find that my new port gets blocked as well, it means that they're sniffing my traffic and looking for HTTP, in which case I'm simply out of here -- we're paying them a small fortune per month, and if they want our money to go elsewhere that much, we can probably oblige them...

Comments

[laurion]

No, not to your curb. That's why I said third party hosting. I guess my question is really if you need to get bandwidth to your curb, or can you move what needs bandwidth to where it can get it. (Mohammad, Mountain)

SoftLayer looks pretty good if you need your own dedicated hardware, and the computing power that implies. If what you need is storage space and bandwidth though, is dedicated hardware worth the extra cost? In my case I'm running several dynamic websites, with databases, e-mail, a handful of cron and backup scripts, and a podcast with gigs of data transfer each month. I'm not doing any massive number crunching, video editing, etc. that requires dedicated hardware, so Dreamhost covers all my needs for a fraction of the cost of a dedicated system.

[jducoeur]

No, the issue is very much the to-the-curb side. I plan on doing my development at home (at least to start), so I need solid bandwidth to here, even though the actual *site* will run elsewhere. (I don't enjoy trying to do major development remotely -- done it enough times to think it introduces unfun pokiness.) I've already got ISPs; the question is how I connect to them.

And Dreamhost isn't an option. This isn't an ordinary website: this is going to be a fairly high-power AJAX/Java application. That in and of itself lets Dreamhost out, since they explicitly *don't* support servlets. (Unless you are doing dedicated hardware, which pretty much misses the point of Dreamhost.)

Keep in mind, this isn't a personal project. I'm building something that is *intended* to have a million daily users in a year's time. (No, I'm not necessarily expecting that fast a growth curve -- but it's plausible, and I want to be able to handle it if it happens.) So rapid scalability is absolutely key here, from the architecture on up. Heck, one of the reasons I'm planning on Hibernate for the middle of the DB layer is so that I can switch from MySQL to Oracle reasonably quickly, should that prove necessary...

[laurion]

Oh, I don't mistake this for a personal project at all. I didn't think Dreamhost was going to be a solution, I was just illustrating that there's no way I could do what I want to do with a bandwidth to the house solution, especially with my even greater financial restraints, and that moving off the curb got me what I wanted.

Clearly one of your defining needs at the moment is the flexibility and accessibility of keeping your development very close at hand. So, you're right -- high speed to the house is what you need now, and something dedicated elsewhere when you've got something a little more stable and releasable, and the concern is scaling the resources to match.