what is it, does it spam the relay with random requests to see if something breaks?
Discussion
nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx has his thing that does something conceptually similar
The tests I have aren't random because then its difficult to meaningfully communicate the outcome. Instead it each NIP had a test suite, and then each test in the suite attempts to obtain samples from relays and then uses the uses those samples to construct filters than satisfy the respective test.
I picked the word “conceptually” very carefully 😉
They are conceptually much different 😂
Both useful on different ways. Randomness is great in fuzz testing and finding edge cases that are difficult to find without randomness, the auditor I wrote is better for unit testing known vectors to validate expected behaviors.
And to be clear, they are complimentary and so is relevant. Just wanted to clarify the functionality.
yes. random requests, random events, random filters, random disconnects...
I've found so many weird bugs, like the unregistration queue filling up causing all threads to be blocked