3 ms·
> The additional drama includes that said open-source author has looked at the leaked code and concluded that it stole some of his open source work in the way i
by neuronexmachina 4y ago
> The additional drama includes that said open-source author has looked at the leaked code and concluded that it stole some of his open source work in the way it tunes text parameters.
My understanding might be out of date, but as I recall it seemed that the code he thought was stolen from his open-source work actually originated from a third project that's MIT licensed.
- Ukv 4y agoI think that's confusing between two issues in opposite directions: 1. Accusations that AUTOMATIC1111 (the web frontend developer) copied code from the NovelAI leak relating to the loading of hypernetworks 2. The leak revealing that Anlatan (the company behind NovelAI) had copied code from AUTOMATIC1111's repo (who, as above, Anlatan are accusing of copying from them) relating to the weighting of words. AUTOMATIC1111's repo does not have a permissive license to allow this The third party MIT-licensed code is relevant to #1. Some code AUTOMATIC1111 was accused of copying from the leak (https://i.imgur.com/r1AkvBG.png https://i.imgur.com/r1AkvBG.png) actually already appears in multiple older permissively-licensed public repos (https://github.com/lucidrains/perceiver-pytorch/blob/main/perceiver_pytorch/perceiver_pytorch.py https://github.com/lucidrains/perceiver-pytorch/blob/main/pe..., https://github.com/CompVis/stable-diffusion/blob/main/ldm/modules/attention.py https://github.com/CompVis/stable-diffusion/blob/main/ldm/mo...), one of which was credited in the readme by AUTOMATIC1111. For #2, the Anlatan CEO blamed it on an intern (https://i.imgur.com/BFjKG1V.png https://i.imgur.com/BFjKG1V.png). The leak shows that the offending code was committed by the CEO (https://i.imgur.com/aLiA2tr.png https://i.imgur.com/aLiA2tr.png), which doesn't necessarily rule it out originating from an intern (e.g: "send me the code over teams to review and I'll add it") but doesn't look great. From other examples I'd say AUTOMATIC1111 did get a bit sloppy in terms of not following clean-room design regarding the leak, but I'm inclined to give some leeway to a solo developer making a hugely popular public tool for free.