I also thought this initially, but actually the time-span group is browsed in sequential chunks, so we can lazy loading them.
The only cons of this i approach seems that you cannot have the real total count for every user of all the published events.
Login to reply
Replies (5)
Wait, I'm confused. I thought you were fetching all follows from last X hours into a map in cache and displaying that, with lazy-loading in the rendering step, when someone clicks on an entry.
How does this work?
This is really good, by the way. I'll host it on my
.

Jumble
Jumble - Imwald Edition ๐ฒ
A user-friendly Nostr client focused on relay feed browsing and relay discovery. The Imwald edition focuses on publications and articles.
It's like that, but for long ranges, e.g. 5-30 days, I actually can load only the events necessary to fill the viewport and permit some scrolling. So I have to query all follows, but for a limited time-span, and then load more in chunks.
An AUTH aggregator like aggr.nostr.land really shines with this view @semisol as you can deliver big data fast without triggering rate-limiting.
This actually helps frequent posters, too, as you can filter them out, temporarily, instead of muting them. Even if you only used this view, they'd reappear during times when they were quieter.