IIIF functionality not clear

[EnnoMeijers]

The Strapi admin offers the "Use Fallback IIIF support?" switch, it is not clear what the functionality does. Should this be added to the Nuxt interface?

[aabelmann]

@EnnoMeijers In the beginning of this project, we talked about implementing IIIF support in the client UI to reduce the size of some of the images we are loading. This was triggered by some datasets having images of 40Mb+.

At the time we implemented a IIIF proxy which replaces the filename part of an IIIF url with a base64 url to an external image.
The image will then be fetched, processed and stored as cached image (visible through the media library in Strapi).
There are some small optimimalisations in the code but I won't go into detail here.

Later in the project we talked about the NDE standaard, which requires datasets to have IIIF support.
As a result we discussed if we should remove the IIIF proxy functionality and agreed to leave the fallback in.
Since it allows datasets to quickly be onboarded even if they don't have IIIF support.

This means that if a dataset provider already supports IIIF, then this option can be turned off. It's only needed for people that don't have IIIF.
Hopefully this explanation will allow you to answer the question: "Does this need to be added to the client UI?"
It all comes down to who has control to turn this feature on/off and that is linekd to the vision of this project.