You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The batched listings code is up on Mainnet now. It splits the block range of [genesisBlock... ethereum.blockNumber] into 10k chunks and blasts capi with calls, pulling down all ffa listeds (or candidates) that have ever existed. Right now that's fine but in the not too distant future that's likely to break.
We need to come up with a strategy and UX for showing listings.
Maybe just an infinite scroll?
The text was updated successfully, but these errors were encountered:
I can see how UX changes (like infinite scroll, pages, etc) will help when we want listings to render in the order they were created, since that will naturally limit the range of blocks that need to be queried at a time.
But what about other groupings / orderings. For example, all listings that belong to a given user?
The batched listings code is up on Mainnet now. It splits the block range of
[genesisBlock... ethereum.blockNumber]
into 10k chunks and blasts capi with calls, pulling down all ffa listeds (or candidates) that have ever existed. Right now that's fine but in the not too distant future that's likely to break.We need to come up with a strategy and UX for showing listings.
Maybe just an infinite scroll?
The text was updated successfully, but these errors were encountered: