Re: [twitter-dev] posting status
Have used both tweepy and twitter. http://dev.twitter.com/doc/post/statuses/update - Is this the documentation you're talking about? On Fri, Feb 11, 2011 at 7:06 AM, Sujit Shah sujit...@gmail.com wrote: Which external libraries do you use? Have a look at the update status documentation. On Fri, Feb 11, 2011 at 3:05 AM, twt kritikasing...@gmail.com wrote: Is there an easy way of posting tweets from a desktop client without using any external library? -- 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 -- xxx The butterfly does not count years, but moments, and therefore has enough time. - Rabindranath Tagore -- 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
Re: [twitter-dev] Re: Update on Whitelisting
I have been reading through the documentation for the stream api and the user stream api and I'm not sure why everyone is getting so upset about. It looks like this is going to benefit developers and allow Twitter to maintain a more stable environment which is a good thing for us. I understand that no being able to get whitelisted will require more work on our end to stay within the 350 requests per hour but the trade off is worth it in my opinion.For our apps DM's are very important and if I am reading the user stream documentation correctly DM's are no longer rate limited if you use the user stream api where as with the REST api you had a 250/day limit. So I'm not sure if I've missed the point but it seems like this is a good thing. Trevor. On Fri, Feb 11, 2011 at 12:43 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Yup that certainly clarifies and thanks for the #newtwitter stats, it's something I've been very curious about (and I'm sure others as well)! -- 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 sdk for iphone login problem
i am using twitter sdk in iphone application. i have downloaded twitter sdk from this site. http://mobile.tutsplus.com/tutorials/iphone/twitter-api-iphone/ place the consumer key and secret in the code and then build and run the application but each time the application gives me this error: Sorry that page does not exist. i can't find any solution on google, please help me anyone. thanks in advance. -- 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] Using the geo/search - can't seem to get any results
Hi there.
I want to grab a set of tweets from an arbitrary location.
I'm using http://dev.twitter.com/console to play with.
Selected the geo/search method. Added parameters of query and
london. Hit Send, get back:
{
errors: [
{
code: 12,
message: You must provide valid coordinates, IP address,
query, or attributes.
}
]
}
I've also tried calling the method via PHP and don't even get the
error, rather it returns some HTML that looks like a Twitter page.
Can anyone help me figure out how to get data back from this and what
I'm doing wrong?
Incidentally, that dev console is maddeningly frustrating to use since
it immediately forgets the entered parameters as soon as you submit a
query. Couldn't it submit via ajax, too?
thanks,
Matt
--
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 share link with display parameter for mobile view ?
Hello, I would like to do a simple thing. If I use this link ( http://twitter.com/share/?url=http://www.google.com ) on my iphone Or android the display is not adapted to my device... Is it possible to add a simple parameter to display a mobile template about share page ? And a URL callBack ? If this parameter exist it's cool but impossible to find it in your api documentation... If doesn't exist you are really late... Give me a simple solution please without Oauth and heavy process to implement this. Best regards -- 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] Is it possible to share link with display parameter for mobile view ?
We don't have a mobile view for this share flow yet -- but we've definitely gotten many requests for it and it's naturally something that we'll provide some day. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Feb 11, 2011 at 6:54 AM, Nicolas Roussel roussel.n...@gmail.comwrote: Hello, I would like to do a simple thing. If I use this link ( http://twitter.com/share/?url=http://www.google.com ) on my iphone Or android the display is not adapted to my device... Is it possible to add a simple parameter to display a mobile template about share page ? And a URL callBack ? If this parameter exist it's cool but impossible to find it in your api documentation... If doesn't exist you are really late... Give me a simple solution please without Oauth and heavy process to implement this. Best regards -- 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
Re: [twitter-dev] Using the geo/search - can't seem to get any results
We don't recommend our dev console really for all the reasons you list --
you'll find much more joy in using Apigee's Twitter console at
http://app.apigee.com/console/twitter
You may also want to consider Twurl at
http://github.com/marcel/twurl-- Also, since this method doesn't
require authentication, you can use curl.
I'm not sure how you're making the request in PHP, but it's not usual for
this API to respond with an HTML page unless there's a general site failure.
Here's an example of your request via curl:
curl http://api.twitter.com/1/geo/search.json?query=London
{result:{places:[{url:http:\/\/api.twitter.com\/1\/geo\/id\/14d17c02200b6fc8.json,country:United
States,contained_within:[{url:http:\/\/api.twitter.com\/1\/geo\/id\/988bfa67502cf995.json,country:United
States,bounding_box:{type:Polygon,coordinates:[[[-94.452875,36.401928],[-94.160558,36.401928],[-94.160558,36.499615],[-94.452875,36.499615]]]},attributes:{},place_type:city,name:Bella
Vista,full_name:Bella Vista,
AR,country_code:US,id:988bfa67502cf995}],place_type:neighborhood,attributes:{},bounding_box:{type:Polygon,coordinates:[[[-94.257714,36.436687],[-94.250204,36.436687],[-94.250204,36.441597],[-94.257714,36.441597]]]},full_name:London,
Bella
Vista,name:London,id:14d17c02200b6fc8,country_code:US},{url:http:\/\/
api.twitter.com
\/1\/geo\/id\/eeb8908666aad27c.json,country:Canada,contained_within:[{url:http:\/\/
api.twitter.com\/1\/geo\/id\/6c6e160a511c48b7.json,country:Canada,bounding_box:null,attributes:{},place_type:admin,name:London,full_name:London,
ON,country_code:CA,id:6c6e160a511c48b7}],place_type:neighborhood,attributes:{},bounding_box:{type:Polygon,coordinates:[[[-81.261064,42.972758],[-81.225745,42.972758],[-81.225745,43.000241],[-81.261064,43.000241]]]},full_name:Central
London, London,name:Central
London,id:eeb8908666aad27c,country_code:CA},{url:http:\/\/
api.twitter.com
\/1\/geo\/id\/cbc189488163dafc.json,country:Canada,contained_within:[{url:http:\/\/
api.twitter.com\/1\/geo\/id\/6c6e160a511c48b7.json,country:Canada,bounding_box:null,attributes:{},place_type:admin,name:London,full_name:London,
ON,country_code:CA,id:6c6e160a511c48b7}],place_type:neighborhood,attributes:{},bounding_box:{type:Polygon,coordinates:[[[-81.313035,42.975341],[-81.256947,42.975341],[-81.256947,42.998583],[-81.313035,42.998583]]]},full_name:West
London, London,name:West
London,id:cbc189488163dafc,country_code:CA},{url:http:\/\/
api.twitter.com\/1\/geo\/id\/03b71c10e43969a2.json,country:United
States,contained_within:[{url:http:\/\/api.twitter.com\/1\/geo\/id\/3df0e3eb1e91170b.json,country:United
States,bounding_box:{type:Polygon,coordinates:[[[-83.183103,39.808631],[-82.771378,39.808631],[-82.771378,40.157317],[-83.183103,40.157317]]]},attributes:{},place_type:city,name:Columbus,full_name:Columbus,
OH,country_code:US,id:3df0e3eb1e91170b}],place_type:neighborhood,attributes:{},bounding_box:{type:Polygon,coordinates:[[[-83.03284116,39.80843604],[-82.99606716,39.80843604],[-82.99606716,39.83236002],[-83.03284116,39.83236002]]]},full_name:West
London, Columbus,name:West
London,id:03b71c10e43969a2,country_code:US},{url:http:\/\/
api.twitter.com\/1\/geo\/id\/3bafd8b7c26533d1.json,country:United
States,contained_within:[{url:http:\/\/api.twitter.com\/1\/geo\/id\/1c69a67ad480e1b1.json,country:United
States,bounding_box:{type:Polygon,coordinates:[[[-95.909985,29.537014],[-95.014496,29.537014],[-95.014496,30.110732],[-95.909985,30.110732]]]},attributes:{},place_type:city,name:Houston,full_name:Houston,
TX,country_code:US,id:1c69a67ad480e1b1}],place_type:neighborhood,attributes:{},bounding_box:{type:Polygon,coordinates:[[[-95.490251,29.988164],[-95.487544,29.988164],[-95.487544,29.990294],[-95.490251,29.990294]]]},full_name:London
Park, Houston,name:London
Park,id:3bafd8b7c26533d1,country_code:US}]},query:{url:http:\/\/
api.twitter.com
\/1\/geo\/search.json?trim_place=falsequery=Londonautocomplete=falseaccuracy=0granularity=neighborhood,type:search,params:{trim_place:false,query:London,autocomplete:false,accuracy:0,granularity:neighborhood}}}
@episod http://twitter.com/episod - Taylor Singletary - Twitter Developer
Advocate
On Fri, Feb 11, 2011 at 2:36 AM, Matt guitarroman...@gmail.com wrote:
Hi there.
I want to grab a set of tweets from an arbitrary location.
I'm using http://dev.twitter.com/console to play with.
Selected the geo/search method. Added parameters of query and
london. Hit Send, get back:
{
errors: [
{
code: 12,
message: You must provide valid coordinates, IP address,
query, or attributes.
}
]
}
I've also tried calling the method via PHP and don't even get the
error, rather it returns some HTML that looks like a Twitter page.
Can anyone help me figure out how to get data back from this and what
I'm doing wrong?
Incidentally, that dev console is maddeningly frustrating to use since
it immediately forgets the entered parameters as soon as you submit a
query.
[twitter-dev] Re: Is includes_rts=true for statuses/mentions broken?
I figured out why I was not seeing native retweets being included in my results. I was calling api.twitter.com/statuses/user_timeline, but should have been calling api.twitter.com/1/statuses/user_timeline. Adding the 1/ for the api version made the difference. Perhaps that is the cause of Anil's problem as well. On Feb 10, 2:06 am, Abraham Williams 4bra...@gmail.com wrote: I think you have the wrong idea of what include_rts does. Include_rts is designed to include native retweets in timelines where default inclusion would break. For example /statuses/user_timeline expects all tweets to be from a user A. But if that user A has retweeted user B then user Bs tweets can be included user As user_timeline with include_rts. Include_rts has no effect on /statuses/mentions because the original tweet is already included due to the fact it is a mention. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.On Wed, Feb 9, 2011 at 21:00, Adam Duke adam.v.d...@gmail.com wrote: I've seen the same behavior with the include_rts parameter. I have tried passing the values 'true', 't', and '1' with no success. On Feb 8, 7:15 pm, Anil Chawla ani...@gmail.com wrote: It's been a while but I want to follow up on this because we still have the issue. Is anyone able to pull native retweets when calling the statuses/mentions endpoint? An indication that includes_rts either works for you or doesn't work would be great. Thanks, -Anil On Dec 14 2010, 11:44 am, Anil Chawla ani...@gmail.com wrote: I've also been facing this issue for quite a long time. I've told myself that this can't be a problem with the API (since nobody else is complaining) but I can't see what is wrong on our end. For example, I have the following status that was retweeted a few times: http://twitter.com/#!/anilchawla/status/14437959797313536 This is the request URL that is generated when I request my mentions using count=200, include_rts=true, and since_id = 13978625736970241 (OAuth tokens omitted): https://api.twitter.com/1/statuses/mentions.json?count=200include_rt... The four mentions of the above status are not present in the response even though those retweets and the original status have an ID greater than since_id. Omitting count and since_id does not make a difference. As a work-around, we have to pull both statuses/mentions and statuses/retweets_of_me and merge them together. It's hard to believe that everyone else has been doing the same and ignoring this API parameter. Any idea what the issue is? -Anil -- 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] user stream api
I can't seem to find any documentation that shows how to go about sending a DM using the new user stream api. I have been through all of the documentation on dev.twitter.com. Can someone point me in the right direction? Thanks, Trevor -- 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] user stream api
Hi Trevor, Write operations in the Twitter API are always done via the REST API. The Streaming APIs are for consumption of data. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Feb 11, 2011 at 7:52 AM, Trevor Dean trevord...@gmail.com wrote: I can't seem to find any documentation that shows how to go about sending a DM using the new user stream api. I have been through all of the documentation on dev.twitter.com. Can someone point me in the right direction? Thanks, Trevor -- 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
Re: [twitter-dev] user stream api
Thanks Taylor. I posted a question to the group yesterday but it might have gotten lost amongst all the other posts about not whitelisting anymore. With our service we rely on sending DM's and we will most likely require to have more of our clients whitelisted. What is will be the future of DM limits and going about getting those rates increased? Trevor. On Fri, Feb 11, 2011 at 11:11 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Trevor, Write operations in the Twitter API are always done via the REST API. The Streaming APIs are for consumption of data. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Feb 11, 2011 at 7:52 AM, Trevor Dean trevord...@gmail.com wrote: I can't seem to find any documentation that shows how to go about sending a DM using the new user stream api. I have been through all of the documentation on dev.twitter.com. Can someone point me in the right direction? Thanks, Trevor -- 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 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] Re: basic authentication not supported error
I haven't done much Flash coding -- I know there are a few approaches to coding in Flash and that there are OAuth libraries available. You might want to check out this library: http://code.google.com/p/oauth-as3/ Also, there's an AIR-based open source project called Spaz that you can look at, though it may be far from what you're wanting: https://github.com/funkatron/spaz-desktop-air @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 7:36 AM, nite21 shanebond1...@gmail.com wrote: hi taylor and paresh i am creating a slideshow of 40 users recent tweet one after another in flash now some of them show when i ctrl enter and some of them dont some of this give me this error errors error code=53Basic authentication is not supported/error /errors im using this code loadTwitterXML(http://api.twitter.com/1/statuses/user_timeline.xml? screen_name=+listArr[twitcount]); how to use oauth to show usertimeline thanks On Feb 10, 8:09 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: As Paresh mentioned, Your URL needs to be: a) pointed to the *api* subdomain b) versioned -- always *1* at this time c) specifying a format - usually either *json* or *xml* And should use: a) the screen_name parameter instead of an interpolated URI element to avoid issues with all-integer screen names. * * In your case you want to issue a GET to this URL instead: *http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=shane. .. * * * Taylor * * @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 3:30 AM, Paresh Nakhe paresh.na...@gmail.com wrote: Are you using twitteroauth library? Also, the url should be like http://api.twitter.com/1/statuses/user_timeline/sh...82 Atleast i am using this and it works for me. On Thu, Feb 10, 2011 at 3:44 PM, nite21 shanebond1...@gmail.com wrote: hi all im loading twitter xml data and showing it in flash when i load this xml to get data http://twitter.com/statuses/user_timeline/shanebond1982 i am getting this error basic authentication not supported error is there any other method to get the usertimeline data pls help 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 -- *What I have is not a dream, because I will make it a reality.* -- 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 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: Update on Whitelisting
Thanks Matt! the trends.api.twitter.com server is working great. Question : what are the Rate Limit restrictions against that server? I am being very careful to respect the as_of time stamp for last request against a specific WOEID, but give 42 locations (the world plus 41 counties and cities) at present, and a 5 minutes refresh rate I expect 20 (60 minutes / 5 ) * 42 woeid point = 840 request per hour. and more when more trend locations are added (I'm also interested in the hourly and daily trend data, but that is minor from a volume perspective) (It does look like I'm okay, but figures crossed) so what is the hard limit currently? Feed back : Please note that neither the documentation (http://dev.twitter.com/doc/ get/trends/:woeid) or the Twitter API Announcements about using the correct API and host (http://groups.google.com/group/twitter-api- announce/browse_thread/thread/46ca6fcb9ea7eb49/34b013f4d092737f? show_docid=34b013f4d092737f) mention new trends.api.twitter.com end point. also their are two undocumented fields in the GET trends results : promoted_content - I can guess what that is for, but so far it's always been null and events - so far always null with respect to the Trends available.json the documentation is a little out of date (parentid) The results from are good after your initial problems when you rolled out all the new location and got the parentid wrong in a couple of cases. (I think you had San Fran in Brazil : ) Ian False Positives : Code and Culture :http://www.FalsePositives.com Connected Thinking : Building the People and Data Driven Web http://www.ConnectedThinking.com Twendr : Your Global Twitter Dashboard : What's happening Now! http://www.Twendr.com On Feb 10, 8:40 pm, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. To use it just map the api.twitter.com trends request onto the trends.api.twitter.com domain name, for example: http://api.twitter.com/1/trends/available.json becomes: http://trends.api.twitter.com/1/trends/available.json and: http://api.twitter.com/1/trends/1.json becomes: http://trends.api.twitter.com/1/trends/1.json Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Feb 10, 2011 at 4:07 PM, Ian Irving ian.irv...@gmail.com wrote: Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers
[twitter-dev] Re: Update on Whitelisting
Hey Ed! I hope you can use Twendr! Yes this is on the five-minute cycle like the main Trending Topics feed. send me money and I'll create a Promoted trends just for you :) (hu...) Ian On Feb 10, 8:48 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Re: Update on Whitelisting
Hi Ian, One step at at time. The server is experimental, which is why it isn't documented anywhere. I should have made that clear. Your feedback will let us know how it's performing. Because the server is hosting a cached version of the trends data you shouldn't find any issues with the rate limits. That being said be sensible about how you query the data. It isn't updating every second or even every minute, so calling more frequently than 5/10 minutes won't achieve anything. Promoted content is also in closed beta at the moment so supporting it through an experimental endpoint would be premature. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Feb 11, 2011 at 9:01 AM, Ian Irving ian.irv...@gmail.com wrote: Thanks Matt! the trends.api.twitter.com server is working great. Question : what are the Rate Limit restrictions against that server? I am being very careful to respect the as_of time stamp for last request against a specific WOEID, but give 42 locations (the world plus 41 counties and cities) at present, and a 5 minutes refresh rate I expect 20 (60 minutes / 5 ) * 42 woeid point = 840 request per hour. and more when more trend locations are added (I'm also interested in the hourly and daily trend data, but that is minor from a volume perspective) (It does look like I'm okay, but figures crossed) so what is the hard limit currently? Feed back : Please note that neither the documentation (http://dev.twitter.com/doc/ get/trends/:woeid) or the Twitter API Announcements about using the correct API and host (http://groups.google.com/group/twitter-api- announce/browse_thread/thread/46ca6fcb9ea7eb49/34b013f4d092737f? show_docid=34b013f4d092737f) mention new trends.api.twitter.com end point. also their are two undocumented fields in the GET trends results : promoted_content - I can guess what that is for, but so far it's always been null and events - so far always null with respect to the Trends available.json the documentation is a little out of date (parentid) The results from are good after your initial problems when you rolled out all the new location and got the parentid wrong in a couple of cases. (I think you had San Fran in Brazil : ) Ian False Positives : Code and Culture :http://www.FalsePositives.com Connected Thinking : Building the People and Data Driven Web http://www.ConnectedThinking.com Twendr : Your Global Twitter Dashboard : What's happening Now! http://www.Twendr.com On Feb 10, 8:40 pm, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. To use it just map the api.twitter.com trends request onto the trends.api.twitter.com domain name, for example: http://api.twitter.com/1/trends/available.json becomes: http://trends.api.twitter.com/1/trends/available.json and: http://api.twitter.com/1/trends/1.json becomes: http://trends.api.twitter.com/1/trends/1.json Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Feb 10, 2011 at 4:07 PM, Ian Irving ian.irv...@gmail.com wrote: Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With
[twitter-dev] Twitter app development require guidance
We are working on Twitter part of this proposed project. we are trying to access twitter from stand alone java application, but got stuck in between. Here is the action flow that we followed. 1. Registered our application with twitter got consumer secrete keys 2. Tried to get request access token with above keys. We got request token but unable to get access token. Before we can get access token its throwing up error.. Suggest some solution please -- 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: user stream api
I too am still worried about the DM limits. If I understand the User API correctly. - The user stream means that an unlimited number of DMs can be received as there is no rate limit on receiving (consuming) of data. - The application would send DMs via the REST API and therefore is limited to sending 250 DMs per day. For my application this is still a problem as my target is social learning and part of that is DMs to send/receive responses to test questions and such--things that need to be private. Conversations between learners are tweeted. So the design changes we need to make are: - Consuming information (Tweets, retweets, and DMs) is done via the user stream API - Sending tweets and DMs is still done by the REST API. It is going to take some time to get my head wrapped around this. Until the announcement yesterday I was not paying attention to the streams as they did not fit all that well with my application. Now I see that it is important to create an application that uses both as the app is both the consumer of users activity (DMs) and originator (DMs and tweets). On Feb 11, 8:31 am, Trevor Dean trevord...@gmail.com wrote: Thanks Taylor. I posted a question to the group yesterday but it might have gotten lost amongst all the other posts about not whitelisting anymore. With our service we rely on sending DM's and we will most likely require to have more of our clients whitelisted. What is will be the future of DM limits and going about getting those rates increased? Trevor. On Fri, Feb 11, 2011 at 11:11 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Trevor, Write operations in the Twitter API are always done via the REST API. The Streaming APIs are for consumption of data. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Feb 11, 2011 at 7:52 AM, Trevor Dean trevord...@gmail.com wrote: I can't seem to find any documentation that shows how to go about sending a DM using the new user stream api. I have been through all of the documentation on dev.twitter.com. Can someone point me in the right direction? Thanks, Trevor -- 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 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: Update on Whitelisting
The one thing I am missing in this announcement is how this affects the rate limit of a non-authenticated request to the REST search API? Thanks, Ben -- 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] Re: user stream api
Be aware that the streaming API does not deliver everything you are tracking. In theory it delivers everything up to 1% of the total flow of tweets. In practice, I find that it delivers about 95% of the tweets that match your keywords or users. This is fine when sampling, which is what I generally use it for, but will cause much anguish if you assume you will get everything sent by people you are following. I have to admit that I have only found this issue with the streaming API, but I'm betting that the user streams are based on the same underlying code. My solution to the missing values from the streaming API is to collect everything I can from streaming, then use the REST API to backfill data I might not have received. If you run the backfill every hour, you only have to go back to the last set of good tweets, adding anything you missed. On Fri, Feb 11, 2011 at 1:10 PM, DaveH d...@idreia.com wrote: I too am still worried about the DM limits. If I understand the User API correctly. - The user stream means that an unlimited number of DMs can be received as there is no rate limit on receiving (consuming) of data. - The application would send DMs via the REST API and therefore is limited to sending 250 DMs per day. For my application this is still a problem as my target is social learning and part of that is DMs to send/receive responses to test questions and such--things that need to be private. Conversations between learners are tweeted. So the design changes we need to make are: - Consuming information (Tweets, retweets, and DMs) is done via the user stream API - Sending tweets and DMs is still done by the REST API. It is going to take some time to get my head wrapped around this. Until the announcement yesterday I was not paying attention to the streams as they did not fit all that well with my application. Now I see that it is important to create an application that uses both as the app is both the consumer of users activity (DMs) and originator (DMs and tweets). On Feb 11, 8:31 am, Trevor Dean trevord...@gmail.com wrote: Thanks Taylor. I posted a question to the group yesterday but it might have gotten lost amongst all the other posts about not whitelisting anymore. With our service we rely on sending DM's and we will most likely require to have more of our clients whitelisted. What is will be the future of DM limits and going about getting those rates increased? Trevor. On Fri, Feb 11, 2011 at 11:11 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Trevor, Write operations in the Twitter API are always done via the REST API. The Streaming APIs are for consumption of data. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Feb 11, 2011 at 7:52 AM, Trevor Dean trevord...@gmail.com wrote: I can't seem to find any documentation that shows how to go about sending a DM using the new user stream api. I have been through all of the documentation on dev.twitter.com. Can someone point me in the right direction? Thanks, Trevor -- 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 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 -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- 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] Re: user stream api
I see that other developers are concerned about the future of getting your DM limits increased but I haven't seen a response yet that addresses this. Will there still be a way, on a case by case basis of course where we can request increases for DM limits? Thanks, Trevor On Fri, Feb 11, 2011 at 1:25 PM, Adam Green 140...@gmail.com wrote: Be aware that the streaming API does not deliver everything you are tracking. In theory it delivers everything up to 1% of the total flow of tweets. In practice, I find that it delivers about 95% of the tweets that match your keywords or users. This is fine when sampling, which is what I generally use it for, but will cause much anguish if you assume you will get everything sent by people you are following. I have to admit that I have only found this issue with the streaming API, but I'm betting that the user streams are based on the same underlying code. My solution to the missing values from the streaming API is to collect everything I can from streaming, then use the REST API to backfill data I might not have received. If you run the backfill every hour, you only have to go back to the last set of good tweets, adding anything you missed. On Fri, Feb 11, 2011 at 1:10 PM, DaveH d...@idreia.com wrote: I too am still worried about the DM limits. If I understand the User API correctly. - The user stream means that an unlimited number of DMs can be received as there is no rate limit on receiving (consuming) of data. - The application would send DMs via the REST API and therefore is limited to sending 250 DMs per day. For my application this is still a problem as my target is social learning and part of that is DMs to send/receive responses to test questions and such--things that need to be private. Conversations between learners are tweeted. So the design changes we need to make are: - Consuming information (Tweets, retweets, and DMs) is done via the user stream API - Sending tweets and DMs is still done by the REST API. It is going to take some time to get my head wrapped around this. Until the announcement yesterday I was not paying attention to the streams as they did not fit all that well with my application. Now I see that it is important to create an application that uses both as the app is both the consumer of users activity (DMs) and originator (DMs and tweets). On Feb 11, 8:31 am, Trevor Dean trevord...@gmail.com wrote: Thanks Taylor. I posted a question to the group yesterday but it might have gotten lost amongst all the other posts about not whitelisting anymore. With our service we rely on sending DM's and we will most likely require to have more of our clients whitelisted. What is will be the future of DM limits and going about getting those rates increased? Trevor. On Fri, Feb 11, 2011 at 11:11 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Trevor, Write operations in the Twitter API are always done via the REST API. The Streaming APIs are for consumption of data. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Feb 11, 2011 at 7:52 AM, Trevor Dean trevord...@gmail.com wrote: I can't seem to find any documentation that shows how to go about sending a DM using the new user stream api. I have been through all of the documentation on dev.twitter.com. Can someone point me in the right direction? Thanks, Trevor -- 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 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 -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- 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
Re: [twitter-dev] Re: user stream api
On Fri, 11 Feb 2011 13:25:07 -0500, Adam Green 140...@gmail.com wrote: Be aware that the streaming API does not deliver everything you are tracking. In theory it delivers everything up to 1% of the total flow of tweets. In practice, I find that it delivers about 95% of the tweets that match your keywords or users. This is fine when sampling, which is what I generally use it for, but will cause much anguish if you assume you will get everything sent by people you are following. I have to admit that I have only found this issue with the streaming API, but I'm betting that the user streams are based on the same underlying code. My solution to the missing values from the streaming API is to collect everything I can from streaming, then use the REST API to backfill data I might not have received. If you run the backfill every hour, you only have to go back to the last set of good tweets, adding anything you missed. Backfill for keywords is easy - just use Search. But how do you determine what you *haven't* received from accounts that you're following? Do you need to grab the most recent 200 tweets from everyone you're following using REST, or do you do a Search with from: OR from: ... as many times as it takes? -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] delay on search results
How long should I expect a new post to show up in a search result? Having just posted with #testing123123 http://search.twitter.com/search.atom?q=%23testing123123 Shows the result once. Then not again. And when I post it again from another account, the original one does show up , but then not again. Thoughts? -- 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: Update on Whitelisting
I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.cafor more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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
Re: [twitter-dev] delay on search results
I would like to know as well, please. It appears to me as if for some users, search gets stuck showing only results from hours behind... Thank you, Jan On Fri, Feb 11, 2011 at 8:27 PM, Lloyd cled...@gmail.com wrote: How long should I expect a new post to show up in a search result? Having just posted with #testing123123 http://search.twitter.com/search.atom?q=%23testing123123 Shows the result once. Then not again. And when I post it again from another account, the original one does show up , but then not again. Thoughts? -- 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] Confused
How do this work because i'm new to this? -- 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] how to communicate with followers
I need a help, I'm developing an app for a client where it needs to communicate with his followers individually, each follower will receive a different link, the solution would be to have DM, but with a limit of 250 per day this becomes impossible, try sending mentions twitter but suspends the User, for thinking and spam, is there any way? thanks Eduardo -- 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] I've got the error:OAuth Authentication Failed.And I tried all the wordpress to twitter plugins.
Hi there. Using WP 3.0.5and WP to Twitter 2.2.6 on a CentOS server, which I don't manage at all. I've got the error OAuth Authentication Failed. Check your credentials and verify that Twitter is running.. I've also checked all the data from the application, including erasing the older and creating a new one, but this issue remains. Twitter is active and working at this very moment I'm writing this message. Anybody help? PS:And I thought the problem is the Wp to Twitter 2.2.6 Plugins.Then I tried to install the other Wordpree to twitter Plugins..The result: Authentication Failed.. -- 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: Is includes_rts=true for statuses/mentions broken?
Abraham, you are right that I had the wrong understanding of the parameter. When I read the timeline will contain native retweets in addition to the standard stream of tweets I didn't realize it meant native retweets of the mentions themselves. It makes sense to me now but I am not sure how that parameter is useful to anyone :-) It's a bit surprising to hear that any REST API client that wants to provide a unified view of mentions/retweets (which makes sense to most users) has to make two calls and merge the results, but I guess that's what I need to do! Thanks, -Anil On Feb 10, 2:06 am, Abraham Williams 4bra...@gmail.com wrote: I think you have the wrong idea of what include_rts does. Include_rts is designed to include native retweets in timelines where default inclusion would break. For example /statuses/user_timeline expects all tweets to be from a user A. But if that user A has retweeted user B then user Bs tweets can be included user As user_timeline with include_rts. Include_rts has no effect on /statuses/mentions because the original tweet is already included due to the fact it is a mention. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Feb 9, 2011 at 21:00, Adam Duke adam.v.d...@gmail.com wrote: I've seen the same behavior with the include_rts parameter. I have tried passing the values 'true', 't', and '1' with no success. On Feb 8, 7:15 pm, Anil Chawla ani...@gmail.com wrote: It's been a while but I want to follow up on this because we still have the issue. Is anyone able to pull native retweets when calling the statuses/mentions endpoint? An indication that includes_rts either works for you or doesn't work would be great. Thanks, -Anil On Dec 14 2010, 11:44 am, Anil Chawla ani...@gmail.com wrote: I've also been facing this issue for quite a long time. I've told myself that this can't be a problem with the API (since nobody else is complaining) but I can't see what is wrong on our end. For example, I have the following status that was retweeted a few times: http://twitter.com/#!/anilchawla/status/14437959797313536 This is the request URL that is generated when I request my mentions using count=200, include_rts=true, and since_id = 13978625736970241 (OAuth tokens omitted): https://api.twitter.com/1/statuses/mentions.json?count=200include_rt... The four mentions of the above status are not present in the response even though those retweets and the original status have an ID greater than since_id. Omitting count and since_id does not make a difference. As a work-around, we have to pull both statuses/mentions and statuses/retweets_of_me and merge them together. It's hard to believe that everyone else has been doing the same and ignoring this API parameter. Any idea what the issue is? -Anil -- 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] Looks like our application is DOA...
I've just been reading the messages on here wabout the whitelisting changes, rate limits, streaming API etc and can only come to the conclusion that the application we were just about to launch to our users is going to have to be cancelled. It's a simple application that uses DM to send notifications to users based on real time events - these events being a purchase from their hosted web store. It was only aimed a low-volume merchants, but even if they each only have one transaction a day (and they get more than that) then we would run out of the 250 message limit. This decision to not entertain any form of whitelisting in the future seems to me like it is going to impact a lot of developers. This is not something we can use the streaming API for as we only send messages, which the streaming API can not do. So we are stuck with REST, and therefore stuck with an enforced extremely low limit on messages. As a direct result of this, we now have to cancel the launch of this application. It was something that a couple of merchants had requestes and we had said we would look into it. Up until recently it certainly looked like an option we could give them, but now we are going to have to go to them and say that it's actually no longer possible to send them messages on twitter, and see if they have any other platform they would prefer us to us instead. Does anyone have any suggestions as to a way that it might be possible to actually launch this app - it's something that our customers requested, and it makes us look bad that we are going to have to say 'sorry, not possible to send mesasges to you on your preferred messaging platform...' -- 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] Re: Update on Whitelisting
Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.cafor more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 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] Looks like our application is DOA...
Our product is in danger of suffering the same fate. I have posted to this group a couple of times today hoping to get a response from twitter regarding the future of DM's but haven't got a response yet. I can only imagine they are trying to get through all of the emails requesting the same information. Out experience is that twitter has been very helpful and want to help developers but they will probably continue to evaluate needs on a case by case basis. There have been many people asking the same question so hopefully we will see a response soon. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-02-12, at 12:49 AM, pl plot.l...@gmail.com wrote: I've just been reading the messages on here wabout the whitelisting changes, rate limits, streaming API etc and can only come to the conclusion that the application we were just about to launch to our users is going to have to be cancelled. It's a simple application that uses DM to send notifications to users based on real time events - these events being a purchase from their hosted web store. It was only aimed a low-volume merchants, but even if they each only have one transaction a day (and they get more than that) then we would run out of the 250 message limit. This decision to not entertain any form of whitelisting in the future seems to me like it is going to impact a lot of developers. This is not something we can use the streaming API for as we only send messages, which the streaming API can not do. So we are stuck with REST, and therefore stuck with an enforced extremely low limit on messages. As a direct result of this, we now have to cancel the launch of this application. It was something that a couple of merchants had requestes and we had said we would look into it. Up until recently it certainly looked like an option we could give them, but now we are going to have to go to them and say that it's actually no longer possible to send them messages on twitter, and see if they have any other platform they would prefer us to us instead. Does anyone have any suggestions as to a way that it might be possible to actually launch this app - it's something that our customers requested, and it makes us look bad that we are going to have to say 'sorry, not possible to send mesasges to you on your preferred messaging platform...' -- 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: Looks like our application is DOA...
Well, guess we just have to wait and see, but to be honest I get the feeling that we are just going to have to can this project. It's a shame that this has happened, all we can do is explain to or customers that it is a situation outside of our control and that it's twitter that are preventing this from being done, not us... On Feb 12, 10:18 am, Trevor Dean trevord...@gmail.com wrote: Our product is in danger of suffering the same fate. I have posted to this group a couple of times today hoping to get a response from twitter regarding the future of DM's but haven't got a response yet. I can only imagine they are trying to get through all of the emails requesting the same information. Out experience is that twitter has been very helpful and want to help developers but they will probably continue to evaluate needs on a case by case basis. There have been many people asking the same question so hopefully we will see a response soon. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.cafor more information -- 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
