I don’t think aggregating by timeframe would work well. For example, when browsing large relays like relay.damus.io, even aggregating notes from just 24 hours could be very difficult and would definitely hit the relay’s rate limits. On the other hand, for smaller relays, there might be so few notes in 24 hours that aggregation wouldn’t even be necessary. I’d prefer to aggregate by count instead — for example, every 500 or 1000 notes.
Login to reply
Replies (1)
I read you already advanced this proposal in the past, but it doesn't accomplish the goal of surfacing profiles that post rarely, it's a completely different view.
About browsing relays, that is a secondary feature compared to browsing the following list with that goal in mind, it could be fixed adding a sufficient delay. The only different approach, that I think is the correct one, is to have a local DB caching data for the last X days.