Not exactly sure how to handle it but … rate limiting that doesn’t break the spec?
Ex: IIRC, nos.lol would “rate limit” my queries by
1) sending a NOTICE to “slow down”. (Notably absent, any subscription ID.)
2) NOT sending an EOSE, CLOSE, or any events for the query that caused triggered the limit.
… Which can make a naive client hang forever waiting for messages that are never coming.
Cody /
npub1m3…7mn6s
2024-05-30 22:19:10
in reply to nevent1q…fm80
Author Public Key
npub1m3p39ertpcuzzpw32s5scsv7vp48xgqye4eqmmceyyqtj9dphxkqz7mn6sPublished at
2024-05-30 22:19:10Event JSON
{
"id": "c315df1b2c1539cd264d339f96aa38013d4acff3090d563f795148eee7554d88",
"pubkey": "dc4312e46b0e382105d154290c419e606a732004cd720def192100b915a1b9ac",
"created_at": 1717107550,
"kind": 1,
"tags": [
[
"e",
"9f1cbe9c0432b0f756ad336d57481cce7072170d6433bccb6830122e597aa3ae",
"",
"root"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "Not exactly sure how to handle it but … rate limiting that doesn’t break the spec?\n\nEx: IIRC, nos.lol would “rate limit” my queries by\n1) sending a NOTICE to “slow down”. (Notably absent, any subscription ID.)\n2) NOT sending an EOSE, CLOSE, or any events for the query that caused triggered the limit.\n\n… Which can make a naive client hang forever waiting for messages that are never coming. ",
"sig": "910de0db51be8cad29062ee29bff5b9cb2d43d8c2a08925d06eeb1cd1348965d09c05febb7e6818ea39817a1722f0651a5bb5bde14778d3f34ab731ce85f54e0"
}