What is jrank and why should anybody trust in law matters a site that confuses prosecution with persecution?
What is jrank and why should anybody trust in law matters a site that confuses prosecution with persecution?
Not that I would personally be offended by this post -nor am I a big fan of PC talk or safe spaces - but don't you think it's a bit funny to compare the monetary value of such a cross-cutting, personal and protected area of life to that of companies? How is this different from doing a similar statistic on races and comparing the value of "blackness" to the value of companies?
Have you tried KDE on Ubuntu? It's in such a sorry state that I consider it a wonder if it starts at all. Even trivially fixable bugs that make a package unusable for everybody go unheeded for the best part of a decade, which is presumably because Ubuntu is not run by that many people. That has been the Ubuntu way as long as I remember, but their KDE support has only gone from bad to nonexistent.
I installed (K)Ubuntu at work, and regret it. At home I run Debian unstable, which mostly just works, but breaks in all kinds of interesting ways once every two years or so. I cannot afford that at work, so I thought I'd give the hyped Ubuntu with its rolling releases a try. (Before you tell me I should try Debian stable, consider that Debian doesn't generally fix
For Ubuntu, presumably they will eventually get any KDE fixes from Debian, but for issues which for some reason happen to be present in Ubuntu but not in Debian, you are out of luck. Moreover, the KDE packages in Ubuntu seem to be essentially an entirely randomly timed snapshot of Debian unstable KDE packages. If KDE was entirely broken in Debian unstable at that point, then it will be in Ubuntu. Nobody cares.
That's a nice theory, but unfortunately it's wrong. For example, it has been established that compelling a suspect to give a handwriting sample (Schmerber v. California, 384 U.S. 757 (1966)) or to speak for voice identification (United States v. Dionisio, 410 U.S. 1 (1973)) does not violate the Fifth Amendment. Also permitted is compelling a suspect to sign a document that e.g. a foreign bank requires to release some information, although I'm too lazy to come up with a reference.
Yes, but the Federal Circuit's decision in this case is binding (only) in the 9th Circuit, I believe. You are right, though, that it will have influence in other circuits.
While I don't like the result, contrary to what others have written, I do not find the Federal Circuit's decision in this case to be hasty; on the contrary, I think it was very well reasoned. It's not for the courts to make law, but to interpret it. The decision made, in my opinion, well the case that this is what the law says and it is for the legislature to fix it if you want it fixed. I think the major problem is the completely broken legislature in the US. I think this probably also factored into why the Supreme Court did not grant certiorari (they also prefer to let issues percolate in lower courts before taking a suitable case).
The same cannot be said of Federal Circuit in may patent cases, though, where they seem to go to ridiculous lengths for the patent owner.
Well, not really. If the relevant facts are roughly as stated in the summary, it's indeed quite possible that the company will be forced to produce the source code or not rely on the evidence. However the only thing this means is that the defendant's paid experts get access to the source code under a strict protective order. They will then produce an expert report, which is the only thing anybody else will have access to, and even that may be sealed in whole or part if it would reveal, in the opinion of the judge (and often anyway unless the defendants object) significant trade secrets.
I think the two most realistic reasons to oppose are the costs of production and the possible loss of reputation if the evidence due to the inevitable criticism by opposing experts.
Some of the changes seem nice to me, some of them bad, and some neutral. However I use DejaVu regularly and some of these might be just a matter of getting used to. The biggest changes are to i and 0 (zero).
Here's an animated gif from Reddit: http://i.imgur.com/8SqL6mT.gif
The changes I like are to comma, underscore and minus.
I don't quite understand their changes to i and 0 (zero); do they solve some problem or do they supposedly just look better? I like DejaVu's zero more. It seems to me the new i is closer to l (lowercase L) than in DejaVu, and I cannot imagine DejaVu's i being confused with anything; however I think I could live with the new i. DejaVu's original parentheses are better too; the new ones almost look like if there's a space in ().
There seems to be a tiny kerning change to r. It makes some words look better, but others look worse. For example, I think "import" looks better in Hack, but "Keyboard" and "Interrupt" in DejaVu.
Then configure your miners to not accept these transactions.
Essentially the blockchain is exactly this: A way to record information in an unforgeable way, for a fee to the miner. Bitcoin works, and the only way it can work, is by being a system that behaves in a desired way when each player maximizes their own benefit. (To a small extent this can be affected in a centralized fashion because the community can develop the reference implementation to a desired direction, but that may or may not turn to be anathema and may or may not be a powerful enough tool.)
True, blockchain bloat causes problems, and it's a limited resource. The bitcoin solution is to sell the space to the highest bidder, because generally that maximizes the seller's benefit. In a sense, someone saying "that's not what the blockchain is for" is very similar to someone complaining that people are using lithium to make these stupid batteries, driving its price up, and "that's not what lithium is for".
Whether Bitcoin can survive all the technical challenges in the long term is not at all obvious. For all we know, it might be that the entire model is game-theoretically self-destructive if analyzed thoroughly enough. In fact, it has provided quite a few surprises where the incentives have turned out to be something different than anticipated, causing weird scenarios where e.g. in some situations it's advantageous for a miner to not immediately report a found block. So far none of these have been such that they would cause a death spiral, but that's far from a given. (Arvind Narayanan's blog posts on the topic are quite insightful; you might want to start from https://freedom-to-tinker.com/...).
Modules are coming in C++1z (the next revision of the language) most likely. That should solve many of the (real) problems with #includes.
I would do this at work for writing code, but alas, I currently work on Windows, and its support for portrait monitors, let alone landscape+portrait, is broken enough that the path of least pain is just to use landscape alone.
Specifically, there seems to be no way to get proper antialiased fonts in portrait mode. While ClearType makes Windows fonts quite tolerable, it doesn't (and arguably can't) work in portrait mode. Traditional antialiasing could work, but for some inexplicable reason Windows disables it for a large range of font sizes (something like 7..13).
Even worse, you can either use ClearType on all of your monitors or none of them. On portrait monitors Windows, when using ClearType, still renders the fonts as if it was landscape; the result is an incredibly blurry, colored mess. So if you have one portrait monitor, you have to tolerate aliased fonts on all of your displays.
I live in Finland. Why do you think there is "instability" in "having to form a coalition government"? To the contrary, I find it ensures that every vote counts to the extent it should. I also would be somewhat horrified if some party in my country got enough votes that it could form a government alone. It would have way too much power.
Let's consider a simple example, say we have parties A (40% of votes), B (35 %), C (15 %) and D (10 %).
To be stable a coalition should have around 60 % of members of parliament behind it. Hence, generally the interesting stable coalitions would be A+B, A+C+D and B+C+D.
Now this allows for the parties to haggle and trade on those issues they consider most important. For example, say that party B strongly wants to have higher taxes for fuel, while party A is strongly opposed to it. Party A somewhat prefers to impose fascism, while the other parties don't want that.
Now, say that parties C and D would, everything else being equal, not want higher taxes for fuel, but they don't consider it a core issue.
Now, let's say party C wants to safeguard some minority to a larger extent compared to the other parties, and none of the other parties is strongly opposed to that (but would not do it on their own). Party D has similarly some core issue of its own.
Now, A+B may not be a good coalition because their agendas are so contradictory that it's hard to figure out a good deal. A+C+D would be a viable coalition: A, C and D get their wish on fuel taxes, but A has to give up on fascism (which it mildly prefers) and accept the core agendas of C and D.
Also, B+C+D would be possible; probably B would have to make some concessions that A is not willing to make.
As you can see, every party has an incentive to offer to give up to an extent on their minor agendas in order to reach a consensus that is preferable to each of them. And this, I believe, makes everybody get a better deal.
Also, a two-party system (which is a natural result of your voting system) seems to be incredibly polarizing. See, you have two kinds of people, democrats and republicans, and it seems to me that the ones you don't belong to are those crazy lunatic bastards. I find it hard to imagine that is healthy for a population.
Current_Pending_Sector > 0 means you most likely already have unrecoverable errors on your disk, because otherwise the sectors would already have been remapped (and thus not pending). So if your CPS = 3, expect there to be at least three sectors which will return an uncorrectable error when read. Writing to these sectors will allow them to be remapped, which will decrease your CPS.
The only thing I don't quite understand is the possible motivation for XimpleWare to only sue for patent infringement, but not for copyright infringement. It's not like you have to choose between the two (you can have both), and anyway it seems that a copyright claim would be quite strong.
Maybe it's just to keep the lawsuit more contained and therefore save in attorney's fees and costs? On the other hand it seems to me that only claiming patent infringement encourages the defendants to challenge the validity of the patents (which are anyway questionable after Bilski and Alice Corp), while they would have much more incentive to settle if there also was a copyright claim that they had little hope of winning.
Whether the access is gained by the same way or a different way from how a copyright owner would do it is not material to the law; the authorization of the copyright owner is the defining criterion. The law defines circumvention thus:
to "circumvent a technological measure" means to descramble a scrambled work, to decrypt an encrypted work, or otherwise to avoid, bypass, remove, deactivate, or impair a technological measure, without the authority of the copyright owner'
For example, most non-authorized decryption would quite obviously be done in the same way as a copyright owner authorized device would do it. This would not make it not circumvention within the meaning of the law; the definition of circumvention is quite broad and essentially focuses on circumventing the requirement for authorization.
A mechanism doesn't need to prevent copying in order to qualify for DMCA's anticircumvention protections; it only needs to control access to a work. That's why you specifically need an exception for phones, among other things, even if phone unlocking does not let you copy the phone or its software.
"No person shall circumvent a technological measure that effectively controls access to a work protected under [the Copyright Law]".
You would be right that this does not qualify as a DMCA takedown request. In this case that doesn't matter very much though, because the letter was sent to the publisher of the article, not only to a mere carrier of the article (like an ISP).
Normally carriers are not liable for what their customers do, unless they have sufficient (in legal terms, actual or constructive) knowledge of the infringing activity. The idea behind DMCA takedown requests is that by sending a certain formal request to an ISP, where you among other things must allege in good faith that your copyrights are being infringed, you put the ISP formally on notice that certain activity is infringing and thereby oblige the ISP to provisionally remove the content pending a counter-notice from the poster of the content. An ISP still has the option to not remove the content, but in that case it assumes liability if it turns out the content was in fact infringing. Significantly, sending a formal DMCA takedown request to an ISP has three special effects compared to sending a free-form cease and desist letter:
1) It puts the ISP under a threat of liability if it does not remove the content;
2) It absolves the ISP from liability towards the customer for removing the content;
3) It makes the sender of the takedown notice liable for damages and attorney's fees for knowingly materially misrepresenting facts in the notice.
So when sending a notice to an ISP (party other than who posted the information), it makes sense to send a DMCA notice, because the party has less incentive to act on free-form requests and because it can actually incur liability if it does. Thus many ISPs routinely disregard non-DMCA takedown requests.
When sending a notice to someone who actually posted the allegedly infringing content, it makes less sense to send a DMCA takedown request. The recipient is liable in any case, and sending the notice puts you in a disadvantage by making it more likely that you are liable for damages and attorney's fees.
I speculate Tektronix's challenge would most likely fail in this case rather because the information posted is not "any technology, product, service, device, component, or part thereof" that is primarily designed to circumvent a technical measure that effectively controls access to a protected work. (It certainly is primarily designed to circumvent, but it doesn't fall into any of the enumerated categories of technology, product, service, device or component.)
One good suit is worth a thousand resumes.