How are entries in Types.statuses sorted by default?

[Xiaogang Han]

Seems like they are not sorted in chronological order. Does the API support customized ordering parameter?

[Justin Parker]

Hi!

They *should* indeed be sorted in reverse chronological order (newest to oldest), like everything returned by Singly. Can you provide me with some example data where this doesn't seem to be the case?

[Xiaogang Han]

Oh sorry, my fault. It turns out to be my misunderstanding of the apis. 

But I still have a question (Suppose I only authorized Twitter). I understand that a tweet from Twitter will be classified into any of the types (contacts, checkins, news, statuses, videos). However, I don't understand the exact difference between news and updates.

For example, my twitter account has 1300+ tweets. When calling the types api (https://api.singly.com/v0/types?), it shows I have 277 updates and 1030 news. Among the 277 updates, most of them are conversations without links, but a few of them do contain links. 

The question is: could you please clarify the definition for updates (take Twitter data as example)? (1) tweets without links? (2) all tweets? (3) tweets without links or those tweets which have urls but the urls are not recognizable? 

Thank you very much.

[Jeremie Miller]

Could you email me directly the id's of the tweets that are a status type but contain links? 

That sounds like a bug, as anything that twitter has tagged as a link entity or our regex fallback catches should be a news type, statuses should only be plain text.

Thanks!

Jer

--
You received this message because you are subscribed to the Google Groups "Singly API" group.
To view this discussion on the web visit https://groups.google.com/d/msg/singlyapi/-/0Qc3Wv17-NkJ.
To post to this group, send email to sing...@googlegroups.com.
To unsubscribe from this group, send email to singlyapi+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/singlyapi?hl=en.

[Xiaogang Han]

E.g.  49671998166663170 and 59821203313000450

If you extract links from the 'entities' attribute of a tweet, then I guess the problem might be caused by Twitter API updates.

It is observed that those tweets are all posted before Mon Apr 18 03:31:00 +0000 2011. At that time, Twitter API may hadn't introduce 'entities' attribute yet.

[Jeremie Miller]

We should still be catching those as a fallback but they must have been missed for some reason, we'll look into it, thanks!

To view this discussion on the web visit https://groups.google.com/d/msg/singlyapi/-/lIyzu80-nd4J.