@redweasel  
But that’s all the fun of coding, isn’t it? :p

@Cirrus Light
 
no, I see a lot of 3 month old pictures, and it also keeps popping up pictures I’ve already seen, even though slot #1234 stays slot #1234 for all of time. it’s just one of those things that’s not annoying enough to spend hours trying to find the error.

@redweasel  
Is it the very unlikely thing that happened because there were enough rolls?

@JerryEnderby
 
well, taking a look at it, back in june of 2015, I added some code that changed the order from random() to (created+random()*100)/(created+100). the effect of this would be identical to random(), except that as the number of seconds since the epoch increased, it would become less random. so images posted in 1970 would have totally random order, while images posted today would have… 0.000006% randomness in their ordering, as if they weren’t random at all. why I did that, I have no clue. considering that your post was 3 months old, that’d still be so little randomness, it would have certainly fallen in the exactly correct order, making it impossible for it to show up on my feed yesterday.
 
therefore, I am not a very good programmer, and I have no clue why my feed’s all scrambled like that.

@redweasel  
how did this 3-month-old image show up on your feed? o.o

time for an early morning fly

also, it’s AudioKritik, it’s just an old name and i forgot to change it lol

YISS Thanksy