could be related to the spam in global and the general slowdown of clients when this started happening?
Discussion
could be, but this is web traffic to nostr.io.
roger.
I may have shot myself in the foot with the stats graphs.. I'm going to do some seat-of-pants caching
turns out it was a bot: https://mj12bot.com/
they did try to read robots.txt, which I didn't have. that's fixed now.
strange behavior though, they were walking through events ids in lexical order calling the thread endpoint nostr.io/t/
yeah, that would definitely cause a performance issue. glad you got it fixed.