3 ms·
My feeling on this would be: they're probably fine shipping the static media assets for my site like the logo, CSS, JS, banner image, etc. Those are trivially c
by mdasen 3y ago
My feeling on this would be: they're probably fine shipping the static media assets for my site like the logo, CSS, JS, banner image, etc. Those are trivially cached with long lifetimes. I'm guessing what they don't want is an Imgur-like site where there's a lot of user-generated media content for free.
The new section says:
Cloudflare’s content delivery network (the “CDN”) Service can be used to cache and serve web pages and websites. Unless you are an Enterprise customer, Cloudflare offers specific Paid Services (e.g., the Developer Platform, Images, and Stream) that you must use in order to serve video and other large files via the CDN. Cloudflare reserves the right to disable or limit your access to or use of the CDN, or to limit your End Users’ access to certain of your resources through the CDN, if you use or are suspected of using the CDN without such Paid services to serve video or a disproportionate percentage of pictures, audio files, or other large files. We will use reasonable efforts to provide you with notice of such action.
To me, that's reasonably clear. If you're a blog that's content with some images between the logo and maybe a picture or two in an article, that's probably fine. That seems "proportionate" - in a similar proportion to most sites on the web. If you're Imgur where you're basically just serving media assets to people or if you're trying to make the next TikTok, that's disproportionate - beyond the normal proportion of media assets of most websites. Likewise, you can't run an NPM clone or download server for Linux ISOs off Cloudflare - that would be disproportionate. And if you're uploading podcasts to your website, those large audio files don't get a free ride.
How much exactly is disproportionate? Of course they're going to have to leave that a tiny bit vague so that people don't game the system. To me, it feels reasonably clear. If you're building an average site, don't worry about traffic to it. Your regular old blog is fine. If you're building something that leans heavily on serving images, audio, or video, you can't do that. Your podcasts should go into R2, your video should go into Cloudflare Stream, etc. or not be served via Cloudflare's CDN.