Delete a Message
antp
I see that in the last two days the "visitor" with the highest number of request was an address in Finland using this software:
https://wiki.archiveteam.org/index.php/ArchiveBot
2nd place was Bingbot, with less than half of requests, but normally it runs only in low-traffic hours now.
The first is probably not the bot of the internet wayback machine (archive.org), cf these points:
and later:
So I suppose I could block it...
Via http://archivebot.com/3 we can see it in realtime, and indeed it is fetching pages too quickly. Now page requests appear in red there, with a 503 error code (service unavailable) instead of the usual "200 ok".
I hope it will be less a burden for imcdb...
edit: I found how to contact them, so they reduced the frequency, it should work better then. Please keep notify me if you see an improvement, or if it is still very slow.
https://wiki.archiveteam.org/index.php/ArchiveBot
2nd place was Bingbot, with less than half of requests, but normally it runs only in low-traffic hours now.
The first is probably not the bot of the internet wayback machine (archive.org), cf these points:
We're not Internet Archive. (We do what we want.)
We're not the Wayback Machine. Specifically, we are not ia_archiver or archive.org_bot. (We don't run crawlers on behalf of other crawlers.)
We're not the Wayback Machine. Specifically, we are not ia_archiver or archive.org_bot. (We don't run crawlers on behalf of other crawlers.)
and later:
Also, please remember that we are not the Internet Archive.
So I suppose I could block it...
Via http://archivebot.com/3 we can see it in realtime, and indeed it is fetching pages too quickly. Now page requests appear in red there, with a 503 error code (service unavailable) instead of the usual "200 ok".
I hope it will be less a burden for imcdb...
edit: I found how to contact them, so they reduced the frequency, it should work better then. Please keep notify me if you see an improvement, or if it is still very slow.