[twitter-dev] Re: Search API
The best way to do this is to use the streaming API and catch all the tweets containing stanley cup when they happen. The search API is very limited and you will never get more then a couple of thousand results in the past. Oftentimes much less. Best regards, Stefan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Java client for Twitter as a student assignment
I second that. Twitter4j is the way to go if you are looking for Java libs. The developer is very quick with relevant updates (which is vital for a moving target like the Twitter API). Stefan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Visual refresh of the OAuth screens
Hi Matt, while being an improvement over the old oauth form, this form still does not tell the user all she needs to know. In particular, it hides the fact that the app will have almost total control over their twitter account. In my experience, most users are totally unaware of this fact. Of course, from a developer's point of view everything that will stop user's from authorizing their apps will always be greeted with skepticism. However, I hope that Twitter will sooner or later inform users that authorizing an app with read/write access can be potentially very dangerous -- and doing so in the oauth form would be the best place to do so. Or we could just hope that we will never see any malicious Twitter apps. Best regards, Stefan -- 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
Re: [twitter-dev] How to obtain latest tweet
Excellent, got this working in under 10 min. If I could buy you a beer I would. Stef On Thu, Sep 2, 2010 at 4:40 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I don't know the PHP, but the call does *not* require authentication if you are willing to live with 150 API calls per hour. It's GET users/show http://dev.twitter.com/doc/get/users/show The last tweet (if there is one) will be an embedded status object. At the same cost of 150 unauthenticated API calls per hour, you can pick up the most recent 200 tweets with GET statuses/user_timeline http://dev.twitter.com/doc/get/statuses/user_timeline The default is 20 tweets, but you can get as many as 200 per call by using the count parameter. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting stef stefankend...@gmail.com: I've been asked to display the latest tweet of one certain twitter account on that person's website. I understand one has to use OAuth. I have added an application in the twitter account and have obtained all the various tokens. The documentation seems to talk a lot about authenticating users but AFAIK this is not required if I simply want to display one tweet, which is public anyway. Even the rss feed can not longer be accessed with OAuth ? What is the easiest way to just display the latest tweet on a site, using php? -- 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?hl=en -- stefankend...@gmail.com phone: +32 479 825 931 -- 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?hl=en
[twitter-dev] Re: Missing tweets in filter:links search
Hi, I have the same problem concerning links in tweets using the search function. The following links produce different results as you can see: http://search.twitter.com/search.atom?q=filter:links+from:_vg and http://search.twitter.com/search.atom?q=from:_vg+http They should return the same links, but they don't.
[twitter-dev] Re: Missing tweets in filter:links search
I can confirm the limitation to seven days, so it's expected behaviour, but should be some kind of documented. Anyways it helpfs, thank you Matt. On 12 Mrz., 16:35, Matt Sanford m...@twitter.com wrote: Hi there, Search does not have as complicated a cacheing system as the main twitter API, so cache inconsistency is a rarity for us. Even when we do have it our longest expiration is less than one minute, so the problem is fixed usually before I can reproduce it (sometimes also a problem). I just double checked the code and it looks like my initial guess is the most likely culprit … if you use filter:links you are being limited only to the last 7 days, which is not the case with http. If you have an example where it looks like that's not the case let me know either here r off list and I can look into it. Thanks; — Matt Sanford On Mar 12, 2009, at 08:18 AM, Stefan Hueg wrote: It seems that the filter:links method uses a cached version, using a predefined threshold for how frequently a user is posting his tweets. It's not affected by how links are postet, e.g.http://www.url.tld orhttp://url.tld. The from:user http method seems to fetch the tweets non-cached. Could you verify that? On 12 Mrz., 15:52, Matt Sanford m...@twitter.com wrote: Hi there, Looking at the results it seems like filter:links is limiting the search time frame. There are some search operators (language and filter:links for example) that have to limit the amount of time they search to prevent them from timing out. Think of it like a table scan. I'll check with the person who added that restriction and see if it's something we can remove without causing massive HTP 500s (which is what you get when a query takes too long and we mark it as timed out). Thanks; — Matt Sanford On Mar 12, 2009, at 05:18 AM, Stefan Hueg wrote: Hi, I have the same problem concerning links in tweets using the search function. The following links produce different results as you can see: http://search.twitter.com/search.atom?q=filter:links+from:_vg and http://search.twitter.com/search.atom?q=from:_vg+http They should return the same links, but they don't.
