Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
It says this in the docs “The Rate Limiting API is backed by the same infrastructure that serves the Rate limiting rules that are built into the Cloudflare Web Application Firewall (WAF).”
"Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you."
That is not what we are here for, we are volunteers here to assist, but should not be pinged for non-discord-server moderation reasons. This is clearly stated in the server rules
Well would you mind assisting? Cause I was about to ask for assistance as well. Yes this is a non discord server moderation reason, this is a cloudflare company reason as we've discussed before but never completed the answers.
Yes I understand, But you assist for cloudflare which is good enough in my book, but anyways then who are the ones that work at cloudflare or that you can direct me to please and thank you?
There are many Cloudflare employees and others able to help in this server. They are all around and theres constantly people reading messages and helping throughout. They will likely get to your messages eventually, if not, the Cloudflare Forums can also provide help. All we ask is that you not @ or ping anyone for quicker help, that is against the server rules.
Depends what you mean by "location limitation" Any location limitation D1 has is from the fact it uses Durable Objects (DOs) which only run in a few locations https://where.durableobjects.live/, and each DO only exists at one of those locations. R2 uses DOs as well for all the metadata, and of course DO has those same limitations too, unless you implemented your own replication across DOs or something
Is is possible to set a custom version id / deployment id during e.g. build time and then communicate that with cloudflare to be deployed under that version / deployment id?
Thanks! Think you might already understood from a similar question in #pages-discussions, I was looking to prevent version skew, saw that Gradual Deployments support Version Affinity and / or Version Overrrides, which could potentially solve this.