isomorphic

Right. Also, unless I missed something, I didn't see anything in their FAQ that states categorically that they're not storing your card information on their servers.

No, Coin, I'm not going to store all of my credit and debit cards in a single spot on the Internet.

Your app has to work without Internet, or it's a security risk.

Adobe's security breach undermines their new Creative Cloud licensing model, because Creative Cloud requires an ongoing trust in Adobe in order to continue functioning. A boxed software (or one-off download) model is transactional, requiring less trust. (One can, at least, firewall boxed software to limit potential damage.) Since Creative Cloud is subscription-based, one has to maintain an account with Adobe to keep the software working.

As someone dithering about transitioning from Creative Suite to Creative Cloud, receiving Adobe's letter was a slap in the face.

Given that the breach not only included accounts and credit cards, but also source code, I believe it's reasonable to speculate about potential exploits, including exploits in the Creative Cloud deployment mechanism. Going a little further into paranoia, I wonder if running Creative Cloud is potentially equivalent to running a trojan delivery system. I.e., how do we know Adobe's servers are now secure? Adobe is being cagey about the extent of the breach; the breach may have included internal Adobe credentials that can only be solved by a system-wide nuke-and-pave.

I really want to buy Adobe's new software, but they're making it extremely difficult for me.

The reason those TRS/TRRS connectors have been around for so long is that they flippin' work.

While I agree that a MagSafe-style equivalent would be nice, it will be a giant step backward if we end up with a gazillion new "standards." Or a de facto standard with a poor mechanical connector (e.g., micro USB). Or a great mechanical connector that's completely proprietary (Lightning).

Bluetooth headsets are not really a solution for the reasons mentioned in the article. Even with voice codecs there's lossy recompression going on, and music is worse. Add the delightful user experience of batteries, and you've managed to replace a light, decent-sounding, completely-reliable $15 set of earbuds with something heavier, lower-fidelity, always in need of charging, and more expensive. All for the sake of removing a wire.

There have been attempts to address git's shortcomings with respect to independent revision control of a single file: There is the "zit" project at

http://git.oblomov.eu/zit

...although it wasn't ideal for me, and it doesn't look like it's been updated in a while. E.g., these days that should be on GitHub!

RCS really fits well with the use-case of /etc configuration files. It's a pity that Git doesn't function very well for that particular case.

How do we measure frequency (or time) precisely if the emission spectra are changing?

Netflix is indeed using some slippery and perhaps contradictory wording that has passed through at least one marketing filter.

Although we may interpret "premium" to connote "better", the usage meaning "something you have to pay" is accurate.

Perhaps we could take back the language and start referring to the extensions as "Media Fee Extensions"?

You are correct in asserting that the EME should become standardized, and that Netflix is participating in that process. I should not throw stones unless I'm willing to help.

I admit to being conflicted about the philosophical need for such extensions--although I have no pragmatic objections. Netflix makes their coin by selling limited access to an artificially-restricted resource; the resource would probably not exist in its present form without the restrictions.

However, as someone who lived through web development in the 1990s, my brain shut off after reading "away from using proprietary" followed by "Microsoft MarketingTerm".

Quoting Netflix, from the article:

  We expect premium video on the web to continue to shift away from using proprietary plugin technologies to using these new Premium Video Extensions.

Quoting the article:

  According to Netflix, Microsoft made this possible by implementing three features in its still-unfinished IE11:

  The Encrypted Media Extensions (EME) using Microsoft PlayReady DRM.

Netflix is using some doublespeak here. Yes, Silverlight was a "proprietary plugin", but they've just shifted to using proprietary DRM with proprietary extensions to HTML5. They got rid of the plugin--great! But they've replaced one proprietary experience with another.

In the case of challenge/response with a single 128-bit block, I think ECB would be just fine. I can't imagine a car key needing to send multiple blocks (thus necessitating CBC, etc.).

The larger point here is that most keys probably aren't using AES to start with, and there's probably some other vulnerability in the overall system.

I use the "Social Widgets" list subscription for Adblock Plus. Just add:

https://monzta.maltekraus.de/adblock_social.txt

...as a filter subscription in Adblock Plus and you'll stop seeing most of these sorts of "share" buttons.