News for hackers. Stuff that matters.
Re:Show HN: thedaywefightback.js by rosser on Wednesday February 05, 2014 @05:17PM (#7187240)
Yes, it is.

AGPL requires you not only to release your changes to that code, but to release any code that talks to AGPL'ed code over the network.

Re:Show HN: thedaywefightback.js by belorn on Wednesday February 05, 2014 @06:43PM (#7187650)
Citation needed!

Really, your statement is simply completely made up. If you read the license, it says:

  your modified version must prominently offer all users
  interacting with it remotely through a computer network...
Users are not code, nor should they be owned. If they are not already released, release them now.
Re:Show HN: thedaywefightback.js by rosser on Wednesday February 05, 2014 @09:04PM (#7188273)
Remember, this is Javascript, so it's not an unreasonable reading of the license that merely serving it counts as "Conveying" it, per the terms of the AGPL. To wit:

To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

Re:Show HN: thedaywefightback.js by belorn on Thursday February 06, 2014 @03:39AM (#7189331)
Thats a question regarding when a combined work is created (not about code communicating over a network...).

Its not that difficult question to look into. Imagine that I would "convey" a photo by using img tags and "link" proprietary photos inside advertisement banners. Would the banner count as a combined work, or as two separate and disconnected works?

I would lean towards the single combined work, because thats how I think a non-technical judge would look at it.