Reading publicly-posted comments is not a problem. At least, not to me. (I do know some thickies that are shocked, SHOCKED, that someone besides their BFFs can read their social networking crap.) Anyways, sure, public posting is public. Even lolcat knows that.
But agencies of state power reading, aggregating, correlating, and scoring... drawing secret conclusions based on hidden agendas and closed criteria... that's disturbing. Shades of J. Edgar Hoover's secret file cabinet and COINTELPRO and the basement of Stasi HQ.
This sounds naive, but on principle this should be opt-in only. If this were for marketing purposes, it certainly would be. But for stuff which actually matters (life, liberty, et al.), it's beginning to look like non-participation is the only opt-out. And the chilling effect is as effective as any active anti-dissent measure.
And, if those Ethernet controller implementations didn't predate the 1994 patent, they don't count as prior art. Instead, they are either licensed applications of the patent, or unlicensed infringements.
Until someone finds prior art to smack the patent down.
I don't know. It seems around here that "common implementation" is equivalent to "prior implementation" in the minds of slashbots. Sorry. Even if every doohickey in the industry uses the technology described in the patent, they can all be infringers if they don't predate the patent and the patent survives administrative and judicial review. "Everybody is doing it" is not a patent infringement defense; it just means the patent holder (patent troll, if applicable) will be very busy negotiating licenses or suing infringers.
And before someone raises the inevitable "but they need to defend that patent immediately, or else they lose it".... sorry, that's trademarks, not patents. One of the thorny issues of patents is the fact that they can lie in wait until someone infringes them, at which point Admiral Akbar yells "It's a TRAP" and the patent-holder sues the infringer into the Stone Age. (That's the "???" before "Profit!" in this scenario.)
Signal propagation in conductors is only a fraction of lightspeed.
This site, a cabling vendor, has a nice graph towards the middle of the page. Reading that graph tells me that the propagation delay of their twisted pair is 470 ns over a 100 m run.
Google calc tells me that that works out to 212,765,957 meters per second. Scorching, eh? But compared to lightspeed?
Oh, that's only 71% of the speed of light. OK, so, that's a bit slower. Based on simple RTT and the signal propagation speed difference, your 2.4 sec ping just went up to just over 4 seconds.
Yeah, ok, you were joking. And carbon nanotubule conductors may have a signal propagation speed higher than even virgin-copper oxygen-free 2-gauge Monster(tm) brand network cable. Or not. But even a superconductor, insulated with either vacuum or a dielectric insulator, has a signal propagation speed measured as a fraction of the speed of light. (I've heard.95c cited.)
At least in the U.S., law is set by judicial precedent as much as by legislation. Therefore, if a copyright holder wins a lawsuit, even when it greatly exceeds the scope (or even makes a travesty) of written legislation, the suit is supported by law, because the judgment makes new law. And therefore, a duck. No, wait. And therefore, not fraudulent.
In other words, if you can convince a jury, all bets are off. Before the law, a douchebag who wins is not a douchebag.
Come to think of it, "apg-get update" is mostly harmless, but I still wouldn't do it on a production server until the entire "upgrade" process is beaten thoroughly down on a test server.
IMHO, you shouldn't do anything with apt on a production server until you're sure you're not shooting yourself in the foot.
Possibly the "automatic unneeded package pruning". It could be dangerous if your custom apps don't specify their dependencies correctly (say, they rely on something that had been automatically installed by one of their other dependencies).
That's OK, that's the kind of thing which is easily caught in non-production test server evaluation of the config change.
You do non-production evaluation of config changes, don't you?
C'mon, no professional just pokes "apt-get update" into the root shell on a live production server. That's just asking for hilarity, fail, and unemployment.
so there's no excuse for MySpace not knowing who owns it.
Sure there is. The excuse is that under the safe-harbor provisions of DMCA, there's no obligation for a service provider to investigate or adjudicate the validity of a takedown claim; in fact, there's incentive not to, since resisting a takedown in any fashion (i.e., anything other than "expeditiously" "removing or denying access to" the alleged infringing material) may disqualify the hosting provider to safe harbor, making them liable along with the original uploader.
Hey. Show a little respect. A few of us are veterans and have fond memories of SOS. I don't want anyone besmirching the reputation of a Food that Fed Freedom by associating it with Lotus Notes in any form.
Not every implant surgery gets a return trip to claim the hardware back. My kid has a fair bit of titanium in his lower tibia and fibula from a closed (i.e., not compound) "sliding into base" accident 10 years ago; as far as I know, its' in there forever.
That said, if the implants were basically replaced slowly with bone, that would be better.
Somebody with an integrated NVidia GPU on the motherboard and an ATI vidcard in a PCI-X slot. The motherboard chip would normally just be sitting there sipping power and wasting board real estate; in theory, running PhysX on the otherwise idle mobo GPU would offload physics calculations from either the display adapter GPU (more frames per second) or the primary CPU cores (more frames per second).
But the interesting thing about US jurisprudence is that "settled law" almost never is. All it takes is a few groundbreaking court judgments to reverse decades of precedent.
Sometimes that's good (see the history of civil rights litigation and criminal cases); sometimes it can be bad.
I don't know if this is the beginning of the end of the first sale doctrine, but I suspect there will be a case which historians will look back on and label that way.
And no, I'm obviously not a lawyer. A student of history, yes.
Even with a degree of shared cultural heritage (such as a common religious holiday), soldiers will eventually resume trying to slaughter each other, because that's the primary* way out of the hell of war, win or lose.
*Yeah, "primary", not "only", regardless of what The Brass says. You could desert, but that's pretty traumatic. You could kill yourself, by your own hand or by "suicide by enemy action", but self-destruction is extreme. You could surrender, but a lot of peer pressure is on you to not weaken your team (element, platoon, etc.) by quitting, plus the uncertainties of being a POW in modern warfare.
Slashdot Mirror
Reading publicly-posted comments is not a problem. At least, not to me. (I do know some thickies that are shocked, SHOCKED, that someone besides their BFFs can read their social networking crap.) Anyways, sure, public posting is public. Even lolcat knows that.
But agencies of state power reading, aggregating, correlating, and scoring... drawing secret conclusions based on hidden agendas and closed criteria... that's disturbing. Shades of J. Edgar Hoover's secret file cabinet and COINTELPRO and the basement of Stasi HQ.
This sounds naive, but on principle this should be opt-in only. If this were for marketing purposes, it certainly would be. But for stuff which actually matters (life, liberty, et al.), it's beginning to look like non-participation is the only opt-out. And the chilling effect is as effective as any active anti-dissent measure.
And, if those Ethernet controller implementations didn't predate the 1994 patent, they don't count as prior art. Instead, they are either licensed applications of the patent, or unlicensed infringements.
Until someone finds prior art to smack the patent down.
I don't know. It seems around here that "common implementation" is equivalent to "prior implementation" in the minds of slashbots. Sorry. Even if every doohickey in the industry uses the technology described in the patent, they can all be infringers if they don't predate the patent and the patent survives administrative and judicial review. "Everybody is doing it" is not a patent infringement defense; it just means the patent holder (patent troll, if applicable) will be very busy negotiating licenses or suing infringers.
And before someone raises the inevitable "but they need to defend that patent immediately, or else they lose it".... sorry, that's trademarks, not patents. One of the thorny issues of patents is the fact that they can lie in wait until someone infringes them, at which point Admiral Akbar yells "It's a TRAP" and the patent-holder sues the infringer into the Stone Age. (That's the "???" before "Profit!" in this scenario.)
But, the difference is that Apple fanbois would willingly sign up to that or worse, as long as Saint Steve asked.
Well, maybe not Windows ME, but they did agree to Snow Leopard. That's in the same ballpark.
Yeah, you need $10 million to cover that. Only in USA.
Well, you need enough to hurt the plaintiff. You need enough to clearly and unambiguously convey the message "Never ever EVER do that again".
I don't think $10 million is going to be enough, but it's a good start.
BTW, your choice of emphasis in your quote of TFA is most peculiar. Was there a point you were trying to, but utterly failed to, make?
Wow. And you thought Li-Ion battery fires were bad. Wait until your iPhone 7GSqqX-aleph gets an antimatter containment failure.
sez "Much fear I sense in you. This trade I cannot allow you to execute."
I guess it's better than the Admiral Akbar model of trading.
Signal propagation in conductors is only a fraction of lightspeed.
This site, a cabling vendor, has a nice graph towards the middle of the page. Reading that graph tells me that the propagation delay of their twisted pair is 470 ns over a 100 m run.
Google calc tells me that that works out to 212,765,957 meters per second. Scorching, eh? But compared to lightspeed?
Again, let's ask Google calc
Oh, that's only 71% of the speed of light. OK, so, that's a bit slower. Based on simple RTT and the signal propagation speed difference, your 2.4 sec ping just went up to just over 4 seconds.
Yeah, ok, you were joking. And carbon nanotubule conductors may have a signal propagation speed higher than even virgin-copper oxygen-free 2-gauge Monster(tm) brand network cable. Or not. But even a superconductor, insulated with either vacuum or a dielectric insulator, has a signal propagation speed measured as a fraction of the speed of light. (I've heard .95c cited.)
Superconductors are used, in fact, as delay lines.
At least in the U.S., law is set by judicial precedent as much as by legislation. Therefore, if a copyright holder wins a lawsuit, even when it greatly exceeds the scope (or even makes a travesty) of written legislation, the suit is supported by law, because the judgment makes new law. And therefore, a duck. No, wait. And therefore, not fraudulent.
In other words, if you can convince a jury, all bets are off. Before the law, a douchebag who wins is not a douchebag.
Come to think of it, "apg-get update" is mostly harmless, but I still wouldn't do it on a production server until the entire "upgrade" process is beaten thoroughly down on a test server.
IMHO, you shouldn't do anything with apt on a production server until you're sure you're not shooting yourself in the foot.
Possibly the "automatic unneeded package pruning". It could be dangerous if your custom apps don't specify their dependencies correctly (say, they rely on something that had been automatically installed by one of their other dependencies).
That's OK, that's the kind of thing which is easily caught in non-production test server evaluation of the config change.
You do non-production evaluation of config changes, don't you?
C'mon, no professional just pokes "apt-get update" into the root shell on a live production server. That's just asking for hilarity, fail, and unemployment.
so there's no excuse for MySpace not knowing who owns it.
Sure there is. The excuse is that under the safe-harbor provisions of DMCA, there's no obligation for a service provider to investigate or adjudicate the validity of a takedown claim; in fact, there's incentive not to, since resisting a takedown in any fashion (i.e., anything other than "expeditiously" "removing or denying access to" the alleged infringing material) may disqualify the hosting provider to safe harbor, making them liable along with the original uploader.
Very good FAQ about DMCA takedown/putback issues.
It may be time-of-the-year related, but personally, I see a green pumpkin.
Kabocha! Yum!
Hey. Show a little respect. A few of us are veterans and have fond memories of SOS. I don't want anyone besmirching the reputation of a Food that Fed Freedom by associating it with Lotus Notes in any form.
The responsiveness and clarity of Notes plus the reliability of Web 2.0
Let me kill myself now. Please.
Not every implant surgery gets a return trip to claim the hardware back. My kid has a fair bit of titanium in his lower tibia and fibula from a closed (i.e., not compound) "sliding into base" accident 10 years ago; as far as I know, its' in there forever.
That said, if the implants were basically replaced slowly with bone, that would be better.
You have got to be some kind of crazy to say that.
NO KILL I
Somebody with an integrated NVidia GPU on the motherboard and an ATI vidcard in a PCI-X slot. The motherboard chip would normally just be sitting there sipping power and wasting board real estate; in theory, running PhysX on the otherwise idle mobo GPU would offload physics calculations from either the display adapter GPU (more frames per second) or the primary CPU cores (more frames per second).
satellite radar altimetry.
Of course, it's accidental radar altimetry, rather than a dedicated instrument. Neat hack.
And the slapper gets a running start of whatever distance it takes to get to maximum running speed.
But the interesting thing about US jurisprudence is that "settled law" almost never is. All it takes is a few groundbreaking court judgments to reverse decades of precedent.
Sometimes that's good (see the history of civil rights litigation and criminal cases); sometimes it can be bad.
I don't know if this is the beginning of the end of the first sale doctrine, but I suspect there will be a case which historians will look back on and label that way.
And no, I'm obviously not a lawyer. A student of history, yes.
The rules also apply, de facto, if you're too cowardly, stupid, or lazy to actually examine the take-down request and the subject matter in play.
Think of it as risk mitigation in the extreme.
Not just the American Civil War.
World War I, too.
Even with a degree of shared cultural heritage (such as a common religious holiday), soldiers will eventually resume trying to slaughter each other, because that's the primary* way out of the hell of war, win or lose.
*Yeah, "primary", not "only", regardless of what The Brass says. You could desert, but that's pretty traumatic. You could kill yourself, by your own hand or by "suicide by enemy action", but self-destruction is extreme. You could surrender, but a lot of peer pressure is on you to not weaken your team (element, platoon, etc.) by quitting, plus the uncertainties of being a POW in modern warfare.
of ganking.
I knew that gankers were compensating.
Gosh, get it right.
"I, for one, welcome our new Cyanogen without the Google applications overlords."