There are a number of levels inside cable companies when it comes to support.

The lowest level is the "cable guy". This person is not likely to have a computer or engineering background. They receive training from the cable company to do basic things like use the diagnostic meter, run coax cable, strip wiring, etc. basically they are kind of like basic electricians. Some may have some training as to what QAM errors are and the like, but not enough to fix problems. Some are employees of the cable company (more likely for trouble calls) and some are contractors (more likely for installs).

Next up the line are the "line techs". These are the guys in the trucks with cherry pickers. The customer rarely deals with them. They are trained in diagnosing line and node problems to find errors in the signals (leaks, interference, etc). Likely they have an electrical engineering background. When there's an "outage" (TV, Internet and/or phone), these are the guys who are deployed.

Lastly, there's the people who manage the headend and servers. These are ghosts, you'll never see them. These are the ones with computer and engineering backgrounds, the ones you could call network specialists. Customers never deal with them directly.

So basically the "cable guy" is still the "cable guy".

The issue is that GoDaddy didn't really reverse their stance, at least not where it counts. They now claim to not support the SOPA bill as written, but they still agree with it for the most part, which isn't surprising since the more or less wrote the thing.

I believe you still have to put the router into setup mode even when using shared PIN mode. That limits the times this attack could possibly work.

Nitpick:

The FCC can't pass laws or "acts" (which aren't "passed" anyway). Only Congress can pass bills which become laws when signed by the President (or via a veto override). The FCC has regulatory power over broadcast networks based on the mandates given to it by Congress, and has the power to levy fines, but it can't enact laws. There's a grey area when it comes to non-broadcast stations and cable companies, but usually they comply.

http://en.wikipedia.org/wiki/Federal_Communications_Commission#Regulatory_powers_and_enforcement

Welcome to Slashdot. You must be new here.

All that's well and good, but it doesn't change the fact that Deutsche Telekom doesn't want T-Mobile USA. They don't want to run it and are putting the bare minimum into it to keep it going. Since the deal fell through, that means that basically Deutsche Telekom can't sell T-Mobile USA to any of the larger companies (I doubt Sprint would get approval either since it's one of the top 3 companies).

That means that either Deutsche Telekom will try to sell T-Mobile to one of the smaller companies for less than they would have gotten or Deutsche Telekom will simply break up the assets of T-Mobile and sell them off in bits and pieces. The spectrum T-Mobile already has plus what they'll get from AT&T is pretty valuable. Actually AT&T could end up buying all of T-Mobile's assets, leaving just the company and it's customers behind. That could end up being worse for T-Mobile customers than an all out buy out.

Since when are "could" and "will" synonymous?

Considering Netflix originally moved from Flash to Silverlight, I doubt this.

That's one of the benefits of the way Anonymous works. Even if the prisoner gives up the names of the few members he knows about (assuming he does), the prisoner would have no idea who the vast majority of members of Anonymous are. That's the way Anonymous is designed.

I would be like trying to stop a swarm of army ants by stepping on a few of them.

Considering Netflix recently lost half their market value, I wonder how they are going to afford this? Are they only going to stream a handful of Dreamworks titles?

Pretty much all of those services haven't been updated in ages or aren't even used. For example I used to use Google Desktop, but uninstalled it about 2 years ago because it was buggy, performance hogging and slowed down my machine.

From what I've read, the worm isn't using an exploit. It's simply trying to log in using a set of common and easy to guess passwords. If you use strong passwords, then your machine won't be compromised. Though flood of RDP access requests could amount to a denial of service attach.