nostr:npub1jtm4dxvu3ccgk60wvvt0uw9j9vz7nuc80f7agrv0vgkkushxk5zq0rrxtn nostr:npub1yqwcsafkzl4fequd25qg6yvmyxusk8gmpe7hkpfcnzc34afx4npsfhwajx nostr:npub1dft4ckvyhfpw3n56zm8j42nzrjeummudr2vmkf304eu5jhnn0ahqz7ta3d

it's a good call, and I started down that road...but this looks like we're going to have to introduce another layer of storage and data mapping to be able to handle...

we can *request from server and save* the image no problem with a HEAD request...but then to get the chapter image out of our local storage/cache, we only have the original chapter image URL to work with, and at that point we don't know the extension again, so we don't know the file path in storage...