In this thread corruption of preview GIFs was discussed: https://forums.nesdev.com/viewtopic.php?p=179813#p179813
Details in that thread, but the problem seems to be that traditionally "optimized" GIFs (with each frame cropped to just the area that is different from the frame before) get severely corrupted by the resizing process.
Koitsu suggested that phpBB uses ImageMagick to do the resizing? If so, it seems that it has a "coalesce" option that needs to be applied before resizing, and probably an optimization flag as well to undo the file size explosion that coalesce will cause?
Might also be worth pointing out that the corrupted "preview" GIF in this example is actually 50% larger than the original one, which defeats part of the purpose of doing previews in the first place. I expect that more properly processing them might help with this.
Details in that thread, but the problem seems to be that traditionally "optimized" GIFs (with each frame cropped to just the area that is different from the frame before) get severely corrupted by the resizing process.
Koitsu suggested that phpBB uses ImageMagick to do the resizing? If so, it seems that it has a "coalesce" option that needs to be applied before resizing, and probably an optimization flag as well to undo the file size explosion that coalesce will cause?
Might also be worth pointing out that the corrupted "preview" GIF in this example is actually 50% larger than the original one, which defeats part of the purpose of doing previews in the first place. I expect that more properly processing them might help with this.