Not a bug Giphy implementaiton is not compatible with their API terms of service

[Jake B.]

Affected version

All versions

Per Giphy's API terms of service

You agree to properly attribute all pieces of content that you obtain through the API and at no time will you falsely attribute any such content. For the avoidance of doubt, this means that you won’t display any content in your applications without Giphy user and/or source attribution where available.

However, when an image from Giphy is embedded using the "GIF" button in the editor it simply uses the img tag to add the source image:

If you user the media embed instead, you would automatically meet these requirements:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[Chris D]

If you're using the API, there's not really an expectation to use the embed. It's an option, but that's not really ideal for a number of reasons, not least overhead for loading everything else that the embed produces.

But I have to point out, you haven't really chosen the best example here.

That particular GIF does not have a source or user attribution.

In this example, there is a user, and that is attributed in the alt and title attributes:

<img src="https://media4.giphy.com/media/4WZlcJ8JJ6fayY7TGA/200.gif" data-url="https://media4.giphy.com/media/4WZlcJ8JJ6fayY7TGA/200.gif" class="bbImage" data-zoom-target="1" style="" alt="Maya Rudolph GIF by Emmys" title="Maya Rudolph GIF by Emmys" width="320" height="200" loading="lazy">

We ran this by GIPHY just under four years ago and they agreed it met the requirements.