ABC(and others) offer content effectively for free via local broadcast. Their profit comes from commercials. All Aereo is doing is providing the antenna and DVR capabilities over the internet, thus allowing you to view from alternative locations and devices. The users are paying a small premium to have the hardware, storage and upload bandwidth managed offsite. There is nothing about this setup that an individual couldn't do with their own equipment. Aereo isn't taking any more money from the content providers than any other DVR/VCR would.

Don't forget all the men you'd be punishing!

Just because some people use the newer naming convention doesn't make either one wrong/right(better/worse). They should of codified kilobytes(etc) earlier on, before it actually became an issue. The standards from the IEC didn't come into place until after the non-codified standard was entrenched. There was no reason to change it, aside from sticking their nose in things. It was a well understood naming convention for the number of bytes. To prevent the people(marketing departments) from abusing the situation, they could of used the defacto standard as the official standard.

Because it's a truthful lie to make the drives look bigger, as was pointed out in the link you provided. The sole cause of confusion, was marketing people wanting to pad their products stats. This could all of been solve quickly in the beginning by firmly defining kilobytes(etc) and forcing manufacturers to uphold truth in advertising.

Not sure if arguing that they didn't specifically mention newer ones were salted, but bcrypt itself salts the passwords.

Being capable, and being allowed... two separate things.

They put a lot of money into making sure that most fail in the 1 to 3 month window after the warranty expires. They wouldn't want to ruin that by having too many fail under warranty.

1, 5, 10, 100 difference services. It actually makes it worse if they're intentionally throttling MORE individual services. Each service affected under "cloud" is affected individually.

To be fair, there is a significant difference between expressing your opinion/belief on a topic, during discussion of said topic, and expressing it to random people.

But, the insurance is paid for ultimately by the customers. Usually, premiums are derived from risk. So, the customers are still paying for it.

You do know, it's possible for both drivers to be in the wrong.

You apparently don't know how triple buffering works. http://en.wikipedia.org/wiki/Multiple_buffering#Triple_buffering

Aside from that, it isn't like thats the ONLY improvement in project butter.

Not every ISP is a major carrier. Rural providers have a limited supply of customers. It would all depend on how much of the ISP traffic is infected crap.

It's not a matter of to a single process. It's a matter of how much is addressable by the system. The more ram you have, the more apps you can keep in memory for quicker access.

The wording in most terms of use would put the ISP in the right to do so. The issue is whether they want to absorb the cost of a reliable detection system, and whether they want to deal with losing some customers that would regularly end up being disconnected.