My current understanding is the correct way to paginate through 'tagged api' data is using the 'before' parameter and setting it to the timestamp returned in the previous results. On occasion I've noticed that the posts aren't returned perfectly sorted by timestamp, but it wasn't a big deal I just sorted them myself and moved on.
I did some sleuthing and from what I can tell it is being included because it wasn't posted around 1370633883 but was reblogged around then, so my new guess as to what is happening is posts are returned from the tagged api sorted by what time they were last posted/reblogged. I don't know if that's a design decision or not, but if that's the desired behavior I don't understand how to paginate because the reblogged timestamp isn't returned here.
Imagine if the problem post was the last post and I used the last post's timestamp to set the next 'before' parameter. I would end up with:
http://api.tumblr.com/v2/tagged?tag=quotes&api_key=xxxxxxxxxx&limit=20&before=1259695320
and miss a few thousand pages.
Perhaps I'm missing something obvious. Thanks!
Grant
{
"highlighted": [],
"source_title": "Flickr / cornhusk",
"reblog_key": "5qz8pb6m",
"format": "html",
"timestamp": 1259695320,
"note_count": 1,
"tags": [
"word art",
"quotes",
"picasso"
],
"photos": [
{
"caption": "",
"original_size": {
"width": 500,
"height": 378
},
"alt_sizes": [
{
"width": 500,
"height": 378
},
{
"width": 400,
"height": 302
},
{
"width": 250,
"height": 189
},
{
"width": 100,
"height": 76
},
{
"width": 75,
"height": 75
}
]
}
],
"id": 52398736101,
"caption": "",
"state": "published",
"date": "2009-12-01 19:22:00 GMT",
"type": "photo",
"slug": "",
"blog_name": "saysoftly"
}