nip 42 flow forces clients to often have to resend events at the beginning of opening a websocket. there should be an ack so the client can just send it once after they know if the relay has allowed their storing of events, just once.
Login to reply
Replies (1)
hmm, they'd have to send some event in any case in order to be ack'd, otherwise the relay can't know who's socketing... only alternative I could think of is pro-active auth, fail/retry is probably the simplest