db0

I am not mad at you.

In that thread I learned that he went for a interview with the outright fash (Tim Pool), so...yeah.

If they haven't taken action against the the genai scraping bots going around, it's likely what causing those slowdowns

Just first I run into and was easy to deploy

Thanks. Iocaine doesn't do detection, it only does the poisoning. The detection is currently manual. We do it based on agents and ip ranges. These bots are extraordinarily stupid atm, which is what is the biggest issue. The ones causing us down times were hitting obsolete domains and stupid links constantly. They are very very crude. They are not sophisticated yet to check DOM but they can tell when they've been blocked and switch to proxies. Sending them to iocaine is meant to not let them realize they're blocked.

Obviously someone smart can easily defeat it, even by just respecting our resources. But these fuckers are very greedy atm. We'll have to evolve along with them.

It's not about the load. It's about not letting the bots know they've been blocked and making them switch to residential proxies and thus making them harder to block.

Hm, probably something that can encompass both 3rd party instance and comm matters

I'm trying to prevent confusion with topics about this comm

I feel this is more of a topic on the moderation practices of a different comm, should have a more specific tag. [comm meta] or [comm policies] perhaps

I'm going to let this up, since it might affect future posts in YPTB. But I think we need some sort of [tag] to assign to these posts to make them easily findable in the comm. It can't be [meta] since that should be about comm-internals. Any ideas?

Blocking whole regions sounds like overkill. Just block the alibaba subnets. We do the same on our end. If you want I can provide you the cidr ranges.