This question is more about conventional practice, so I don't include the detail about code or environment. It should be applied to all type of API call.
This question was asked on SE exchange, but it is off topic so I repost a new one here as suggested (with adjustment to the question). I don't delete the question on SE to preserve the answers. My GitHub project: https://github.com/hunghvu/dynamic-wallpaper
- Let's say I make a call to Lorem Picsum (a public free image API without API key) in my code. My intention is to implement the feature that get a picture from an API call and make it as wallpaper.
- Is it legal to push the codebase to GitHub public repository (without executable file)?
- Is it legal to make an executable file and put to release section?
I cannot find any clear information about these, since they don't have Q&A section.
When I look at other APIs like Placeholder or Pexels, it seems like there is a restriction when putting the application to production server, or the application has a high amount of request to the API server, which make senses (rate, access limit, etc).
The thing is, an application, or code snippet, I want to publish are simply out-of-class/personal/student project that I make during spare times. Certainly, it isn't the same as what commercial apps do (high amount of API call, etc); well, unless my repository somehow becomes popular and my application is downloaded/used 1 million times, then it will be a different story.
Because Lorem Picsum uses database of Unsplash, how will this relationship affect the rules? I choose Lorem Picsum because they don't require Authorization, so it is safe to publish code on GitHub (or is it?), and I can ignore the complexity of applying authorization process into the code (I'm learning about API).
For the matter that I asked in question 1 and 2, can they be applied to all public API, or will it vary from one to another?