Live data from Hacker News

Cloudflare crawl endpoint

developers.cloudflare.com

161–170 of 194 posts

Re: Cloudflare crawl endpoint

#161
post #160

Doesn't work for pages protected by cloudflare in my experience. What a shame, they could've produced the problem and sold the solution.

That’s what they are doing. This is a textbook protection racket. “Buy Cloudflare bot protection, otherwise it would be a shame if your site got scraped and ddos’d.” Who is doing the scraping and ddosing? Cloudflare.

[deleted]

Re: Cloudflare crawl endpoint

#163

It seems like there's a missed use case: web archiving. I don't see any mention of WARC as an output format. This could be useful to journalists and academically if they had it.

GETOLD /index.html "2026-03-11T10:30:45Z" would be such cool functionality...

Re: Cloudflare crawl endpoint

#164

Earlier quoted context omitted.

fuck firecrawl. they copied my idea by showing interest in my product and then copied it, used their YC money to give it all out for free. fuck nick in particular. I'm still salty over this

"they copied my idea by showing interest in my product and then copied it". What exactly is revolutionary about Firecrawl or your product? Scraping APIs have been around for over a decade.

I was the first to return markdown and use reader mode stuff to strip irrelevant stuff. Theres copying and there's talking to the founder sounding interested to have your team copy what I did in the background. One is fair game, the other is a dick head move.

Re: Cloudflare crawl endpoint

#165
post #153

Doesn't work for pages protected by cloudflare in my experience. What a shame, they could've produced the problem and sold the solution.

That's too funny. If true, really looking forward to the Cloudflare response here. I'm unsure how you would spin that in a way that didn't seem self-serving.

It's very clearly disclosed in the linked docs already, it says that Cloudflare Bot Protection will block it same as all other bots, unless you choose to allow it as an exception. If they didn't do it that way, people would accuse them of either bypassing their own product (possibly anticompetitive) or just having a low quality one.

Re: Cloudflare crawl endpoint

#166
If anyone is taking feature requests, could you add an option to return the snapshot as an MHTML with all static assets embedded? (I know this could get inefficient from a storage perspective, but if it really matters you could dedupe assets on your end, which is what my janky homegrown crawler does.)

Re: Cloudflare crawl endpoint

#167
post #160

Doesn't work for pages protected by cloudflare in my experience. What a shame, they could've produced the problem and sold the solution.

That’s what they are doing. This is a textbook protection racket. “Buy Cloudflare bot protection, otherwise it would be a shame if your site got scraped and ddos’d.” Who is doing the scraping and ddosing? Cloudflare.

In this case, sure... that said, I've worked on a few sites where more than half the traffic was bots because the content was useful for other sites (classic car classifieds/sales site). The fact that just over half the page requests were actually search query results is what meant a lot of optimization steps in practice... Implementing a "search" database (mongodb and elastic were pretty new at the time), denormalizing a lot of the data structures on the "enterprise" SQL structures for search and display for not logged in users, etc. Heavier caching, donut caching, etc.

It was an interesting and sometimes fun part of my career. Working on a site/application that isn't necessarily a tech site, and that I have a personal interest in was pretty great... some of the pace for sales/commercial features less so, with sales making deals requiring deep integrations on impossible timelines. You learn a lot when a self-hosted site is being kicked while it's down... The cloud migration to get a better use of flexible resources, etc.

Re: Cloudflare crawl endpoint

#168

Doesn't work for pages protected by cloudflare in my experience. What a shame, they could've produced the problem and sold the solution.

Came here to write this. I am getting much better results from Firecrawl (not affiliated with them, just a happy customer).

As someone who helps keep a site online with a lot of content, I have mixed feelings on Firecrawl.

On one hand, their bots seem much more well behaved than others.

However, running a crawler fleet which is deceptive and evasive in its identification and don't honor REP is no way to build a business.

Re: Cloudflare crawl endpoint

#169

It seems like there's a missed use case: web archiving. I don't see any mention of WARC as an output format. This could be useful to journalists and academically if they had it.

And while at it, ability to mount the resulting archives at some virtual root in nginx|apache. E.g. serve site-archive.extension at /somepath/site. And standalone simple webserver that can take one or more archives from command line and servers them.

Re: Cloudflare crawl endpoint

#170

Earlier quoted context omitted.

"they copied my idea by showing interest in my product and then copied it". What exactly is revolutionary about Firecrawl or your product? Scraping APIs have been around for over a decade.

I was the first to return markdown and use reader mode stuff to strip irrelevant stuff. Theres copying and there's talking to the founder sounding interested to have your team copy what I did in the background. One is fair game, the other is a dick head move.

Not sure about the first claim. But yes, talking to the founder, sharing details and having it stolen is not a good look. Sorry that happened to you.
Post reply on HN