this should be interesting, since coracle (and I think others) use a windowing algorithm to force sort order. Will the relay respect that or ignore since/until? Seems like there are downsides to both approaches 

 clients also discard ordering info

I think we should add a new REQ-like message type meant for this with cursors 

 The relay will provide the list in what it believes is the best order, but clients can choose to use it or not or just sort by timestamp if they want  

 More specific it's not going to intake any req params, you will just hit a single endpoint like my relay.com/popular/today and it just gives you a list of k1s 

 Is there a way to give the user control over the parameters? Or to change the parameters based on individual preference? 

 Maybe in the long run, to start it's gonna be pretty dumb and basic  

 Will be cool to see what you come up with 

 Doesn't clients usually force the order of incoming data? I think so. 

 Well they will have to make some updates then 🤠 

 It's also quite fiddly to switch  between relays so feed to only show certain relays, afaik.

They could appear on #amethyst on the drop down like lists currently so maybe? 🤔 nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau just an idea