Natanael

Sprinklers and all kinds of stuff are more efficient with sensors and electronic regulators

The API has the wrong abstraction and the type definitions fail to capture necessary information (such as in which year you were of the given age) and thus conversions can not be guaranteed to be correct

How to we know what to test? Maybe with some kind of specification?

Of course a group of people could use violence to oppress other people. But then you no longer have anarchy.

The irony is that the amount of coordination needed to protect anarchism would no longer be called anarchism

You will always end up recreating some form of organizations to manage resources. The best you can do is ensure those organizations are structured with accountability to make sure they’re fair to everybody

If you’ve already noticed incoming traffic is weird, you try to look for what distinguishes the sources you don’t want. You write rules looking at the behaviors like user agent, order of requests, IP ranges, etc, and put it in your web server and tells it to check if the incoming request matches the rules as a session starts.

Unless you’re a high value target for them, they won’t put endless resources into making their systems mimic regular clients. They might keep changing IP ranges, but that usually happens ~weekly and you can just check the logs and ban new ranges within minutes. Changing client behavior to blend in is harder at scale - bots simply won’t look for the same things as humans in the same ways, they’re too consistent, even when they try to be random they’re too consistently random.

When enough rules match, you throw in either a redirect or an internal URL rewrite rule for that session to point them to something different.

The trick is distinguishing them by behavior and switching what you serve them