|
|
Log in / Subscribe / Register

Class action against GitHub Copilot

Class action against GitHub Copilot

Posted Nov 10, 2022 19:11 UTC (Thu) by bluca (subscriber, #118303)
In reply to: Class action against GitHub Copilot by Rigrig
Parent article: Class action against GitHub Copilot

Nah, that is called concern trolling or sealioning. Those are not real world use cases, they are fabricated for clickbait effect. Absolutely nobody who's working on something real goes around trying to recreate the inverse square root algorithm or things like that that have been doing the rounds.

What this is really used for in the real world is to take care of boilerplate and such.


to post comments

Class action against GitHub Copilot

Posted Nov 10, 2022 21:05 UTC (Thu) by ballombe (subscriber, #9523) [Link] (27 responses)

How do you know that ?

Class action against GitHub Copilot

Posted Nov 10, 2022 21:17 UTC (Thu) by bluca (subscriber, #118303) [Link] (26 responses)

I use it every day, and talk to other developers who use it every day. Do you?

Class action against GitHub Copilot

Posted Nov 11, 2022 9:51 UTC (Fri) by gspr (subscriber, #91542) [Link] (11 responses)

Someone has made a machine that outputs *potentially* copyright-infringing code. Whether or not it really is, is the core of the debate, and not something that's easy to answer. What I fail to understand is how "I and all my peers just use that machine to output non-copyrightable boilerplate" is any sort of excuse.

Class action against GitHub Copilot

Posted Nov 11, 2022 10:24 UTC (Fri) by bluca (subscriber, #118303) [Link] (10 responses)

Because it's not an excuse, it's explaining how this works in the real world, outside of clickbaity articles and copyright troll lawsuit fishing for money. Because this matters, a lot.
My smartphone camera can also *potentially" output copyright-infringing pictures. My mp3 player *potentially* plays copyrighted songs. And so on - these are tools, and their main intended and common use matters, and for alleged open source supporters to side with copyright maximalists and trolls looking for a quick payday is missing the point so much that it's not even fun anymore.

Copyright maximalism is bad for us. The only reason this gains any traction is because it's done by Microsoft, if Copilot had been built by Mozilla reactions would be quite different, and that's just sad and short-sighted.

Class action against GitHub Copilot

Posted Nov 11, 2022 11:11 UTC (Fri) by gspr (subscriber, #91542) [Link] (9 responses)

I think these analogies are terrible. Your camera and your music players are indeed tools that you can use to infringe on copyright. They didn't come to you in a state infringing on copyright. The claim about Copilot, however, is that it "contains" (for some value of contains) and produces copyrighted material.

Class action against GitHub Copilot

Posted Nov 11, 2022 11:47 UTC (Fri) by bluca (subscriber, #118303) [Link] (8 responses)

No, those analogies are perfectly adequate. Copilot does not contain any infringing material, it's not a repository. And you have to intentionally make it produce exact copies, with carefully selected inputs that you need to have pre-existing knowledge of, it does not happen randomly, it takes a lot of effort. So it's exactly like a camera or a music player, in that regard. It's the user intent that causes that behaviour, not the tool itself.

Class action against GitHub Copilot

Posted Nov 11, 2022 12:14 UTC (Fri) by gspr (subscriber, #91542) [Link] (7 responses)

> Copilot does not contain any infringing material

That's the question at the heart of the conundrum, and it's a very complex one. Sure, we can probably agree that Copilot does not contain bit-for-bit copies of copyrighted material. But that's not the bar. Distributing a lossily compressed copy of a copyrighted image without permission can still be infringement. On the other hand, distributing the average value of all the pixels in said image certainly is not. The spectrum in-between is where it gets hard, and this is (in my opinion) probably where Copilot and similar fall.

Class action against GitHub Copilot

Posted Nov 11, 2022 15:32 UTC (Fri) by Wol (subscriber, #4433) [Link]

As a completely different example, copying material as part of a lawsuit does not infringe copyright. I can copy a work, present it to court, and copyright cannot touch me.

But if somebody else then takes my work and publishes it in a newspaper, that's not a legal document. Me putting it in a legal document did not strip copyright, it just gave ME immunity. The publisher can still get done for it.

Cheers,
Wol

Class action against GitHub Copilot

Posted Nov 11, 2022 19:55 UTC (Fri) by bluca (subscriber, #118303) [Link] (5 responses)

Of course it is complicated, but the crux is that I don't see how this tool can be defined as something that distributed copies of anything. It is very obviously not built to pick existing snippets and shove them out of the door 1:1 to users. It's not how it works in the vast majority of cases, where it builds something adapted to the surrounding environment - which is what makes it so darn beautiful and useful to use. Then there are users who go out of their way to carefully construct a surrounding environment (=> input query) using their pre-existing knowledge to intentionally cause it to spit out pre-existing snippets in order to write clickbaity articles or, in this case, look for a quick payday.

Class action against GitHub Copilot

Posted Nov 12, 2022 15:24 UTC (Sat) by farnz (subscriber, #17727) [Link] (4 responses)

It can be defined as something that distributes copies of something in exactly the same way as a human engineer can be defined as someone who distributes copies of something.

If I have, in my notebooks, details of how to do something in kernel-dialect C, and I read a snippet of code from those details then adapt it to the codebase I'm working on, then I've distributed a copy of the snippet in my notebook. If the snippet in my notebook is not protected by copyright, then this is not an issue; if it is, then I've potentially infringed copyright by copying out that snippet and adapting it.

The same applies to Copilot - its model takes the place of the engineer's notebooks and knowledge of what they can find in their notebooks, and its output is potentially infringing in exactly the same way as a human engineer's output is potentially infringing, complete with fun questions around "non-literal copying".

Class action against GitHub Copilot

Posted Nov 17, 2022 13:16 UTC (Thu) by esemwy (guest, #83963) [Link] (3 responses)

A human engineer can be inspired by someone else’s code. An AI has no such ability. Computers memorize, and have rules. The fact that the AI is really complicated doesn’t change that. It’s more as if they obfuscated the source and are trying to pass it off as their own.

Class action against GitHub Copilot

Posted Nov 17, 2022 14:08 UTC (Thu) by farnz (subscriber, #17727) [Link] (2 responses)

You're getting into the philosophy of what it means to be human, and missing my point at the same time.

My point is simply that if a human can infringe while doing the same thing that Copilot does, then it's absurd to say that Copilot cannot infringe because it's an AI - rather, it's reasonable to say that Copilot's ability to infringe copyright is bounded on the lower end by the degree to which a human doing the same thing can infringe copyright.

I've also provided a sketch of how a human can infringe copyright, which I can expand upon if it's not clear; unless you can demonstrate that Copilot is incapable of doing what the human does to infringe, however, you can't then claim that Copilot can't infringe where a human can.

Class action against GitHub Copilot

Posted Nov 17, 2022 15:57 UTC (Thu) by esemwy (guest, #83963) [Link] (1 responses)

The distinction does make a difference in this case. If a human takes a snippet of code and copies it, only changing the identifiers, my understanding is that is still a violation of copyright, and a company can’t take code, compile it, and claim it’s not an infringement. Copilot seems more like the latter, where the former example would be the human analog.

Class action against GitHub Copilot

Posted Nov 17, 2022 17:10 UTC (Thu) by farnz (subscriber, #17727) [Link]

I'm not following your reasoning here - in what way should Copilot be permitted to do something that would make Microsoft liable for the infringement if an employee did it?

Remember that I'm setting a lower bound - "if Copilot was just a communication interface to a human being at Microsoft who looked at the context sent to and then responded with a code snippet, would Microsoft be liable?". My claim is that if Microsoft would be liable in this variant on Copilot, then Microsoft are also liable if Copilot is, in fact, an "AI" based around machine learning, but that this is a one-way inference - if Microsoft would not be liable if Copilot was a comms channel, this doesn't tell you anything about whether Microsoft are liable if Copilot is actually an AI.

To summarize: my reasoning is that "an AI did it, not a human" should never be a get-out clause - it can increase your liability beyond that you'd face if a human did it, but it can never decrease it.

Class action against GitHub Copilot

Posted Nov 11, 2022 11:06 UTC (Fri) by paulj (subscriber, #341) [Link] (10 responses)

For transparency, can you state if you have any relationships with either Microsoft or GitHub (I vaguely recall you have with MS, but ICBW)?

Class action against GitHub Copilot

Posted Nov 11, 2022 13:11 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link] (9 responses)

> For transparency, can you state if you have any relationships with either Microsoft or GitHub (I vaguely recall you have with MS, but ICBW)?

Bluca works for MS but is not involved with GitHub directly as I understand it. He has said before he doesn't think it is important to add such notes but I think the repeated level of participation in topics like these warrants one. It is a complex issue and it was clear from the beginning this is all going to end up in court(s). It may very well end with rulings that affect the future of such tools and even copyright in general. If you are going to come in strongly on one side (even if it happens to be coincidentally favorable to your employer which I can completely accept it is), other folks might want to take that into consideration when evaluating your opinion.

Class action against GitHub Copilot

Posted Nov 11, 2022 14:30 UTC (Fri) by bluca (subscriber, #118303) [Link] (4 responses)

Absolute drivel. This is the comments section of a news article, not a court room. Are you going to post your tax returns to show you haven't invested in any of the companies involved? No? Thought so. Wind yer heid in.

Class action against GitHub Copilot

Posted Nov 11, 2022 14:50 UTC (Fri) by paulj (subscriber, #341) [Link]

Aye right pal.

Class action against GitHub Copilot

Posted Nov 12, 2022 20:16 UTC (Sat) by k8to (guest, #15413) [Link]

Others seem to think it matters, myself included.

Class action against GitHub Copilot

Posted Nov 18, 2022 1:20 UTC (Fri) by jschrod (subscriber, #1646) [Link] (1 responses)

This is not drivel.

You are currently posting 20% of the comments on this article, without disclosing your affiliation.

I.e., you are a MS shill.

*plonk*

PS: I know a lot of folks who work at MS Research, and I'm grateful for the great work they are doing there. It is also obvious that there are some folks at MS who are doing very good work at the Linux kernel. But they are always open about their affiliation, even when commenting articles. And lwn.net is not some obscure Web site with an obscure community -- we are here at the heart of the Linux community that takes such issues seriously and discusses is with open visor.

PPS: For the record: I'm an owner of a company that is a MS partner, but my company has nothing to do with the Linux side of MS's business.

Class action against GitHub Copilot

Posted Dec 7, 2022 11:06 UTC (Wed) by nye (guest, #51576) [Link]

> I.e., you are a MS shill.
> *plonk*

This kind of ad hominem trolling has no place in LWN. Corbet, please for the love of god can we start seeing some temporary bans for repeat trolls like this?

Class action against GitHub Copilot

Posted Nov 11, 2022 17:52 UTC (Fri) by paulj (subscriber, #341) [Link] (3 responses)

Yes, bluca is very vocal on topics related to his (IIRC) employer MS. Hence why the association stuck in my mind.

It's almost impossible for such associations not to colour one's thinking at least a little. The enthusiasm shown for the debate by bluca is clear anyway.

Class action against GitHub Copilot

Posted Nov 11, 2022 19:47 UTC (Fri) by bluca (subscriber, #118303) [Link] (2 responses)

Except of course you say that as if you knew if for a fact, when it is very obviously factually incorrect, and one just has to go and see what my comments were for example on the whole secure-core-pc debacle to realise how nonsensical your proposition is. So you are misrepresenting reality either out of ignorance or malice. Either way, how about you stick to the facts of the matter and leave out the ad-hominems and doxxing?

Class action against GitHub Copilot

Posted Nov 14, 2022 10:29 UTC (Mon) by paulj (subscriber, #341) [Link]

Nothing in my comment was ad-hominem. It is widely recognised that people's associations - particularly any with tangible benefits - may at times colour their opinions of their associates, and even indirectly, friendly associates of their associates. It is a general human thing - not specific to you. It may or may not apply to you, but I - and others - would prefer to be aware of the association.

Nor did I "doxx" you. You acknowledged your employement with MS before here on LWN.

Class action against GitHub Copilot

Posted Nov 14, 2022 10:43 UTC (Mon) by LtWorf (subscriber, #124958) [Link]

> Either way, how about you stick to the facts of the matter and leave out the ad-hominems and doxxing?

Ok, here's some facts: at the moment of writing

your comments amount to the 22% of the comments

there are 40 usernames that commented, so you are clearly over represented

Class action against GitHub Copilot

Posted Nov 11, 2022 19:03 UTC (Fri) by ballombe (subscriber, #9523) [Link] (2 responses)

> I use it every day, and talk to other developers who use it every day.

Nice to know.

> Do you?
No, that is what I ask.

My issue is that there is no verifiable claim about the size of the AI model.
For all we know it can be in the petabyte size. The model could just return table of indices to a gigantic array of strings.

Github made everyone nervous by changing the TOS. They pay the price now.

Class action against GitHub Copilot

Posted Nov 11, 2022 19:34 UTC (Fri) by bluca (subscriber, #118303) [Link] (1 responses)

If it was, it wouldn't work how it does. It very clearly learns and adapts to the surrounding context - which is what makes it truly amazing to use to deal with boilerplate and repeated local patterns. I am a very lazy person, and it saves me some keystrokes when for example adding function-level unit tests - it's an automated copy-paste-search-replace that adapts to the current content. You couldn't do that with an index that returns pre-existing snippets.

Besides, some folks are reimplementing their own server + model, using the same client interface, and yes it's an actual AI model, not an index: https://github.com/moyix/fauxpilot

Class action against GitHub Copilot

Posted Nov 13, 2022 11:49 UTC (Sun) by ballombe (subscriber, #9523) [Link]

> If it was, it wouldn't work how it does. It very clearly learns and adapts to the surrounding context - which is what makes it truly amazing to use to deal with boilerplate and repeated local patterns. I am a very lazy person, and it saves me some keystrokes when for example adding function-level unit tests - it's an automated copy-paste-search-replace that adapts to the current content. You couldn't do that with an index that returns pre-existing snippets.

There would be two stages: first locate the relevant code snippet in the database, and then the
AI would post-process the snippet to adapt it to the context.

The second step is something that AI are well suited to do and nobody is claiming it is violating copyright, except
in so far that it is obfuscating the first stage.

The whole concept of using function name to infer their implementation requires some kind of storage, from purely information-theoretic consideration if only to conserve Kolmogorov complexity.

> Besides, some folks are reimplementing their own server + model, using the same client interface, and yes it's an actual AI model, not an index: https://github.com/moyix/fauxpilot

So even if copilot is shut down, you can go about your work by using fauxpilot ? Good!

Class action against GitHub Copilot

Posted Dec 16, 2022 7:45 UTC (Fri) by ssmith32 (subscriber, #72404) [Link] (1 responses)

Using someone else's boilerplate code is still a copyright violation.

Class action against GitHub Copilot

Posted Dec 18, 2022 2:25 UTC (Sun) by anselm (subscriber, #2796) [Link]

Using someone else's boilerplate code is still a copyright violation.

That would depend on the exact circumstances. In many jurisdictions, code must exhibit a certain minimal degree of creativity to be eligible for copyright. If the boilerplate code in question is a very obvious or indeed the only sensible way of achieving a certain result in the programming language (and just a hassle to type out), then it may not fall under copyright because it is not sufficiently creative to warrant protection.

In such cases the main advantage of GitHub Copilot is probably that it is able to regurgitate the boilerplate with adapted variable names etc. But if all you're interested in is saving yourself some typing for boilerplate code that you use often, many programming editors have their own facilities to do this in a way that is a lot simpler and safer and doesn't involve referring to a ginormous proprietary search engine with a complete disregard of the legalities and etiquette of sharing code.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds