Hi Peter, Hi Peter,
Can you explain what you mean when you say the differences 'only in async' are strange to you. Examples of specific Tweets and the predicates you used would be particularly helpful. Also can you give an example of what you mean by a long Tweet. Thanks, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Feb 16, 2011 at 9:13 AM, Karussell <tableyourt...@googlemail.com>wrote: > Hi John, > > Well, for a search term 'java' the async API is 'ok' and the > differences 'only in search' can be easily explained: the keywords are > in the URL. > But the differences 'only in async' (tweets grabbed only via streaming > API) are strange to me: > > https://github.com/karussell/TestTwitterAPI/blob/master/discrepancy.txt > > Why are they lost? > > You can build the java mini programm via (or via your favourite IDE): > mvn clean install > > and call it via: > ./myjava -Dtwitter4j.oauth.consumerKey=key - > Dtwitter4j.oauth.consumerSecret=value de.jetwick.tw.NewClass "java" > token tokenSecret > > to see what I mean ... > > Another strange fact is that a lot of long tweets retrieved via the > streaming api have a text which is ~15 character shorter than the > identical tweet from the search API ! > > Regards, > Peter. > > -- > > http://jetwick.com Twitter Search without Noise > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
