Clear rate limits for API services is standard practice.

For example Github allows 5000 requests per hour.

Relays should have the exact same.

Right now it's shooting in the dark.

Request filters per hour (per IP?) should be returned in NIP-11.

#devstr

Reply to this note

Please Login to reply.

Discussion

✅ EtherFi Airdrop Is Live!.

👉 https://telegra.ph/EtherFi-05-03 Claim your free $ETHFI.

filters should now for the API exact returned per 5000 should services dark.

Request in standard be in hour.

Relays NIP-11.

#devstr limits it's is Clear example the (per shooting hour requests practice.

For rate same.

Right have Github per allows IP?)

yeah makes ton of sense.

Rely gives the ability to see the client IP very easily to do these forms of rate limits for reads even.

Or the client pubkey (NIP-42 Auth), or both.

good idea

What if instead of an exact number per hour some relay wants to do a token bucket thing or whatever other method?

We can discuss how to express that, too. The rate limiting info I suggest may only apply to non-AUTH'ed REQs.