16
Does the AGPL license allows not disclosing the source of third party scripts (in)directly interacting with the main software? (lemmybefree.net)
submitted 1 year ago by to c/programming@programming.dev
14 comments fedilink hide all child comments
 

cross-posted from: https://lemmybefree.net/post/1201042

Let's say I use some AGPL software like Mastodon or Gitea. If I write a script to interact with some elements, like a nodejs script that interacts with the messages posted to act as an antispam, is it considered derivative work?

If I use a custom theme, does it have to be AGPL? If I add an overlay over the interface or interact with Mastodon through JS, does it have to be AGPL?

For Gitea, if I make a script to scrap some visual elements and send it by email to some people, does it have to be AGPL?

For an email software like Mailcow, if I write an antispam script that communicates with Mailcow's API, does it have to be AGPL?

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 1 year ago*

That’s for deployed services that others are using.

What I meant to say is that it's a public mastodon, gitea, mailcow instance

then talk to a lawyer who specializes in copyright for your jurisdiction

It would be a nice answer, but I'm not going to if I'm not going to make money with the projects. I can't justify this spending

  • permalink
  • fedilink
  • source
  • parent