zlacker

[parent] [thread] 9 comments
1. yardst+(OP)[view] [source] 2022-10-17 06:25:20
What’s the most github could reasonably be expected to do? Identify if multiple licenses are found for the same code then maybe it should be flagged for review or the most restrictive license applied.
replies(3): >>samast+U4 >>kitsun+ob >>bjourn+a62
2. samast+U4[view] [source] 2022-10-17 07:20:25
>>yardst+(OP)
Check timestamps of commits of replicated code to find the original.
replies(2): >>barson+08 >>LelouB+Jj
◧◩
3. barson+08[view] [source] [discussion] 2022-10-17 07:55:45
>>samast+U4
That would only work if the original was uploaded to GitHub before the copies. Like, somebody could copy from GitLab or BitBucket. And git histories don’t always help if they’re not copied over.
replies(1): >>lokedh+Ec
4. kitsun+ob[view] [source] 2022-10-17 08:31:39
>>yardst+(OP)
If it's possible for video and audio content (ContentID, YT), then I don't see why it shouldn't be possible for OSS.
replies(1): >>rocqua+Kg
◧◩◪
5. lokedh+Ec[view] [source] [discussion] 2022-10-17 08:44:54
>>barson+08
But copyright law doesn't really care about how you prevent infringement, just that it doesn't happen. Isn't it up to Github to come up with a way to do it, or otherwise not do it at all?
replies(2): >>yardst+TB >>minhaz+Aj3
◧◩
6. rocqua+Kg[view] [source] [discussion] 2022-10-17 09:27:01
>>kitsun+ob
Do we want that though? I personally believe copyright as implemented today is harmful. The fact that code largely is able to dodge this could be seen as arguing we should be laxer with copyright, rather than arguing for strict enforcement of copyright on code.
◧◩
7. LelouB+Jj[view] [source] [discussion] 2022-10-17 10:08:00
>>samast+U4
Timestamps of commits can't be trusted, just like commit authors.

Github can only trust push timestamps.

◧◩◪◨
8. yardst+TB[view] [source] [discussion] 2022-10-17 12:41:30
>>lokedh+Ec
GitHub just needs to show they have taken reasonable precautions, and if a conflict is identified, that they remediate it without undue delay.

It’s not a binary all perfectly or nothing at all. The law looks at intent and so doesn’t punish mistakes or errors so long as you aren’t being malicious or reckless or negligent.

9. bjourn+a62[view] [source] 2022-10-17 19:30:39
>>yardst+(OP)
The point is that CoPilot should not emit a word-for-word copy of someone else's work because that is called plagiarism.
◧◩◪◨
10. minhaz+Aj3[view] [source] [discussion] 2022-10-18 04:50:48
>>lokedh+Ec
Github is protected by section 230, which states:

> No provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider

So the act of hosting copyrighted content is not actually a copyright violation for Github. They're not obligated to preemptively determine who the original copyright owner of some piece of code is, as they're not the judge of that in the first place. Even if you complain that someone stole your code, how is Github supposed to know who's lying? Copyright is a legal issue between the copyright holder and the copyright infringer. So the only thing Github is required to do is to respond to DMCA takedown notices.

[go to top]