It's a known bug. The list of items L0 you initially loaded changed, so when you hit more you are viewing the next 21 items of L1 (which may contain some of the first 21 items of L0).
I was just digging into this and there's a cursor identifier passed with the request. I guess this means that the cursor isn't stateful in the backend?