As explained in the last post, I was trying to get s3 (R2) set up with kbin.earth, and now it’s complete. Now storage costs should be significantly lower (with more capacity) and maybe images will load even faster now.
Also, think of this as an experiment; if it doesn’t work out, I’ll switch it back to file storage.
If you mean Cloudflare Images, then no. I thought about using it, but since Mbin stores the sha hash of the images, I didn’t want Cloudflare to serve an optimized image and then Mbin (or an Mbin app) check the hash and see it didn’t match. Additionally, I believe Mbin does some sort of optimization anyway (there’s a “cache” directory that’s likely the optimized and resized versions of the original images). Unfortunately, this “cache” isn’t used with the Mbin API (and, therefore, any external client). IMO, the best place to optimize the image is when it’s first federated or uploaded anyway.
From what I know, cloudflare images also costs more than just serving the existing image through R2.
Cool. Just curious.
How much are they charging for r2 if you don’t mind me asking?Edit: nvm I can just look at the rates published online :)
There’s a calculator here if you’d like to try a certain setup (amount of storage & operations).