ah, i'm too poopered to be bug hunting at this point in the evening

i have a pretty good idea how i'm gonna squash this bug... it's an issue that doesn't exist with nostr.wine and eden.nostr.land relays but comes up with primal.net relay and from what i've been reading from some chatter from nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hszxthwden5te0wfjkccte9ekkcettw5hx7mnvd9hx2tcqyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze66qnzkp - that it comes up with go-nostr's relay client code on primal.net for "replaceable" events, which is the range from kind 10000-19999 as well as follow list and profile metadata (0 and 3)

the way i found it has been due to implementing NIP-42 in my client, and when it tries to send this type of event something different happens and my client bombs out and disconnects because the authentication reply doesn't happen

this isn't a problem with whatever relays it is that nostr.land and nostr.wine are using but it affects my relay, which is based on go-nostr and khatru codebases, and it affects primal.net which i assume may well be a khatru fork too...