Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Saturday, 30-May-2026 06:40:19 JST Rich Felker

   @ariadne Quite the opposite I think. I think it leads to a resurgence in interest in copyleft, since these are largely the projects not embracing slopware and the fraudulent "non-copyleft" "rewrites" are pandering to techbro asshats and the and the corporate AI-slop program.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Saturday, 30-May-2026 06:48:03 JST Rich Felker

     in reply to

     • yoasif

     @yoasif @ariadne The derivative works are going to have wildly unclear infringement status that varies by jurisdiction and perhaps by short-term political winds. That is an incredibly precarious thing for anyone to be depending on. We need to be amplifying this narrative to make potential users terrified of legal consequences that might befall them in unexpected locations even when they think they have certain countries' legal systems under their thumbs.

   • Embed this notice
     yoasif (yoasif@mastodon.social)'s status on Saturday, 30-May-2026 06:48:04 JST yoasif

     in reply to

     @dalias @ariadne I said different, but I suppose I assumed that the GPL projects @ariadne was thinking about the ones who have given into slop coding; GPL code that isn't GPL, essentially.

     I think if people are the ones developing the codebase, we are still stuck with the problem of derivative works not complying with the GPL (as the slop coded projects are derivatives of the GPL projects that have been trained on).

     Copyleft becomes less of a cudgel - I don't think it is anything but weaker.