💾 Archived View for ainent.xyz › gemlog › 2022-04-21-bad-bot.gmi captured on 2023-04-19 at 22:32:35. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2022-04-28)

➡️ Next capture (2023-09-08)

-=-=-=-=-=-=-

Bad Bot?

At precisely 2022-04-21T06:02:02.444-0000, a Swedish IP starting hitting this Gemini server. Over the course of the following 133 *milli*seconds, the same IP sent no less than five hundred thirty-nine requests. 539. In 133 milliseconds.

With this limited data, I have to assume that the the source is 1 of 3 things, most likely the first:

This started with a request that resulted in a Gemini 59 response code (bad request), and every other attempt was rate limited with a Gemini 44 1 response code (slow down, wait 1 second before trying again). None of these were respected. At the same timestamp as each response, there is also an SSL error. I have not yet looked into what this specific error means, but it looks as follows:

2022-04-21T06:02:02.449-0000: SYSTEM: ERROR: Error: Error code: 6(0x6), ERROR: SSL_write, code: 6, reason: EVP lib

Needless to say, this is not ok. If this is a bot, and you own it, stop it. If I see it again, I will publicly list the IP of the offender right here on this gemlog. I may even reach out to the ISP, whose name I can see very clearly from a reverse DNS query.

If this was an honest mistake from a client developer, then please reach out and let me know and I will provide a new post that is not so annoyed.

That is all.