Is there an order by in NIP01?

I wanna pull data sorted by created at.

nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1cgd35mxmy37vhkfcmjckk9dylguz6q8l67cj6h9m45tj5rx569cql9kfex nostr:npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f #asknostr #nostrdevs

Reply to this note

Please Login to reply.

Discussion

you can only order by descending created_at via limit

(I added limit as a last minute thing, didn’t want to hard fork it too much)

so there is a scope of introducing order by in future?

Possibly, its becoming harder to touch nip01 now though

Do relaypool abide by this sorting?

Most of times, it works as you said but sometimes the order is random in query results

They can come back in interleaved order if you’re using a relay pool, so you need to do an insertion sort when putting them into a timeline

understood. thanks

If I am to use just one single relay and I am loading 20-30 posts per load, would using relay pool be better or a single relay is a better option.

I am using relay pool but the feed on my app is barely refreshing. Same content always. Not sure why.

Could you suggest a better way?