| ▲ | willtemperley 5 hours ago |
| Their copyright clause reflects my own quandry about LLM usage: I am responsible for ensuring copyright has not been violated with LLM generated code I publish. However, proving the negative, i.e. the code is not copyrighted is almost impossible. I have experienced this - Claude came up with an almost perfect solution to a tricky problem, ten lines to do what I've seen done in multiple KLOC, and I later found the almost identical solution in copyrighted material. |
|
| ▲ | mierz00 5 hours ago | parent | next [-] |
| I’m curious have you ever been burnt or seen anyone burnt by copyright infringements in code? Sometimes it’s super obvious because a game company steals code from a previous employer, but I have never seen this play out in entreprise software. |
| |
| ▲ | willtemperley 4 hours ago | parent [-] | | Personally I have not experienced it, but I have heard of people scanning for LGPL library usage in iOS apps, then essentially extorting the developers for their source code. I can't find the specific article now, but I am extremely careful to avoid anything GPL or LGPL. It's unlikely to be a problem until an app is highly successful, but once that happens people will grasp at whatever straws they can, e.g. https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America%2.... |
|
|
| ▲ | foxglacier 5 hours ago | parent | prev | next [-] |
| Copyright is for creative work so if it really is the best way to do it, you should be safe even if the AI copied the idea from somebody else. You can't use copyright to restrict access to useful technology like a patent. |
| |
| ▲ | 4 hours ago | parent | next [-] | | [deleted] | |
| ▲ | 5 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | willtemperley 4 hours ago | parent | prev [-] | | That's very useful feedback. I suspect if the solution is irreducible it's OK, which in this case is close to true (this is for bit-unpacking integers): // bytes are added to the buffer until a value of bitwidth is available
for _ in 0..<bitWidth {
let byte = try UInt8(parsing: &input)
buffer |= UInt64(byte) << bitsInBuffer
bitsInBuffer += 8
// Values of bitwidth are right-shifted off the buffer.
while bitsInBuffer >= bitWidth && outPos < numValues {
let value = Int(buffer & mask)
out[outPos + outOffset] = value
outPos += 1
buffer >>= bitWidth
bitsInBuffer -= bitWidth
}
}
|
|
|
| ▲ | octoberfranklin 5 hours ago | parent | prev [-] |
| > However, proving the negative, i.e. the code is not copyrighted is almost impossible. Nonsense, it's trivially easy if you wrote the code yourself. You hold the copyright. If you had some LLM puke out the code for you, well, then you have no idea. So you can't contribute that puke. |
| |
| ▲ | willtemperley 5 hours ago | parent [-] | | Did you read my comment? I was specifically talking about publishing LLM generated code: > I am responsible for ensuring copyright has not been violated with LLM generated code I publish Your comment: > If you had some LLM puke out the code for you, well, then you have no idea. So you can't contribute that puke. That's not true. You can if it's not violating copyright. That "puke" as you put it comes in many flavours. |
|
