What do you mean by that?

Actually no, it's not that one, let me find it

Yeah I understood it's duration pricing model for unbound

Ah this diagram shows it

The dark blue is the places where you're actually billed - specifically because on unbound mode you're billed for the duration the worker is alive

That concept isn't a thing for bundled, so it doesn't matter there

Ok, I've just understood your point, so my solution with worker (A) is not good.

Yeah, you'd be adding an unnecessary extra step for the same end result

Is there any other downside with using the workers.dev route for things like a webhook listener?

ah right possible rate limits it seems? https://discord.com/channels/595317990191398933/779390076219686943/1066090962268471387

There's no rate limits by default, we were just talking about adv. rate limiting behavior with workers

The downsides I can think of are: Each new worker gets issued a tls/ssl cert so they get visited by bots pretty quickly No Zone level controls or analytics (No WAF, Firewall rules, etc)

There are rate limits in some aspect to the workers.dev im pretty sure but you dont really have any control over the firewall settings that trigger if it should be blocked or not

hmm right, so probably safer to do a custom domain anyway?

I think Workers in general have some max request per IP rate limit, but is that exclusive to workers.dev? Edit : Looks like it's not, at least for that one , not sure about other ones

Yeah

As far as I know it's not like r2.dev where it's not recommended for production use at all, but using a custom domain will just give you more control/insight. I usually use Worker Custom Domains and then delete the generated cert afterwards if not needed, makes it pretty easy

I have the paid total TLS thingy which makes it nice

oh hmm odd, Zaraz runs in front of CF Workers

that's both good and bad depending 😛

lots of stuff does

hmm

is there no secure/safe string comparison in V8?

there's a timingSafeEqual under crypto

oooooo

interesting 🤔

is there a sane way to put env var objects in a secret?

if I have a Worker that just makes POST requests (it's basically a proxy) that take 0.5 to 2 seconds, bundled will be way cheaper, right?