[judge2020]

I address that - $200/mo is a lot more than the $20/mo a pro plan costs, which is why upgrading to Business might've been enough, depending on the traffic levels of the service in question. But if your service is pushing terabytes of images or billions of requests, you're costing CF a lot more than they're getting back (in both money and a stronger network presence). Pretty much every booru gets away with paying $200/mo to Cloudflare for pushing likely 20TB/day minimum with a lot of it cached (thus saving them on bandwidth costs to their main image hosting provider).

[tmikaeld]

Also, using r2 to host the images and a worker to proxy them, is allowed, with unlimited traffic and requests.

[joshspankit]

Can you elaborate or point to a guide with more detail?

[corobo]

For it being allowed, the CEO commented as such here. I realise it's not the best reference but I'm not searching through ToS during lunch haha https://news.ycombinator.com/item?id=20791605

As for how to, something like this (Maybe don't use this specifically in production, it was cobbled together from examples as a proof of concept).

It may be missing caching, depending on if/how Cloudflare caches the output of Workers. It's been a moment since I've looked at this project but I'm pretty sure it was caching files that could be cached (using the etag bit on line 22).

https://gist.github.com/cohan/1b154156c9c3d3b269581c940339ce...

You configure what `R2` in my example refers to in wrangler.toml

  [[r2_buckets]]
  binding = 'R2' # <~ valid JavaScript variable name
  bucket_name = 'mybucketname'

E: Random thought you probably don't actually need to do this anymore, R2 has public bucket and custom domain settings now. I needed this for the CORS headers, as that was being a pita at the time