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.

Replies (5)

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.
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.
โ†‘