Building bots to mend badges, or how to get your GitHub account suspended
The answer to this is to do human rate limiting.<p>Build your pipeline so that a human has to approve each automated action being taken. The difference between a bot making 5000 network requests in a day and a human making 100-200 semi-automated requests isn&#x27;t a whole lot in terms of throughput, but makes an enormous difference in terms of quality control and not stepping on toes.<p>I really wish more companies would do this. Fully automated business procedures that make demands on human attention are just plain awful. Humans should be interacting with humans, machines should interact with machines. Machines can help the human, and the human can help the machines, but interaction points should only be between two of the same types of entity.<p>Every time I&#x27;ve ever suggested human rate limiting though, I get looked at like I&#x27;m a moron. Even when I build the entire workflow myself and tune it so it only takes a relatively tiny amount of time to clean massive amounts of data, people just don&#x27;t want to do it. It&#x27;s beneath them. Even when it creates a massive difference in the quality of the product &#x2F; service you&#x27;re offering.