We (some friends and I) built it because we wanted to understand how these things worked and also had max accounts. It has since grown into a ton more, but is still in essence a very full featured local proxy.

Seems "reject individual flight plan" might be a better system response than "down hard to prevent corruption"

Bad assumption that a failure to interpret a plan is a serious coding error seems to be the root cause, but hard to say for sure.

https://www.sierraspace.com/commercial-space-stations/life-s...

For example, I relocated to Puerto Rico several years ago and am taking advantage of a 50% transferrable R&D tax credit. Because it's transferrable I can sell the tax credit to people that have a tax liability even if I don't.

After fees, this means I get roughly 40% cash back on my R&D expense. This is a big deal to me and my company.

If you don't do your home work you can potentially miss out on some great opportunities. That said, you do still need to build a good business, or the best tax structure in the world won't save you.

We did end up adding some additional generics which allows us to get strong typing between producers and consumers. That I think has been a key piece of making it easy to use and avoiding dumb mistakes.

If an endpoint is decorated with something that is considered dangerous (i.e. public access), that triggers additional review steps. In addition, the authentication forbids certain combinations of decorators and access patterns.

It's not perfect, but it has saved us a few times from securing endpoints incorrectly in code.

I'm not saying cloudflare can't do it, I'm just saying it's wrong.