Yes, I will offer it as a relay however clients are going to sort whatever notes we give them by created_at time (unless they create a separate view).
So I can say here are the top 50 notes from the last 4 hours, but they won’t be ranked by popularity beyond that, only time.
How about a new TOP verb for relays that would accept filters like REQ does but would return a list of ids of "best" events? I have it implemented on relay.nostr.band for kind 0 and 31990 and used in a couple places already our clients. You would get say top 100 ids and then would load events themselves in batches for pagination.
Requires new code on clients ofc but seems like a good general approach.
I’m in to it, thanks for pushing us forward. Happy to adopt whatever standard you guys are using/building. Interoperability of our services is key.
