Fix oldest-first sorting after f84b0c934e60f01919818e06d16157660f8ec010
Fix oldest-first sorting after f84b0c934e60f01919818e06d16157660f8ec010

Also stop reversing the whole list, instead use negative indices (shaves ~50ms
from the response time for my read items stream).

mihaip/readerisdead,mihaip/readerisdead,mihaip/readerisdead,mihaip/readerisdead,mihaip/readerisdead