@PABLOF7z your relay.nsecbunker.com doesn't reply with OK to ephemeral events, which causes my single-threaded nak bunker to have to wait many seconds for a timeout before it proceeds to process the next RPC request after publishing the previous request, it's horrible UX and I won't fix, you must!
gm @fiatjaf
nostr:nevent1qqsvlsz2c9cx2z6hx2lkeeyhlxhmm5rmvkwz9qpg2vadtdm8hl97y8gpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqvzqqqqqqyug8qme
OK
`publishing to wss://relay.nsecbunker.com... failed: context deadline exceeded`
👇
`publishing to wss://relay.nsecbunker.com... success.`
you should consider making it multithreaded tho
i've just bumped up against a bug involving a client not receiving an ok message from the relay (my khatru based relay) and it stalls the NIP-42 protocol and causes the client to time out and die
the common factor every time is that i get a log printing "replaceable event" which i put in there, and clearly the replaceable event code is not sending the ok
guess who wrote the original version i forked from... no, i'll wait
nostr:nprofile1qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgcwaehxw309aex2mrp0yhxxatjwfjkuapwveukjtcqyrafsj7hmweg9ur7zmn6apajdg48hxuskujx53rhrux0ttjcqx84yx35fg2 this is actually a bug in go-nostr
I didn’t write go-nostr 😅
I think that’s another creation of the @fiatjaf
Oddbean new post about login | logout