Not yet afaik: https://cfdata.lol/workerd/
Automated datamining from workerd, the Cloudflare Workers runtime. Including compatibility flags.
JRPC is only enabled by default since 2024-04-03. I imagine there will be a new types compat date cut soon
Joh that's a handy page!
Jopened a docs issue https://github.com/cloudflare/cloudflare-docs/issues/13899
J@James but actually, I'm double confused now. The demo repo uses 2023-07-01.. and after cloning it there don't seem to be any type errors https://github.com/cloudflare/js-rpc-and-entrypoints-demo/blob/d1180c6d17983ca10e775009fc05d4aa9c01dc01/tsconfig.json#L16
Jdon't know if there's an easy way to see what types have changed between two compatibility versions
JHmm that's odd. I guess it's not a breaking types change so it's probably in all of them
JI have https://npmdiff.dev/@cloudflare%2fworkers-types/4.20230419.0/4.20230511.0/ for diffing between npm versions, but not that useful for quickly diffing two files in each folder. You could probably just throw those 2 files from the most recent version into a diff checker
JThis is sadly not a direct solution to your issue, but I would recommend avoiding MailChannels and using some other service like Amazon SES, Sendgrid, Postmark, etc.
There are a lot of security implications and their responses to the situation have been very undesirable. Further reading:
There are a lot of security implications and their responses to the situation have been very undesirable. Further reading:
- https://github.com/byt3bl33d3r/SpamChannel
- https://www.youtube.com/watch?v=NwnT15q_PS8
- https://media.defcon.org/DEF%20CON%2031/DEF%20CON%2031%20presentations/byt3bl33d3r%20-%20SpamChannel%20Spoofing%20Emails%20From%202%20Million%20Domains%20and%20Virtually%20Becoming%20Satan.pdf
Jhmm, but this doesn't seem to be a difference in behaviour between release versions, just a difference in behaviour between compatiblity dates
Jtype error with 2023-07-01, no type error with experimental
Jdoes anyone know of any kind of instrumentation that works with RPC?
Cbunjs support as runtime?
HNot very likely. Workers runs its own runtime(not Node, Bun, or Deno)
Acan someone explain why theres 2 different pricing charts for workers? on the homepage it says this
Ain the docs its this
Ahomepage says 1 million included, .15 per + million, docs say 10 million included, .30 per + million
Amy understanding is that the spam channel stuff had been fixed after forcing the requirements of domain lockdown records on your domain.
as for direct solution, I reached out to mailchannels directly as from some debugging it seems that it was an issue on their side
as for direct solution, I reached out to mailchannels directly as from some debugging it seems that it was an issue on their side
Jit was "fixed", yeah, if you add that. Their approach to the situation though has still been very poor, and until recently, you were able to signup on their site for $80 and send verified emails from most of their customers like
boston.govTo this day, they haven't acknowledged the seriousness of the issue, nor alerted their customers afaik. I would heavily advise against using them for any purpose
Ainteresting
Awould really prefer not moving to SES but ill have to look into it
JSendgrid is also a great option
JPostmark too
Apostmark and sendgrid are way out of budget for what im building unfortunately
JRealistically anything other than MailChannels. I've not seen any other provider not do basic domain sender verification
XIs there discussion channel for CloudFlare Calls ?
HNot at the moment
XGitHub
Contribute to cloudflare/orange development by creating an account on GitHub.
X[ERROR] A request to the Cloudflare API failedYou would paste the ID and Key you got from https://dash.cloudflare.com/?to=/:account/calls
Ahttps://developers.cloudflare.com/calls/example-architecture/
looks like the example image and numbers dont match up
looks like the example image and numbers dont match up
Aand also i believe there is a typo on https://developers.cloudflare.com/calls/https-api/#lifecycle-of-a-simple-session
"Remote Client Joints" instead of "Remote Client Joins"
"Remote Client Joints" instead of "Remote Client Joins"
Cloudflare Docs
Cloudflare Calls simplifies the management of peer connections and media tracks through HTTPS API endpoints. These endpoints allow developers to …
Jwhat doesn't match up? seems fine to me on a quick read
HThe 6 bubble is in Admin, which is list item 4
Jgood catch! You might want to open up a docs PR/issue: https://github.com/cloudflare/cloudflare-docs/blob/production/content/calls/https-api.md
A5 in the image is 6 in the bottom area
admin bubble is 6 when it should be 4
admin bubble is 6 when it should be 4
Jah yeah, also good catch
Ja docs issue would be best for that
Awill do
XIn what text format? I tried only secret value, VALUE=SECRET, etc
XEnter a secret value:
XIt does not accept
XAPI calls fail
Awhen you use
wrangler secret put CALLS_APP_SECRET you dont need to specify the value in the command. you will write the value when it asks for the secret valueXok. I needed add correct app ID, account ID etc, then it did work.
.Trying to understand something with workers, if I am gonna rate limit my api, would it not be better to do this in a worker so it doesn’t hit my origin server at all?
.Is there any good rate limit packages that work with itty router ?
JI'm not sure about packages, but you might be interested in the new rate limiter bindings announced during dev week: https://blog.cloudflare.com/workers-production-safety#new-rate-limiting-api-in-workers
