I'd guess this is because it only works in ssh PTY sessions. So it would have no effect on tunneling or when piping arbitrary data through ssh to a non-interactive remote command (unless you use the -t switch to force PTY allocation even when stdin is not a TTY).
Sure, but we already have good enough players, open source even, that don't support this technology, and recent codecs have, if anything, become more open, so this only seems problematic for playback on non-general purpose computing devices like smart TVs, set top boxes, and maybe smartphones, tablets, and battery-powered PCs if the tech is incorporated into hardware decoders for all acceptable codecs.
I'm still waiting for the first password manager to incorporate biometrics and security questions, as predicted decades ago by Douglas Adams:
There were so many different ways in which you were required to provide absolute proof of your identity these days that life could easily become extremely tiresome just from that factor alone, never mind the deeper existential problems of trying to function as a coherent consciousness in an epistemologically ambiguous physical universe. Just look at cash point machines, for instance. Queues of people standing around waiting to have their fingerprints read, their retinas scanned, bits of skin scraped from the nape of the neck and undergoing instant (or nearly instant-a good six or seven seconds in tedious reality) genetic analysis, then having to answer trick questions about members of their family they didn't even remember they had, and about their recorded preferences for tablecloth colours. And that was just to get a bit of spare cash for the weekend. If you were trying to raise a loan for a jetcar, sign a missile treaty or pay an entire restaurant bill things could get really trying.
Hence the Ident-i-Eeze. This encoded every single piece of information about you, your body and your life into one all-purpose machine-readable card that you could then carry around in your wallet, and therefore represented technology's greatest triumph to date over both itself and plain common sense.
This is an exceptionally good point. For example, I suspect two major reasons DRM has been more successful on game consoles than video players are the much smaller ecosystems and much larger BOMs, not necessarily in that order.
GP works for Netflix. The team that maintains their FreeBSD stack includes FreeBSD committers, as noted in the linked presentation. Bit of a special case.
With that said, I've quickly upgraded to every production release, including .0 releases, on my personal infrastructure boxes for decades and have never been bitten in the ass or spent more than a few minutes making required configuration changes, and have run -CURRENT on development boxes, where it usually works fine.
As a rough analogy, -CURRENT is a bit like Debian Sid. You probably wouldn't run it directly in production, but it's not an unreasonable option if you have the resources to maintain an internal fork (or, for that matter, as the upstream for a downstream distro).
Side note: Netflix support for FreeBSD is one reason I've continued to subscribe through price increases and periods of low use. Keep up the good work!
I have to laugh as progressively higher time derivatives are invoked to claim improvements. "The rate of increase in the deficit slowed this month" and the like.
Interacting with network stacks via Apple Events and file sharing supported users and passwords, so at least considered security.
reply