The tech community is rallying in an effort to convince the Supreme Court to review a federal court decision granting copyright protection to APIs (application programming interfaces.)

A few years ago, tech giant Oracle sued Google when Google’s engineers used Java APIs to build the Android operating system. Although Google designed its own original programs, it based those programs off of the original Java APIs so that independent developers could create apps and programs for use on Android phones.

Pause button. If everything I just said sounded like Greek, the Electronic Frontier Foundation explained in their press release about their request to SCOTUS how APIs work:

Generally speaking, APIs are specifications that allow programs to communicate with each other. So when you type a letter in a word processor, and hit the print command, you are using an API that lets the word processor talk to the printer driver, even though they were written by different people.

The brief explains that the freedom to re-implement and extend existing APIs has been the key to competition and progress in both hardware and software development. It made possible the emergence and success of many robust industries we now take for granted—for example, mainframes, PCs, and workstations/servers—by ensuring that competitors could challenge established players and advance the state of the art.

After Google released its Android OS, Oracle sued Google for patent and copyright infringement. A California judge rejected the claim, saying that an API is essentially a “process or method” that allows different computer programs to talk to one another. (Source code, on the other hand, is treated like a literary work and is covered under copyright laws.)

A federal circuit appeals court disagreed with the analysis and overturned the decision, instead holding that APIs are copyrightable, upending years of industry practice and sending the tech community into a frenzy.

Is this a niche issue? Yes. Is it an important niche issue? Absolutely. From the perspective of a computer scientist or developer, this decision threatens their very ability to create anything new:

“The Federal Circuit’s decision was wrong and dangerous for technological innovation,” EFF Intellectual Property Director Corynne McSherry said. “Excluding APIs from copyright protection has been essential to the development of modern computers and the Internet. The ruling is bad law, and bad policy.”

“For decades, computer scientists and the courts have all understood that copyright doesn’t protect APIs,” EFF Special Counsel Michael Barclay said. “We hope that the Supreme Court will review this case and reverse the Federal Circuit’s misguided opinion, which up-ended decades of industry practice and threatens the basic principles upon which our technology sector was built.”

Think of an API as a foundational building block. When you sit down to build something new, you have a choice: you can create your own building blocks that only your programs will understand, or you can use building blocks that are universally used and understood by many different builders. By using the universal building blocks, you ensure that other builders will be able to understand your work, learn from it, and build off of it. That’s innovation, right?

If the Supreme Court refuses to take this case up, those who own copyright on various APIs will be able to prevent developers from creating compatible programs. This means tools like Twitter, Facebook, and cloud computing services could be frozen in time unless the owners of the API give another entity permission to use the code from the original API implementation.

That’s not innovation, and it should worry you. March on, nerds—I’ll be right behind you.

h/t Computational Legal Studies