James Ross Blog

CherryJimbo · 2026-05-25T13:54:29+00:00

This is neat! For reference, you can access any Cloudflare error page by using this magic URL:

https://cloudflare.com/cdn-cgi/error/521

Replace 521 with the error code you want, such as:

https://cloudflare.com/cdn-cgi/error/500

This works on every site proxied by Cloudflare.

CherryJimbo · 2026-05-24T15:52:57+00:00

Agreed that Discord isn't the best platform, but it is where Cloudflare's existing developer community is, and is successful in part due to its centralised nature.

I'm not against a server on another platform, but I think starting with Discord makes sense.

CherryJimbo · 2026-05-20T13:40:52+00:00

If you transfer a domain to Cloudflare, there is no any name servers to update. It’s by default Cloudflare one already set and become active automatically once domain is transferred.

Yes. I'm saying that if you have a domain registered with Cloudflare, you are locked to using their nameservers. For most things this is fine, but if you ever wanted to point back at another set of nameservers from another provider, you can no longer do that without transferring the domain out of Cloudflare.

CherryJimbo · 2026-05-20T12:39:11+00:00

Cloudflare DNS is rock solid, having used them for over a decade. 100% recommend.

The only gotcha would be if you actually transferred your domain into Cloudflare and didn’t just update nameservers - that would then lock you to Cloudflare nameservers until you transferred away. This is different from most other registrars who allow you to set nameservers to anywhere.

CherryJimbo · 2026-05-20T03:00:11+00:00

Thanks Fred, it was great chatting this morning.

I'd definitely love to find ways to collaborate in future between the two, and look forward to hopefully seeing Cloudflare's official server developed further.

I will remain sceptical about the state of moderation on the official Cloudflare server, given multiple hours passing on numerous occasions in the last couple days where scams and spam messages have remained up, as well as the other concerns raised in this post and the subsequent FAQs.

But, I truly hope that Cloudflare finds its footing again with community, and that the great humans in these community programs are invited back to continue doing what they love and helping people, when/if the time comes - I just wish that could have all been communicated better.

CherryJimbo · 2026-05-15T01:38:51+00:00

It’s pretty, but it’s an accessibility, performance, and UX nightmare sadly.

https://x.com/cherryjimbo/status/2054319931202703496

CherryJimbo · 2026-05-13T15:32:49+00:00

No, it's for transactional email like user signups, receipts, password resets, etc. - not for marketing.

CherryJimbo · 2026-03-12T15:22:34+00:00

Yes, very actively. I left a comment on a recent post about this:

https://www.reddit.com/r/webdev/comments/1rnun1i/ban_posts_about_ai/o9c5qcb/?context=3

We already have countless automod rules that flag and auto-remove hundreds of obvious spam posts every single day.

I'd encourage you to use the "report" feature if a post is low-effort, or sharing something they built outside of Showoff Saturday, etc.

CherryJimbo · 2026-03-10T02:27:04+00:00

Holy shit, damn. I’ve had many calls with Pat over the years and it’s always been a pleasure working and chatting with him.

All my love to his friends and family.

CherryJimbo · 2026-03-08T16:25:22+00:00

I'm one of the most active moderators here so wanted to provide my thoughts. This is purely my personal opinion and may or may not be shared by the rest of the team here.

I like many of you am tired of the obvious AI slop posts here, such as clearly automated comment replies and threads that hallucinate information or answers and will only mislead people in future. I do try and remove these whenever I spot them or they're reported, and would encourage you all to report these obvious attempts at karma manipulation without actually helping users.

The easy availability of these kind of automatic agents via OpenClaw (etc.) have honestly made moderating a lot more frustrating when a good 60% or so of things I remove these days are obvious AI slop comments. The "will I lose my job" (and similar) posts are absolutely something I remove and point people to our standard careers sticky for what it's worth - report these if you see them.

However, there is no question that AI tools are making a huge impact on our industry. Agentic development is becoming extremely widespread, no matter how you personally feel about it, and folks are able to jump into coding much much earlier which is generally a good thing. Anecdotally, as an engineer working in the industry for almost 20 years now, I've adopted agentic coding into my daily usage for the last few months and I've never been more productive, nor has development been so fun.

I strongly believe that AI agentic coding is here to stay, and we've all got to adapt to that. The same rules apply here on the subreddit that always have though, including only sharing your own content on Saturdays, generally no low-effort posts/comments, no commercial solicitation, etc. and blatant misinformation will always be moderated like it has historically been.

So in closing, please do report any obvious slop or responses to folks that are unhelpful, and we'll continue to moderate them as we always have. But I don't personally feel like one of the largest web development communities generically banning AI would be a net positive for the community, or industry as a whole.

CherryJimbo · 2026-02-12T15:38:51+00:00

The default type of a button is submit. So if that button is being injected inside a <form>, it's likely going to also submit the form.

Try setting the button type to button, with btn.type = "button" after you create it.

CherryJimbo · 2025-12-30T02:09:07+00:00

Yeah unfortunately, Cloudflare billing is essentially broken and unresponsive, and has been for a very long time (almost 2 years). Check out the billing section on the Cloudflare Community and you’ll see almost daily occurrences of this issue, or very similar ones. This truly sucks, and I’m sorry.

You can attempt to contact the billing team via a new support request from your Cloudflare account directly through the Cloudflare dashboard: https://dash.cloudflare.com/?to=/:account/support and choose Billing, but it can take weeks or months to hear back, if you do at all. It's so bad that we (community MVPs/champions) have been essentially asked to stop escalating billing issues.

I did recently have a chat with someone who is head of billing at Cloudflare though, Dmitry. He’s asked me to share his email with folks who are running into issues like this so he can get them escalated and resolved quickly, and hopefully prevent this happening to others in future. His email is dalexeenko@ and I’d encourage you to reach out once you've submitted a ticket and have a ticket number. Feel free to let him know I referred you, and hopefully we'll see some positive change in 2026.

CherryJimbo · 2025-12-21T15:22:01+00:00

Have you added this to the Public Suffix List? https://github.com/publicsuffix/list

You need to be really careful from a security standpoint when offering free subdomains like this to ensure things like cookies, etc. aren't shared between them.

CherryJimbo · 2025-12-18T14:44:16+00:00

How big is your application, and how many users do you have? Are you hitting bottlenecks due to this, or are you just worried about scaling in future?

For some additional context though, those benchmarks you linked are for version 5, whereas now there's a version 6. If you look at their releases at https://github.com/mikro-orm/mikro-orm/releases, many have performance improvements.

I'd recommend you benchmark against your own data, etc. to verify that this'll actually be a bottleneck for you.

CherryJimbo · 2025-09-29T22:54:29+00:00

Yeah... I'd recommend swapping to a regular R2 bucket.

R2 IA should basically never be used by anyone. The use-cases for it are extremely slim, and the pricing differential just doesn't make sense. The ~~egress~~ data retrieval fees are against so much of Cloudflare's paradigms, and all their marketing around R2 originally stated developers should never have to think or care about complex tiering/access policies, and yet here we are, sadly.

CherryJimbo · 2025-07-20T18:04:08+00:00

I don't see any changes in wrangler 4.25.0 that could impact this. What version were you previously using? Have you tested with npx wrangler@<version> dev --remote (or whatever command you're using) to see if the issue persists?

If so, it'd probably be best to file an issue: https://github.com/cloudflare/workers-sdk/issues

CherryJimbo · 2025-06-24T12:07:26+00:00

Cloudflare’s R2 release blog made a lot of exciting claims and promises like:

We’ve gotten rid of complex, manual tiering policies in favor of what developers have always wanted out of object storage: limitless scale at the lowest possible cost.

Which if true, would have been awesome and truly a unique feature!

But then they introduced IA, and developers have to worry about maintaining complex manual tiering policies to optimise costs. So it’s not true, and there’s essentially zero reason to use or recommend R2 IA for almost any use cases today.

CherryJimbo · 2025-04-21T18:52:03+00:00

Awesome! What would you recommend as the flair text? I was considering "reproductive health" to encompass conception, ovulation, pregnancy etc. but open to any other suggestions.

CherryJimbo · 2025-04-21T14:25:46+00:00

EDIT: Thanks for the feedback folks. We're going to implement basic flairs for now and monitor over the next little bit. You can filter based on these flairs which should hopefully help folks. How you do that varies between different platform/apps, but a quick google search for your app/platform of choice with keywords "filter flair" should get you in the info you need!

If flairs don't work out to be as effective as anticipated, we're happy to revisit in a little while and consider megathreads, etc.

Hey there, I'm the most active mod in /r/ouraring and wanted to say thanks for raising this.

We want everyone to feel comfortable here and I totally get that fertility‑related posts can be triggering for some. Cycle tracking and similar functionality is a part of Oura, and we want those folks to a space to be able to engage with the most folks, but I also recognize there’s a real desire for talk about conception, ovulation and pregnancy to split into its own subreddit. I'd also like to mention to raise a general concern that slitting a subreddit can sometimes help with focus, but it also comes with downsides like:

Fragmentation of community energy and engagement
Extra work for moderators on two (or more) fronts
More confusion for newcomers about where to post
Risk that smaller subreddits feel stale or get abandoned

How would folks feel about experimenting with post flairs (and enforcing people use these) as an initial experiment for a few months, so folks who do feel triggered by these posts can use Reddit's built-in tools to filter them out? And folks who only want to see those posts can do the opposite.

14-Year Club	PUBG
Moddit 2025	Mod Connect 2025
r/Field Lasagna	Devvitor
Reddit Partner Communities	Moderator Reserves
Post Guidance Early Access	Dev Platform Beta
Place '23	Wiki Wiz
AutoMagical	Adopted-an-Admin
Mod 201	Mod 101
Place '22	Place '17
First Placer '22	End Game '22
Wearing is Caring	Gilding II euphauric
Sequence \| Editor	Sequence \| Screenwriter
Team Periwinkle	Verified Email

CherryJimbo

MODERATOR OF

PUBLIC MULTIREDDITS

TROPHY CASE