Turns out it's nostr:nprofile1qyv8wumn8ghj7un9d3shjtnnd9sk6um5wghxxmmd9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzamhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6tcqyzse4t0w2w78r5j6lmek2pn689u2cvx42gxndmyvcaxh02rj4ae4jahuj4t. I've had 200 hits for their profile in the last 10 minutes. nostr:nprofile1qyvhwumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wshsqgr26zpe95d650m07755p832chj5gdv8yewckjjcr3sx0kyw5vq4sslntv3w any idea what's going on here?
Discussion
.3 req/sec you should see what nostr clients do to your .. oh wait..😁
Relays don't have to serve 2.8 MB for every request
Hmm. No idea.
I’ll ask the boys. Standby
I asked. There’s no jobs set up on our end.
Seems somebody is looking up Satlantis via coracle?
Yeah, it isn't automated because it's coming from a lot of different IPs (unless its a bot attack). I thought it might be more a marketing thing, but the second most common request is for a very obscure pubkey. Very weird, I'm looking into the possibility that it's a bug on my end. Thanks for checking.
Hmm. Weird. Let me know what you find buddy
Trying to understand the issue — what exactly is the problem, and is nostr:nprofile1qqs2rx4daefmcuwjttl0xegx0guh3tps64fq6dhv3nr56aagw2hhxkgpzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2vxprm6 causing it in some way? If it’s something from our side, happy to help resolve it 🙌