Fix pagination#2407
Conversation
|
Couldn't I just send a bunch of events with the same created_at to fill relay pages and force them to implement a default limit of a million? Dynamically setting this limit seems complex too. Here's another idea: what about just adding a |
|
Relays are free to delete those events if people abuse. My take is that we don't actually need to change anything... We just need relay operators to know their limits might be making it impossible for clients to get their complete data. |
|
Even so, this could negatively impact scaling. Let's say a big relay reaches 10k tps without any abuse. Now pages have to be 10k minimum. It's a weird thing to couple. |
|
They can do dynamic limits too. If the req happens to go over the dense created at, that page returns over the limit, the rest is fine. |
Sharper language
Describes a foolproof way of doing this without extra commands or information.