← Back to context

Comment by dawnerd

15 hours ago

It’s also a “you can’t scrape us but we can scrape you” mentality these companies are getting into.

It really sucks for small businesses. Their websites get absolutely hammered and they can’t afford or don’t know how to stop it. Cloudflare ends up winning as they’re the easiest solution.

In the spirit of open source thought about it and created sibuna (https://github.com/insanai/sibuna)

It works similar to cloudflare WAF but is an open source software. It can be on your own infrastructures even if its a $5 VPS.

The idea is same let the bot or AI agent do more work than it takes to serve that request. Also it needs to follow rules, similar to cloudflare enterprise web application firewalls. It was OWASP CRS and J4A TLS support.

Cloudflare doesn't even stop bots very well. Many bots are using real browsers, which pass all fingerprint checks, and scripts that can click the checkbox. What Cloudflare has is mindshare, and being a checklist item and an accountability sink.

> Cloudflare ends up winning as they’re the easiest solution.

What prevents other hosting sites from providing similar tooling?

  • It's a cognitive tax on all the parties involved. It works on buyers (websites that pay for it) much the way that llm's work on their users, by working up to the point at which the buyers can't discern it working.

    As a user (bot or flesh) you have to jump through these hoops, and to the website operators they get fewer complaints when users (and bots) are able to contort themselves in predictable ways. Versus you'd perceive as a website operator, if your blocking worked at all, that you'd risk seeing a precipitous dropoff of bots if you did things in bespoke ways, as both bots (true positives, among dd and cf survivors) and people (false positives) get jammed.

    The net effect in this model would be that such things as cloudflare and datadome take money from websites in order to block "dumb" bots and enfranchise "smart" bots to the point of creating a market for bot services. People that want to bot have to use AI or go to bot service providers.

    For website operators that's a worthwhile exchange for dollars, in that dumb bots can cause a lot of harm in wasted compute. Bots are typically dead end users who won't buy ever anyway, or merely inefficient way of doing business if they scrape excessively. And many do scrape excessively.

    "reform school for bots" is a good mental model. For this to work, the "reforms" have to be consistent so that bots can conform to them.

    It's a peculiar equilibrium and I am not sure that it's all that stable as an equilibrium. Would be a good subject for a formal treatment, game theory and economics.

    • Huh. I would expect even a nominal time or monetary cost would prevent spambots from being able to scale. That seems like a net good.

  • Mostly economies of scale. They have enough data to do the statistics to identify bad actors, and enough bandwidth and servers to facetank the request volume.

Saying this to a group of people who hold ad-blocking in the highest regard is near peak irony.

what solution is there other than cloudflare that a small business (with decent dev knowledge and claude/codex) could use?

  • Cloudflare is probably one of the most popular, reasonably priced for general public. You have fastly, akamai, cloudfront as other proxy providers and CDNs with similar capability but higher price point mostly catering to enterprise customers.

    Bunny.net is another one that I find similar to Cloudflare from pricing and functionality perspective

  • Depends on the small business obviously. I've been in IT for 40+ years and enjoy torturing clankers; I ran a bot motel 20 years ago. These things are so badly written, and obviously they don't care because they're not truly conscious, but the meat in charge is ignorant or doesn't care. So web scraping, and the point cloud of nearly indistiguishable abuse it travels with, is pretty easily tripped by some simple technical tests and salting of content. At least mostly.[0]

    I've been wondering to myself "how can I get people to go through a login process without going through a login process?" for a few months, and I've come up with a simple solution which I'll be implementing in the next few weeks.[1] Like the other technical measures it doesn't identify bots but there will be a gate with backpressure that at a point in time a given IP address has some probability (adjusted in realtime based on $things) of passing through, and through my mysterious process is then "logged in". Then that address is pretty much given a free pass as long as its behavior remains "human". Real humans may be denied access initially and have to try again, and their luck will be affected by how aggressively the bots are fighting it out at that point in time. This isn't much different than the extant reality, but it is in terms of what happens after an initial successful page load. It's an experiment, I'm hoping it's tunable so that the experience is more or less indistinguishable from the status quo; we will see.

    I'd love to find a group of likeminded individuals where we can discuss some of this TLP:YELLOW or Chatham House Rules. If you are savvy enough to hunt me down and can demonstrate that you're a real human, small operator, and that you can keep things closely held I'll talk with you, if you want someone to run your mitigations that would cost money.

    [0] Had an episode last week where somebody scanned approximately 1000 URLs (maybe 60% of the discoverable URLs) over six hours. 1200 addresses fetched exactly one URL, another 400 or so fetched two or three. Every one of those URLs was fetched exactly two times. Real showshoe stuff, nicely done.

    [1] Firewall rules and fail2ban. I give fail2ban special powers in terms of the logs it follows and the actions it can invoke. Conntrack without conntrack (of course the firewall has conntrack, it's just not the best option for this use case).

  • TikTok, Instagram, X, etc. These platforms will host you for free and will distribute updates to people, including potential customers via the algorithm.

    • Those are no longer useful as a "public square" because of the increasingly walled garden design.

    • Funny that I can't barely access any of those just because I don't have an account. Plus Facebook. They show me almost nothing and push their shitty app to nausea. And I am sure the "site" owners get zero info on how many clients they are losing for being behind that fence.

      2 replies →

    • I'm not sure just skipping the scraping by providing your data directly for harvesting is the solution

Small businesses should be the people happiest about AI scraping. It's a new venue opening up for them to sell their products and services. And it's easy and free to use Cloudflare so that you don't have to worry about excess traffic, if you don't want to use a different solution.

Does it suck if you offer a product and someone’s looking for it and the agent can’t look on Amazon but they can look on your small side maybe that’s good

  • Dude, I had a 1Gb of nginx logs daily then I blocked them and it dropped to 10mb weakly.

    • Legit what one of our clients problem was. Normal web traffic wasn’t an issue and the logs were just a few megs. Yeah there was a problem where they were not rotating but once meta started crawling them 24/7 ignoring the robots.txt it kept filling their vps up. An annoying problem to fix once a server is completely full and you can’t even ssh in.

    • There are also some pathological bad use cases out there that are caused by the combination of trying to scrape all the content, a randomized param, and the scrapers trying to be anonymous. The one I've encountered is pbpBB.

      phpBB will assign you a randomized session if if you visit it anonymously (without logging in), and will serve the page to you with that sid param added to all links. Using that link will load a page without the sid param appended to links, because the system assumes you have a session I'd saved in a cookie since it saw you have a sid, even I'd you don't have/didn't send a cookie with it. Following any of those links starts the chain over if you aren't sending a cookie along with a sid, which the AI scrapers never do so they can't easily be blocked by that, and a new unique sid is generated, and all the links have the new sid appended.

      Every page with a unique set of params and values needs to be investigated, because it can be an entirely different page, so AI scrapers will scrap forever, always finding more and more URLs to harvest, even though they're all duplicates of what they already have. It's easy to have multiple scrapers stuck going through a very small bulletin board continuously.

      Maybe they've gotten smart enough to deal with this situation in the last few months, or maybe they put in a specific workaround. I ended up just throwing the site behind cloudflare because spending time trying to outsmart AI agents in a battle of escalation doesn't seem like an effective use of my time.

    • 30GB a month isn't too terrible? I guess it depends - for example my provider includes 10TB egress per month, so 30gb would be negligible if it's static content. I'm not sure what others do, but I often click on the links that the agents pull up as sources so the websites do get more discoverable.

      What really sucks is e.g. Gemini that pulls images without being able to go to the source (unless it changed recently.)

      Edit: I didn't read "logs"

      3 replies →