Hi there!
Just a link to my open source twitter search (without noise) developed
in my spare time:
http://jetwick.com/
Regards,
Peter.
PS: Most of the features are listed here:
http://www.pannous.info/products/jetwick-twitter-search/
--
Twitter developer documentation and resources:
Hi,
this problem was already posted to the twitter4j mailing list [1]. Not
sure if it is an issue with my code, twitter4j or an API issue... user
reported similar problems in the past [2].
First:
I'm doing a 100 tweet search (without paging) every 5 minutes e.g.
against 'twitter search'. I get
Hmmh, would you mind to test this without the geo location filter?
And report your findings here? I'm having an issue even with that.
See:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/f5a0f2a416893c27
Kind Regards,
Peter.
--
http://jetwick.com Twitter Search
the callback url is created from you so just let twitter know where it
should go after 'accept'.
regarding the session: don't you use (secured) cookies or a sessionid
to get the session??
On 15 Feb., 13:49, manish verma manish.verma...@gmail.com wrote:
I am using oauth, i need to know that
/
Regards,
Peter.
On 15 Feb., 20:48, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
On Tue, 15 Feb 2011 03:20:40 -0800 (PST), Karussell
tableyourt...@googlemail.com wrote:
Hi there!
Just a link to my open source twitter search (without noise)
developed
in my spare time
Thanks Colin!
--
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:
Hi Colin, hi John,
To increase recall, search sometimes includes keywords in followed links and
other techniques.
This is indeed the case. and 'twitter search' is a lot in urls ala:
http://search.twitter.com/search?q=jetwick
that is where the big differences came from. Can I turn off this
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
sorry, once more again:
With 'only in async' I meant tweets which were only retrieved via the
streaming API but not via search API
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
in the given file:
https://github.com/karussell/TestTwitterAPI/blob/master/discrepancy.txt
--
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
whatever
post-processing you'd like.
-John Kaluckihttp://twitter.com/jkalucki
Twitter, Inc.
On Thu, Feb 17, 2011 at 12:15 AM, Karussell
tableyourt...@googlemail.comwrote:
Hi Matt,
sorry for being unspecific. By 'only in async' I meant tweets which
were only found by the streaming API
11 matches
Mail list logo