Last week as T-Mobile CEO John Legere announced that his company’s Binge On program would expand to cover YouTube, he mentioned a strange point: that even the “mobile optimized” 480p Netflix streams T-Mobile offers were higher-res than what you get streaming via AT&T or Verizon. Executives from those companies said they don’t reduce the resolution of videos on their networks, although tests revealed that Legere was right — Netflix does only stream at 360p on AT&T and Verizon. Now the Wall Street Journal has reported that the culprit behind this restriction was actually Netflix itself. 7/ @TMobile has been listening to customers and thanks to a little partnership, @YouTube is now a #BingeOn partner! https://t.co/VQVZoM86Jh — John Legere (@JohnLegere) March 17, 2016 In an odd wrinkle on net neutrality discussions over whether or not broadband providers might restrict video quality of streaming companies they compete with, Netflix chose to limit its own quality on those two networks. Through a blog post and statements to WSJ , Netflix explains that it set a cap at 600kbps to avoid using up too much data under the caps set by those providers for their customers. Sprint and T-Mobile were apparently exempt because of a history of “more consumer friendly policies.” It all makes sense considering how quickly users can chew through bandwidth caps with HD video on mobile, although it seems odd that it wasn’t made clear until now. According to Netflix, this hasn’t been an issue for its users, who are more concerned about saving bandwidth than quality. However, it will soon introduce a “data saver” feature on its mobile apps to let users choose what bandwidth they want to stream over cellular networks — just in case you’re willing to burn a few GB so you can actually see what’s going on in Daredevil . Source: Netflix Blog , Wall Street Journal
Read the original:
Netflix is the one limiting its video quality on AT&T and Verizon
An anonymous reader quotes an article written by Chris Williams for The Register: Programmers were left staring at broken builds and failed installations on Tuesday after someone toppled the Jenga tower of JavaScript. A couple of hours ago, Azer Koculu unpublished more than 250 of his modules from NPM, which is a popular package manager used by JavaScript projects to install dependencies. Koculu yanked his source code because, we’re told, one of the modules was called Kik and that apparently attracted the attention of lawyers representing the instant-messaging app of the same name. According to Koculu, Kik’s briefs told him to take down the module, he refused, so the lawyers went to NPM’s admins claiming brand infringement. When NPM took Kik away from the developer, he was furious and unpublished all of his NPM-managed modules. ‘This situation made me realize that NPM is someone’s private land where corporate is more powerful than the people, and I do open source because Power To The People, ‘ Koculu blogged. Unfortunately, one of those dependencies was left-pad. It pads out the lefthand-side of strings with zeroes or spaces. And thousands of projects including Node and Babel relied on it. With left-pad removed from NPM, these applications and widely used bits of open-source infrastructure were unable to obtain the dependency, and thus fell over. Read more of this story at Slashdot.