It actually makes sense to use tweet ID to sort tweets, because
timestamp is not a valid source of information for accurate sorting.
It is a very common case to have multiple tweets posted at the exact
same second, and it is not possible to reproduce the correct ordering
of tweets on the client
client hits to the rate limit on twitter.com, but
they didn't know about the rate limit. So they tried to send DM again
and again.
Thanks
Aki
--
To unsubscribe, reply using remove me as the subject.
have much better accuracy.
On Apr 2, 3:39 am, Mark McBride mmcbr...@twitter.com wrote:
Just out of curiosity, what applications are you building that require
sub-second sorting resolution for tweets?
---Mark
http://twitter.com/mccv
On Wed, Mar 31, 2010 at 11:01 PM, Aki yoru.fuku
it is
expected to happen in few weeks, but it would be good to know the
estimated date for this, so the developers can make appropriate
decisions on the application deployment timeline.
-- Aki
On Jan 21, 9:48 am, Eric Woodward e...@nambu.com wrote:
I will come straight to the point: we need
I agree with PJB. The previous announcements only said that the
pagination will be deprecated.
1.
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/41369cb133175d0f#
2.
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/52d4e68040d4ca45#
However,
Thank you for responding so quickly!
It's nice to know that the issues have been reported to the
appropriate people.
-- Aki
On Oct 27, 12:35 am, John Kalucki jkalu...@gmail.com wrote:
I've forwarded your message to the Japan product manager and to the
engineer who first brought Japanese
it even matched at all.
I consider Twitter Search to be the major feature of Twitter, and I
think correcting these issues will make Twitter much better web
service for Japanese people.
Thank you.
-- Aki
