nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hszxthwden5te0wfjkccte9ekkcettw5hx7mnvd9hx2tcqyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze66qnzkp this is a demo of the same bug you are experiencing

https://v.nostr.build/87qG.mp4

it is choking on 10002 events in both cases i demonstrate

either the khatru based server side is not sending an ok, or the go-nostr client side is not receiving the ok and the context deadline is expiring

looking closer at my logs i see that on the relay, what seems to be happening is that it's sending out a burst of 10002 events before whatever craps out the client, i mean like 10-20 10002 knid events and then it shits itself

that is just one screenful, there is two or three more above it involved

it sorta looks like your code must be jamming up because of a cluster of 10002s

probably the relay.primal.net is sorting its results by kind intermittently, i guess, but i think something in the go-nostr code to do with replaceable events is shitting itself in response to such an onslaught

i will nail this bug tomorrow and you can count on me atting you tomorrow with my solution

Reply to this note

Please Login to reply.

Discussion

i am not sure at this point whether it's in the client code or in the relay code or both, i strongly suspect it's a combination