I think by keeping the HLS segments at a few megabytes each and not using a file extension in the URL, I've slipped through the cracks.
(My religion forbids me from recognizing any terms of service that haven't been given the three blessings of the matriarch)
Saint Trader Joes tried to unite them by using both light and dark sesame years ago, but there’s just too much bad blood for them to work together. We are still waiting for the chosen one that will bring balance to the bagel.
May the bagel balanced be.
> 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.
- https://www.cloudflare.com/service-specific-terms-applicatio...
Reading between the lines a bit: they really only care if you're using Cloudflare to front a site whose primary purpose is to deliver video content, and lots of it (like, say, if you're running a tube site or a livestreaming site). They don't care about web sites which happen to incidentally include a small amount of video content.
Just make sure that player supports right click->Save I'd much rather download and view a video in VLC than somebodies janky JS player
You’ll have to learn some ffmpeg incantations but the bandwidth will be free and your total costs will be the tiny VM and block storage. Might even be able to point Cloudflare at a public bucket and skip the VM.
If you need to store and serve several terabytes of content, a dedicated server instead of block storage will be your best bet (again with Cloudflare), you’ll just need to figure out offsite backup and restoration.