When we first discussed Giphy integration I was under the impression that we'd be making API calls on a regular basis on behalf of user agents. But instead we decided to just make API calls prior to deployment to grab a list of some images we like and serve them, rather than making the API calls regularly. This was simpler and allowed us to curate the images directly.
I revisited http://giphy.com/terms and I think the only sections that strongly apply to us are 5a and 6c.
5a:
You shall (i) conspicuously label any Application with the words "Powered by Giphy," and the Giphy logo, and (ii) comply with the branding requirements that we may provide to you from time to time.
^^ We should add this.
You shall not use Content to create a database, directory, or index containing GIFs or to improve, edit, augment or supplement any existing database, directory, or index containing GIFs
^^ This is a little tricky. What constitutes a "database, directory, or index containing GIFs"? I think we might get a pass here since we just are randomly choosing one via a (cached) API call and displaying it, making no claims of ownership or copyright. From an end-user standopint, they don't have any relationship with the content in an organized manner that would be necessary to constitute a "database, directory, or index containing GIFs."
carlwiedemann
commented
7 years ago
When we first discussed Giphy integration I was under the impression that we'd be making API calls on a regular basis on behalf of user agents. But instead we decided to just make API calls prior to deployment to grab a list of some images we like and serve them, rather than making the API calls regularly. This was simpler and allowed us to curate the images directly.
I revisited http://giphy.com/terms and I think the only sections that strongly apply to us are 5a and 6c.
5a:
^^ We should add this.
^^ This is a little tricky. What constitutes a "database, directory, or index containing GIFs"? I think we might get a pass here since we just are randomly choosing one via a (cached) API call and displaying it, making no claims of ownership or copyright. From an end-user standopint, they don't have any relationship with the content in an organized manner that would be necessary to constitute a "database, directory, or index containing GIFs."