Sorry if this has been asked, but will this go public beta soon? I applied to the private beta but doubt I'll get in any time soon. This service would be huge for me.

No, there are no public timelines for public beta (and doubt there are even internal ones tbh).. a lot is going to depend on the private beta side of things

That is a very good point. Let me forward that query to the relevant people 🙂

Understood. Hopefully I can enjoy some day. One thing I gotta say that would be really awesome for Cloudflare to do is make sure to add better Range support. AWS S3 you have to make seperate requests for multiple ranges. If you could make a request that was like

Range:bytes=0-10,40-50,100-300

that would be massive.

Maybe it is because it is so far a fully closed beta, with only just a few currently participating, who would have to agree to the terms privately anyway?

Hey, I was wondering how the pricing is currently planned for burst read operations. I have a use-case where I would download ~2k+ files as quickly as possible (almost all under 1mb, most of them a few kb), then barely any for at least one, often multiple hours. The average req/s will be less that 1 over a day, but it will be a lot higher over those couple of minutes. Would this use-case incur storage operation costs?

big brain

From what I know, it's extremely limited, if there even is one (but I'm speculating) to external users.

From my memory I think the reqs/s limit on pricing was per file, so unless the file is the same downloaded multiple times, no issues. If this was different, Cloudflare's cache playing a role (maybe, don't know how or if it would work), limit is per bucket, or something then time will tell.

Ah alright. Was asking because this being a public channel made me wonder if there's some kind of rollout to external users currently going on

If there was I'd love be in it, but as far as I can tell there is none.

Guess I'll keep my fingers crossed for a couple more months hehe

Ah okay, thanks. I didnt read that anywhere in the blog post, it just said request per second.

What's the benefits of using R2 over backblaze and replicating files between their EU/US data centres?

ToS 2.8 won't apply to R2

I was expecting an answer to be more about response times/workers integration/better global distribution not ToS 😅 Does that imply https://www.backblaze.com/blog/free-image-hosting-with-cloudflare-transform-rules-and-backblaze-b2/ is potentially against ToS 2.8 if your usage were to scale enough? I thought due to the cloud alliance so long as images etc were cached efficiently there wouldn't be issues.

Everything is against that 2.8 ToS, the trust and safety team uses this ambiguous paragraph to arbitrary suspend whatever they want, even business plan accounts are at risk, for example not so long ago they broke the Deno ecosystem and all its dependencies without any warning, Deno uses GCP now, look on HN for more complaints, this ambiguous behavior is a known issue

Makes sense if you were using it for videos etc, but yeah the wording there is pretty concerning that you could be using the service as advertised and still be shut down according to that clause if you grow large enough.

I have no idea about particular instances, but you aren't going to be shut down instantly whenever someone in Cloudflare damn well pleases.. And yes, if you have a site with a massive amount of traffic that technically isn't within the ToS for free/pay as you go plans, you can opt to pay for an Enterprise plan with custom terms.. I fail to see how that is controversial?

also, the backblaze guide isn't as advertised by cloudflare

> Additionally, we may at our sole discretion terminate your user account or suspend or terminate your access to the Service at any time, with or without notice for any reason or no reason at all. We also reserve the right to modify or discontinue the Service at any time (including, without limitation, by limiting or discontinuing certain features of the Service) without notice to you. 8 ToS

It's more the ambiguity, don't get me wrong I love so much of what cloudflare offers, but that'll always be something at the back of my mind that if anything built around it grows large enough it could be forced onto enterprise, where bandwidth is metered and pricing around everything is custom. And not really being sure when that would happen.

but this is getting a little side tracked from R2 😅

> "you aren't going to be shut down instantly" That's exactly what happened to the Daily Stormer (political reasons), Deno (technical reasons) and others for ambiguous "Non-HTML" limits, (note: I'm not endorsing nor defending anyone these are just examples of instant suspension) Regarding the ToS, the Trust & Safety team usually shoots first and asks questions later, the point 2.8 "Non-HTML" is controversial because it's a logical catch 22 that enables arbitrary decisions. I hope the R2 team won't follow these kinds of procedures and will have unambiguous supplemental terms. Tonight is the Q4 earnings call, in the last months $NET has gone from $220 to $80 and rebounded to $110, R2 has created so much hype that Cloudflare's reputation is tied to this launch, I'm still bullish, please be meticulous with R2's ToS.

(Please keep in mind that discussions of Cloudflares financial/stock performance is not allowed in this server as per #775391577790611466)

> Regarding the ToS, the Trust & Safety team usually shoots first and asks questions later, the point 2.8 "Non-HTML" is controversial because it's a logical catch 22 that enables arbitrary decisions. I don't think that is fair tbh. If anything, CF Trust and Safety is known for taking a while to fully see if a site breaks ToS before taking any action. Anyone who has ever submitted an abuse complaint knows that they do not "shoot first and asks questions later."

You are talking about manually reviewed complaints, I'm talking about the automatic and immediate suspension that triggers after your account goes over a certain threshold that is not documented and nobody knows about. In the Deno incident, if I remember correctly, someone on a HN thread knew a friend of a friend that worked at Cloudflare and contacted them via Twitter because support wasn't helpful, even with that insider contact it was easier to migrate the entire infrastructure to Fly than to wait for the suspension lift. Imagine that Cloudflare Workers imported its dependencies/modules via URLs and that repository domain was suspended for an entire day, that's the impact of a policy "shoot first and ask questions the next day".

Well, I know of no automated system that has done this, and there is no documented automated system that does this, so I can't form an opinion on the topic. If you want to discuss further, lets do it in #812577823599755274