-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudflare as a Risk #111
Comments
Right now we're using Cloudflare only for the kernel and plugins, right? The only thing that stops us from quickly switching over is the KV. |
In the context of the bot, yes its basically just for Workers. However we also do handle all of our DNS settings on there for our domains which can be complex to fix if we need to hastily move off. Perhaps we should set up redundant serverless infra and then we can switch faster when they pull the rug. For example we have CI deploys as well on personal Vercel instances (free, if ran from forks.) I already have ubq.fi hosted on a separate registrar so it shouldn't be too difficult to point the nameservers elsewhere. |
It is quite ludicrous. But they seem to target big whales because they expect to make money out of it. I do not think we would be a target before reaching quite a heavy payload. I can't think of many alternatives, but one I could mention is Azure services with https://azure.microsoft.com/en-us/products/functions . They are usually quite generous on the usage, and I never heard such extortion scenarios. And on the plus side, we would stick to Microsoft products, since we already use GitHub quite extensively. |
Pretty interesting although I'm very cautious to introduce new technologies. Fortunately they emphasize being small and performant which implies it is probably simple to use. |
I've received a few emails from Cloudflare sales but didn't make time to speak with them. Turns out they are developing a reputation for extortion. It's something we should have a plan for/think about. I'm expecting them to pull the plug just when we start onboarding partners.
The text was updated successfully, but these errors were encountered: