Mike Dilger ☑️ on Nostr: To whom it may concern, Quite a few nostr clients connect to my relay and then don't ...
To whom it may concern,
Quite a few nostr clients connect to my relay and then don't submit a subscription request. After 6 seconds I time them out. I think they may be getting confused by the fact that I send them an AUTH right off the bat. Clients should be able to tolerate AUTH messages, and ignore them if they don't care to authenticate.
This happens with at least 3 clients because I've seen 3 different user-agent strings exhibit this behavior:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36
Go-http-client/1.1
and clients that do not submit a user-agent
Published at
2024-04-09 19:31:24Event JSON
{
"id": "17a62825f3dfb6ada07a01160aa340e961f85cc2dccad76ec6b93c227602589e",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1712691084,
"kind": 1,
"tags": [],
"content": "To whom it may concern,\n\nQuite a few nostr clients connect to my relay and then don't submit a subscription request. After 6 seconds I time them out. I think they may be getting confused by the fact that I send them an AUTH right off the bat. Clients should be able to tolerate AUTH messages, and ignore them if they don't care to authenticate.\n\nThis happens with at least 3 clients because I've seen 3 different user-agent strings exhibit this behavior:\n Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36\n Go-http-client/1.1\n and clients that do not submit a user-agent",
"sig": "5e2ee32c31f3421383abfa09a0f75294bfba85d3ebbde56854bcdcf1f4f7d4ef175b22236b5609bff674f74b8877314456d211ac9568ef441cb55b7a6b062fac"
}