An Update On The Pretty Crummy Supreme Court Term So Far On Issues We Care About

from the bad-beginnings dept

As the Senate hearings continue over what the future United States Supreme Court may do, it’s worth taking a moment to talk about what the current Court has already just done. The RBG-less Supreme Court is now back in session, and in view of the actions it’s taken in at least four separate cases, it has not been an auspicious beginning.

Even some of the best news still managed to be awful. For instance, cert was denied the Enigma Software v. Malwarebytes case. Denial is bad news because it leaves a terrible Ninth Circuit Section 230 decision on the books. On the other hand, having it denied may have dodged a bullet. Section 230 is already in the cross-hairs of Congress and the Executive Branch; inviting the Supreme Court to go to town on it too seemed like a risky proposition, and Justice Thomas’s unprompted dissent ripping Section 230 jurisprudence to shreds makes clear how much damage the Court could do to this critically important law if it took on this case.

And the risk of cert being granted here just might not have been worth it. For one thing, the case may continue. The Ninth Circuit had overturned the original granting of defendant Malwarebytes’ motion to dismiss, which sent the case back to the district court. Which means there could be another opportunity at some point later in the litigation for Malwarebytes to challenge the lousy reasoning the Ninth Circuit employed to revive the case. Of course, it’s possible that the parties might settle and leave the Ninth Circuit decision on the books, unchallenged. However, even if that happens, it’s a precedent already called into question by the more recent Supreme Court decision in Bostock v. Clayton County, Ga.. So it’s not great that future defendants will have to argue around the Ninth Circuit’s ruling, and by no means a certainty that the Bostock statutory construction argument would prevail, but at least there is something of substance to enable future defendants to make a good run at it.

Meanwhile, at least two other cert denials left us with even more bad news. One of these cases was Austin v. Illinois. Supreme Court review was sought after the Illinois Supreme Court left in place Illinois’s revenge porn law. As we pointed out at the time ? and the lower court in Illinois had recognized ? the Illinois revenge porn law is not a content neutral law, and as such it’s also not one sufficiently narrowly-tailored to meet the strict scrutiny the First Amendment requires. The law also doesn’t take the intent of the defendant into account. Unfortunately the Illinois Supreme Court did not seem bothered by these constitutional infirmities and upheld the law. We were hoping the United States Supreme Court would recognize the problems and grant review to address them ? but it didn’t. The law now remains on the books. And while it might indeed punish some of the deserving people that a constitutional revenge porn law would also catch, the problem with unconstitutional laws is that they also tend to catch other people too, even those whose speech should have been constitutionally protected.

The other cert denial of note is in G&M Realty v. Castillo. This cert petition sought review of the shockingly awful Second Circuit decision doubling-down on the terribly troubling EDNY decision awarding a multi-million dollar judgement ostensibly for violating the Visual Artists Rights Act (VARA). Never mind that, despite its apparent policy intent, VARA will actually lead to less public art and thus actually hurt artists, and ignore for the moment the short shrift the law gives to real property rights, these decisions managed to offend the constitution in several other outrageous ways. As we explained previously, there were multiple due process issues raised by how this particular case was adjudicated and the extraordinarily punitive penalty awarded against the defendant property owner, who had simply painted over his own building after the district court told him he could.

But the problem isn’t just that this particular case was a travesty; what this case also illustrated is how badly VARA offends both the First Amendment and the equal protection clause of the Constitution. It gratuitously awards an extra benefit to only certain expression based in some way on the content of that expression, which is not supposed to happen. (Put another way: it also denies a benefit to certain expression based on its content.) It is an utterly irredeemable law, and it is a great shame that the Supreme Court refused to grant review, not just to overturn the Second Circuit’s galling miscarriage of justice but to free us all from this law’s unconstitutional reach. Assuming Congress will refuse to repeal it, we will have to await a new victim of the law with the means and ability to challenge their injury before we will have any chance of being rid of it.

The reality is that Supreme Court jurisprudence is always at best a mixed bag when it comes to copyright. Earlier this year it did produce a good decision in Georgia v., but it missed a rare opportunity to restore sanity when it comes to the VARA amendment to the copyright statute. Now the question is whether it will restore sanity when it comes to how copyright in software works.

Oral argument at the Supreme Court was finally held last week in Google v. Oracle, after having been postponed from its original March hearing date due to the pandemic. It’s impossible to read the tealeaves and know how the court will rule, but it was hard to come away with too much optimism. What was concerning about the hearing is the undercurrent reflected in the justices’ questions that if the Court rules in Google’s favor it is somehow doing Google a favor and diminishing Oracle’s copyright. When in actuality it is Oracle’s copyright claim that is much broader than the law has ever allowed.

Copyrights have always (or at least until recently) been understood as limited monopolies granting their owners a limited set of exclusive rights for limited periods. Over the years these periods have become less limited, and interpretations of what these exclusive rights cover have tended to get broader. But the basic monopoly has still always been curtailed by the subject-matter limitation of Section 102(b) of the statute, which limits what can actually be subject to copyright in the first place, and fair use, which limits what uses of the work the copyright owner can exclude.

Both of these limitations are at issue before the Court: whether Oracle could even claim a copyright monopoly over the API in the first place, and, even if it could, whether that copyright could allow it to prevent other people from freely using the software’s API to make their own interoperable software, or if that would be fair use. The complication in this case is that there’s a special section in the copyright statute ? Section 117 ? that enunciates other exceptions to the reach of software copyright’s, due to their unique nature that makes them different than other sorts of copyrightable works. Oracle argued that this section exhaustively articulated the limits to its software copyright, but if this view were correct it would mean that software copyright would not be subject to any of the other limitations that have always applied to any other form of copyright.

Worse, not only would such a conclusion be bad policy that would deter future software development ? the sort of authorship a software copyright is supposed to incentivize ? but it would also constitute a significant change from the status quo.

The one bit of good news to report is that at least Justice Sotomayor recognized this issue. In particular she observed how out of step the Federal Circuit’s decisions had been from those of most other courts that had considered whether APIs could be subject to copyright. Their consensus had been no, and the freedom this view afforded software developers to make their software interoperable has enabled an entire industry to take root. In her questioning Justice Sotomayor appeared to recognize how badly it would threaten that industry if the Supreme Court adopted the Federal Circuit’s decisions in favor of Oracle’s copyright claims because of how much it represented a significant change in the previously understood reach of a software copyright.

JUSTICE SOTOMAYOR: Counsel, at the –in your beginning statement, you had the sky falling if we ruled in favor of Google. The problem with that argument for me is that it seems that since 1992, and Justice Kagan mentioned the case, the Second Circuit case, a Ninth Circuit case, an Eleventh Circuit case, a First Circuit case, that a basic principle has developed in the case law, up until the Federal Circuit’s decision. I know there was a Third Circuit decision earlier on in the 1980s. But the other circuits moved away from that. They and the entire computer world have not tried to analogize computer codes to other methods of expression because it’s sui generis. They’ve looked at its functions, and they’ve said the API, the Application Programming Interface, of which the declaring code is a part, is not copyrightable. Implementing codes are. And on that understanding, industries have built up around applications that know they can — they can copy only what’s necessary to run on the application, but they have to change everything else. That’s what Google did here. That’s why it took less than 1 percent of the Java code. So I guess that’s the way the world has run in every other system. Whether it’s Apple’s desktop or Amazon’s web services, everybody knows that APIs are not — declaring codes are not copyrightable. Implementing codes are. So please explain to me why we should now upend what the industry has viewed as the copyrightable elements and has declared that some are methods of operation and some are expressions. Why should we change that understanding? [transcript p. 52-53.]

The question is whether her skepticism about Oracle’s copyright claim is one that will be adopted by the rest of the justices, or whether sometime later this term we’ll be writing even more posts about how the Supreme Court has let everyone down on this front too.

Filed Under: , , , , , ,

Rate this comment as insightful
Rate this comment as funny
You have rated this comment as insightful
You have rated this comment as funny
Flag this comment as abusive/trolling/spam
You have flagged this comment
The first word has already been claimed
The last word has already been claimed
Insightful Lightbulb icon Funny Laughing icon Abusive/trolling/spam Flag icon Insightful badge Lightbulb icon Funny badge Laughing icon Comments icon

Comments on “An Update On The Pretty Crummy Supreme Court Term So Far On Issues We Care About”

Subscribe: RSS Leave a comment
This comment has been deemed insightful by the community.
TKnarr (profile) says:

When it comes to the Oracle case, I think Oracle better hope they lose their appeal. Remember that they published their own implementation of the AWS S3 APIs when they started offering their own S3-compatible service, so if they win against Google then Amazon can sue them on the same grounds and ask the judge to block any Oracle arguments that are contrary to the ruling against Google.

Thad (profile) says:

Re: Re:

I wouldn’t be surprised to see a non-precedential ruling in the Oracle case — either a tie (in which case the lower court ruling stands in its district, but sets no precedent in other districts) or a narrow ruling that only makes a determination on the specific details of the Oracle/Google case and makes no judgement on the broader issues raised in the case, because that’s the way the Roberts Court rolls.

This comment has been flagged by the community. Click here to show it.

F. U. Marole, volcano designer says:

Re: "their own implementation of the AWS S3 APIs"

is different! Google infringed copyright by NOT doing "their own", but simply COPYING the API text verbatim. — NOT the API, but the very text.

Also, who says Oracle can’t quickly and reasonably come to terms with Amazon if challenged? Just LICENSE it! — As GOOGLE should have done, instead of lawyering this out to the bitter end.

I hope that the end is BITTER indeed for Google.

Anonymous Coward says:

Re: Re: "their own implementation of the AWS S3 APIs"

There is this property of API’s, they define an interface used at a source code level, and therefore names of routines and types have to be the same, otherwise it is not compatible with the original API.

Also, just license it, if APIs are protected will not work, as that means a company enables competition, while refusing keep customer lock in.

This comment has been flagged by the community. Click here to show it.

F. U. Marole, volcano designer says:

GOOD that cert was denied the Enigma Software v. Malwarebytes.

VERY GOOD. You corporatists who believe The Public isn’t to be beneficiary of our own Laws at all times should read that decision and try to grasp how wrong you are.

Here the link again. Most important decision of last year. FULL of good quotes that exactly refute Masnick and this lawyer’s legalistic corporate-serving anti-Americanassertions.

This comment has been flagged by the community. Click here to show it.

F. U. Marole, volcano designer says:

Now, the "defendant property owner,...

"who had simply painted over his own building". — No, according to Maz’s report, you are whitewashing facts:

would be a few years before the time would be right. So in the meantime he let some graffiti artists use the building for their aerosol paintings.

I highlight the crucial word. "Letting" someone use "your" property makes it at least partly theirs. That’s nailed down in Common Law since forever: if you "let" someone improve your land which is just literally lying around (as by farming it, putting up a building), then they can come to OWN it. — So as usual, this lawyer fiend is arguing against ancient Common Law.

This comment has been flagged by the community. Click here to show it.

F. U. Marole, volcano designer says:

MORE assertions from the re-phrasing fiend:

Copyrights have always (or at least until recently) been understood as limited monopolies granting their owners a limited set of exclusive rights for limited periods.

FLATLY WRONG. Copyright/Patents were originally understood as Common Law Rights that existed before the Constitution, proved by the word "CopyRIGHT" itself, not "copyMONOPOLY", and that the gov’t is explicitly directed to "secure" those rights. If the right didn’t exist prior to the Constitution, it could not "secure" them, now could it?

2nd point: Copyrights are worth MORE these days with gadgets to easily reproduce and spread the content, NOT LESS. Therefore terms should be longer. I’m not harmed by FOREVER copyright, neither are you. — NO, the LACK of someone else’s work CANNOT harm you. Techdirt is just grifters and couch pumpkins who think they’re entitled to the work-products of the creative.

On the Oracle case: API is itself creative, often KEY, didn’t just arrange itself. Google could have licensed very cheaply, but its practice is to just take, lawyer up — and hire PR flacks like Maz and this shill to defend it. Leave the decision alone and BURN IT GOOD.

Bartonltu (user link) says:

hot russian mom

Worrying or feeling anxious a lot can be a sign of anxiousness disorder disorder

"Worry has taken my life. I have interested in everything and everybody, And am always preparing for the chance of things going wrong, Said Marla refined, A 55 year old publicist from are generally.

tips: What to know of the omicron variant of the coronavirusArrowRight

As a clinical psychologist in the Washington metropolitan area and an adjunct professor at Georgetown University, Excessive worry is very pressing psychological problems I see.

My patients watch work, working relationships, tiny, health and money. When worrying becomes determined, more durable and difficult to control, It can seriously affect daily living. And if the unrelenting worry is associated with anxiety symptoms such as irritability, Difficulty mentally focusing, Muscle rigidity, weakness and poor sleep, That person may be suffering from something called generalized anxiety disorder (GAD).

GAD belongs to the newer anxiety diagnoses, Appearing in the American Psychiatric Association’s manual of mental disorders now in 1980. Research and recognition of excessive worry and GAD have lagged behind other disorders that have been acknowledged longer, Such as gloominess, Or have captured the public’s eyesight more, Such as obsessive compulsive disorder and post traumatic stress disorder.

Worriers often suffer alone.

And many people suffer for an extended time.

Story continues below marketing

the way it feel to have GAD? One of my customers told me: "I am frustrated by my mind always moving 100 mph and going down a rabbit hole. Adults experience GAD once, Yet less than half get treatments. Many people with GAD also have other panic disorders and depression, As well as significant work and communal problems. GAD also represents a significant risk factor for heart problems.

Story continues below advertising campaign

But research shows that worrying does not help people better prepare for the future, Nor does it inoculate them from feeling bad when harmful events come to pass.

further, Worriers will be not good problem solvers. they often times procrastinate, hence, As well as having perfectionistic propensities, Has been linked to worse operation. When tackling a lot of worry, it is critical to acknowledge a person’s positive beliefs about it and a possible ambivalence toward change.

By transforming those beliefs, A path toward less stressful often can be cleared.

research conducted recently found that 91percent of worries held by people with GAD did not come true. Psychologists Daniel Gilbert from Harvard and Timothy Wilson from the University of Virginia have found that humans generally are bad at predicting how we will have future events. Their research indicates that people tend to overestimate the emotional effect of bad events and underestimate their ability to cope with those events.

"When negative outcomes work out as planned, almost everyone at least 70 percent handle it okay, Leahy said.

One way to minimize catastrophizing is by distinguishing between worrying and problem solving and then improving the latter.

Story continues below posting

whatever you have control over calls for problem solving. Worriers often view problems as intimidating, Doubt astounding to solve them and distrust potential solutions. knowing potential problems allows for early detection, Which allows worriers to tackle those problems before procrastination sets in. Basic problem fixing steps, Laid out in many worry self help books and cognitive behavior training protocols, Include defining very difficult, creating multiple solutions, scrapbook one, utilizing it and assessing the result.

Extensive studies suggest mindfulness training can help reduce problematic worry. in a study of 40 worriers presented at a recent conference, University of Pittsburgh professor Lauren Hallion and colleagues looked into the usefulness of various mindfulness approaches. They found how the "Focused desire" system, In which the students redirected attention from their worries to an external sound, minimize worrying the most. compared, Accepting thoughts without searching for change them helped less.

Engaging in regular guided mindfulness mediations more informally or practicing a mindful <a href=>dating Asian brides</a> way of being can also be beneficial.

Douglas Mennin, A tutor at Teachers College, Columbia or even who has researched worry, Said those with GAD are more fearful of and distressed by negative emotions. and so, he was quoted saying, "They tend to set up their lives in very predictable, Routinized and organized ways, Effectively the actual devil they know <worried> Over opening up to new alternatives,

Taking chances on new solutions might bring about more anxiety in the short run. But joy and vitality are also likely to increase as someone engages in a richer, More significant existence. Eventually, Worry and anxiety will reduce, on the. Try the same technique straight away where you feel an urge to ask your partner to ease your worries. If that sounds like a tall order, At least delay the behavior.

When sensing an urge to put things on a hard project at work, Take a first step right away. Or push yourself gently to do what your unreasonable worries tell you not to.

absolutely, techniques: The factors that turn worry into GAD and the strategies that can help alleviate them are part of a standard cognitive behavioral therapy approach. Following self-help books, motion pictures, And apps can benefit you.

Add Your Comment

Your email address will not be published. Required fields are marked *

Have a Techdirt Account? Sign in now. Want one? Register here

Comment Options:

Make this the or (get credits or sign in to see balance) what's this?

What's this?

Techdirt community members with Techdirt Credits can spotlight a comment as either the "First Word" or "Last Word" on a particular comment thread. Credits can be purchased at the Techdirt Insider Shop »

Follow Techdirt

Techdirt Daily Newsletter

Techdirt Deals
Techdirt Insider Discord
The latest chatter on the Techdirt Insider Discord channel...