... FWIW, though, the word in this case is "mugging" - theft by violence or the threat of violence. In the actual scenario at hand, there is no threat of violence, only the use of deception, so "fraud" is correct.
No, you didn't. Read your own comment more carefully. You said nothing about "threatening to shoot".
However: threatening to shoot a robber unless he leaves or surrenders would not be wrong. Threatening to shoot a robber unless he gives you his wallet would be, though I'm not sure that "fraud" is the correct word. Lousy analogy really, since it would be equally wrong whether or not you in fact had the gun.
But the lie *is* what leads to them getting the payment! (As demonstrated by the observation that an innocent victim is just as likely to pay up as a guilty one.)
I haven't researched this, but it is my understanding that the ISPs just have to forward the notice to the customer; at that point, at least, they don't have to give the complainant the customer's details. (Similar to the system here in NZ.)
Once again, though, you're assuming (against all evidence) that the purpose of these notices is in fact to suppress illegal activity, rather than to line the pockets of the mobster, er, "copyright holder". The business model is based on the "voluntary" fines, not on the original content.
It might be legal, though I'm unconvinced. It is definitely unethical, and it *should* be illegal.
Keep in mind that the only possible justification for copyright's existence is that, on the whole, it benefits society. Every time it is abused, it tips the balance a little more. I'm no longer certain that it *is* a net benefit to society; we may be better off without it.
But they're not trying to suppress copyright infringement. They're trying to get people to send them money. (Whether those people actually committed copyright infringement is a moot point; this sort of extortion works just as well either way.)
That's a theoretical analysis, not an experimental measurement, and is likely to be particularly dubious since we don't have a working theory for quantized general relativity yet. Interesting, but the phrase "does indeed" in the summary is a significant overstatement.
If you read the actual article (and perhaps some of his replies in the comments) you'll find he isn't really saying "never", he's talking about the short to medium term: the next few decades. And the main thrust of his argument depends on post-9/11 security measures rather than overall pricing. That won't last forever either... or at least I hope not... but it probably won't change much in that timeframe.
Washington State is part of the US, isn't it? (According to Wikipedia, anyway.) So I would expect the phrase "US government" to include the government of Washington State, along with all other governments within the US. Do you really use it only to describe the federal government? What do you say instead when you mean the federal government *and* the government of the States and other territories collectively?
No, the security bulletin is very clear that the vulnerability doesn't affect client versions of Windows. The patch has been made available anyway only as a defense in depth precaution.
If you look at the "Affected Software" table, you will note that the "Maximum Security Impact" is "None" for client versions.
(OK, I guess it depends on what you mean by "affect". But the upshot is that you only need to patch servers - more specifically DCs - now, everything else can wait and be done with next month's updates.)
Hmmm. Good points. Well, I don't suppose it matters to me any more, it's been years since I wrote anything in Java. (It was a major pain at the time, though; I had a small but significant investment in Java code, and I pretty much had to abandon it. At the time, at least, Microsoft's Java was the only one that produced executables that would just run without needing something else installed first.)
Very cool technically speaking, and good for system designers... it will, however, make it that much harder to comparison shop, if the same CPU has a different speed depending on how it's wired up.
Slashdot Mirror
"Why is it OK to shoot him but not OK to demand his wallet?" - are you kidding me?
Sorry, but if your grasp of ethics is really that poor, there really isn't any point in further discussion.
No, you didn't. Read your own comment more carefully. You said nothing about "threatening to shoot".
However: threatening to shoot a robber unless he leaves or surrenders would not be wrong. Threatening to shoot a robber unless he gives you his wallet would be, though I'm not sure that "fraud" is the correct word. Lousy analogy really, since it would be equally wrong whether or not you in fact had the gun.
But the lie *is* what leads to them getting the payment! (As demonstrated by the observation that an innocent victim is just as likely to pay up as a guilty one.)
They're not shooting the "robber", they're pulling a gun on him and demanding his wallet. I'm fairly sure that doesn't count as self-defense.
Also, you're confusing the porn company's business model with Rightscorp's business model.
Did you read the notice? They're demanding money. The lies are there in the hopes of making the victim scared enough to pay up.
I haven't researched this, but it is my understanding that the ISPs just have to forward the notice to the customer; at that point, at least, they don't have to give the complainant the customer's details. (Similar to the system here in NZ.)
Once again, though, you're assuming (against all evidence) that the purpose of these notices is in fact to suppress illegal activity, rather than to line the pockets of the mobster, er, "copyright holder". The business model is based on the "voluntary" fines, not on the original content.
It might be legal, though I'm unconvinced. It is definitely unethical, and it *should* be illegal.
Keep in mind that the only possible justification for copyright's existence is that, on the whole, it benefits society. Every time it is abused, it tips the balance a little more. I'm no longer certain that it *is* a net benefit to society; we may be better off without it.
But they're not trying to suppress copyright infringement. They're trying to get people to send them money. (Whether those people actually committed copyright infringement is a moot point; this sort of extortion works just as well either way.)
Then you're a bad person. Copyright infringement is far less serious than extortion.
That's a theoretical analysis, not an experimental measurement, and is likely to be particularly dubious since we don't have a working theory for quantized general relativity yet. Interesting, but the phrase "does indeed" in the summary is a significant overstatement.
If you read the actual article (and perhaps some of his replies in the comments) you'll find he isn't really saying "never", he's talking about the short to medium term: the next few decades. And the main thrust of his argument depends on post-9/11 security measures rather than overall pricing. That won't last forever either ... or at least I hope not ... but it probably won't change much in that timeframe.
Huh? Who said anything about federal law?
Washington State is part of the US, isn't it? (According to Wikipedia, anyway.) So I would expect the phrase "US government" to include the government of Washington State, along with all other governments within the US. Do you really use it only to describe the federal government? What do you say instead when you mean the federal government *and* the government of the States and other territories collectively?
That they can't change the law?
Does that include the security guards?
There's a bit more information available now:
http://blogs.technet.com/b/srd...
An elevation of privilege affecting the entire domain is certainly critical, particularly when it's already being used in attacks.
This means that if the attacker has control of one machine in the domain, he or she can take control of every other machine, including the servers.
No, the security bulletin is very clear that the vulnerability doesn't affect client versions of Windows. The patch has been made available anyway only as a defense in depth precaution.
If you look at the "Affected Software" table, you will note that the "Maximum Security Impact" is "None" for client versions.
(OK, I guess it depends on what you mean by "affect". But the upshot is that you only need to patch servers - more specifically DCs - now, everything else can wait and be done with next month's updates.)
Hmmm. Good points. Well, I don't suppose it matters to me any more, it's been years since I wrote anything in Java. (It was a major pain at the time, though; I had a small but significant investment in Java code, and I pretty much had to abandon it. At the time, at least, Microsoft's Java was the only one that produced executables that would just run without needing something else installed first.)
(If Google wins, does that mean Microsoft can put Java back into Windows again?)
Very cool technically speaking, and good for system designers ... it will, however, make it that much harder to comparison shop, if the same CPU has a different speed depending on how it's wired up.