Ars Technica is reporting and analyzing Comcast’s 57-page response to the FCC investigation into its internet traffic throttling policies.
A few questions have been answered: Yes, Comcast has been doing this for a while, though their press releases would have a rational person believe they had never done so. Yes, they are disrupting customers’ traffic by sending phony TCP reset packets that masquerade as originating from remote computers that customers are connected to. No, they don’t like calling these “forged packets.” No, they don’t think this is in any way wrong (regardless of their actions to conceal this behavior).
One interesting change in their rhetoric is they’re no longer justifying their actions as necessary anti-piracy steps. Plus, they seem to realize they’re on the defensive, accusing their critics of “inflammatory hyperbole.”
A few questions are unanswered. If this interference with normal communications is supposed to enhance everyone’s internet experience, why do all my internet programs (browsers, email, web publishing, synchronizing my computers) time out and fail when they’re throttling my connection? To hear them explain it, only P2P uploads should be affected, only some of the time. Why did they waste all our time with disingenuous answers for so long, so that the AP and the EFF had to independently prove they were, well, lying? As Art Technica writes, if this bandwidth issue is such a problem, why haven’t they had a similar issue with downloads? As I wrote, doesn’t their recent announcement offering a 20x speed boost to “millions of customers” contradict their stated need to conserve bandwidth to preserve their customer’s satisfaction?
The opinions expressed in Steve’s Peeves are intended to entertain and, in some cases, uplift. They may not be appropriate for young readers or the satirically challenged. Parental supervision is advised.