[twitter-dev] Saas Provider for User Stream
I am wondering if there are any companies that are providing access to user streams as SaaS. I am looking for a service that will allow me to setup filters specifically I only want DMs and I would want the service to call my application via a callback URL when a DM is received. I have spent the day looking for a solution provider that provides this and I have not found any--but I am sure there must be several already out there. Any suggestions? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Application not getting R/W/DM access
Twitter Team: My application was changed weeks ago to request DM permission. My understanding was all we needed to do was edit the settings for the app, and then re-authenticate the application. Which I did. When I look at the app settings it shows that Read, Write, Direct Messages is selected. However, when I go to authorize the application, I see that my application will not not be able to access DMs. This is a white listed app that needs access to DMs to work. From what I can tell, it should be able to authenticate and get DM access as the application is registered as needed DM level. So why is it not being allowed the correct access level? -- 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: Application not getting R/W/DM access
Tom: App does not use xAuth and calls /oauth/authorize--in fact has always done so. Not sure why Twitter is only granting R/W access. Dave On Jul 4, 4:21 pm, Tom van der Woerdt i...@tvdw.eu wrote: 1) Don't use xAuth 2) Don't use /oauth/authenticate but /oauth/authorize Tom On 7/5/11 1:20 AM, DaveH wrote: Twitter Team: My application was changed weeks ago to request DM permission. My understanding was all we needed to do was edit the settings for the app, and then re-authenticate the application. Which I did. When I look at the app settings it shows that Read, Write, Direct Messages is selected. However, when I go to authorize the application, I see that my application will not not be able to access DMs. This is a white listed app that needs access to DMs to work. From what I can tell, it should be able to authenticate and get DM access as the application is registered as needed DM level. So why is it not being allowed the correct access level? -- 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: Application not getting R/W/DM access
Tom, you were right. I thought the app was making the right call to authorize, but it was somehow making a call to authenticate. All is working once again! THANK-YOU!!! :-) On Jul 4, 4:21 pm, Tom van der Woerdt i...@tvdw.eu wrote: 1) Don't use xAuth 2) Don't use /oauth/authenticate but /oauth/authorize Tom On 7/5/11 1:20 AM, DaveH wrote: Twitter Team: My application was changed weeks ago to request DM permission. My understanding was all we needed to do was edit the settings for the app, and then re-authenticate the application. Which I did. When I look at the app settings it shows that Read, Write, Direct Messages is selected. However, when I go to authorize the application, I see that my application will not not be able to access DMs. This is a white listed app that needs access to DMs to work. From what I can tell, it should be able to authenticate and get DM access as the application is registered as needed DM level. So why is it not being allowed the correct access level? -- 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: Update on Whitelisting
I disagree, Abraham. I requested whitelisting for my app because I needed more than 250 DMs per day. Twitter granted my request and my limit was increased considerably. This may be that Twitter did not increase DMs as a default. But at one time, if requested and justified, they would. This is why the questions are being asked about DM limit changes going forward. On Feb 11, 10:12 pm, Abraham Williams 4bra...@gmail.com wrote: 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.caformore 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
[twitter-dev] Re: DM rate limit
Dossy: Don't be so quick to condemn. I have an app that uses DMs and ALL DM traffic is generated by users and they know it--so there is no spamming. There are legitimate uses of DMs that users are OK with that push an app beyond 250/day. Think of it this way, if an application has 300 followers and they all interact via private message (DM) one time per day, then 50 users will be unable to communicate on any given day. On Feb 12, 11:46 am, Dossy Shiobara do...@panoptic.com wrote: Any one Twitter account that sends 250 DM's in a 24 hour period is DOIN' IT RONG. DM spamming your followers is JUST NOT OK. On 2/12/11 2:31 PM, Trevor Dean wrote: Just out of curiosity why can't DM's be limited by the hour instead if having this cap of 250/day? I think if this was an option most of the issues expressed by other developers including myself would be resolved. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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...
Change the message so that it can go into their activity stream instead of a DM. It may be that you have less information, but a @storeowner, You just received an order is better than nothing. Granted with DM you could include more information, but at least a generic message would suffice to have them complete the order fulfillment. Hope this helps give you some other ideas. On Feb 11, 9:49 pm, 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-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
Yes, Do tell. I have a whitelisted app, but came to the realization that I needed to switch to IP based so that all users of the application would have a higher DM limit--critical as my app is a social learning tool for mobile users. Now it looks like my project is dead in the water. Having each person have their own account is fine, but the 250 per day DMs is the problem. Is there any way to increase DMs per day for accounts? I suspect that Twitter may need to rethink this change as there are some applications that needed the whitelisting for DMs while the hourly limits were never a problem. Bitting my nails and waiting for an answer On Feb 10, 6: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-dev] How to change from Application Name to IP Whitelist
Is there streamlined way to request change a whitelisted application to IP whitelisted? As I have been pondering my application and scale I have come to realize that I really need to use several dedicated IPs instead of maintaining the whitelisted application name. -- 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] Whitelisted account needing full control of multiple Twitter Accounts
I understand how to request permission via the callback, but... What I would like to do is have the application that is already whitelisted be able to post to multiple accounts--this is to support a scenario where each Twitter account represents a single class (think University). In this case the Learning Management System (LMS) would need to write student activity to the correct class--and students may be in more than one class. I think that if I had the application gain write permission to accounts it would then be using the API limits for each account and the fact that the main application is whitelisted would no longer matter. Which defeats the value of being whitelisted. Since many of you are far better at using the API than I, what are your thoughts? Have I missed something obvious in the documentation? -- 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: Random 403 Denied due to update limit errors.
Peter: You mention 150/hour so I am guessing that you are not authenticating with Twitter. This means that if there are any other applications sharing the same IP address (shared hosting) then they are also using the same rate limit as your app. If you authenticate you will get the 250/hour ratelimit and it will be all yours to consume. Dave On Nov 1, 6:06 pm, PeterElsner peter.els...@gmail.com wrote: I've written a small app for use with some auction software. All this app does is run via cron every 2 hours and picks a random auction (that is open) and then posts it to my twitter page using OAuth. This works great, and many times it does update just fine. However occasionally, I get a failed response back from Twitter stating 403 - Request has been refused. Possible causes: denied due to update limits. Since my cron only runs every 2 hours, then I am only submitting 12 tweets to my Twitter page in a 24 hour period... That's certainly less than the 150/hour or the 1000/day that is listed in the wiki. My script/app does not do any deleting, following etc... It just sends an update to my page with a random auction listing. So in a 24 hour period, I get on average about 8 successful tweets instead of the 12 I should be getting. I'm just wondering if there is something else that the 403 could be representing other than update limits. Perhaps Twitter itself is over loaded? If that is the case, should it not provide a different error code??? Something that says Twitter is busy right now, try again later, instead of the rate limit error which makes it sound like there's something wrong with my script/app. I sent an email to a...@twitter.com and the response was to come and ask here. If anyone wants to see the code, it can be downloaded fromhttp://www.aggielandauctions.com/mods Thanks in advance, Peter Elsner -- 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: Random 403 Denied due to update limit errors.
Yaemog: You are right, he does say he is posting to his Twitter Page and that he is using oAuth. My bad... So there is something else going on. - Check that authentication was successful. The rate limit should be higher if he has successfully authenticated. - Check the return message from Twitter. When I see a 403 Twitter also sends a response that tells me why the 403 was returned. - Make sure there is no other program using the same Twitter Application name; the other application will draw down the rate limit. On Nov 2, 10:00 am, yaemog Dodigo yae...@gmail.com wrote: You mention 150/hour so I am guessing that you are not authenticating with Twitter. This means that if there are any other applications sharing the same IP address (shared hosting) then they are also using the same rate limit as your app. If you authenticate you will get the 250/hour ratelimit and it will be all yours to consume. Dave Hi Dave, When I read Peter's post, I thought of the same thing. However, since he is successfully posting, wouldn't that require to be authenticated? --d -- 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: Remaining hits for rate limit going down, I'm not doing anything
Josh: The obvious thing is to register you app and then authenticate with OAuth. You will then have your very own rate limit to consume based on the application name. On Oct 20, 4:57 pm, Josh godatp...@gmail.com wrote: Yeah...I forgot about the whole shared host thing. That really sucks. My application uses all unauthenticated calls, so there's nothing I can do, right? That's what I got from the rate limiting page. On Oct 20, 6:35 pm, Slate Smith sl...@slatesmith.com wrote: Yeah unfortunately rate limits are checked via IP AND App keys, so if it's a shared server ... I don't think that you can see unless you have access to the server logs [doubtful at best] - 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] Re: t.co question
Does anyone have an update from the Twitter team on when t.co will make its way into messages sent via API calls? On Oct 16, 7:01 pm, DaveH d...@idreia.com wrote: What are the plans to implement the automaticallyt.courl shortening feature via tweets that are sent in via the API? I am getting ready to add this ability to my application, but if Twitter is going to make it an automatic feature then I can save myself the trouble if they will have it implemented soon. I looked at the announcements and did not see any recent updates on this feature. Looking forward to your comments. Dave -- 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] t.co question
What are the plans to implement the automatically t.co url shortening feature via tweets that are sent in via the API? I am getting ready to add this ability to my application, but if Twitter is going to make it an automatic feature then I can save myself the trouble if they will have it implemented soon. I looked at the announcements and did not see any recent updates on this feature. Looking forward to your comments. Dave -- 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] direct_messages/destroy returning 404
My code is able to send and receive direct messages just fine. So when I build the string to destroy an old direct message, I get a 404. It does not make sense. The url that is sent to Twitter is: https://api.twitter.com/1/direct_message/destroy/1625579645.json The ID is the message id that is returned within the direct message, the requesting account is the recipient of the direct message. I am using the twitteroauth php library. Anyone see what I am missing? -- 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] Rate Limit Remaining makes no sense
See if this chain of calls and the ratelimit remaining make any sense... API callReturned Ratelimit Remaining Verify Credentials 188 Followers IDs181 Direct Messages 171 The request to verify credentials established that I have 188 calls left. Since I have been testing this is OK, my max is 350. The request for followers returned 1 follower and Twitter reduced the ratelimit by 7. The request for 10 direct messages, returned ZERO, and my ratelimit is reduced by 10. While I was typing this note, I did not perform any API calls. Then, to see what happens with the calls, I execute the above sequence again, and this is what I see. API callReturned Ratelimit Remaining Verify Credentials 71 Followers IDs52 Direct Messages 39 Now, I would have expected that my application would have had 171 remaining when I ran it again, not 71. It is also strange that it is 100 off. Then the difference between the other API calls is bigger than the last time I ran to code. It seems that the rate limit is a bit capricious. I understand that Twitter says they will reduce based on load, but this is behavior is a bit strange. This makes no sense to me. Anyone have an idea why the rate limit would jump around so much? -- 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] Using API to accept a follow request, but it does not clear pending request when tweets are protected.
Here is my problem. 1. My Twitter account is set to Protect My Tweets. It is private. 2. User 1234 send a follow request to my account. 3. My application authenticates with Twitter and using the friendships/ incoming call sees that a request to follow is pending. 4. My application sends a friendships/create to follow User 1234, response is OK (200). 5. My account shows that I am now following User 1234. 5. User 1234 still shows as pending approval. This is not what I expected. I can accept the follow request via my program, but I cannot clear the pending follow request and as such, am unable to grant permission to follow my protected account via the API. Does anyone know what I am missing? Or is this one of those things that Twitter is still working on? My head hearts at this point from reading the docs and trying different things. -- 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: POST Daily limits and Direct Messages
Thanks, Matt. Since I am still in development I do not need higher limits. So there is no concern at the moment. Once I am in production it will be an issue. From what you say here, my recourse is to use the whitelisting process so seek higher limits when they are needed. Thanks for the clarification! Dave On Aug 24, 6:13 pm, Matt Harris thematthar...@twitter.com wrote: Hi Dave, Thanks for the reply, and i'm sorry the documentation didn't answer your question. OAuth does have a rate limit of 350 REST API requests per hour which applies mainly to GET requests. This API rate limit is separate to the limits you found on the support pages. In fact, the limits on the support pages are ones which apply if you use the API or not. The options you have are this: If your application requires a higher rate limit you can apply for whitelisting using the Whitelisting Request Form. Be aware that whitelisting is only available to developers and to applications in production though; all other requests are rejected. The link and details of what to expect for this can be found in the Whitelisting section of the Rate Limiting documentation: http://dev.twitter.com/pages/rate-limiting#whitelisting The alternative is to open a support ticket explaining your situation. The user support team will then be able to advise you on what options are available. You can open a ticket usinghttp://bit.ly/twicket Hope that helps, Matt On Tue, Aug 24, 2010 at 9:09 AM, DaveH d...@idreia.com wrote: Matt: Not sure what you want me to pick up in the documentation. I must be missing something. When I read the page on daily POST limits [http://support.twitter.com/ forums/10711/entries/15364] I see: quote Current Twitter Limits The current technical limits for accounts are: Direct Messages: 250 per day. API Requests: 150 per hour. Updates: 1,000 per day. The daily update limit is further broken down into smaller limits for semi-hourly intervals. Retweets are counted as updates. Changes to Account Email: 4 per hour. Following (daily): Please note that this is a technical account limit only, and there are additional rules prohibiting aggressive following behavior. You can find detailed page describing following limits and prohibited behavior on the Follow Limits and Best Practices Page. The technical follow limit is 1,000 per day. Following (account-based): Once an account is following 2,000 other users, additional follow attempts are limited by account-specific ratios. The Follow Limits and Best Practices Page has more information. /quote When I read the page you pointed me to, I see that OAuth calls are 350 per hour. So I am still left with the same question, when we hit the daily POST limit, is there a process to ask for an increase? The documentation says it is controlled at a user level, which implies an increase is possible. Yet the documentation does not explicitly say how an increase is requested. I am sure the answer is obvious, I just have been unable to find it. Looking forward to your reply... Dave -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- 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: POST Daily limits and Direct Messages
Matt: Not sure what you want me to pick up in the documentation. I must be missing something. When I read the page on daily POST limits [http://support.twitter.com/ forums/10711/entries/15364] I see: quote Current Twitter Limits The current technical limits for accounts are: Direct Messages: 250 per day. API Requests: 150 per hour. Updates: 1,000 per day. The daily update limit is further broken down into smaller limits for semi-hourly intervals. Retweets are counted as updates. Changes to Account Email: 4 per hour. Following (daily): Please note that this is a technical account limit only, and there are additional rules prohibiting aggressive following behavior. You can find detailed page describing following limits and prohibited behavior on the Follow Limits and Best Practices Page. The technical follow limit is 1,000 per day. Following (account-based): Once an account is following 2,000 other users, additional follow attempts are limited by account-specific ratios. The Follow Limits and Best Practices Page has more information. /quote When I read the page you pointed me to, I see that OAuth calls are 350 per hour. So I am still left with the same question, when we hit the daily POST limit, is there a process to ask for an increase? The documentation says it is controlled at a user level, which implies an increase is possible. Yet the documentation does not explicitly say how an increase is requested. I am sure the answer is obvious, I just have been unable to find it. Looking forward to your reply... Dave
[twitter-dev] POST Daily limits and Direct Messages
I am working on a project that will make extensive use of the direct message feature of Twitter. However, I see that there is a daily limit of 250 direct messages. This will become an issue once I am out of test and begin to deploy my application. What, if any, is the process for requesting a higher limit on direct messages?
[twitter-dev] Re: Coming soon: a solution for Open Source applications using OAuth with the Twitter API
Strange that this was stated to be ready weeks ago and now we hear nothing about the progress. Any one that is actually involved in testing this able to weigh in and provide an update?
