• 3 Posts
  • 75 Comments
Joined 5 months ago
cake
Cake day: October 17th, 2025

help-circle



  • The danger being raised with the licensing is that you can’t license something if you’re not considered to be the author. There are growing examples of courts and lawmakers determining AI output to be public domain:

    The US Supreme Court recently refused to reconsider Thaler v. Perlmutter, in which the plaintiff sought to overturn a lower court decision that he could not copyright an AI-generated image. This is an area of ongoing concern among the defenders of copyleft because many open source projects incorporate some level of AI assistance. It’s unclear how much AI involvement in coding would dilute the human contribution to the extent that a court would disallow a copyright claim.

    https://www.theregister.com/2026/03/06/ai_kills_software_licensing/

    This is an evolving, global situation and hard to know what to do right now. I think what you’ve got is fine though - you’ve made it clear your intention is to license with AGPL. It’s just that depending on the jurisdiction it might be public domain instead.

    This is another reason to be clear about the use of AI in the README so your users can make an informed decision.













  • The author assesses both Tidal and Spotify to be no longer under European influence:

    To be clear from the beginning, Spotify was founded in Sweden but now operates within financial structures that place it firmly inside the global Big Tech ecosystem.

    Similarly, Tidal was founded in Norway, but it now holds a marginal European market share of less than 1% and is controlled by American capital.

    Both now operate within financial and corporate structures that place them outside the European sphere of influence. The cultural and economic centre of gravity is no longer European for these companies.