[twitter-dev] Re: location based search and user location field
Any update on this? It is still an issue. On Oct 7, 9:46 pm, Siim Saarlo siim.saa...@gmail.com wrote: Hi, Search API with location restriction (geocode parameter) used to search through tweets that were geotagged and also tweets that were tweeted by user who had set her location in profile settings. Seems that currently search API, when both geocode and and q parameters are set, only goes through the geotagged tweets. Although seems that when only geocode is set, tweets are included by user' location field as well. I was told (by @twitterapi) that this is temporary situation to be fixed soon. 1) Can anyone suggest when will it probably be fixed? is there alternative solution until then? 2) I would like to try out Streams API' filter method, but it is states that this only goes through geotagged tweets. Is there any workaround to make frequent location specific searches through geotagged tweets and also the ones that are not geotagged? Thank you in advance, siim -- 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-dev] Extreme caching of deleted tweets in 'statuses/home_timeline'
Hello, I start noticing this issue 3-4 days ago. The deleted tweets disappeared after several hours (up to 12 h). Today there's a deleted status (26830561229) that still show up in 'statuses/home_timeline' after 22 hours. 'statuses/show' on that Id gives a correct: Not Found: The URI requested is invalid or the resource requested, such as a user, does not exists. Also in ''statuses/user_timeline'' the tweets disappear immediately after deletion. It seems only 'statuses/home_timeline' does that extreme caching. Anybody else noticing this? Thanks Christian -- 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-dev] Is it possible to search with wildcard in streaming api?
For example I want is to search for words that have 'truck' in it and want to get all tweets that have 'truck', 'trucks', 'trucking', 'dumptruck', etc. I it possible to use wildcards like *truck* or do I have to just include all possible words that contain truck? -- 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-dev] Re: Search with geocode does not respect search radius?
Hi Matt, Just thought I add more heat. My app is dead because of this bug. Looking forward to a fix. On Oct 5, 7:42 pm, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Twitter Bulk User Lookup API returning information about unknown users while missing valid users!!
Hi, Twitter Bulk User Lookup API (http://apiwiki.twitter.com/Twitter-REST- API-Method:-users-lookup) seems to be have given two problems. 1) Random users which were not part of the screen_names parameter passed. 2) is missing valid existing users from the results. I have pasted sample query, and result that I got back here - http://pastebin.com/VDT7xuCV Is somebody else also facing similar problem? -- 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-dev] new_id Gone From Streaming API Statuses
Hi, I was attempting to test my apps with the new status_ids but it appears that the new_id field is no longer being included in the Streaming API json. They were there earlier in the week but are no longer being included. According to John Kalucki's post on the subject[1], I was under the impression this would be enabled from 9/30 until the transition. Are there plans to re-enable this before the transition on Tuesday? Hayes [1] http://groups.google.com/group/twitter-development-talk/browse_thread/thread/9cf92935379d8022/e4eaa56485b2e2e7 -- 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-dev] API Erros - Connection reset by peer
Hi! I am getting Connection reset by peer for every API call made by my applications. My application requests come from IP 213.13.144.4 . Is this only my problem, or anyone else is getting all these errors too? Regards. -- Tiago Teresa Teodósio Equipa de desenvolvimento SAPO / Portugal Telecom -- 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-dev] Could not login
Hello there everyone. I have a problem regarding twitter login. When I try logging in using mobile emulator in my PC, I get no error ang get logged in , but when i try it on my real mobile device, my login fails. But previously it worked fine in my real device too. I got problem now. My device is Nokia N70. If anyone out there is familiar with my problem and got solution, please help me out. Thanks -- 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-dev] Re: Tweet button with AJAX content
I'm no longer seeing the updateTweetCount error when rendering the iframe directly, so this looks like the best method to allow AJAX updates. An additional advantage is that you can make the iframe slightly bigger than that generated by the Twitter JS, eliminating clickjacking warnings from the NoScript Firefox plugin. -- 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-dev] Re: Search with geocode does not respect search radius?
We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,134.121094,2500km These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Re: Extreme caching of deleted tweets in 'statuses/home_timeline'
Christian, I have noticed this and actually posted about it on 10/5 (Subject: status destroy / caching in NewTwitter). I was planning on making a bit of noise tomorrow to see if there were any updates. Sorry I don't have more to add (except lots of data about what's actually happening). Best, Tom On Oct 10, 4:06 am, CWorster cwors...@schlimmer.com wrote: Hello, I start noticing this issue 3-4 days ago. The deleted tweets disappeared after several hours (up to 12 h). Today there's a deleted status (26830561229) that still show up in 'statuses/home_timeline' after 22 hours. 'statuses/show' on that Id gives a correct: Not Found: The URI requested is invalid or the resource requested, such as a user, does not exists. Also in ''statuses/user_timeline'' the tweets disappear immediately after deletion. It seems only 'statuses/home_timeline' does that extreme caching. Anybody else noticing this? Thanks Christian -- 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
