Hacker News new | ask | show | jobs
by JeremyNT 100 days ago
I'm not sure this is really true, since copyright applies to distribution.

If you have a substantial amount of backend code (as with most SaaS projects) you're never actually distributing the code, and copyright is never at play. Computer generated artifacts are already in this boat and are protected by virtue of being trade secrets not by copyright.

This could maybe be true of shipping javascript to the browser, which presumably is not going to qualify as a trande secret, but I don't think that's where most companies derive value.

2 comments

The idea that copyright applies solely to distribution is a popular myth, but it has no support in the actual copyright law. The core exclusive rights in copyright are (in the US, 17 USC § 106):

---

(1) to reproduce the copyrighted work in copies or phonorecords;

(2) to prepare derivative works based upon the copyrighted work;

(3) to distribute copies or phonorecords of the copyrighted work to the public by sale or other transfer of ownership, or by rental, lease, or lending;

(4) in the case of literary, musical, dramatic, and choreographic works, pantomimes, and motion pictures and other audiovisual works, to perform the copyrighted work publicly;

(5) in the case of literary, musical, dramatic, and choreographic works, pantomimes, and pictorial, graphic, or sculptural works, including the individual images of a motion picture or other audiovisual work, to display the copyrighted work publicly; and

(6) in the case of sound recordings, to perform the copyrighted work publicly by means of a digital audio transmission.

---

OTOH, distributing copies created in violation of copyright is a good way to cause legally-cognizable harms to the copyright holder that will increase the potential damage award when you are found liable for copyright infringement, and it also makes it much more likely that someone will notice the infringement in the first place. But its not where the law, on its own terms, begins to apply. Doing any of those without permission (unless it falls into one of the exceptions to copyright protection, like fair use) is a violation of copyright.

>I'm not sure this is really true, since copyright applies to distribution.

Do you mean that a work has to be published prior to registration? What do you mean by "copyright applies to distribution"?

The idea of copyright is to prohibit unauthorized use and reproduction, but none of this actually happens with a proprietary software SaaS backend. You don't actually give anybody the code - they connect to the service.

Access to the service is already governed by computer access laws, which don't depend on copyright. And if you never intentionally distributed your code outside of your org, you can call it a trade secret and nobody else has any legitimate right to access it - whether or not it is copyrightable.

There are other things that aren't copyrightable that are trade secrets already. This would be true of any kind of automated data collection for example. You couldn't copyright it but you can call it a trade secret.

And for any of that stuff, if you want to share it and limit distribution, you just have whoever wants access explicitly agree to be bound by contract law.

>The idea of copyright is to prohibit unauthorized use and reproduction, but none of this actually happens with a proprietary software SaaS backend. You don't actually give anybody the code - they connect to the service.

The point isn't that you have to give it to people, but okay?

>Access to the service is already governed by computer access laws, which don't depend on copyright

Yeah, copyright doesn't control everything, and?

>There are other things that aren't copyrightable that are trade secrets already. This would be true of any kind of automated data collection for example. You couldn't copyright it but you can call it a trade secret.

Okay?

>And for any of that stuff, if you want to share it and limit distribution, you just have whoever wants access explicitly agree to be bound by contract law.

Your point being? You're just rambling assumptions about copyright and other things, which don't even track the actual law.

> Your point being? You're just rambling assumptions about copyright and other things, which don't even track the actual law.

I'm replying to the post that claimed:

> If that’s how the court interpreted it, then the software industry is hosed, since that’d mean none of the generated code running in production right now is under any sort of copyright or otherwise protection, lol.

There is in fact "otherwise protection" for the software industry by... not distributing the code. They don't need copyright over the generated code if they vibe code a SaaS backend. Whether there's copyright or not is irrelevant for the business model.

Copyright is the strongest legal protection available. It does not have a state of mind element. Breach of contract is much more complicated and context-dependent.

>There is in fact "otherwise protection" for the software industry by... not distributing the code.

Copyright protects against reverse engineering in some circumstances, for example.

>Whether there's copyright or not is irrelevant for the business model.

Yeah, I'm going to continue to disagree with you as I'm actually a litigator.

> Yeah, I'm going to continue to disagree with you as I'm actually a litigator.

OK, can you explain to me why this is a disaster for a vibe-coded SaaS? Why are computer access and/or contract laws insufficient and why would a vibe-coded backend be a huge risk?

I really don't understand where copyright on the code itself is necessary to protect these business models, and hopefully you can help fill the gaps.