3 ms·
Yea these AI bots are getting out of hand. The article mentions that some requested pages are less likely to be legit traffic (old commits) and more likely to
by trashb 1mo ago
Yea these AI bots are getting out of hand.
The article mentions that some requested pages are less likely to be legit traffic (old commits) and more likely to have bot activity. Perhaps they could increase difficulty on those pages for the proof of work. Keeping the "current" at a lower difficulty allows most normal users to use the pages as normal, while penalizing the bots.
One other way I have been thinking of is just delay the delivery of the pages, either limit bandwidth or just wait for a bit until you deliver the page. For one user a (lets say max)3s delay on some pages is not a huge deal, however at scale that adds up and means the client can't gather other pages in the meantime.
Another option is to lock the out of date html renderings behind a login page while keeping the git openly available.
- nxobject 1mo ago> One other way I have been thinking of is just delay the delivery of the pages, either limit bandwidth or just wait for a bit until you deliver the page. For one user a (lets say max)3s delay on some pages is not a huge deal, however at scale that adds up and means the client can't gather other pages in the meantime Or some kind of vintage “set up a request in a form and press a submit form, and we’ll pretend to take a while to put things together.”
- trashb 1mo agoHowever you can implement it. There are several options but probably you'll want to do it server side since I believe most bots don't run javascript. If you search there are ways to implement something similar in nginx using modules or buildins.