Nostr Web Client

Notices from relays need more info. I was getting this from relay.nostr.band and I have to guess what the issue is.

error: too fast, slow down please

- am i making too many requests in a period of time? if so, whats the rate limit

- am i retrieving events on a subscription too fast? is that possible or is that controlled by the relay and i get an eose to determine end?

im guessing its an unpublished rate limit and have added an arbitrary delay. but i wish i knew more of whats going on. relay model is really bad for comms without a standard message protocol or status indication when one side has a policy the other is unaware of.

Reply to this note

Please Login to reply.

Discussion

Derek Ross 2y ago

i would assume that you're most likely submitting too many events in a short time period. which sucks, if you're scrolling and giving a reaction to all of the notes in your feed. you'll hit this hidden rate limit fairly quickly. i get the reason for having it though, to prevent spam.

Nice and Kind Vic 2y ago

yeah. i can guess, but without a policy i either knee jerk back request rates or try to discover the policy via trial and error

Nice and Kind Vic 2y ago

Also worth noting that normally these notices just get swallowed to /dev/null, or sometimes logged. User clients generally dont expose this stuff. because it would be bad UX as its unactionable in its current form.

nostr:nevent1qqsqv70jc77xnptydh8kahrc0pfxhzpxkker4s9dc6yjajw7ee74spcpvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c3309urvur209cxgdrjxacksvn809ek56rkdfjrjmpjddknv6rwd56xzmtyde48j6nhxv6rvdmx0ycr2unxxpckvuphddaxz0mzwfhkzerrv9ehg0t5wf6k2q3qyx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qxpqqqqqqzzxmypf

cloud fodder 2y ago

Ya, that's not very fun. The good news is the spec does have a lot more good stuff if people implement it. Nip11 limit descriptions, and messages per-reject with a specified 'reason'. Course it's up to the mods to set a reason, but it's there none the less (it does not reject silently).