fiatjaf's avatar
fiatjaf _@fiatjaf.com 1 year ago
@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!

Replies (7)

PABLOF7z's avatar
PABLOF7z _@f7z.io 1 year ago
OK `publishing to wss://relay.nsecbunker.com... failed: context deadline exceeded` 👇 `publishing to wss://relay.nsecbunker.com... success.`
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ's avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ me@mleku.dev 1 year ago
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 @PABLOF7z this is actually a bug in go-nostr
1 replies ↓
↑