4 ms·
I'm concerned about the implications of these license terms: [...] you do hereby grant Algorithmia, in its capacity as the provider of the Services, a worl
by logn 12y ago
I'm concerned about the implications of these license terms:
[...] you do hereby grant Algorithmia, in its capacity as the provider of the
Services, a worldwide, non-exclusive, perpetual, irrevocable, fully paid-up and
royalty free license to use and permit others to use the Software (including
the source code if made viewable) in any manner and without restriction of any
kind or accounting to you, including, without limitation, the right to make,
have made, sell, offer for sale, use, rent, lease, import, copy, prepare
derivative works, publicly display, publicly perform, and distribute all or any
part of the Software and any modifications, derivatives and combinations
thereof and to sublicense (directly or indirectly through multiple tiers) or
transfer any and all such rights; provided, however, that if your Software
includes any FOSS, in the event of a conflict between the applicable FOSS
license terms and the license terms set forth in this paragraph, the applicable
FOSS license terms will control, but only to the extent required by the FOSS
that you use.
https://algorithmia.com/api_dev_terms https://algorithmia.com/api_dev_terms
(edited to add line breaks)
- deleted 12y ago[deleted]
- wlesieutre 12y agoIf you use a code block for text, including line breaks is helpful
- platypii 12y agoThe terms here are necessary to provide the services that we offer via Algorithmia. We need the right to run your code and make it available. It needs to be in perpetuity so that consumers of the API can put it in production with the assurance that it will continue to be available in the future. That being said, the quoted passage lacks the context of the rest of our terms -- namely, yes, we get the right to make your work available, but in return it's OUR obligation to share the profits with the original authors. (Kenny @ Algorithmia)
- logn 12y agoThis just seems overly broad for your purposes. Plus you reserve the right to update the terms, yet you have an irrevocable license to your users' software. I just don't see this being realistic for anything except thin wrappers around FOSS projects. That's great in itself, but I'm not sure why you offer the "closed source" option for projects. Based on your terms, you could turn around and open source all those since users have given you power to sub-license. Granted, I doubt you'd do that but it demonstrates how needlessly broad your terms are. (I'm not a lawyer; this is just my speculation and not advice)