Hey! NIP-42 is about client auth, and I can see how that can be confusing bc write events are signed. The challenge is that read requests are not… not to mention sometimes websocket connections for a given user are used to rebroadcast messages for other users. So occasionally you’ll even see events come through for more than one pubkey on the same connection. NIP-42 is a spec that would allow for the websocket connection itself to be authed so that the relay can know immediately on connection who the connection is with. This is useful for private relays, or relays that have some more specific read policies.