Not exactly. The telecine 2:3 pulldown conversion is from 24 full frames per second to ~60 interlaced fields (half-frames) per second, which means 4 input frames get converted to 10 output fields. In a straight 2:3 pulldown, film frames ABCD are output as interlaced fields AABBBCCDDD. This transform interacts badly with naïve deinterlacing though: if you just pair off the fields, you get AA BB BC CD DD, leaving you with two mixed-up frames and no intact C frame. Some other pulldown patterns are better behaved when naïvely deinterlaced, such as 2:3:3:2 which produces AA BB BC CC DD.

Many nonlinear editing toolkits, and maybe even a few viewing sets, can recognize when pulldown has been applied and remove it, reconstructing video at the original frame rate.

I think you have value, transactions, and blocks a bit confused.

A typical transaction redeems the output of one or more prior transactions as its inputs, and generates one or more new outputs. Each output specifies the conditions required to redeem it; usually this condition is to sign the new transaction with a specific key. Any excess value from the inputs that is not directed to an output is deemed a transaction fee. Executing a transaction consists simply of specifying inputs and outputs, signing it, and sending it out to some Bitcoin peers.

A block is a data structure that contains a header including a proof of work, a reference to the preceding block it was based on (forming the block chain), a special "coinbase" transaction specified by the miner that disburses collected transaction fees and subsidies, and a collection of whatever additional transactions the miner sees fit to include in the block (subject to a few limits intended to prevent denial of service attacks).

While I agree that economic majority is a rather nebulous concept, it ultimately boils down to whether nodes agree on the validity of a transaction, and in this context, as Lessig so eloquently put it, code is law.

I think this wiki page says it best.

Normally, however, a change proposal is floated with the community, and if adoption seems likely but not certain, the course of action may be to take a poll by specifying a voting period in which miners are asked to include a vote in any blocks they find if they support the proposal. In this context, it is quite literally 'one block, one vote'. In the case of pooled mining, it's up to pool participants to work out how they want to vote with their combined power, with the default being to acquiesce to the pool operator's preference.

The Free Software Foundation recommendation for GPL-licensed Free software that runs interactively is to display a notice when started interactively.

It's pretty obvious to me that liberty is not static. It has to be an instance method, and a virtual one at that, given how frequently it seems to be overridden.

Why not a 28 hours per logical day, 6 logical days per week setup? This maintains the 168-hour length of a week, and also results in some xkcd giggles.

You'd think they'd learn from others' gaffes. Western Digital had a problem with Velociraptor firmware where an unsigned 32-bit count of milliseconds since power on, combined with poorly written read timeout ("TLER") logic, caused all read requests submitted within TLER-timeout of counter rollover to fail. Imagine the confusion that ensues when a RAID controller (or Linux md) sees all its drives vanish for a few seconds then come back ...

The criteria you give are accurate for key agreement in the absence of a preexisting trust anchor, such as the classic Diffie-Hellman key exchange protocol. However, once a trust anchor is established — for example, by meeting and agreeing on a shared secret or verifying one another's public keys in person — that shared secret or known-good public key can be used for authenticating or verifying digital signatures on messages that arrive over an untrusted communication path.

It's unusual to see /. mention a company that has a lick of design sense unless it's either Apple or someone on the defending end of a patent infringement claim from Apple. So when can we expect to see a lawsuit over the rear doors having too clean of a profile? (To the humor-impaired: the second sentence is a joke.)

Communication security is a combination of integrity, authentication, and optionally privacy. You also trust the postman not to modify what you write or forge your signature on your postcards, even though there is no privacy provided by a postcard.

Now if only they'd clout Kontera and similar advertising providers with this patent. I don't want the word "books" to automatically become a pay-per-click link to Amazon, thanks.

If I recall correctly, at least in humans, influenza hemagglutinin 5 tends to attach very well down deep in the lungs but not so well higher in the airway. Therefore H5 flus are particularly nasty if you get one, but they haven't historically been very contagious. I have to wonder if that's where the difference lies: something improving on H5's ability to attach higher in the airway, without compromising its existing affinity too much.

Graphic design and usability are two different disciplines. Anyone who wants a good introduction to usability could easily do worse than reading Jakob Nielsen's Alertbox column. (I hesitate to call it a blog for several reasons, not least because it predates the coining of the term!)

California already does -- speed limits are capped at 55 for commercial trucks and anyone towing a trailer, even if the speed limit is otherwise higher.

NBA tried to claim that in NBA v. STATS. At 1088, 1093, 1094 [come on Google, put in page and paragraph anchors!]:

A state law claim of misappropriation was dismissed on appeal on the basis that federal copyright law preempts the state law. The 2nd Circuit's decision at 851 quotes Computer Associates v. Altai at 717 (this case is a good read for the Slashdot crowd: copyright, trade secret and software):

That said, the above case law may be merely academic if the sports leagues are just trying to run you out of business with legal fees and hassles.