Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How does it limit what code you are allowed to integrate with? Do you think that running someone else's code on your machine obliges you to somehow acquire the code to the module that you loaded and share it somehow?


It does when the license says so. Of course, such a document cannot override the local law, and it might be hard to enforce.

For the AGPL, you cannot link against something that isn't also (A)GPL. That means that if you integrate it any tighter than 'running it standalone on an OS' you're probably linking it.


In order to run afoul of it don't you have to provide it to another user either by distributing it or making it available as a service?


Isn't that the entire model of commercial VST plugins?


I believe that such plugins are run locally by the user who then delivers the edited sound file. You know as opposed to being run as SAAS.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: