The 'bug' didn't last for over a year and a half. The product has existed for that long.
The bug was in the advertiser selection process. There was an issue with the job/dataset we use to select which advertisers to choose. It should only have been people in the follow lists.
As for "a change in sort order does not normally change the contents of the lists". Due to the size of some of the lists, we don't load the entire list when we show you the first 20 or so. Therefore, we would require an insertion process.
Thank you for clarifying this. I'm obviously not familiar with Twitter's code to any extent, but it seems reasonable you'd need the insertion process regardless.
Out of curiosity, can you speak to how long this bug actually appear in the wild before it was corrected?
Comments
Sorry, this is me: http://twitter.com/x5315. I'll update my bio, how's that?
The 'bug' didn't last for over a year and a half. The product has existed for that long.
The bug was in the advertiser selection process. There was an issue with the job/dataset we use to select which advertisers to choose. It should only have been people in the follow lists.
As for "a change in sort order does not normally change the contents of the lists". Due to the size of some of the lists, we don't load the entire list when we show you the first 20 or so. Therefore, we would require an insertion process.
Thank you for clarifying this. I'm obviously not familiar with Twitter's code to any extent, but it seems reasonable you'd need the insertion process regardless.
Out of curiosity, can you speak to how long this bug actually appear in the wild before it was corrected?