mleku on Nostr: oh yeah, something that might help to understand, in fact, over websockets, all sends ...

oh yeah, something that might help to understand, in fact, over websockets, all sends are acked, and return an error if they time out, so you don't really need an ack in the protocol

but you need an ack for EVENT in the sense of "invalid event/not storing/duplicate/other error" so the role of OK is something like a machine-oriented NOTICE, and NOTICE is something that clients should show to the user, whereas OK isn't intended to do this, the user can even just receive "Something Went Wrong" as javascript devs are wont to do