I reported this to HN a month ago: https://social.mikutter.hachune.net/@mok/116208294430782702 BunnyCDN intentionally mis-writes any Mastodon request signing, as to make it incompatible with Mastodon. And, they confirmed it's intentional.
[dead]
Dropping Cloudflare for Bunny.net
211–220 of 225 posts
Re: Dropping Cloudflare for Bunny.net
#212I’ve mainly been using cloudflare for the very excellent (and free) premium DNS offering. Easy upload of bind test files Flattened CNAME to support naked domains Robust free role based permissions to add other ppl Anyone have suggestions for moving a stack of domains, many being little community and hobby projects away from cloudflare for a small overall price. Agency pricing like migadu offers for email on custom do…
I've tested just about every DNS provider I could find. Self-hosting and Bunny aside, my needs are especially well met by CloudDNS and LuaDNS. https://www.cloudns.net/premium/ https://www.luadns.com/pricing.html I've found every other offering to be lacking. Some examples: Cloudflare is alright but has settings footguns if you're not used to Their Way of Doing It™ (e.g., before using DNSControl, I had to manually fli…
> DNSimple seemed nice but IIRC I couldn't get a different API token per zone (?).
We overhauled our account tokens a few years back: https://blog.dnsimple.com/2023/11/scoped-access-tokens/ . With account tokens you can specify fine-grained scoped access control, including specifying only one or more zones that a token has read or read/write access to.
Re: Dropping Cloudflare for Bunny.net
#213Earlier quoted context omitted.
I've tested just about every DNS provider I could find. Self-hosting and Bunny aside, my needs are especially well met by CloudDNS and LuaDNS. https://www.cloudns.net/premium/ https://www.luadns.com/pricing.html I've found every other offering to be lacking. Some examples: Cloudflare is alright but has settings footguns if you're not used to Their Way of Doing It™ (e.g., before using DNSControl, I had to manually fli…
I think you're right about dnsimple tokens unless they've changed recently. I ended up writing a proxy that held the powerful token and then issued its own tokens to get around that... A bit convoluted Annoying for dynamic DNS and DNS ACME challenges where you want a server to manage its own records and nothing else
I've put a comment on the parent thread, but unless I've misunderstood what the poster said, we addressed the limitation back in 2023 with scoped access tokens.
Re: Dropping Cloudflare for Bunny.net
#214Earlier quoted context omitted.
The platform yes, but the runtime and the APIs are apache 2.0 licensed and uses web standards wherever possible. Thats way more open than most alternatives i am aware of.
Unless the project is controlled by democratic committee where cloudflare doesn't have a majority of seats it's not open source in any meaningful sense of the word, maybe we should stop acting like corporate sourced software is anything but an attempt to get free labor from the commons.
Have you seen the codebase? Please don’t blanket reply like that just because it is a corp. Workerd is one of my favorite piece of engineering and its not comparable at all to openwashing projects that have extreme internal garbage not possible to free from the companies infrastructure. Kenton and others fought hard to make the abstractions among the cleanest and well designed in the industry and while it is not a multi contributor apache foundation style project it is a codebase that you could hard fork if cf decided to close it or go a direction you cannot accept.
Re: Dropping Cloudflare for Bunny.net
#215Earlier quoted context omitted.
The platform yes, but the runtime and the APIs are apache 2.0 licensed and uses web standards wherever possible. Thats way more open than most alternatives i am aware of.
Their fetch handler [1] is not a web standard. [1] https://developers.cloudflare.com/workers/runtime-apis/handl...
but not to lock people in but to avoid the context overhead of service worker api, which they tried first and which still works btw.
Re: Dropping Cloudflare for Bunny.net
#216I'm currently running a SaaS on Cloudflare Workers + Pages. The developer experience is genuinely good, deploying serverless functions and static sites from the same repo has been seamless. But I hit a real issue recently: CDN edge caching served stale HTML after a deploy, and the service worker cached the bad response. Took a CDN purge from the dashboard to fix. The debugging experience when things go wrong at the e…
Bunny has a lot of that (they have a sqlite compatible API, edge functions, but the call it something different, etc.) That being said, I had enough issues with Bunny and CF debugging across regions that I made this free tool to do both remote HTTP and TCP traceroutes to keep my sanity: https://dnsisbeautiful.com/global-http-availability
Nice tool. Bookmarked. Thanks for building it.
Re: Dropping Cloudflare for Bunny.net
#217Earlier quoted context omitted.
Their fetch handler [1] is not a web standard. [1] https://developers.cloudflare.com/workers/runtime-apis/handl...
but not to lock people in but to avoid the context overhead of service worker api, which they tried first and which still works btw.
Sorry, what? I never mentioned lock-in.
I assume by Service Worker API, you mean FetchEvent? [1] As in:
self.addEventListener("fetch", (event) => {});
That is a web standard indeed, but not one that was designed for use as a general-purpose HTTP handler, but rather for use in a Service Worker proxy.
[1] https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent
Re: Dropping Cloudflare for Bunny.net
#218Earlier quoted context omitted.
but not to lock people in but to avoid the context overhead of service worker api, which they tried first and which still works btw.
Sorry, what? I never mentioned lock-in. I assume by Service Worker API, you mean FetchEvent? [1] As in: self.addEventListener("fetch", (event) => {}); That is a web standard indeed, but not one that was designed for use as a general-purpose HTTP handler, but rather for use in a Service Worker proxy. [1] https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent
Maybe i misunderstood what you were going for. Just saying: Yes, their web fetch handler is not a web standard but the only standard there is to accomplish something like that had a few issues and they picked something that looks as generic as possible. vs import {pretendToStartServer} from ('our:global-injected-pseudo-sdk')
I really loved the idea of using service worker sdk and having something that works in browsers too so the conceptual model of edge functions are spanning backends, edge POPs and browser runtimes.
Re: Dropping Cloudflare for Bunny.net
#219I reported this to HN a month ago: https://social.mikutter.hachune.net/@mok/116208294430782702 BunnyCDN intentionally mis-writes any Mastodon request signing, as to make it incompatible with Mastodon. And, they confirmed it's intentional.
Are they using C# on their servers? Not Windows I hope?
Their CDN layer is believed to be written in C# yes
Re: Dropping Cloudflare for Bunny.net
#220Earlier quoted context omitted.
Maybe it technically under some regulation runs afoul. The FTC would never bother themselves with this and I don’t believe it’s in the spirit of the intent.
They might not enforce it consistently, but they do bother themselves with it enough to have guidelines. https://www.ftc.gov/business-guidance/resources/disclosures-...
Right and some random blog is never going to be enforced.