3 ms·
This might be technically correct but doesn't seem to matter much in practice because of how many practical cases of NN outputting copyright-infriging content t
by phoe-krk 4y ago
This might be technically correct but doesn't seem to matter much in practice because of how many practical cases of NN outputting copyright-infriging content there are. These include examples in the recent lawsuits that made the rounds on HN. Either even the best specialists behind these NNs cannot make the NNs not contain data that is "massively overrepresented or cliche", or they are unwilling to.
- CuriouslyC 4y agoOr they're focusing on performance to get the tools to the place where they're good enough to start being adopted. Once getting sued is more of a problem than not having a product at all, it's not hard to switch gears. I imagine there are a number of ways to avoid storing "too close" copies in a model that have various tradeoffs, I'm sure they'll be adopted quickly in the face of litigation.
- fzil 4y ago> the recent lawsuits that made the rounds on HN I happened to have missed those discussions, do you have some links you can point towards? thanks!
- phoe-krk 4y agohttps://stablediffusionlitigation.com/ https://stablediffusionlitigation.com/ https://githubcopilotlitigation.com/ https://githubcopilotlitigation.com/ Both along with their respective HN threads.
- throwaway675309 4y ago"Many practical cases of NN outputting copyright-infriging content there are" I have seen very few practical cases of generative models such as copilot and even less of a stable diffusion of reproducing original copyrighted works in exact detail, and the few that I did encounter were instructed torturously to do so, which strikes me as highly contrived.