Whether or not the entire broadcast is itself a copyrighted work, the copyrighted components from which it is assembled certainly are, so distribution of them without license would be legally sticky. If the entire broadcast is also copyrighted in itself, then you'd have two parties who could go after you for redistribution.
The alarming thing here is that Fox seems to be claiming that a totally distinct mechanism for modifying the end-user's experience of the broadcast somehow constitutes a violation of copyright. That (in addition to the clearly pernicious practical effects) would seem to open the door to absurdities like 'copyright infringement' that does not involve any copying(the machine-readable equivalent of 'skip from time w to time x and from time y to time z' is in no way even slightly like a copy of a television show...)
I very strongly doubt that this is relevant on the scale of recorded human history and naked-eye observation; but doing all that mass-energy conversion and indiscriminate radiating must be slowly changing the sun's size, with some sort of balance between loss of mass and thermal expansion or contraction.
I'm told that the 'expands and engulfs the inner planets' stage will be dramatic; but is the expectation before that event a very, very gradual shrinking or something more complex?
It isn't really a question of whether the pacific rim ODMs will be manufacturing the gear. It's just a question of whether HP and Dell will be providing case badges and customer support or not...
Foxconn, among others, already handles a nontrivial amount of manufacturing for HP, not sure about Dell. The open question appears to be whether large operators like Rackspace will find it economically viable to handle system integration for themselves, in addition to operations, or whether existing systems integrators will continue to smooth over the rough edges of the ODM side and serve as the final vendor.
Honestly, I don't really care about the TV issue one way or the other; but the potential precedent is ugly.
If Dish's plan were to tape the broadcasts, chop out the chaff, and send you the final cut, that'd be a clear-cut case of a copyright infringing unauthorized derivative work.
However, their actual implementation, as best I've been able to tell, doesn't modify the copyrighted source material at all, it just adds specific automated behavior to the playback device. If that is 'copyright infringement' then virtually anything a playback device might choose to get fancy about is subject to the veto of team content. Automatic volume reduction on your music when you get a phone call? Sure. Replaygain volume normalization? Sure. Stretching or letterboxing to put 4:3 on 16:9 or vice-versa? Why certainly. Applying a custom CSS stylesheet to a website against the operator's wishes? You bet.
Yes, it may well happen to be true that OTA broadcasts aren't going to be helped by easy commercial skipping; but something isn't 'copyright infringement' merely because it happens to be bad for the checkbooks of people who hold copyrights. It also has to, y'know, infringe. In this case, if the definition of 'infringement' is stretched far enough to save our poor, beleaguered, broadcasters it is stretched far enough to allow near-total control over any device that handles rendering of copyrighted material, which is virtually anything.
Compared to that, letting all of broadcast TV burn looks like a fantastic idea, even if you are otherwise sympathetic to it...
I'd suspect comparative advantage in action: These were phone scammers. The techie scammers are out there dumping drive-by downloads and building attack toolkits for sale. The less technical ones are falling back on their people skills and doing social engineering attacks...
Since we are talking about implementing 6502s in questionably efficient ways, it seems like a good time to plug http://visual6502.org/. Efficient? No. Logic-accurate emulation of a 6502 implemented in javascript based entirely on photographs of a decapped 6502 die? Fuck Yeah.
My impression of the metagame that is Minecraft is that doing things the hard and/or rube-goldberg way is part of the charm. There is some reason why people are trying to build ALUs in crap redstone logic rather than just alt-tabbing to the logic circuit simulator of their choice(or a VM, or an emulator of some popular retro architecture).
Given that, at what point do mods that improve minecraft's program-ability go too far and turn it from a perverse simulation game of enormous popularity into a really dreadful IDE?
It could also be construed to cover virtually all protocols and file formats, as well, since those are descriptions of the 'interface' by which an application can interact with another system or data storage structure in a compatible way. You'd basically end up in a situation where interoperability would be possible only at the pleasure of the original vendor for the duration of an entire copyright term. That would be pretty dramatic.
That's certainly true enough, even aside from security, the sheer logistics of networking every little widget would be ugly. I was(perhaps incorrectly) assuming that since the machine in TFA's timestamp had entered the patient's EMR that it had been collected electronically. If a human read it out and recorded it, the solution would likely involve them sanity checking the instrument's present time when reading it, rather than adding complexity to the instrument after the fact.
If the APIs turn out to be non-copyrightable, does this mean we can really all enjoy/suffer Java for free?
It's a great deal more important than that: If APIs are copyrightable, API-compatible implementations of anything without that thing's blessing would be on legally shaky ground. I'll leave imagining the technology world in an alternate universe where IBM simply sued Compaq for producing an API-compatible BIOS to the reader; but that's the sort of magnitude we are talking here...
The "atomic" clocks that merely sync to the NIST radio timebase are toys; but you can get perfectly real atomic clocks for (relatively) small money. I haven't been comparison shopping or anything recently; but the 5071a provided a handy rack-mount caesium frequency reference for ~$50,000 back when Agilent sold them. Compared to the rest of the cost of getting an hospital-wide EMR system and a whole bunch of life critical gear from several dozen vendors chatting amicably, the timebase will count as a pleasant break...
I assume that the continued demand for timing-critical components in contemporary cell networks has increased volume and miniaturization in the market since then.
Given that it isn't too likely to matter within nanoseconds when exactly Joe Patient was admitted, even an only modestly accurate RTC would likely do the job, so long as all the devices in the building were listening to it. GPS would be a dirt cheap way of keeping the master source from drifting excessively over time, and in the short term even the resolution limits of a modest quartz oscillator wouldn't really be a big deal. Outside of truly dreadful stuff, inaccuracies are a big issue when you have multiple clocks that are never checked against each other and run independently long enough to drift quite far from one another.
You could do an implementation of NTP on a closed network, with a local time source(compared to the rest of a hospital, an OK atomic clock doesn't cost that much, and a GPS timebase could be lost in a rounding error) with devices flagging anomalies in the NTP source and falling back on local quartz oscillators if needed.
It'd be more expensive than just having IT bring a patch cable; but there isn't anything about "NTP" that requires putting gramps' pacemaker on the internet...
My impression is that IBM is marketing Watson as 'basically a super computer version of Siri that the customer pays IBM old-school-mainframe money for the privilege of keeping on-site'...
Whether the sort of banal shit that Siri gets asked to handle most of the time is actually a risk or not, it does seem fairly likely that some level of mining and 'monetization' is being done, same as other search mechanisms(and even if it isn't now, disk is cheap and EULAs are flexible, so that could change retroactively).
Realistically(especially once you tie the user to a more-or-less not-spoofed-in-practice phone UUID, as Siri does), any of the contemporary search mechanisms do constitute a pretty significant 'side channel' into the user's activities, interests, and so forth. Their popularity suggests that most people don't know or don't care, and(so far, to the extent publicly known) their operators have confined themselves to generic advertising and rounding up the occasional dissident(rather than, say, attempting algorithmic insider trading based on analysis of search queries coming from different companies IP blocks....); but the theoretical capability can't be dismissed.
So, broadly, IBM's position is not false, even if it isn't clear whether it is operationally true anywhere. More narrowly, in terms of IBM's interests, a bunch of operators providing natural-language expert systems on cheap commodity gear paid for by advertising isn't clearly helpful to IBM's business model. A bunch of paranoid C-levels buying in-house IBM solutions, securely humming away on IBM iron behind locked doors and a legion of IBM integration consultants, on the other hand...
There are arguably two categories of biblical pricing:
In the "The laborer is worthy of his hire" camp, you have the pretty-much-cost-of-printing-and-distribution prints of KJV and other out-of-copyright versions, along with moderately expensive editions of newer translations and revisions and slightly more expensive still 'critical editions' that are either a classic translation with a heavy addition of new marginal notes, explanatory sections, essays, etc. or a revised translation with the same.
In the "Yeah, the seller is probably an unscruplous weasel; but WTF is wrong with the buyer?" camp, are the vanity-printed and overpriced versions of cheap or free translations and(most horrible of all) the assorted commercial, political, and celebrity tie-in versions. If, for example, you find yourself purchasing The Holy Bible: Stock Car Racing Edition there are no words...
What is surprising is not that he's a kleptomaniac; but that he's such a bad kleptomaniac(or, even more oddly, he brings a degree of technical skill, creating his own barcodes, to a typically downmarket form of shoplifting, normally accomplished just by sticker-swapping, but doesn't actually improve the rate of return notably...)
It's like discovering that some sleazy commodities speculator is breaking into foreclosed houses to steal copper in his nights and weekends. Sure, it isn't a surprise that a commodities trader might have a questionably ethical relationship with metals prices; but it is a surprise to find him getting his hands dirty with a sideline in blue-collar crime.
All part of an elaborate plot to sell Target some sort of heuristic-theft-detection ERP module that slides 'seamlessly' into a SAP implementation and absolutely nowhere else...
In all seriousness, of course, people who commit crimes despite having no reasonable incentive to do so ($30k isn't peanuts; but in $/hour plus legal exposure, how well could box-at-a-time retail fraud have really stacked up compared to just staying a little later at the office when you are a VP?) are really ones to be watched. People who merely want the good things money can buy are comparatively easy to satisfy. People who want money per se are always more expensive than you can afford...
The law does not, apparently, require that takedown demands have a name attached. Clearly, the cyberbullies will give up in abject defeat in no time...
My understanding is that the two schemes are the same. The software version is just the cheap-n-lazy implementation for people who don't want to deal with airgapped hardware tokens.
Honestly, what makes me nervous about this is not the fact that, shocking!, software can be reverse engineered; but that RSA seems to mix a disconcerting amount of laziness and hubris in with their competent math.
As best we currently know, it is Not Possible to deduce subsequent token outputs merely given access to previous token outputs. However, it is trivial to do so given access to the seed value. And yet, RSA's last big security fuckup was because they weren't purging seed values for tokens sold to customers. And now it turns out that their software 'tokens' retain their seed values in local storage forever.
Way to let a desire for convenience drag defeat from the jaws of victory, guys.
Random Access on tapes makes using your HDD as RAM seem like fun; but contemporary tape drives are actually pretty damn fast. It may be necessary to flog the tape minions on occasion, in order to spur them to greater effort; but that isn't tape's fault...
Slashdot Mirror
Whether or not the entire broadcast is itself a copyrighted work, the copyrighted components from which it is assembled certainly are, so distribution of them without license would be legally sticky. If the entire broadcast is also copyrighted in itself, then you'd have two parties who could go after you for redistribution.
The alarming thing here is that Fox seems to be claiming that a totally distinct mechanism for modifying the end-user's experience of the broadcast somehow constitutes a violation of copyright. That (in addition to the clearly pernicious practical effects) would seem to open the door to absurdities like 'copyright infringement' that does not involve any copying(the machine-readable equivalent of 'skip from time w to time x and from time y to time z' is in no way even slightly like a copy of a television show...)
I very strongly doubt that this is relevant on the scale of recorded human history and naked-eye observation; but doing all that mass-energy conversion and indiscriminate radiating must be slowly changing the sun's size, with some sort of balance between loss of mass and thermal expansion or contraction.
I'm told that the 'expands and engulfs the inner planets' stage will be dramatic; but is the expectation before that event a very, very gradual shrinking or something more complex?
It isn't really a question of whether the pacific rim ODMs will be manufacturing the gear. It's just a question of whether HP and Dell will be providing case badges and customer support or not...
Foxconn, among others, already handles a nontrivial amount of manufacturing for HP, not sure about Dell. The open question appears to be whether large operators like Rackspace will find it economically viable to handle system integration for themselves, in addition to operations, or whether existing systems integrators will continue to smooth over the rough edges of the ODM side and serve as the final vendor.
Honestly, I don't really care about the TV issue one way or the other; but the potential precedent is ugly.
If Dish's plan were to tape the broadcasts, chop out the chaff, and send you the final cut, that'd be a clear-cut case of a copyright infringing unauthorized derivative work.
However, their actual implementation, as best I've been able to tell, doesn't modify the copyrighted source material at all, it just adds specific automated behavior to the playback device. If that is 'copyright infringement' then virtually anything a playback device might choose to get fancy about is subject to the veto of team content. Automatic volume reduction on your music when you get a phone call? Sure. Replaygain volume normalization? Sure. Stretching or letterboxing to put 4:3 on 16:9 or vice-versa? Why certainly. Applying a custom CSS stylesheet to a website against the operator's wishes? You bet.
Yes, it may well happen to be true that OTA broadcasts aren't going to be helped by easy commercial skipping; but something isn't 'copyright infringement' merely because it happens to be bad for the checkbooks of people who hold copyrights. It also has to, y'know, infringe. In this case, if the definition of 'infringement' is stretched far enough to save our poor, beleaguered, broadcasters it is stretched far enough to allow near-total control over any device that handles rendering of copyrighted material, which is virtually anything.
Compared to that, letting all of broadcast TV burn looks like a fantastic idea, even if you are otherwise sympathetic to it...
Your 'peak hatred' attitude is disguistingly defeatist.
Hate player, the game, the phrase 'don't hate the player, hate the game' and anybody who uses that phrase. And you'll still have plenty to go around!
I'd suspect comparative advantage in action: These were phone scammers. The techie scammers are out there dumping drive-by downloads and building attack toolkits for sale. The less technical ones are falling back on their people skills and doing social engineering attacks...
I suspect that NASA isn't too worried about anybody staying on the moon long enough to evade them...
Since we are talking about implementing 6502s in questionably efficient ways, it seems like a good time to plug http://visual6502.org/. Efficient? No. Logic-accurate emulation of a 6502 implemented in javascript based entirely on photographs of a decapped 6502 die? Fuck Yeah.
My impression of the metagame that is Minecraft is that doing things the hard and/or rube-goldberg way is part of the charm. There is some reason why people are trying to build ALUs in crap redstone logic rather than just alt-tabbing to the logic circuit simulator of their choice(or a VM, or an emulator of some popular retro architecture).
Given that, at what point do mods that improve minecraft's program-ability go too far and turn it from a perverse simulation game of enormous popularity into a really dreadful IDE?
It could also be construed to cover virtually all protocols and file formats, as well, since those are descriptions of the 'interface' by which an application can interact with another system or data storage structure in a compatible way. You'd basically end up in a situation where interoperability would be possible only at the pleasure of the original vendor for the duration of an entire copyright term. That would be pretty dramatic.
That's certainly true enough, even aside from security, the sheer logistics of networking every little widget would be ugly. I was(perhaps incorrectly) assuming that since the machine in TFA's timestamp had entered the patient's EMR that it had been collected electronically. If a human read it out and recorded it, the solution would likely involve them sanity checking the instrument's present time when reading it, rather than adding complexity to the instrument after the fact.
If the APIs turn out to be non-copyrightable, does this mean we can really all enjoy/suffer Java for free?
It's a great deal more important than that: If APIs are copyrightable, API-compatible implementations of anything without that thing's blessing would be on legally shaky ground. I'll leave imagining the technology world in an alternate universe where IBM simply sued Compaq for producing an API-compatible BIOS to the reader; but that's the sort of magnitude we are talking here...
The "atomic" clocks that merely sync to the NIST radio timebase are toys; but you can get perfectly real atomic clocks for (relatively) small money. I haven't been comparison shopping or anything recently; but the 5071a provided a handy rack-mount caesium frequency reference for ~$50,000 back when Agilent sold them. Compared to the rest of the cost of getting an hospital-wide EMR system and a whole bunch of life critical gear from several dozen vendors chatting amicably, the timebase will count as a pleasant break...
I assume that the continued demand for timing-critical components in contemporary cell networks has increased volume and miniaturization in the market since then.
Given that it isn't too likely to matter within nanoseconds when exactly Joe Patient was admitted, even an only modestly accurate RTC would likely do the job, so long as all the devices in the building were listening to it. GPS would be a dirt cheap way of keeping the master source from drifting excessively over time, and in the short term even the resolution limits of a modest quartz oscillator wouldn't really be a big deal. Outside of truly dreadful stuff, inaccuracies are a big issue when you have multiple clocks that are never checked against each other and run independently long enough to drift quite far from one another.
You could do an implementation of NTP on a closed network, with a local time source(compared to the rest of a hospital, an OK atomic clock doesn't cost that much, and a GPS timebase could be lost in a rounding error) with devices flagging anomalies in the NTP source and falling back on local quartz oscillators if needed.
It'd be more expensive than just having IT bring a patch cable; but there isn't anything about "NTP" that requires putting gramps' pacemaker on the internet...
Siri, Siri, give me your answer do...
My impression is that IBM is marketing Watson as 'basically a super computer version of Siri that the customer pays IBM old-school-mainframe money for the privilege of keeping on-site'...
Whether the sort of banal shit that Siri gets asked to handle most of the time is actually a risk or not, it does seem fairly likely that some level of mining and 'monetization' is being done, same as other search mechanisms(and even if it isn't now, disk is cheap and EULAs are flexible, so that could change retroactively).
Realistically(especially once you tie the user to a more-or-less not-spoofed-in-practice phone UUID, as Siri does), any of the contemporary search mechanisms do constitute a pretty significant 'side channel' into the user's activities, interests, and so forth. Their popularity suggests that most people don't know or don't care, and(so far, to the extent publicly known) their operators have confined themselves to generic advertising and rounding up the occasional dissident(rather than, say, attempting algorithmic insider trading based on analysis of search queries coming from different companies IP blocks....); but the theoretical capability can't be dismissed.
So, broadly, IBM's position is not false, even if it isn't clear whether it is operationally true anywhere. More narrowly, in terms of IBM's interests, a bunch of operators providing natural-language expert systems on cheap commodity gear paid for by advertising isn't clearly helpful to IBM's business model. A bunch of paranoid C-levels buying in-house IBM solutions, securely humming away on IBM iron behind locked doors and a legion of IBM integration consultants, on the other hand...
There are arguably two categories of biblical pricing:
In the "The laborer is worthy of his hire" camp, you have the pretty-much-cost-of-printing-and-distribution prints of KJV and other out-of-copyright versions, along with moderately expensive editions of newer translations and revisions and slightly more expensive still 'critical editions' that are either a classic translation with a heavy addition of new marginal notes, explanatory sections, essays, etc. or a revised translation with the same.
In the "Yeah, the seller is probably an unscruplous weasel; but WTF is wrong with the buyer?" camp, are the vanity-printed and overpriced versions of cheap or free translations and(most horrible of all) the assorted commercial, political, and celebrity tie-in versions. If, for example, you find yourself purchasing The Holy Bible: Stock Car Racing Edition there are no words...
This guy Sells SAP how much more revenge upon the world could you possibly desire?
Didn't the executives at 'Premier Election Systems' meet in prison?
What is surprising is not that he's a kleptomaniac; but that he's such a bad kleptomaniac(or, even more oddly, he brings a degree of technical skill, creating his own barcodes, to a typically downmarket form of shoplifting, normally accomplished just by sticker-swapping, but doesn't actually improve the rate of return notably...)
It's like discovering that some sleazy commodities speculator is breaking into foreclosed houses to steal copper in his nights and weekends. Sure, it isn't a surprise that a commodities trader might have a questionably ethical relationship with metals prices; but it is a surprise to find him getting his hands dirty with a sideline in blue-collar crime.
Surely VP of SAP doesn't need to be doing that?
Some sort of mental illness of thrill-seeking?
All part of an elaborate plot to sell Target some sort of heuristic-theft-detection ERP module that slides 'seamlessly' into a SAP implementation and absolutely nowhere else...
In all seriousness, of course, people who commit crimes despite having no reasonable incentive to do so ($30k isn't peanuts; but in $/hour plus legal exposure, how well could box-at-a-time retail fraud have really stacked up compared to just staying a little later at the office when you are a VP?) are really ones to be watched. People who merely want the good things money can buy are comparatively easy to satisfy. People who want money per se are always more expensive than you can afford...
The law does not, apparently, require that takedown demands have a name attached. Clearly, the cyberbullies will give up in abject defeat in no time...
Without the GNU userland it's a consumer toy.
Even if one accepts it purely as an android box, what would possess them to use 2.3, rather than ICS which isn't a total mess on larger screens?
My understanding is that the two schemes are the same. The software version is just the cheap-n-lazy implementation for people who don't want to deal with airgapped hardware tokens.
Honestly, what makes me nervous about this is not the fact that, shocking!, software can be reverse engineered; but that RSA seems to mix a disconcerting amount of laziness and hubris in with their competent math.
As best we currently know, it is Not Possible to deduce subsequent token outputs merely given access to previous token outputs. However, it is trivial to do so given access to the seed value. And yet, RSA's last big security fuckup was because they weren't purging seed values for tokens sold to customers. And now it turns out that their software 'tokens' retain their seed values in local storage forever.
Way to let a desire for convenience drag defeat from the jaws of victory, guys.
Random Access on tapes makes using your HDD as RAM seem like fun; but contemporary tape drives are actually pretty damn fast. It may be necessary to flog the tape minions on occasion, in order to spur them to greater effort; but that isn't tape's fault...