I think I kept the lazy-loading logic from you, nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn , but it loads the 30040s immediately, and then the others trickle in. So, the cards appear quickly and the other data follows, at a delay.
I can't remember. What do you think is best?
I'd expect the "clear" button to clear the query in the search bar, as well, on an intuitive level.
I like the lazy-loading. We can do that easily via WebSocket connections. Send out a query to relays, setup a subscription, then sort the responses as they trickle in.
We have to make sure we have a limit on the number of search results returned, and pagination logic, or else we'll overwhelm the browser and network with an endless stream of matching events.
It's set to 100, at the moment. Was thinking maybe a smaller number for card view than table, tho, because of the image loading.
Maybe 32 for cards, and 128 for table? Those should be user-configurable.
probably should be dictated by the device based on its performance capabilities
it really depends on how fast the interface can assemble the list, and adding new elements.
Also needs to be a bit dynamic, for the grid view, as it's 3 columns on Laptop/PC, 2 on Tablets and 1 on Phone. So, you need mutliples of two or three, to keep from having an unsightly gap, at the bottom.
