Many relays operate in this way, no? They only ask for AUTH after a REQ if the REQ or EVENT needs auth.
I don't think it makes sense to wait for AUTH upon connection.
Many relays operate in this way, no? They only ask for AUTH after a REQ if the REQ or EVENT needs auth.
I don't think it makes sense to wait for AUTH upon connection.
But NIP-11 says
auth_required: this relay requires NIP-42 authentication to happen before a new connection may perform any other action. Even if set to False, authentication may be required for specific actions.
*any other action* - so to support relays that have auth_required=true and don't immediately send the challenge I would have to basically ignore the auth_required field...
That seems like an error in NIP-11. I have seen relays send AUTH at a lot of different times. Sometimes only certain actions are gated behind auth (like requesting content from a closed NIP-29 group).