3 ms·
Why would the rest of the site have to be published under AGPL? I'm thinking other parts of the site aren't the same "work" as the conversation platform? Is th
by KajMagnus 7y ago
Why would the rest of the site have to be published under AGPL? I'm thinking other parts of the site aren't the same "work" as the conversation platform?
Is the reason possibly AGPL Javascript? Maybe then server side code, could be AGPL, and Javascript instead e.g. MIT?
However don't one typically place a blog commenting system in an iframe. Then personally I think you wouldn't have to release the website that embeds the blog comments iframes, under AGPL? And a discussion forum, one places on a sub domain, on a separate server? Also separate from your main website?
Background: I'm developing AGPL discussion software that you can also embed in an iframe, for blog comments. https://www.talkyard.io/blog-comments https://www.talkyard.io/blog-comments. What are your thoughts about using sth like that, if the code that creates the iframe is MIT or Apache2, and the code that runs inside the iframe is AGPL?