0 reply
0 recast
2 reactions
2 replies
0 recast
6 reactions
actually, i'd pay attention to the real why:
"This presents a challenge for FOSS projects in that the use of generated slop is highly likely to violate intellectual property law by way of regurgitating the aforementioned stolen training material. This likelihood is proportional to the specificity of the problem area."
its IP related.
call it a slop generator, or whatever asahi chooses to, but imagine i asked to write a feature of mongodb today because i had a fork of it...
source is available right? https://github.com/mongodb/mongo
but mongo is *not* open source. it is source available.
a lot of people may not realise this, but an llm generating something similar feature wise can actually be detrimental to the new fork project, because it is effectively violating mongodb's copyright.
now, mongodb isn't alone in the SSPL. there is also the BSL (time delayed open source).
and plenty other licenses that an llm has definitely trained on, and will regurgitate similar functionality. so it will be api compatible, wire compatible, but effectively, something made from "stolen" IP.
this is a problem... that i dont think the asahi linux people want to, or care to deal with.
cc: @jc4p because we talked about something very similar recently 1 reply
0 recast
3 reactions
1 reply
0 recast
2 reactions
