nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z you were right, there was a bug on our side, not just a strict limit. the read throttle is a per-IP byte budget (~1 MiB/min). when it ran dry mid-query we silently dropped the rest of that batch, kept scanning, and still sent a no...