Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:It seems clear to me why (Score 1) 181

Except T-Mobile doesn't charge for this. They just provide a (human and machine) protocol by which content providers can opt in to what amounts to dynamic traffic control. What it is is giving the consumer an incentive (not counting toward caps) for conserving a limited resource (T-Mobile radio spectrum.)

Now, if T-Mobile *were* charging content providers for this service it would be a very, very different matter.

Comment This is fine... (Score 1) 181

What they are targeting, without kickbacks or other backroom deals, is a service by which users on mobile devices get a downgraded version of a particular service which most likely accounts for 80% or more of their traffic. As long as any provider can opt in without T-Mobile charging them anything more than a reasonable one-time administrative fee I don't see any problem.

I, as a T-Mobile customer, have the ability to opt out which is critical. If I lived somewhere where I could only get slow DSL or no wired Internet at all I might want to be able to stream via the mobile network onto a large screen. Then I pay for the privilege, and that is okay, but as of right now I have Binge On enabled because I don't need high resolution video on my 6" cell phone screen.

Also, consider the number of people who pull up Youtube videos just to listen to music...

Comment A sign of the times (Score 3, Insightful) 245

It is a good sign of the times how far things have advanced that a country in Western Europe cannot come up with any military exercise scenario which can be considered credible. This hasn't exactly been the norm, to put it mildly. At this point in time, the risk of a war in Europe is largely confined to the Balkans, and even there is looking increasingly unlikely that we'll have a full-scale return to fighting.

Comment Re:Linus is just a mean old asshole... (Score 5, Informative) 1501

From one of the more recent things he engaged his primary flame-cannon over, the person he aimed it at did screw up pretty badly and for no apparent reason (I mean, seriously, submitting code that you don't know if it works and you admit is probably not necessary? Don't do that).

So no, I don't think he's a dick for the sake of being a dick - he's a dick because people shouldn't be submitting things that are broken and that kind of person deserves to be told off.

As the main target for said outburst, it was definitely an epic f*ckup on my part. When I got the email, I pretty much chuckled and then said I need to do some damage control. I was not in any way offended. Linus later said:

For example, my latest cursing explosion was for the x86 maintainers, and it comes from the fact that I *know* they know to do better. The x86 tip pulls have generally been through way more testing than most other pulls I get (not just compiling, but even booting randconfigs etc). So when an x86 pull request comes in that clearly missed that expected level of quality, I go to town.

That is part of why I don't get offended when Linus curses at me.

Slashdot Top Deals

Our business in life is not to succeed but to continue to fail in high spirits. -- Robert Louis Stevenson