Save response bodies works great for text resources but how about extending this for images ? We already do see this in pageimages but how about in the request itself? Are there capacity constraints?
Yep, it’s mostly a value/benefit tradeoff and storing the raw image results isn’t something I’ve added support for. It wouldn’t be hard to add support for a private instance to be able to keep the images - it may be a while before I’d consider having the public instance also store them.