Skip to content

AGPL can't realistically apply to browser code #24

@coolaj86

Description

@coolaj86

How about an MIT license?

What does AGPL even mean in the browser? If the code is jitted along with other code in Safari, does that mean running the client in Safari (or Opera, or Chrome-not-Chromium, or Firefox-not-Iceweasel) is against the license?

Am I allowed to use the client code in a commercial application without it infecting my entire application?

This is an absolutely amazing concept, but AGPL is closed source as far as I'm concerned - there are just too many legal issues for me to consider using it for anything other than research or concept demos.

As far as the python server goes, I don't care if that's AGPL or not - a reverse proxy through another application should mitigate legal issues well enough, but the browser / client code really needs a truly open source license.

P.S. I love free software, and I try to release as much as I can open source, but the freedom of being able to use free and proprietary code as the occasion calls is really important. Not everything can be all open source all the time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions