How to respect the API image policy

I would like to know how app developers respect the following policy:

Please cache all images! All images are required to be cached in your app or server and not loaded directly from our CDN. Hotlinking images is not allowed and will be blocked.

ONCE PER USER: Do you have a user download an image once and maintain a permanent local cache?

ONCE PER APP: Do you use something like Cloudinary to download an image from the CDN once ever for your whole app?

Thanks

1 Like

What do you say @support ? How do you define acceptable use to prevent being blocked?

1 Like

If you don’t get a response here, maybe try trakt/trakt-api · Discussions · GitHub

1 Like

GitHub Comment Link

The short answer is to just implement a cache of some sort and not be hitting the actual image directly every time you want to display it outside of the first time, per client or whichever level of service you’re using.

While I can only speak from mobile app client level experience, I assume there are similar web app/server concepts:

For example, in iOS you might use something like Kingfisher or SDWebImage which allows you to load the image in the UI and it handles all the caching under the hood.

In Android you might use something like Glide for the same thing as mentioned above.

1 Like