News for hackers. Stuff that matters.
Re:Verizon's video app gets special data privileges by bediger4000 on Saturday February 06, 2016 @03:21PM (#11049624)
Doesn't excluding some services from a data cap make a lie out of having data caps to ease congestion, or to penalize "data hogs"?

For example, couldn't you just run Verizon's video app 24x7, and consume much more than your allotment, and not pay for the amount over your cap? Is Verizon prepared for this to happen? In how many cases?

So, data caps, and "bandwidth amounts" are just a way to wring money out of people, without some kind of consumer revolt, right?

Or is it that Verizon's bytes are smaller or more slippery than Netflix' bytes?

Re:Verizon's video app gets special data privileges by amazon_not on Saturday February 06, 2016 @03:33PM (#11049683)
Yes, I believe it was Comcat who publicly admitted that data caps are just a way of wringing more money out of you.
Re:Verizon's video app gets special data privileges by zarify on Sunday February 07, 2016 @02:35AM (#11052081)
Not sure how this can be levelled at the congestion argument. Presumably Verizon's video service is running from their data centres over their internal pipes, rather than external networks where bandwidth is considerably more expensive and probably more limited.

Anti-competitive, sure, but I think that's about it.

I've always felt conflicted about this here in Australia where different ISPs have been setting up peering agreements to achieve similar situations for years. It works out better for the customers who get the unmetered service but at the expense of competition.

Re:Verizon's video app gets special data privileges by bediger4000 on Sunday February 07, 2016 @08:55PM (#11056008)
I live in Denver, Colorado. It looks like Hulu has servers located in Highlands Ranch, Colorado, right on the Centurylink network. Actually, they're Akamai servers, but still. Hulu has servers right next to a VPS in Los Angeles I have access to. Google appears to do the same, without Akamai. Your anti-congestion argument fails. It appears that large content providers co-locate servers on lots of networks.

So apparently Verizon's bytes are slippery or smaller than other people's bytes. Maybe they use smaller bits or something?