Re: [twitter-dev] 500 errors from the search api on specific queries, related to geocode parameter.
It's also responding with the 500 in less than two seconds (sometimes less than one), which makes timeouts seem unlikely. -- 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
Re: [twitter-dev] 500 errors from the search api on specific queries, related to geocode parameter.
I considered that, but this fails too: http://search.twitter.com/search.json?rpp=4&q=bieber&geocode=33.25,-84,12.35mi -- 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] 500 errors from the search api on specific queries, related to geocode parameter.
I noticed some 500 responses to our search api requests this morning that were oddly consistent - specific queries that would always error, when most queries never (rarely) do. I started trying to reproduce with smaller queries, and arrived at a few examples. This search fails with a 500 error: http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.75,-84.37,12.35mi It probably should be returning an empty results list (notice the 12 mile radius). The same search with the decimals chopped off the latitude woks fine (empty results as expected): http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33,-84.77,12.35mi Removing the decimals from the longitude instead doesn't work: http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.25,-84,12.35mi *Changing* the value of the decimal digits on the latitude sometimes works, and sometimes doesn't: http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84,12.35mi http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.44,-84,12.35mi Changing the value of the decimal digits on the longitude doesn't seem to produce failures no matter what I put in. http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.99,12.35mi http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.01,12.35mi<http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.99,12.35mi> http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.44,12.35mi<http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.99,12.35mi> http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber&geocode=33.44,-84.99,12.35mi fails, but http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&geocode=33.44,-84.99,12.35mi<http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=palin&geocode=33.44,-84.99,12.35mi> (geocode only) works fine. I tested a few of these without rpp, lang, and result_type params with identical results, so you can probably disregard those. These aren't random failures - every time I try one of the failing queries, it continues to fail (though that may change as the result set changes over time). Are there any known bugs with the geocode handling in the search api? - Eric -- 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: Search API rate limit change?
We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver wrote: > Hello, > > After the latest performance issues with the search api i have been > seeing a lot of 420 response codes.From yesterday until now i only get > 420 responses on the every search i make. In particular, i search for > about 100 keywords simultaneously every 6 mins. Why is this happening? > Was there any change on the Search API limit? > > Any help is greatly appreciated. > > Thanks, > Zaver -- 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: consistency and ecosystem opportunities
"More specifically, developers ask us if they should build client apps that mimic or reproduce the mainstream Twitter consumer client experience. The answer is no." "We need to ensure users can interact with Twitter the same way everywhere." I'm not sure you can say these things and simultaneously try to say you have a welcoming developer environment. All third party Twitter developers, no matter what they make, are now walking on eggshells, constantly at risk of offending Twitter's ideas of how users should interact with Twitter. You may feel you "need" this consistency, but you don't. You want it, and are willing to make tradeoffs to get it. I just hope you realize how big those tradeoffs are, and how chilling it is for Twitter to decide that only certain kinds of innovation on the Twitter API are welcome. -- Eric -- 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] web app with mobile clients
Hi. I'm creating mobile clients (Android - iPhone) for a website which uses a twitter application configured as Web. Mobile applications require twitter applications configured as client, disconnecting the mobile apps users with the website. Is there a workaround? Does anyone dealt with this before? Is there a way to use the twitter application configured as Web from the mobile clients? 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] Re: Streaming Api returning tweets with NULL value for object place
Same question here. Eric On Feb 17, 12:59 am, aci wrote: > Hello, > > I am using the streaming api in order to be able to save tweets that > uses the geoJSON place key of the returned json object. Tt was working > fine last Tuesday, Feb 15, But now, there seems to be a problem with > the place tag of the tweet object. > > I was just wondering if it's just me or is there some sort of bug or > changes have been made in the API? > > Aci Cartagena -- 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: xAuth request returns 401, need help
Was the cause of the empty response body ever discovered? I'm having a similar issue, except my 401 response body has "Content-Length: 1" containing an empty space " ". On Nov 19 2010, 3:44 pm, Matt Harris wrote: > Hey Chrys, > > Agreed. The authentication header doesn't have to be in order but as said > previously, it helps with debugging. > > It is really strange that the response body is empty. It maybe easier if you > email me the full request headers, with response headers and content so I > can debug further. For security it'll be easier if you email me that > directly. > > Best, > @themattharris > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > > On Fri, Nov 19, 2010 at 12:20 PM, Chrys Bader wrote: > > Also, the example here shows that the Auth header and the base string > > aren't in the same order: > > >http://dev.twitter.com/pages/xauth > > > On Nov 19, 11:04 am, Matt Harris wrote: > > > Hey Chrys, > > > > The order of the parameters in the base string matter and they should be > > in > > > lexicollexicographical order. For ease of debugging and to remove any > > > ambiguity it would be better to have the authorization header use the > > same > > > order too. > > > > Can you tell me what the body content of the 401 error is? > > > > Best, > > > @themattharris > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > On Thu, Nov 18, 2010 at 6:55 PM, Chrys Bader wrote: > > > > Does the order of the params in either the Authorization or Base > > > > string matter? > > > > > Here are my Request Headers: > > > > > Authorization = "OAuth oauth_timestamp=\"1290134876\", oauth_nonce= > > > > \"D3EC42D2-A37F-4298-987D-0F9603B0C9C7\", oauth_version=\"1.0\", > > > > oauth_consumer_key=\"xxx\", oauth_signature_method=\"HMAC-SHA1\", > > > > oauth_signature=\"MOWT%2BaSs35RhzvRRMVxRG0Y5p0E%3D\""; > > > > "Content-Length" = 71; > > > > "Content-Type" = "application/x-www-form-urlencoded; > > > > charset=utf-8"; > > > > > Here is my actual base string: > > > > > POST&https%3A%2F%2Fapi.twitter.com%2Foauth > > > > %2Faccess_token&oauth_consumer_key%3Dxxx%26oauth_nonce%3DD3EC42D2- > > > > A37F-4298-987D-0F9603B0C9C7%26oauth_signature_method%3DHMAC- > > > > SHA1%26oauth_timestamp%3D1290134876%26oauth_version%3D1.0%26x_auth_mode > > > > %3Dclient_auth%26x_auth_password%3Dxxx%26x_auth_username%3Dchrysb > > > > > On Nov 18, 6:47 pm, Chrys Bader wrote: > > > > > Yes I compared the UTC timestamp that my phone is generating with the > > > > > actual UTC timestamp, and they were the same. > > > > > > Is there anything else I can show you for more information? > > > > > > No matter what, I just keep getting a 401 response from Twitter. > > > > > > On Nov 18, 6:41 pm, Matt Harris wrote: > > > > > > > OK, but is the UTC timestamp actually accurate? we've heard of a > > number > > > > of > > > > > > phones whose date/time are wildly wrong. It maybe find but it's > > quite > > > > > > common. > > > > > > > Your content-type is fine. > > > > > > Matt > > > > > > > On Thu, Nov 18, 2010 at 6:03 PM, Chrys Bader > > wrote: > > > > > > > Ok, I looked into it. According to the iPhone SDK documentation, > > I > > > > am > > > > > > > indeed sending the UTC (GMT) timestamp. > > > > > > > > Still not sure what else could be wrong? > > > > > > > > Is this the right Content-Type? > > > > > > > > "Content-Type" = "application/x-www-form-urlencoded; > > charset=utf-8"; > > > > > > > > On Nov 18, 5:53 pm, themattharris > > wrote: > > > > > > > > Hey Chrys, > > > > > > > > > A couple of things to check first: > > > > > > > > > 1. Have you been granted xAuth access? > > > > > > > > 2. Double check the timestamp of your request is within 10 or > > so > > > > > > > > minutes of the time returned by Twitter's servers. Our server > > time > > > > is > > > > > > > > in UTC. > > > > > > > > 3. Verify your encoding is correct. For example: a password > > like > > > > ab$ > > > > > > > > %&123 should be in your basestring as ab%2524%2525%2526123 and > > in > > > > your > > > > > > > > post body as ab%24%25%26123. > > > > > > > > > Best, > > > > > > > > Matt > > > > > > > > > On Nov 18, 5:31 pm, Chrys Bader wrote: > > > > > > > > > > *bump* > > > > > > > > > > I've run my base string through an oAuth verifier ( > > > >http://quonos.nl/ > > > > > > > > > oauthTester/), and it all checks out! > > > > > > > > > > Any ideas? > > > > > > > > > > On Oct 27, 4:50 pm, Chrys Bader wrote: > > > > > > > > > > > Hey all, > > > > > > > > > > > This is my first post in this group, hi! > > > > > > > > > > > I am having trouble making a request onhttps:// > > > > > > > api.twitter.com/oauth/access_token. > > > > > > > > > > I've been at this for 2 days and I can't make any progress. > > I > > > > feel > > > > > > > > > > like everything matches up with all examples, > > documentation, > > > > and > > > > > > > other > > > > > > > > > > forum posts perfectly. > > > > > > > > > > > Here is my post body: >
[twitter-dev] xAuth access_token returning 1-length 401 response
I'm trying to to get xAuth to work with my application, using libcurl and a modified TwitCurl engine. Whenever I attempt to obtain an access token, I get a 401 error that contains a single space character (0x20) and nothing else, which is extremely unhelpful. Whenever I try to do other things that shouldn't work (like setting a status without a token), the 401 error returns a useful message, so I'm pretty sure my system is working fine. Can someone point out what I'm missing here? Thanks. Here's what I'm sending to the Twitter servers... URL https://api.twitter.com/oauth/access_token HTTP Header OAuth oauth_consumer_key="cmPTwoVnltXa2N8FAgepw", oauth_nonce="12947058132c2", oauth_signature="6nWCiAN9vg4UYXtaLqh7FLFuq7E%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1294705813", oauth_version="1.0" Data x_auth_mode=client_auth%26x_auth_password%3DMYPASSWORD %26x_auth_username%3DMYUSERNAME Signature Base POST&https%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_token&oauth_consumer_key%3DcmPTwoVnltXa2N8FAgepw %26oauth_nonce%3D12947058132c2%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1294705813%26oauth_version%3D1.0%26x_auth_mode %3Dclient_auth%26x_auth_password%3DMYPASSWORD%26x_auth_username %3DMYUSERNAME And here's what I'm seeing in my logs: * About to connect() to api.twitter.com port 443 (#0) * Trying 128.242.240.253... * connected * Connected to api.twitter.com (128.242.240.253) port 443 (#0) * SSL connection using DHE-RSA-AES256-SHA * Server certificate: *subject: serialNumber=Zys2dJJ09EPoEVGXYtegIdxG3OZtEOib, C=US, O=*.twitter.com, OU=GT57932074, OU=See www.rapidssl.com/resources/cps (c)10, OU=Domain Control Validated - RapidSSL(R), CN=*.twitter.com *start date: 2010-07-13 10:40:16 GMT *expire date: 2011-08-15 12:55:17 GMT *subjectAltName: api.twitter.com matched *issuer: C=US, O=Equifax, OU=Equifax Secure Certificate Authority *SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. > POST /oauth/access_token HTTP/1.1 Host: api.twitter.com Accept: */* Content-Length: 85 Content-Type: application/x-www-form-urlencoded < HTTP/1.1 401 Unauthorized < Date: Tue, 11 Jan 2011 00:25:19 GMT < Server: hi < Status: 401 Unauthorized < X-Transaction: 1294705519-89572-46458 < Last-Modified: Tue, 11 Jan 2011 00:25:19 GMT < X-Runtime: 0.00697 < Content-Type: text/html; charset=utf-8 < Content-Length: 1 < Pragma: no-cache < X-Revision: DEV < Expires: Tue, 31 Mar 1981 05:00:00 GMT < Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 < Set-Cookie: k=38.98.60.253.1294705519623615; path=/; expires=Tue, 18- Jan-11 00:25:19 GMT; domain=.twitter.com < Set-Cookie: guest_id=129470551976790627; path=/; expires=Thu, 10 Feb 2011 00:25:19 GMT < Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJhsdnItAToHaWQiJWFjZDlkNWQ2YmNkOTc0%250ANmU0ZTkxNzlmZjdlMGQ0OWUxIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--075877d72b9a221a932648a45490dab951649d50; domain=.twitter.com; path=/ < Vary: Accept-Encoding < Connection: close < * Closing connection #0 -- 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: how can i get posts count when i use search api?
anybody can help ? 2010/12/30 Macro > when i user search api like : > http://search.twitter.com/search.json?q=google > for a keyword, i just get a list ,but i also want to get the all posts > count retweets count or like that. > > I have no idea any APIs can help me to get this and t would like to > get the data day by day in a month or week.eq: posts 100 > 12/1/2010 ;posts 321 12/2/2010.. > > Am i allowed to get this number and how ? > > > thanks very 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
[twitter-dev] Streaming API, GeoLocation Filtering
Hello all, Just a general question about a location-based predicate. According to the streaming API docs... "Only tweets that are both created using the Geotagging API and are placed from within a tracked bounding box will be included in the stream..." But, as other have pointed out, a lot/most of the statuses that come back from such a filtered query don't always contain GeoLocation data. So... what's going on here? Am I missing something? I'm not necessarily concerned that I'm getting more data than I can use (although it's unfortunate from a rate-limiting standpoint), but my curiosity is certainly piqued. For the project I'm working on (I'm a grad student), I'm trying to "listen" to activity in different locations and sonify it on the fly. In keeping with best practices, I build one filter predicate for a handful of locations and try to make sense of the data as it comes by, rather than opening a handful of streams. As a result, I end up with a great many tweets I can't attribute to a geographic source, sans GeoLocation data. Based on the wording above though, I understand it to mean a status that clears the filter should have that information. Any insight would be greatly appreciated. Best, Eric Humphrey -- 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: twitter api throwing lots of technical errors
We are seeing same at Twitalyzer. Seems to be isolated to the search API but we haven't had a chance to dig in. The problems seem to be correlated to Twitter's announcement of the new search platform as well. Anyone else seeing lower rate limits on the search API last few days? @erictpeterson On Oct 7, 9:56 am, Adam Covati wrote: > Is anyone else seeing an elevated rate of API errors right now? It > seems to be throwing a lot "technical error"s (the one with the image > of the robot) right now. > > Any help or response on this would be appreciated. -- 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: Searching for tweets containing a specific domain
I'll start digging into the Search API and seeing how that performs. I can tell you from experience that the streaming API does not currently carry the expanded URL metadata in its payload. All you get is a match on raw tweet content. On Sep 24, 6:34 am, Brian Medendorp wrote: > I just did a search for a domain, and it did indeed return results > from shortened URLs, so it seems to still work (or they fixed the > problem). > > The only reasonable way I have found to consume the feed of a specific > domain is to use the search API. You'll need to periodically perform a > search, and keep track of the most recent ID that you found in the > previous search so you'll know when to stop. You may also need to > adjust the time between searches based on how many results you get. > > You could probably also use the streaming API with a filter for the > domain, though I am not sure if that will work with the shortened > URLs, and it would of course require keeping a connection open. -- 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] Searching for tweets containing a specific domain
If you query search.twitter.com for a specific domain, such as techcrunch.com, you'll get a list of all tweets that contain that domain, even if it's contained in a shortened URL. Using domains as predicates in Streaming Track doesn't result in the same behavior, only matching on actual body text as opposed to metadata. What is the most effective strategy to consume a feed of domain- specific tweets at this point? Thanks! Eric -- 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
Re: [twitter-dev] Over 3 weeks waiting on whitelist approval
Greetings, Thank you for the offer. I resubmitted my request on Friday. My username is @evidencebot with the email e...@ecei.tohoku.ac.jp Take care, Eric Nichols Tohoku University On Aug 17, 2010, at 11:32 PM, Taylor Singletary wrote: > We're still pretty backed up and taking a divide and conquer strategy, > processing recent ones and older ones to gradually meet in the middle. The > scale of requests is large. Feel free to resubmit your request and drop a > note in this thread with your Twitter screen name and we can look into them > for you. > > Just as a general reminder: whitelisting is a privilege and you should always > be working within the bounds of the basic limits provided to you by Twitter > rather than counting on a whitelisted scenario being in your future. > > Taylor > > On Mon, Aug 16, 2010 at 11:26 PM, Eric Nichols > wrote: > Greetings, > > I applied for whitelist approval for the account @evidencebot back on > 7/23 and am still waiting for a reply. > I read in the archives that whitelist approval was suspended until the > end of the World Cup but that was a while ago. > Are there still a lot of requests in the pipeline, or has my > application slipped through the cracks somehow? > > Thank you for your time, > > Eric Nichols > Tohoku University >
Re: [twitter-dev] Update on Twifficiency
On behalf of the Internet. Thank you. ~e On Wed, Aug 18, 2010 at 3:45 PM, Brian Sutorius wrote: > Hi all, > > Over the past 24 hours, we've received some questions about the > Twifficiency app, so we thought we'd use this as an opportunity to > quickly share some information around our Developer Principles. > > For background, the Twifficiency app computes a "Twifficiency score" > based on different aspects of your Twitter account and posts the score > as a Tweet. While the developer included a disclaimer that these > Tweets would be posted to Twitter, user feedback indicated that the > text was too far down on the page to be noticed before proceeding. As > a result, many users were surprised that their scores were being > tweeted automatically. > > Which brings us to our Developer Principles, one of which is "Don't > surprise users." Specifically, we require developers to get users' > permission before sending Tweets or other messages on their behalf. > Allowing an application to access your account does not constitute > consent for actions to automatically be taken on your behalf. > > Twifficiency violated this principle, so we suspended the app > yesterday afternoon while we worked with the developer to make sure > users were better informed about the application's actions and could > control whether or not a Tweet would be posted. With these changes > --which include a more prominent warning and a checkbox on the main > page-- the application has been re-enabled. > > Our developer principles can be found in our API Terms of Service: > http://dev.twitter.com/pages/api_terms > > Brian Sutorius > API Policy >
[twitter-dev] Over 3 weeks waiting on whitelist approval
Greetings, I applied for whitelist approval for the account @evidencebot back on 7/23 and am still waiting for a reply. I read in the archives that whitelist approval was suspended until the end of the World Cup but that was a while ago. Are there still a lot of requests in the pipeline, or has my application slipped through the cracks somehow? Thank you for your time, Eric Nichols Tohoku University
Re: [twitter-dev] Re: API HTTP Post statuses/update.xml
Thanks. Sounds good. How about this to bake your noodle. Not to be a dead horse. But, looking here <http://dev.twitter.com/doc/post/statuses/update> it appears as though the statuses/update does not have a rate limit, other than the 1000 limit for the day that applies regardless which i have not hit. Figure it all seems confusing. Still appears that I should not even have an hourly limit with this api only the daily 1000. I guess rules of thumb although I would like to have not gotten rate limited until a higher number than the ~150 because of to much at one time. So the 150 is only for GET not POST. POST is what I do. So it looks like the 1000 is what I do hit and something that governs that limit seems to have a condition that states that if there is a lot of statuses/update within a certain time period flag the account with this rate limit for the next hour or so. On Thu, Jul 29, 2010 at 4:59 PM, natefanaro wrote: > From personal experience the limit is around 150 per hour. That number > has been raised/lowered in the past and yes the error message is > misleading. It is possible that the 150 per hour is just a hard limit > and 1000 per day is a policy limit. Either way if you can technically > post 150 an hour that's as many as you're going to be able to do. > Unless you present a very very good case to Twitter I don't believe > this limit can be raised. > > I know the link Matt gave has some solid numbers but I wouldn't expect > any more detail than that. It's been mentioned in this group before > that exact numbers can't be given about some limits. They can change > at any time and spammers could use that info to fly under the spam > team's radar. > > On Jul 29, 3:50 pm, Eric Mortensen wrote: > > Why not? If Twitter states I can send 150 an hour or 1000 a day I should > be > > able to. Not my rules its twitters. So I guess it needs to be written > > somewhere that 42 per hour is the limit. I am just trying to understand > why > > it appears that I am hitting a limit when i am only doing what twitter > > apparently allows. The limit I see is possibly the number of messages > sent > > at one time and twitter can't handle it and throws the error I have been > > receiving. So if that exists than I understand. I just need to know > where > > it is stated. The error message appears to wrong as well since I can > still > > send tweets and it has been a couple hours later. Then I can tell the > > program manager that this is why we can't send this many messages because > of > > this limit. Maybe what will help is a link stating that there are > > protections that prevent a certain number of updates/tweets happening at > > once. > > > > Thanks > > > > On Thu, Jul 29, 2010 at 3:22 PM, Matt Harris >wrote: > > > > > Why are you sending so many Tweets? It sounds like you are being > restricted > > > because you are sending too many per hour. The limit of updates per day > > > exists but there are protections to prevent all those updates happening > at > > > once. I'm not familiar with the code that handles the measure windows > or > > > what the limits are but consider that 1000 tweets per day is approx 42 > per > > > hour. > > > > > Matt > > > > > On Thu, Jul 29, 2010 at 8:59 AM, Eric Mortensen >wrote: > > > > >> For instance, set up the my database to create 200 tweets to post to a > > >> account. It ran at 11:49 AM EST. I noticed that 127 tweets were > posted and > > >> the remaining got kicked with the error response. Not sure if there is > a > > >> limit of 127 I thought it was 150 limit per hour. This also does not > hit > > >> the 1000 daily limit since it was only 200 tweets. I will try this > again in > > >> about 1 hour. I should be able to start tweeting again. Let me know > what > > >> you think? > > > > >> On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen >wrote: > > > > >>> But, It appears did not hit a 1000 update limit since after an hour > and > > >>> can start updates again. That why it appears to be an hourly limit. > Not to > > >>> mention when this started I did not even have a 1000 tweets total on > the > > >>> account. That is why it can't be the 1000 a day limit. There is > should be > > >>> another reason for this. > > > > >>> On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris < > thematthar...@twitter.com>wrote: > > > > >>>> Hey Eric, > > > > >>>
Re: [twitter-dev] API HTTP Post statuses/update.xml
Why not? If Twitter states I can send 150 an hour or 1000 a day I should be able to. Not my rules its twitters. So I guess it needs to be written somewhere that 42 per hour is the limit. I am just trying to understand why it appears that I am hitting a limit when i am only doing what twitter apparently allows. The limit I see is possibly the number of messages sent at one time and twitter can't handle it and throws the error I have been receiving. So if that exists than I understand. I just need to know where it is stated. The error message appears to wrong as well since I can still send tweets and it has been a couple hours later. Then I can tell the program manager that this is why we can't send this many messages because of this limit. Maybe what will help is a link stating that there are protections that prevent a certain number of updates/tweets happening at once. Thanks On Thu, Jul 29, 2010 at 3:22 PM, Matt Harris wrote: > Why are you sending so many Tweets? It sounds like you are being restricted > because you are sending too many per hour. The limit of updates per day > exists but there are protections to prevent all those updates happening at > once. I'm not familiar with the code that handles the measure windows or > what the limits are but consider that 1000 tweets per day is approx 42 per > hour. > > Matt > > > On Thu, Jul 29, 2010 at 8:59 AM, Eric Mortensen wrote: > >> For instance, set up the my database to create 200 tweets to post to a >> account. It ran at 11:49 AM EST. I noticed that 127 tweets were posted and >> the remaining got kicked with the error response. Not sure if there is a >> limit of 127 I thought it was 150 limit per hour. This also does not hit >> the 1000 daily limit since it was only 200 tweets. I will try this again in >> about 1 hour. I should be able to start tweeting again. Let me know what >> you think? >> >> >> On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen wrote: >> >>> But, It appears did not hit a 1000 update limit since after an hour and >>> can start updates again. That why it appears to be an hourly limit. Not to >>> mention when this started I did not even have a 1000 tweets total on the >>> account. That is why it can't be the 1000 a day limit. There is should be >>> another reason for this. >>> >>> >>> On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris >>> wrote: >>> >>>> Hey Eric, >>>> >>>> That error is the Twitter Limits kicking in saying there are too many >>>> status updates being posted by the account. This isn't an API rate limit >>>> but >>>> a natural limit which applies to all of Twitter. A user may not Twitter >>>> more >>>> than 1000 updates a day (this includes retweets). >>>> >>>> More information on these limits are explained on the page I linked to >>>> before: http://support.twitter.com/forums/10711/entries/15364 >>>> >>>> Hope that clarifies the what is happening. >>>> Matt >>>> >>>> >>>> On Tue, Jul 27, 2010 at 12:27 PM, Eric Mortensen wrote: >>>> >>>>> Here is a response: >>>>> >>>>> >>>>> User is over daily status update limit. >>>>> /1/statuses/update.xml >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, Jul 15, 2010 at 5:41 PM, Matt Harris < >>>>> thematthar...@twitter.com> wrote: >>>>> >>>>>> Hey Eric, >>>>>> >>>>>> Sorry that help article didn't answer your question. Can you provide >>>>>> the actual HTTP request being made and the HTTP response you get back? >>>>>> We're >>>>>> interested in the response body content in particular. >>>>>> >>>>>> Also, remember we disable basic authentication on August 16th so you >>>>>> want to switch to that method of authentication now. >>>>>> >>>>>> Matt >>>>>> >>>>>> On Thu, Jul 15, 2010 at 12:46 PM, Eric Mortensen >>>>>> wrote: >>>>>> >>>>>>> Unfortunately not. Do you have anything else that might explain it? >>>>>>> >>>>>>> >>>>>>> On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris < >>>>>>> thematthar...@twitter.com> wrote: >>>>>>> >>>>>>>> Hi
Re: [twitter-dev] API HTTP Post statuses/update.xml
For instance, set up the my database to create 200 tweets to post to a account. It ran at 11:49 AM EST. I noticed that 127 tweets were posted and the remaining got kicked with the error response. Not sure if there is a limit of 127 I thought it was 150 limit per hour. This also does not hit the 1000 daily limit since it was only 200 tweets. I will try this again in about 1 hour. I should be able to start tweeting again. Let me know what you think? On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen wrote: > But, It appears did not hit a 1000 update limit since after an hour and can > start updates again. That why it appears to be an hourly limit. Not to > mention when this started I did not even have a 1000 tweets total on the > account. That is why it can't be the 1000 a day limit. There is should be > another reason for this. > > > On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris wrote: > >> Hey Eric, >> >> That error is the Twitter Limits kicking in saying there are too many >> status updates being posted by the account. This isn't an API rate limit but >> a natural limit which applies to all of Twitter. A user may not Twitter more >> than 1000 updates a day (this includes retweets). >> >> More information on these limits are explained on the page I linked to >> before: http://support.twitter.com/forums/10711/entries/15364 >> >> Hope that clarifies the what is happening. >> Matt >> >> >> On Tue, Jul 27, 2010 at 12:27 PM, Eric Mortensen wrote: >> >>> Here is a response: >>> >>> >>> User is over daily status update limit. >>> /1/statuses/update.xml >>> >>> >>> >>> >>> On Thu, Jul 15, 2010 at 5:41 PM, Matt Harris >>> wrote: >>> >>>> Hey Eric, >>>> >>>> Sorry that help article didn't answer your question. Can you provide the >>>> actual HTTP request being made and the HTTP response you get back? We're >>>> interested in the response body content in particular. >>>> >>>> Also, remember we disable basic authentication on August 16th so you >>>> want to switch to that method of authentication now. >>>> >>>> Matt >>>> >>>> On Thu, Jul 15, 2010 at 12:46 PM, Eric Mortensen wrote: >>>> >>>>> Unfortunately not. Do you have anything else that might explain it? >>>>> >>>>> >>>>> On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris < >>>>> thematthar...@twitter.com> wrote: >>>>> >>>>>> Hi Eric, >>>>>> >>>>>> In addition to the API Rate Limits there are general usage limits >>>>>> which apply to all of Twitter, including the website. These limits >>>>>> restrict >>>>>> various actions including the number of updates that can be posted per >>>>>> day. >>>>>> >>>>>> You can read more about Twitter Limits on our help website: >>>>>> http://support.twitter.com/forums/10711/entries/15364 >>>>>> >>>>>> Hope that answers your question, >>>>>> Matt >>>>>> >>>>>> >>>>>> On Thu, Jul 15, 2010 at 10:11 AM, Eric wrote: >>>>>> >>>>>>> It appears that I am hitting a 150 post rate limit when I use the >>>>>>> statuses/update.xml api to update a twitter account eventhough I >>>>>>> should not have this limit doing only a post. Is there a reason why? >>>>>>> Here is the code I am using from oracle to do this: >>>>>>> >>>>>>> create or replace PACKAGE BODY tweet >>>>>>> AS >>>>>>> >>>>>>> twit_host VARCHAR2(255) := 'api.twitter.com'; >>>>>>> twit_protocol VARCHAR2(10) := 'http://'; >>>>>>> >>>>>>> -- URL for status updates >>>>>>> tweet_url VARCHAR2(255) := '/1/statuses/update.xml'; >>>>>>> >>>>>>> >>>>>>> FUNCTION tweet >>>>>>>( >>>>>>> p_user IN VARCHAR2, >>>>>>> p_pwd IN VARCHAR2, >>>>>>> p_string IN VARCHAR2, >>>>>>> p_proxy_url IN VARCHAR2 DEFAULT NULL, >>>>>>> p_no_domains IN VARCHAR2 DEFAULT NULL ) &g
Re: [twitter-dev] API HTTP Post statuses/update.xml
But, It appears did not hit a 1000 update limit since after an hour and can start updates again. That why it appears to be an hourly limit. Not to mention when this started I did not even have a 1000 tweets total on the account. That is why it can't be the 1000 a day limit. There is should be another reason for this. On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris wrote: > Hey Eric, > > That error is the Twitter Limits kicking in saying there are too many > status updates being posted by the account. This isn't an API rate limit but > a natural limit which applies to all of Twitter. A user may not Twitter more > than 1000 updates a day (this includes retweets). > > More information on these limits are explained on the page I linked to > before: http://support.twitter.com/forums/10711/entries/15364 > > Hope that clarifies the what is happening. > Matt > > > On Tue, Jul 27, 2010 at 12:27 PM, Eric Mortensen wrote: > >> Here is a response: >> >> >> User is over daily status update limit. >> /1/statuses/update.xml >> >> >> >> >> On Thu, Jul 15, 2010 at 5:41 PM, Matt Harris >> wrote: >> >>> Hey Eric, >>> >>> Sorry that help article didn't answer your question. Can you provide the >>> actual HTTP request being made and the HTTP response you get back? We're >>> interested in the response body content in particular. >>> >>> Also, remember we disable basic authentication on August 16th so you want >>> to switch to that method of authentication now. >>> >>> Matt >>> >>> On Thu, Jul 15, 2010 at 12:46 PM, Eric Mortensen wrote: >>> >>>> Unfortunately not. Do you have anything else that might explain it? >>>> >>>> >>>> On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris >>> > wrote: >>>> >>>>> Hi Eric, >>>>> >>>>> In addition to the API Rate Limits there are general usage limits which >>>>> apply to all of Twitter, including the website. These limits restrict >>>>> various actions including the number of updates that can be posted per >>>>> day. >>>>> >>>>> You can read more about Twitter Limits on our help website: >>>>> http://support.twitter.com/forums/10711/entries/15364 >>>>> >>>>> Hope that answers your question, >>>>> Matt >>>>> >>>>> >>>>> On Thu, Jul 15, 2010 at 10:11 AM, Eric wrote: >>>>> >>>>>> It appears that I am hitting a 150 post rate limit when I use the >>>>>> statuses/update.xml api to update a twitter account eventhough I >>>>>> should not have this limit doing only a post. Is there a reason why? >>>>>> Here is the code I am using from oracle to do this: >>>>>> >>>>>> create or replace PACKAGE BODY tweet >>>>>> AS >>>>>> >>>>>> twit_host VARCHAR2(255) := 'api.twitter.com'; >>>>>> twit_protocol VARCHAR2(10) := 'http://'; >>>>>> >>>>>> -- URL for status updates >>>>>> tweet_url VARCHAR2(255) := '/1/statuses/update.xml'; >>>>>> >>>>>> >>>>>> FUNCTION tweet >>>>>>( >>>>>> p_user IN VARCHAR2, >>>>>> p_pwd IN VARCHAR2, >>>>>> p_string IN VARCHAR2, >>>>>> p_proxy_url IN VARCHAR2 DEFAULT NULL, >>>>>> p_no_domains IN VARCHAR2 DEFAULT NULL ) >>>>>>RETURN BOOLEAN >>>>>> AS >>>>>>v_req UTL_HTTP.REQ; -- HTTP request ID >>>>>>v_resp UTL_HTTP.RESP; -- HTTP response ID >>>>>>v_value VARCHAR2(1024); -- HTTP response data >>>>>>v_status VARCHAR2(160); -- Status of the request >>>>>>v_call VARCHAR2(2000); -- The request URL >>>>>>v_log_value varchar2(4000) := 'status'; >>>>>> BEGIN >>>>>> >>>>>>-- Twitter update url >>>>>>v_call := twit_protocol || >>>>>> twit_host || >>>>>> tweet_url; >>>>>> >>>>>>-- encoded status string >>>>>>v_status := utl_url.escape( >>>>>> url => 'status='
Re: [twitter-dev] API HTTP Post statuses/update.xml
Here is a response: User is over daily status update limit. /1/statuses/update.xml On Thu, Jul 15, 2010 at 5:41 PM, Matt Harris wrote: > Hey Eric, > > Sorry that help article didn't answer your question. Can you provide the > actual HTTP request being made and the HTTP response you get back? We're > interested in the response body content in particular. > > Also, remember we disable basic authentication on August 16th so you want > to switch to that method of authentication now. > > Matt > > On Thu, Jul 15, 2010 at 12:46 PM, Eric Mortensen wrote: > >> Unfortunately not. Do you have anything else that might explain it? >> >> >> On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris >> wrote: >> >>> Hi Eric, >>> >>> In addition to the API Rate Limits there are general usage limits which >>> apply to all of Twitter, including the website. These limits restrict >>> various actions including the number of updates that can be posted per day. >>> >>> You can read more about Twitter Limits on our help website: >>> http://support.twitter.com/forums/10711/entries/15364 >>> >>> Hope that answers your question, >>> Matt >>> >>> >>> On Thu, Jul 15, 2010 at 10:11 AM, Eric wrote: >>> >>>> It appears that I am hitting a 150 post rate limit when I use the >>>> statuses/update.xml api to update a twitter account eventhough I >>>> should not have this limit doing only a post. Is there a reason why? >>>> Here is the code I am using from oracle to do this: >>>> >>>> create or replace PACKAGE BODY tweet >>>> AS >>>> >>>> twit_host VARCHAR2(255) := 'api.twitter.com'; >>>> twit_protocol VARCHAR2(10) := 'http://'; >>>> >>>> -- URL for status updates >>>> tweet_url VARCHAR2(255) := '/1/statuses/update.xml'; >>>> >>>> >>>> FUNCTION tweet >>>>( >>>> p_user IN VARCHAR2, >>>> p_pwd IN VARCHAR2, >>>> p_string IN VARCHAR2, >>>> p_proxy_url IN VARCHAR2 DEFAULT NULL, >>>> p_no_domains IN VARCHAR2 DEFAULT NULL ) >>>>RETURN BOOLEAN >>>> AS >>>>v_req UTL_HTTP.REQ; -- HTTP request ID >>>>v_resp UTL_HTTP.RESP; -- HTTP response ID >>>>v_value VARCHAR2(1024); -- HTTP response data >>>>v_status VARCHAR2(160); -- Status of the request >>>>v_call VARCHAR2(2000); -- The request URL >>>>v_log_value varchar2(4000) := 'status'; >>>> BEGIN >>>> >>>>-- Twitter update url >>>>v_call := twit_protocol || >>>> twit_host || >>>> tweet_url; >>>> >>>>-- encoded status string >>>>v_status := utl_url.escape( >>>> url => 'status=' || SUBSTR( short_url.encode_text(p_string) , >>>> 1,140)); >>>> >>>>-- Authenticate via proxy >>>>-- Proxy string looks like 'http://username:passw...@proxy.com' >>>>-- p_no_domains is a list of domains not to use the proxy for >>>>-- These settings override the defaults that are configured at the >>>> database level >>>>IF p_proxy_url IS NOT NULL >>>>THEN >>>> Utl_Http.set_proxy ( >>>>proxy => p_proxy_url, >>>>no_proxy_domains => p_no_domains >>>>); >>>>END IF; >>>> >>>>-- Has to be a POST for status update >>>>v_req := UTL_HTTP.BEGIN_REQUEST( >>>> url => v_call, >>>> method =>'POST'); >>>> >>>>-- Pretend we're a moz browser >>>>UTL_HTTP.SET_HEADER( >>>> r => v_req, >>>> name => 'User-Agent', >>>> value => 'Mozilla/4.0'); >>>> >>>>-- Pretend we're coming from an html form >>>>UTL_HTTP.SET_HEADER( >>>> r => v_req, >>>> name => 'Content-Type', >>>> value => 'application/x-www-form-urlencoded'); >>>> >>>>-- Set the length of the input >>>>UTL_HTTP.SET_HEADER( >>>> r => v_req, >>>> name => 'Content-Length', >>>> value => length(v_status)); >>>> >>>>-- authenticate with twitter user/pass >>>>UTL_HTTP.SET_AUTHENTICATION( >>>> r => v_req, >>>> username => p_user, >>>> password => p_pwd ); >>>> >>>>-- Send the update >>>>UTL_HTTP.WRITE_TEXT( >>>> r => v_req, >>>> data => v_status ); >>>> >>>>UTL_HTTP.end_request (v_req); >>>> >>>>RETURN TRUE; >>>> >>>> EXCEPTION >>>>-- normal exception when reading the response >>>>WHEN UTL_HTTP.END_OF_BODY THEN >>>>UTL_HTTP.end_request (v_req); >>>> RETURN TRUE; >>>> >>>>-- Anything else and send false >>>>WHEN OTHERS THEN >>>> UTL_HTTP.end_request (v_req); >>>> Dbms_Output.Put_Line ( 'Request_Failed: ' || >>>> Utl_Http.Get_Detailed_Sqlerrm ); >>>> Dbms_Output.Put_Line ( 'Ora: ' || Sqlerrm ); >>>> RETURN FALSE; >>>> >>>> END; >>>> >>>> END tweet; >>>> >>>> >>>> >>>> Thanks >>>> >>> >>> >>> >>> -- >>> >>> >>> Matt Harris >>> Developer Advocate, Twitter >>> http://twitter.com/themattharris >>> >> >> > > > -- > > > Matt Harris > Developer Advocate, Twitter > http://twitter.com/themattharris >
Re: [twitter-dev] API HTTP Post statuses/update.xml
Unfortunately not. Do you have anything else that might explain it? On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris wrote: > Hi Eric, > > In addition to the API Rate Limits there are general usage limits which > apply to all of Twitter, including the website. These limits restrict > various actions including the number of updates that can be posted per day. > > You can read more about Twitter Limits on our help website: > http://support.twitter.com/forums/10711/entries/15364 > > Hope that answers your question, > Matt > > > On Thu, Jul 15, 2010 at 10:11 AM, Eric wrote: > >> It appears that I am hitting a 150 post rate limit when I use the >> statuses/update.xml api to update a twitter account eventhough I >> should not have this limit doing only a post. Is there a reason why? >> Here is the code I am using from oracle to do this: >> >> create or replace PACKAGE BODY tweet >> AS >> >> twit_host VARCHAR2(255) := 'api.twitter.com'; >> twit_protocol VARCHAR2(10) := 'http://'; >> >> -- URL for status updates >> tweet_url VARCHAR2(255) := '/1/statuses/update.xml'; >> >> >> FUNCTION tweet >>( >> p_user IN VARCHAR2, >> p_pwd IN VARCHAR2, >> p_string IN VARCHAR2, >> p_proxy_url IN VARCHAR2 DEFAULT NULL, >> p_no_domains IN VARCHAR2 DEFAULT NULL ) >>RETURN BOOLEAN >> AS >>v_req UTL_HTTP.REQ; -- HTTP request ID >>v_resp UTL_HTTP.RESP; -- HTTP response ID >>v_value VARCHAR2(1024); -- HTTP response data >>v_status VARCHAR2(160); -- Status of the request >>v_call VARCHAR2(2000); -- The request URL >>v_log_value varchar2(4000) := 'status'; >> BEGIN >> >>-- Twitter update url >>v_call := twit_protocol || >> twit_host || >> tweet_url; >> >>-- encoded status string >>v_status := utl_url.escape( >> url => 'status=' || SUBSTR( short_url.encode_text(p_string) , >> 1,140)); >> >>-- Authenticate via proxy >>-- Proxy string looks like 'http://username:passw...@proxy.com' >>-- p_no_domains is a list of domains not to use the proxy for >>-- These settings override the defaults that are configured at the >> database level >>IF p_proxy_url IS NOT NULL >>THEN >> Utl_Http.set_proxy ( >>proxy => p_proxy_url, >>no_proxy_domains => p_no_domains >>); >>END IF; >> >>-- Has to be a POST for status update >>v_req := UTL_HTTP.BEGIN_REQUEST( >> url => v_call, >> method =>'POST'); >> >>-- Pretend we're a moz browser >>UTL_HTTP.SET_HEADER( >> r => v_req, >> name => 'User-Agent', >> value => 'Mozilla/4.0'); >> >>-- Pretend we're coming from an html form >>UTL_HTTP.SET_HEADER( >> r => v_req, >> name => 'Content-Type', >> value => 'application/x-www-form-urlencoded'); >> >>-- Set the length of the input >>UTL_HTTP.SET_HEADER( >> r => v_req, >> name => 'Content-Length', >> value => length(v_status)); >> >>-- authenticate with twitter user/pass >>UTL_HTTP.SET_AUTHENTICATION( >> r => v_req, >> username => p_user, >> password => p_pwd ); >> >>-- Send the update >>UTL_HTTP.WRITE_TEXT( >> r => v_req, >> data => v_status ); >> >>UTL_HTTP.end_request (v_req); >> >>RETURN TRUE; >> >> EXCEPTION >>-- normal exception when reading the response >>WHEN UTL_HTTP.END_OF_BODY THEN >>UTL_HTTP.end_request (v_req); >> RETURN TRUE; >> >>-- Anything else and send false >>WHEN OTHERS THEN >> UTL_HTTP.end_request (v_req); >> Dbms_Output.Put_Line ( 'Request_Failed: ' || >> Utl_Http.Get_Detailed_Sqlerrm ); >> Dbms_Output.Put_Line ( 'Ora: ' || Sqlerrm ); >> RETURN FALSE; >> >> END; >> >> END tweet; >> >> >> >> Thanks >> > > > > -- > > > Matt Harris > Developer Advocate, Twitter > http://twitter.com/themattharris >
[twitter-dev] API HTTP Post statuses/update.xml
It appears that I am hitting a 150 post rate limit when I use the statuses/update.xml api to update a twitter account eventhough I should not have this limit doing only a post. Is there a reason why? Here is the code I am using from oracle to do this: create or replace PACKAGE BODY tweet AS twit_host VARCHAR2(255) := 'api.twitter.com'; twit_protocol VARCHAR2(10) := 'http://'; -- URL for status updates tweet_url VARCHAR2(255) := '/1/statuses/update.xml'; FUNCTION tweet ( p_user IN VARCHAR2, p_pwd IN VARCHAR2, p_string IN VARCHAR2, p_proxy_url IN VARCHAR2 DEFAULT NULL, p_no_domains IN VARCHAR2 DEFAULT NULL ) RETURN BOOLEAN AS v_req UTL_HTTP.REQ; -- HTTP request ID v_resp UTL_HTTP.RESP; -- HTTP response ID v_value VARCHAR2(1024); -- HTTP response data v_status VARCHAR2(160); -- Status of the request v_call VARCHAR2(2000); -- The request URL v_log_value varchar2(4000) := 'status'; BEGIN -- Twitter update url v_call := twit_protocol || twit_host || tweet_url; -- encoded status string v_status := utl_url.escape( url => 'status=' || SUBSTR( short_url.encode_text(p_string) , 1,140)); -- Authenticate via proxy -- Proxy string looks like 'http://username:passw...@proxy.com' -- p_no_domains is a list of domains not to use the proxy for -- These settings override the defaults that are configured at the database level IF p_proxy_url IS NOT NULL THEN Utl_Http.set_proxy ( proxy => p_proxy_url, no_proxy_domains => p_no_domains ); END IF; -- Has to be a POST for status update v_req := UTL_HTTP.BEGIN_REQUEST( url => v_call, method =>'POST'); -- Pretend we're a moz browser UTL_HTTP.SET_HEADER( r => v_req, name => 'User-Agent', value => 'Mozilla/4.0'); -- Pretend we're coming from an html form UTL_HTTP.SET_HEADER( r => v_req, name => 'Content-Type', value => 'application/x-www-form-urlencoded'); -- Set the length of the input UTL_HTTP.SET_HEADER( r => v_req, name => 'Content-Length', value => length(v_status)); -- authenticate with twitter user/pass UTL_HTTP.SET_AUTHENTICATION( r => v_req, username => p_user, password => p_pwd ); -- Send the update UTL_HTTP.WRITE_TEXT( r => v_req, data => v_status ); UTL_HTTP.end_request (v_req); RETURN TRUE; EXCEPTION -- normal exception when reading the response WHEN UTL_HTTP.END_OF_BODY THEN UTL_HTTP.end_request (v_req); RETURN TRUE; -- Anything else and send false WHEN OTHERS THEN UTL_HTTP.end_request (v_req); Dbms_Output.Put_Line ( 'Request_Failed: ' || Utl_Http.Get_Detailed_Sqlerrm ); Dbms_Output.Put_Line ( 'Ora: ' || Sqlerrm ); RETURN FALSE; END; END tweet; Thanks
[twitter-dev] User Streams and Desktop Apps
Working on an app that could definitely benefit from User Streams and wanted to know what qualifies as a "Desktop App"? Is it specifically an Air or Silverlight app installed on the desktop or is it more indicative of a certain set of behaviors / access needs? If the latter, can a "web" app with the same usage characteristics be qualify as a desktop app? Cheers! Eric
[twitter-dev] Search API returning rate limit errors at an increased rate
Folks, We make a fair number of calls to the Twitter Search API every day. When I set up our use of Search APIs with Matt Sanford over a year ago he asked us to A) identify with Twitter username and B) identify with a unique User-Agent. Based on my read of Twitter documentation we should be "good to go" with a higher rate limit for requests, although we have no idea what our rate limit is. Recently, and unfortunately because it appears to have coincided with our launch of paid services, we are seeing a pretty high rate of API responses "You have been rate limited. Enhance your calm." We have an open ticket with support (1018921) but wanted to see if A) any other of you are seeing rate limits increase using the Twitter Search API and B) if you have, if you have figured out a solution/ workaround? My calm is enhanced, but I'd love a more viable solution. We have looked at the Stream API but it's not clear to me that Stream API solves for our specific needs. I'm happy to go into all of this more deeply with Twitter API staff and can be reached at e...@twitter.com or 503-282-2601. Thanks for any/all help. Sincerely, Eric T. Peterson @erictpeterson and @twitalyzer http://twitalyzer.com
Re: [twitter-dev] Abridged summary of twitter-development-talk@googlegroups.com - 6 Messages in 5 Topics
RRe On 6/6/10, twitter-development-talk+nore...@googlegroups.com wrote: > = > Today's Topic Summary > = > > Group: twitter-development-talk@googlegroups.com > Url: http://groups.google.com/group/twitter-development-talk/topics > > - Simple Twitter App? [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/1861f4fb447e222d > - API Suggestion - Add Meta Data to twitter links... [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/650001bd6569aaca > - Incorrect Signature for oAuth [2 Updates] > > http://groups.google.com/group/twitter-development-talk/t/a5e0bfd8e1cd4177 > - Is tweet retweeted or not. [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/f686aefeb508972e > - Where to post documentation bugs? [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/963f9650a5d79c00 > > > = > Topic: Simple Twitter App? > Url: > http://groups.google.com/group/twitter-development-talk/t/1861f4fb447e222d > = > > -- 1 of 1 -- > From: John Meyer > Date: Jun 06 05:07PM -0600 > Url: > http://groups.google.com/group/twitter-development-talk/msg/e350337272234063 > > On 6/5/2010 3:21 PM, Iguanasan wrote: >> account. > >> Can anyone help point me in the right direction? > >> PS: I'm working in PHP for this project. > > It's really not all that different than > > > = > Topic: API Suggestion - Add Meta Data to twitter links... > Url: > http://groups.google.com/group/twitter-development-talk/t/650001bd6569aaca > = > > -- 1 of 1 -- > From: Lil Peck > Date: Jun 06 12:08PM -0500 > Url: > http://groups.google.com/group/twitter-development-talk/msg/f88029748471ca4f > > Are there any screenshots of how annotations will look to the > non-techie end-user? Or, will annotations always be hidden in json and > xml? I like the concept of the structure, which extends Twitter's > > > = > Topic: Incorrect Signature for oAuth > Url: > http://groups.google.com/group/twitter-development-talk/t/a5e0bfd8e1cd4177 > = > > -- 1 of 2 -- > From: rhysmeister > Date: Jun 06 05:56AM -0700 > Url: > http://groups.google.com/group/twitter-development-talk/msg/c9ac076c2b43ca5a > > Hi All, > > I am having problems identifying what is wrong with converting my app > to use oAuth. All my GET requests work fine but my POST requests all > fail with an incorrect signature error. > > -- 2 of 2 -- > From: Hwee-Boon Yar > Date: Jun 06 10:07AM -0700 > Url: > http://groups.google.com/group/twitter-development-talk/msg/2950c12d8fbc1575 > > Since it's GET works and POST, no. 1 reason is to make sure the base > URI in the base signature string is constructed correctly. In your > example, you don't need source= since it's OAuth. > > -- > > > = > Topic: Is tweet retweeted or not. > Url: > http://groups.google.com/group/twitter-development-talk/t/f686aefeb508972e > = > > -- 1 of 1 -- > From: Furkan Kuru > Date: Jun 06 02:46PM +0300 > Url: > http://groups.google.com/group/twitter-development-talk/msg/90a1753a73d36b8d > > upss sorry, > > I did not notice statuses/home_timeline. > > I have been using friends_timeline and it does not include rts for backward > compatibilities. > > > -- > Furkan Kuru > > > > = > Topic: Where to post documentation bugs? > Url: > http://groups.google.com/group/twitter-development-talk/t/963f9650a5d79c00 > = > > -- 1 of 1 -- > From: Andrew > Date: Jun 05 05:46PM -0700 > Url: > http://groups.google.com/group/twitter-development-talk/msg/3076fb92bb6a4d29 > > Folks, > > I've just successfully implemented xAuth for my iPad app. During this > process, I went down a few ratholes due to what I now consider > documentation bugs. I list them below but I would like > > > > -- Sent from my mobile device -- Eric Renz-Whitmore twitter: @ewhitmore cell: 505-227-1086 Program Coordinator, ARTS Lab http://artslab.unm.edu http://artslab.blogspot.com http://www.facebook.com/artslab twitter: @artslab_nm office: 505-277-2253
Re: [twitter-dev] Abridged summary of twitter-development-talk@googlegroups.com - 6 Messages in 5 Topics
On 6/6/10, twitter-development-talk+nore...@googlegroups.com wrote: > = > Today's Topic Summary > = > > Group: twitter-development-talk@googlegroups.com > Url: http://groups.google.com/group/twitter-development-talk/topics > > - Simple Twitter App? [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/1861f4fb447e222d > - API Suggestion - Add Meta Data to twitter links... [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/650001bd6569aaca > - Incorrect Signature for oAuth [2 Updates] > > http://groups.google.com/group/twitter-development-talk/t/a5e0bfd8e1cd4177 > - Is tweet retweeted or not. [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/f686aefeb508972e > - Where to post documentation bugs? [1 Update] > > http://groups.google.com/group/twitter-development-talk/t/963f9650a5d79c00 > > > = > Topic: Simple Twitter App? > Url: > http://groups.google.com/group/twitter-development-talk/t/1861f4fb447e222d > = > > -- 1 of 1 -- > From: John Meyer > Date: Jun 06 05:07PM -0600 > Url: > http://groups.google.com/group/twitter-development-talk/msg/e350337272234063 > > On 6/5/2010 3:21 PM, Iguanasan wrote: >> account. > >> Can anyone help point me in the right direction? > >> PS: I'm working in PHP for this project. > > It's really not all that different than > > > = > Topic: API Suggestion - Add Meta Data to twitter links... > Url: > http://groups.google.com/group/twitter-development-talk/t/650001bd6569aaca > = > > -- 1 of 1 -- > From: Lil Peck > Date: Jun 06 12:08PM -0500 > Url: > http://groups.google.com/group/twitter-development-talk/msg/f88029748471ca4f > > Are there any screenshots of how annotations will look to the > non-techie end-user? Or, will annotations always be hidden in json and > xml? I like the concept of the structure, which extends Twitter's > > > = > Topic: Incorrect Signature for oAuth > Url: > http://groups.google.com/group/twitter-development-talk/t/a5e0bfd8e1cd4177 > = > > -- 1 of 2 -- > From: rhysmeister > Date: Jun 06 05:56AM -0700 > Url: > http://groups.google.com/group/twitter-development-talk/msg/c9ac076c2b43ca5a > > Hi All, > > I am having problems identifying what is wrong with converting my app > to use oAuth. All my GET requests work fine but my POST requests all > fail with an incorrect signature error. > > -- 2 of 2 -- > From: Hwee-Boon Yar > Date: Jun 06 10:07AM -0700 > Url: > http://groups.google.com/group/twitter-development-talk/msg/2950c12d8fbc1575 > > Since it's GET works and POST, no. 1 reason is to make sure the base > URI in the base signature string is constructed correctly. In your > example, you don't need source= since it's OAuth. > > -- > > > = > Topic: Is tweet retweeted or not. > Url: > http://groups.google.com/group/twitter-development-talk/t/f686aefeb508972e > = > > -- 1 of 1 -- > From: Furkan Kuru > Date: Jun 06 02:46PM +0300 > Url: > http://groups.google.com/group/twitter-development-talk/msg/90a1753a73d36b8d > > upss sorry, > > I did not notice statuses/home_timeline. > > I have been using friends_timeline and it does not include rts for backward > compatibilities. > > > -- > Furkan Kuru > > > > = > Topic: Where to post documentation bugs? > Url: > http://groups.google.com/group/twitter-development-talk/t/963f9650a5d79c00 > = > > -- 1 of 1 -- > From: Andrew > Date: Jun 05 05:46PM -0700 > Url: > http://groups.google.com/group/twitter-development-talk/msg/3076fb92bb6a4d29 > > Folks, > > I've just successfully implemented xAuth for my iPad app. During this > process, I went down a few ratholes due to what I now consider > documentation bugs. I list them below but I would like > > > > -- Sent from my mobile device -- Eric Renz-Whitmore twitter: @ewhitmore cell: 505-227-1086 Program Coordinator, ARTS Lab http://artslab.unm.edu http://artslab.blogspot.com http://www.facebook.com/artslab twitter: @artslab_nm office: 505-277-2253
[twitter-dev] Re: Twitter OAuth & Timestamps
Thanks. I did look through the archives before posting but did not find anything. I will look harder next time. I still don't see where in the OAuth specifications it says this comparison is necessary, but I will continue to look around. --ejw Eric Woodward Email: e...@nambu.com On May 25, 5:49 pm, "Brian Smith" wrote: > This is known and expected behavior. There have been other threads about it > in the last couple of weeks. If you get a 401 response, you should compare > the Date header of Twitter's response to the current system time. If it is > significantly off then you should warn the user so they can fix it and/or > calculate the difference and add that offset to all your timestamps. More > details are available in the mailing list archive. > > Regards, > Brian > > > > > > > -Original Message- > > From: twitter-development-talk@googlegroups.com [mailto:twitter- > > development-t...@googlegroups.com] On Behalf Of Eric Woodward > > Sent: Tuesday, May 25, 2010 7:40 PM > > To: Twitter Development Talk > > Subject: [twitter-dev] Twitter OAuth & Timestamps > > > I have confirmed a problem with xAuth/OAUth that I believe resides within > > Twitter OAuth implementation that has been a thorn in our side for a > while. I say > > *believe* because I do not claim to know for sure, thus this post. > > > I assume no one at Twitter will be inclined to do me any favours, but > please > > answer for the sake of the users in general, and other developers in here > that do > > a better job of not publicly expressing their opinions of what Twitter has > been > > doing to its ecosystem. > > > If a user's desktop time is off by a significant margin, say 30m, we have > > confirmed that a valid username/password via an xAuth request will fail. > This has > > been very painful to track down since those working on Nambu tend to have > the > > desktop time set correctly, and only a handful users complain > legitimately, with > > credibility. This tweet started us on to a solution: > >http://twitter.com/imhassan/status/14639986090. > > It is not affecting just Nambu. > > > I cant find anything in the OAuth specs to suggest this comparison to the > actual > > time should take place, so I assume Twitter is just going ahead and > comparing > > the submitted timestamp to the actual time, and rejecting the request (for > > perhaps a good reason), or it is a bug. We are getting a 401 on a valid > request > > with an inaccurate timestamp. > > > This issue is hinted at here:http://weblog.bluedonkey.org/?p=959. > > > Anyway, we are putting a workaround in place, so if no one at Twitter > responds, > > no worries, Nambu will work going forward. Other developers, be aware that > > this issue exists. This is very annoying to me because users with > inaccurate time > > settings have tried to verify their accounts in Nambu, failed, and then > use the > > official Twitter application for OSX (aka Tweetie), which works because it > is still > > on HTTP Basic authentication, and declared Nambu to be broken. > > > Twitter, please clarify which part of the process is indeed broken, and > what you > > expect to see regarding timestamps on your end. I assume that by the time > > Twitter for OSX is updated to use xAuth you will have put a solution in > place for > > this, or will at some point soon afterward as users complain. It would be > nice if > > you outlined that solution for the rest of us when the time comes, so > perhaps > > we can improve on what we have come up with. > > > I apologize in advance if I missed something obvious in the docs > somewhere. I > > am not an expert on OAuth by any means, and have not studied this issue > per se. > > I have only been trying to resolve the issue for us to move on to > something more > > important. Our OAuth implementation works fine otherwise. Well, as well as > the > > rest of the Twitter API "works", anyway. > > > Cheers. > > > --ejw > > > Eric Woodward > > Email: e...@nambu.com
[twitter-dev] Twitter OAuth & Timestamps
I have confirmed a problem with xAuth/OAUth that I believe resides within Twitter OAuth implementation that has been a thorn in our side for a while. I say *believe* because I do not claim to know for sure, thus this post. I assume no one at Twitter will be inclined to do me any favours, but please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here: http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API "works", anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
At this point I am not why anyone that cares enough to be in this group is surprised. It is clear that Twitter is going to take *everything* for themselves. I don't understand why anyone would continue to develop on Twitter's platform as anything more than a hobby. First it was us (Twitter clients) and now it is the ad platforms' turn. Next it will be somebody else. Lots of us enjoy developing for its own sake, and that is what Twitter is now: a feature you add to something else, or a hobby activity. Time we all just faced up to it. --ejw Eric Woodward Email: e...@nambu.com On May 24, 9:23 am, Mo wrote: > You guys couldn't have hinted about this to me at the developer meetup > or at Chirp before I built up a team? Thanks.
[twitter-dev] Re: Basic authentication
We are using the Streaming API and will only be using our own credentials. Our experience with OAuth in other services has not been positive, so like TJ says "huge hassle for no gain". +1 Thanks. -Eric On May 18, 9:28 am, TJ Luoma wrote: > On Tue, May 18, 2010 at 11:32 AM, Jef Poskanzer > wrote: > > For my command-line twitter applications there is no third party, just > > the end-user and twitter. Basic Auth + https would be just fine for > > that. > > +1 > > I don't access anyone's account information except my own. This is a > huge hassle for no gain at all for me. > > Not that I expect that to change.
[twitter-dev] Re: Background Image & twitteroauth library
Hey Abraham,
Thanks for the reply! Just curious if there was any ETA on the release
of the BETA?
On May 12, 9:45 am, Abraham Williams <4bra...@gmail.com> wrote:
> Images are not supported in the current version. Look for the next beta
> soon.
>
> Abraham
>
>
>
> On Tue, May 11, 2010 at 22:08, Eric wrote:
> > Hi Everyone,
>
> > I'm attempting to use the twittoauth library by Abraham Williams and
> > am having a little trouble. I am able to authenticate and get
> > everything, for the most part, working properly. The only thing I
> > can't do is get the background image to update.
>
> > Function I'm Using in index.php:
> > $connection->post('account/update_profile_background_image',
> > array('image' => 'images/cool-blue.jpg'));
>
> > index.php is in a root directory and there is a folder called images
> > with the cool-blue.jpg background in there. The file size is only
> > 215kb.
>
> > I'm not sure why it isn't working. Any help would be greatly
> > appreciated.
>
> --
> Abraham Williams | Developer for hire |http://abrah.am
> @abraham |http://projects.abrah.am|http://blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Background Image & twitteroauth library
Hi Everyone,
I'm attempting to use the twittoauth library by Abraham Williams and
am having a little trouble. I am able to authenticate and get
everything, for the most part, working properly. The only thing I
can't do is get the background image to update.
Function I'm Using in index.php:
$connection->post('account/update_profile_background_image',
array('image' => 'images/cool-blue.jpg'));
index.php is in a root directory and there is a folder called images
with the cool-blue.jpg background in there. The file size is only
215kb.
I'm not sure why it isn't working. Any help would be greatly
appreciated.
[twitter-dev] Re: Tweeting from PHP backed will also require OAuth in the upcoming changes?
Is the point of oauth_single_token that you can only work with a single account? Meaning if I have a feature on my site, I can't use this library to interact with the users accounts, I can only use this library to work with my own, or one account? Much appreciated! On May 3, 2:35 pm, Abraham Williams <4bra...@gmail.com> wrote: > You can checkout this page describing using a script to post to a single > Twitter account:http://dev.twitter.com/pages/oauth_single_token > > One of the examples is for my PHP > library:http://github.com/abraham/twitteroauth > > Abraham > > > > On Mon, May 3, 2010 at 13:04, YCBM wrote: > > Hi Paul, > > > Posting status updates using Basic Auth like that won't work any more > > after 6/30. You'll need to use a PHP oAuth class (there are a few of > > them athttp://dev.twitter.com/pages/oauth_libraries#php) as well as > > register an oAuth app. > > > Best, > > Y > > > On May 3, 3:17 pm, "Paul A." wrote: > > > Hi guys, > > > > Quick question that "hunts" me and can't find an answer. > > > > I'm using this line of code to post tweets to my account direclty > > > from my website > > > > $host = "http://twitter.com/statuses/update.xml? > > > status=".urlencode(stripslashes(urldecode($message))) > > > and posting it with curl with my user/password > > > > Will this still going to work after Twitter upcoming June requirement > > > for Oauth. It's unclear to me. > > > > Thanks, Paul > > -- > Abraham Williams | Developer for hire |http://abrah.am > @abraham |http://projects.abrah.am|http://blog.abrah.am > This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] @anywhere Drupal and WordPress Plugins?
On Fri, Apr 16, 2010 at 1:09 AM, M. Edward (Ed) Borasky wrote: > Are there any plugins for @anywhere that will run on Drupal and > WordPress? My blog is on WordPress, and I want to get rid of as many > non-Twitter gizmos and widgets as possible. I'll be keeping AddToAny, > since it goes to Developer Zone, and I'll be keeping Twitoaster, since > it threads conversations. But I'm ditching Topsy and a couple of > others as soon as I can get @anywhere running. > I will be pouring over the @anywhere docs this weekend to see how I would use the new tech in WordPress. The Twitter Connect is at the top of my list, since I have a project right now that requires it, and @anywhere might make it easier to implement. ~e -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: What's happening with Tweetie for Mac
Ryan, Thanks for clarifying, finally, at least. Rebranded Twitter or not, Tweetie as owned and developed by Twitter basically reinforces and confirms everything that we posted on the Nambu blog this morning: Twitter will take anything significant built around Twitter for itself, 100%. Twitter is now officially developing native applications on three platforms: iPhone OS, OSX and Blackberry, all free. Simply brutal. But I am not nearly affected as the iPhone developers. They should be rightfully livid that Twitter moved to wipe them out and take all advertising revenue (iAd and other stuff) on the iPhone and iPad for themselves rather than share it, as almost all other platforms do. Pretty sad. Make no mistake, "Twitter for iPhone" will take all significant market share, and there is nothing any of the developers there that have done great work can do about it. If you do not see this, you do not understand the basics of business. Making Tweetie free is pretty brutal as well, but only because Twitter is doing it. Everyone else should be put on notice that you will be next, as we have been. Mr. Wilson and Twitter, with these moves, and have basically told everyone of competence that they must accept their development efforts as only ending up as a nice lifestyle business. Anything more, and Twitter will move to take it from you, simple as that. --ejw Eric Woodward Email: e...@nambuc.om On Apr 12, 10:39 am, Michael Macasek wrote: > Ryan, > > Great news thanks for the update! > > Jesse, > > Well said. > > On Apr 12, 10:40 am, Ryan Sarver wrote: > > > > > One more from me. People have been asking for specific details around > > Tweetie for Mac and I wanted to make sure we clearly message our plans > > as we know it. To be clear, Tweetie for the iPhone and it's developer, > > Loren Brichter, were the focus of our acquisition, but as part of the > > deal we also got Tweetie for Mac. > > > Loren had been hard at work on a new version of Tweetie for Mac that > > he was going to release soon. Our plan is to still release the new > > version and it will continue to be called Tweetie (not renamed to > > Twitter). We will also discontinue the paid version. > > > Hope that's clear. Please let me know if you have any questions. > > > Best, Ryan -- To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Re: Twitter buying Tweetie
I am also happy for Loren, he deserves it based purely on the quality of his product. I would like some clarification on the intended future of Tweetie for OS X. The plans for the iPhone and iPad have been made very very clear: stay away. Please clarify the plans for OS X. But at this point I don't really expect a response, but I need to ask. --ejw Eric Woodward Email: e...@nambu.com -- To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Re: Profile avatars with AWS S3 versioning
Browsers are not the only thing to consider. If a standard URL is used that never changes a desktop or mobile client will not know it has changed. I will have to redownload it now and again to be sure, or manually track and check these cache headers myself, which is annoying. Adding payload to the user object in the API response with the last timestamp the avatar was changed would make it dead simple to know if you have the latest one (already downloaded) or not. In my mind, this is the proper solution that should have been implemented years ago. These avatar issues have been an issue since day one, and no one at Twitter has ever seemed to mind much (or it would have been fixed long ago). They do have bigger ongoing problems, I will grant. --ejw Eric Woodward e...@nambu.com On Apr 5, 9:19 am, Abraham Williams <4bra...@gmail.com> wrote: > There is now a petition going to get screen_name based > profile_image_urls:http://act.ly/1vk > > Abraham > > > > > > On Fri, Feb 12, 2010 at 19:03, Andrew Badera wrote: > > On Fri, Feb 12, 2010 at 10:02 PM, Abraham Williams <4bra...@gmail.com> > > wrote: > > > Now that Amazon S3 supports versioning couldn't profile avatars use > > static > > > URLs and let browsers handle the caching with ETags? > > > More info on S3 Versioning:http://goo.gl/CMch > > > Abraham > > > > -- > > > Abraham Williams | Community Advocate |http://abrah.am > > > Project | Out Loud |http://outloud.labs.poseurtech.com > > > This email is: [ ] shareable [x] ask first [ ] private. > > > Sent from Seattle, WA, United States > > > +1 > > > --ab > > -- > Abraham Williams | Community Advocate |http://abrah.am > PoseurTech Labs | Projects |http://labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private. -- To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Re: RateLimit value look to be incorrect in 3G/Edge
ok, thank you very mutch for your help.
I'll add the mandatory authentication to solve this problem.
On 24 mar, 19:05, Andrew Badera wrote:
> Most GPRS/Edge/3G is proxied through a single IP at some point. It's
> not as intrusive as it once was, but it was definitely very common 3-5
> years ago, and nothing I've read or heard seems to indicate that has
> changed.
>
> ∞ Andy Badera
> ∞ +1 518-641-1280 Google Voice
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me:http://www.google.com/search?q=andrew%20badera
>
>
>
> On Wed, Mar 24, 2010 at 11:58 AM, Eric wrote:
> > Hi Raffi,
> > Thank for your answer
> > Thank to Josh Bleech too, who answered me by mail. (He think the same
> > thing of you Raffi)
>
> > I just test with the friends_timeline methode, and the RateLimit is
> > correctly decremented !
> > You are probably right, maybe my IP is shared with other users...
> > I can force users to log-in but it's annoying...
>
> > However, other Twitter clients like twitterific look to work
> > wonderfull...
>
> > On 24 mar, 16:16, Raffi Krikorian wrote:
> >> hi eric.
>
> >> are you authenticating to this call, or are these unauthenticated? i'd be
> >> curious to know if you're having this problem in an authenticated session
> >> as
> >> that rate limit is tied to your user. in an unauthenticated world, i
> >> wonder
> >> whether its because your request is coming from some form of shared IP
> >> address?
>
> >> On Wed, Mar 24, 2010 at 3:02 AM, Eric wrote:
> >> > I have made complementary tests on my iPhone with
> >> >http://api.twitter.com/1/account/rate_limit_status.jsonandi get
> >> > theses results :
>
> >> > {"reset_time_in_seconds":1269426542,"reset_time":"Wed Mar 24 10:29:02
> >> > + 2010","remaining_hits":132,"hourly_limit":150}
> >> > {"hourly_limit":150,"reset_time":"Wed Mar 24 10:37:50 +
> >> > 2010","reset_time_in_seconds":1269427070,"remaining_hits":123}
> >> > {"reset_time":"Wed Mar 24 10:16:27 + 2010","remaining_hits":
> >> > 118,"hourly_limit":150,"reset_time_in_seconds":1269425787}
> >> > {"remaining_hits":119,"reset_time":"Wed Mar 24 10:37:50 +
> >> > 2010","hourly_limit":150,"reset_time_in_seconds":1269427070}
> >> > {"reset_time":"Wed Mar 24 10:16:27 + 2010","remaining_hits":
> >> > 115,"hourly_limit":150,"reset_time_in_seconds":1269425787}
>
> >> > Nobody have always seen this problem ?
>
> >> > To unsubscribe from this group, send email to twitter-development-talk+
> >> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> >> > ME" as the subject.
>
> >> --
> >> Raffi Krikorian
> >> Twitter Platform Teamhttp://twitter.com/raffi
>
> > To unsubscribe from this group, send email to
> > twitter-development-talk+unsubscribegooglegroups.com or reply to this email
> > with the words "REMOVE ME" as the subject.
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words "REMOVE ME" as the subject.
[twitter-dev] Re: RateLimit value look to be incorrect in 3G/Edge
Hi Raffi,
Thank for your answer
Thank to Josh Bleech too, who answered me by mail. (He think the same
thing of you Raffi)
I just test with the friends_timeline methode, and the RateLimit is
correctly decremented !
You are probably right, maybe my IP is shared with other users...
I can force users to log-in but it's annoying...
However, other Twitter clients like twitterific look to work
wonderfull...
On 24 mar, 16:16, Raffi Krikorian wrote:
> hi eric.
>
> are you authenticating to this call, or are these unauthenticated? i'd be
> curious to know if you're having this problem in an authenticated session as
> that rate limit is tied to your user. in an unauthenticated world, i wonder
> whether its because your request is coming from some form of shared IP
> address?
>
>
>
>
>
> On Wed, Mar 24, 2010 at 3:02 AM, Eric wrote:
> > I have made complementary tests on my iPhone with
> >http://api.twitter.com/1/account/rate_limit_status.jsonand i get
> > theses results :
>
> > {"reset_time_in_seconds":1269426542,"reset_time":"Wed Mar 24 10:29:02
> > + 2010","remaining_hits":132,"hourly_limit":150}
> > {"hourly_limit":150,"reset_time":"Wed Mar 24 10:37:50 +
> > 2010","reset_time_in_seconds":1269427070,"remaining_hits":123}
> > {"reset_time":"Wed Mar 24 10:16:27 + 2010","remaining_hits":
> > 118,"hourly_limit":150,"reset_time_in_seconds":1269425787}
> > {"remaining_hits":119,"reset_time":"Wed Mar 24 10:37:50 +
> > 2010","hourly_limit":150,"reset_time_in_seconds":1269427070}
> > {"reset_time":"Wed Mar 24 10:16:27 + 2010","remaining_hits":
> > 115,"hourly_limit":150,"reset_time_in_seconds":1269425787}
>
> > Nobody have always seen this problem ?
>
> > To unsubscribe from this group, send email to twitter-development-talk+
> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> > ME" as the subject.
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words "REMOVE ME" as the subject.
[twitter-dev] Re: RateLimit value look to be incorrect in 3G/Edge
I have made complementary tests on my iPhone with
http://api.twitter.com/1/account/rate_limit_status.json and i get
theses results :
{"reset_time_in_seconds":1269426542,"reset_time":"Wed Mar 24 10:29:02
+ 2010","remaining_hits":132,"hourly_limit":150}
{"hourly_limit":150,"reset_time":"Wed Mar 24 10:37:50 +
2010","reset_time_in_seconds":1269427070,"remaining_hits":123}
{"reset_time":"Wed Mar 24 10:16:27 + 2010","remaining_hits":
118,"hourly_limit":150,"reset_time_in_seconds":1269425787}
{"remaining_hits":119,"reset_time":"Wed Mar 24 10:37:50 +
2010","hourly_limit":150,"reset_time_in_seconds":1269427070}
{"reset_time":"Wed Mar 24 10:16:27 + 2010","remaining_hits":
115,"hourly_limit":150,"reset_time_in_seconds":1269425787}
Nobody have always seen this problem ?
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words "REMOVE ME" as the subject.
[twitter-dev] RateLimit value look to be incorrect in 3G/Edge
Hi, (sorry for my English) I currently develop a little twitter client for my iPhone application, and i have a problem with the rate limit when i'm connected in 3G/ Edge. (no problem when connected in WIFI) This parameter look to be completly random ! For example, there are the returned values for 5 successive requests : X-Ratelimit-Remaining : 0 X-Ratelimit-Remaining : 0 X-Ratelimit-Remaining : 60 X-Ratelimit-Remaining : 105 X-Ratelimit-Remaining : 0 I use the API with the following code : NSString *adresse = [@"http://api.twitter.com/1/statuses/user_timeline/ applisiphone.json?page=1" stringByAddingPercentEscapesUsingEncoding:NSASCIIStringEncoding]; NSURLRequest* request = [NSURLRequest requestWithURL:[NSURL URLWithString:adresse] cachePolicy:NSURLRequestUseProtocolCachePolicy timeoutInterval:60]; NSURLConnection* connection = [[NSURLConnection alloc] initWithRequest:request delegate:self]; I really don't understand the problem ... Someone can help me ? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] Re: Find Location where tweet came from
Raffi -- you are absolutely correct. It turns out it's a frequency
thing. I've done a whole bunch of random looks at result data in the
last couple of months and I've never seen one. Now that I know what
to look for, I just grabbed a batch of 50,000 search results and found
several.
Many apologies for any work you had to do to drop some knowledge on
me :)
Eric
On Feb 12, 9:22 am, Raffi Krikorian wrote:
> hi eric.
>
> just to make sure i understand what you're saying - you're saying that the
> geo tag (from the geotagging API) is not showing up from search? i beg to
> disagree
>
> deskdog:Desktop raffi$ *curlhttp://search.twitter.com/search.json?q=tomcoates*
> {
> "results":
> [
> ...
> {
>
> "profile_image_url":"http://a1.twimg.com/profile_images/523070730/twitterProfilePhoto_norm...
> ",
> "created_at":"Fri,
> 12 Feb 2010 05:05:51 +",
> "from_user":"vicchi",
> "to_user_id":1292126,
> "text":"@tomcoates You did really well today. Rest. Relax. Blog.
> Sleep. See you tomorrow.",
> "id":8995500197,
> "from_user_id":59842,
> "to_user":"tomcoates",
> *"geo":*
> * {*
> * "type":"Point",*
> * "coordinates":*
> * [*
> * 37.2655,*
> * -121.9648*
> * ]*
> * },*
> "iso_language_code":"en",
> "source":"<a href="http://www.tweetdeck.com/";
> rel="nofollow">TweetDeck</a>"
> },
> ...
> "max_id":9014080861,
> "since_id":0,
> "refresh_url":"?since_id=9014080861&q=tomcoates",
> "next_page":"?page=2&max_id=9014080861&q=tomcoates",
> "results_per_page":15,
> "page":1,
> "completed_in":0.053853,
> "query":"tomcoates"
>
> }
>
> seems to be working for me?
>
> On Fri, Feb 12, 2010 at 6:59 AM, Eric Marcoullier @ Gnip <
>
>
>
> e...@marcoullier.com> wrote:
> > I apologize if this has been previously covered, but it appears that
> > explicit geotag info is not shown for any tweet returned via the
> > search API, regardless of whether a user has authorized public geo
> > reporting.
>
> > As a result, it is possible to determine what is being said in a
> > specific location, but it is not possible to determine where people
> > are talking about a specific subject.
>
> > I understand you not wanting to show all the signals that lead to a
> > geo search match, but I can't grok why you're witholding specific
> > metadata from the search results.
>
> > Any light you can shed would be valuable to my customers. Any plans to
> > change this policy would be rad.
>
> > Thanks!
> > Eric
>
> > (on my iPhone. Sorry for typeos)
>
> > On Feb 11, 8:20 pm, Raffi Krikorian wrote:
> > > each user has a location field associated with it - but that is self
> > > reported.
>
> > > On Thu, Feb 11, 2010 at 2:17 PM, don wrote:
> > > > Thanks for the reply. Thats what I was thinking.
>
> > > > Would there be any way to return the location data of user with the
> > > > search results for a word?
>
> > > > So that I didn't need to make seperate calls for each user?
>
> > > > thanks so much for your help.
>
> > > > On Feb 12, 3:20 am, Raffi Krikorian wrote:
> > > > > twitter only returns data back in its "geo" field if the tweet has
> > been
> > > > > explicitly geotagged.
>
> > > > > search, however, attempts to use other signals to determine where the
> > > > tweet
> > > > > is, and will attempt to return "more" tweets when you use its
> > "search"
> > > > > parameter. it does not, however, expose those signals in the search
> > > > > results.
>
> > > > > On Wed, Feb 10, 2010 at 1:39 PM, don wrote:
> > > > > > Hi All,
>
> > > > > > I'm trying to determine the location where a tweet came from.
>
> > > > > > I know you can do a search specifying the location you want to look
> > at
> &
[twitter-dev] Re: Find Location where tweet came from
I apologize if this has been previously covered, but it appears that explicit geotag info is not shown for any tweet returned via the search API, regardless of whether a user has authorized public geo reporting. As a result, it is possible to determine what is being said in a specific location, but it is not possible to determine where people are talking about a specific subject. I understand you not wanting to show all the signals that lead to a geo search match, but I can't grok why you're witholding specific metadata from the search results. Any light you can shed would be valuable to my customers. Any plans to change this policy would be rad. Thanks! Eric (on my iPhone. Sorry for typeos) On Feb 11, 8:20 pm, Raffi Krikorian wrote: > each user has a location field associated with it - but that is self > reported. > > > > > > On Thu, Feb 11, 2010 at 2:17 PM, don wrote: > > Thanks for the reply. Thats what I was thinking. > > > Would there be any way to return the location data of user with the > > search results for a word? > > > So that I didn't need to make seperate calls for each user? > > > thanks so much for your help. > > > On Feb 12, 3:20 am, Raffi Krikorian wrote: > > > twitter only returns data back in its "geo" field if the tweet has been > > > explicitly geotagged. > > > > search, however, attempts to use other signals to determine where the > > tweet > > > is, and will attempt to return "more" tweets when you use its "search" > > > parameter. it does not, however, expose those signals in the search > > > results. > > > > On Wed, Feb 10, 2010 at 1:39 PM, don wrote: > > > > Hi All, > > > > > I'm trying to determine the location where a tweet came from. > > > > > I know you can do a search specifying the location you want to look at > > > > and this checks againist any geo data and then against the location > > > > data. I'm guessing that twitter does a lot of error checking and > > > > transforms the location data into a geo coord on the backend when you > > > > do this search. > > > > > My question is: if I do a search for say a "word" and get my results > > > > back I want to be able to check where each of the returned tweets came > > > > from. Not just using the geo data that the user may have allowed but > > > > also the location data (just like the search for location based tweets > > > > does). > > > > > Essentially getting back a geo coord for each tweet if there is any > > > > releveant geo data or location data given by the tweeter. > > > > > this site would be doing something similar:http://trendsmap.com/ > > > > > any ideas? sorry if this is really obvious, I have searched and just > > > > can't find it. > > > > > thanks > > > > don > > > > -- > > > Raffi Krikorian > > > Twitter Platform Teamhttp://twitter.com/raffi > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Getting First Status After since_id
Hello, I'd like to be able to request just the first status in a timeline after an arbitrary ID. Using since_id=###&count=1 gives the latest status, which seems like the proper result. since_id=###&page=##&count=1, where the page number is higher than the number of statuses, returns no tweets. Is there any parameter or combination of parameters that will give me just the next one?
[twitter-dev] API Limit of 150 is Obsolete
I will come straight to the point: we need to an increase to the API limit to properly implement Twitter within a desktop client application given the addition of: 1) three retweets timelines; 2) checking the account's saved searches; and 3) up to 10-20 Twitter Lists timelines. Twitter Lists alone are causing real problems if a user follows more than 5 or so. We cant poll Twitter List subscriptions with one API call that combines them altogether, which we could then split apart client-side with some attached meta-data. That alone would have been a big help, and without it we are left polling each List as if it was a separate timeline, since that is what they are. Implementing proper Lists management is a non-starter within this limit, so is regular confirmation of a relationship between two users when asked for by the user (on Lists or search results). There is simply a lot of stuff I cannot do properly that is standard on twitter.com, all because I am subject to the API limit while twitter.com is not. Users simply do not understand this distinction in possibilities. I would like to formally ask on behalf of all client developers that the API limit increase to 250, from 150, for all applications whether they use OAuth or HTTP Basic Authentication. We are simply not able to implement Twitter properly within a limit of 150, but dont need a lot more, only another 100-200 API calls or so. If Twitter can even technically contemplate a 10x API limit increase to 1,500 for OAuth applications, surely an increase to 250 based on the addition of core features like official retweets and Lists is a reasonable request. A limit of 150 is simply obsolete, and has been for a long time. I do not want to wait for the UX repairs around OAuth for desktop applications, and I dont like being forced into OAuth sooner than we are ready just because we need the extra API hits just to do basic features properly. And besides, that was announced as two weeks away three weeks ago. I dont want to wait any longer. I want to properly implement the basics, like Lists polling, now. This is a considered email because I care about the quality of our Twitter implementation and I care about the Twitter ecosystem. I would appreciate a considered reply. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Re: Ambiguity with 401 error response code
Heya, this will definitely work for now. Thanks for the good idea. Eric On Dec 29, 10:45 am, Raffi Krikorian wrote: > hi eric. > > yup - you've hit it right on the head. one of the main initiatives in us > starting to version our API is so that we can really consolidate and make > our error codes consistent. unfortunately, for legacy compatibility > reasons, we can't change the second case to have a 402 error and we will > have to keep it as a 401. > > what you could do is parse the response that comes back in the 401, however. > in the case that your password is wrong, the error should be > > "Could not authenticate you." > > for basic auth and OAuth. the second case has an error of > > "Not authorized" > > On Mon, Dec 28, 2009 at 3:38 PM, Eric Marcoullier @ Gnip < > > > > e...@marcoullier.com> wrote: > > We're trying to build some logic into our data collector and we've > > been fighting with an issue for a while involving the 401 > > "Unauthorized" error code. > > > There are two instances where I can get this response > > > 1) Bad credentials. I try to log in with an invalid username or > > password. > > 2) I don't have access to a specific user's private account. > > > The former can be a real problem for a user. I changed my password a > > few weeks ago and forgot that I was using it for whitelisted REST API > > access. Querying three times in rapid succession with a bad password > > causes a temporary lockdown of a user's account. I was querying once > > per second and locked the account for a five days. This is an account- > > level issue and the proper way to deal with this from our perspective > > is to immediately sleep the poller for 30 minutes and send an alert > > about bad credentials. > > > This is completely different than if someone I'm following has taken > > their account private. In this case, sleeping for 30 minutes (or any > > amount of time, really) is overkill. Unless I'm querying for a single > > person over and over, there's no reason to pause before moving onto > > the next rule that I'm querying for. > > > Unfortunately, we have no way to disambiguate between the two 401s and > > we're forced to either lock someone's account (ignoring 401s) or > > severely reduce their polling efficiency (acting on 401s). > > > Best case would be to break these two error conditions out into > > separate error codes. Perhaps a 401 for bad credentials and a 402 for > > lack of authorization for a specific piece of content. > > > Please let know if I've overlooked something that would help me > > disambiguate the use cases in the current system. > > > Thanks! > > Eric > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Ambiguity with 401 error response code
We're trying to build some logic into our data collector and we've been fighting with an issue for a while involving the 401 "Unauthorized" error code. There are two instances where I can get this response 1) Bad credentials. I try to log in with an invalid username or password. 2) I don't have access to a specific user's private account. The former can be a real problem for a user. I changed my password a few weeks ago and forgot that I was using it for whitelisted REST API access. Querying three times in rapid succession with a bad password causes a temporary lockdown of a user's account. I was querying once per second and locked the account for a five days. This is an account- level issue and the proper way to deal with this from our perspective is to immediately sleep the poller for 30 minutes and send an alert about bad credentials. This is completely different than if someone I'm following has taken their account private. In this case, sleeping for 30 minutes (or any amount of time, really) is overkill. Unless I'm querying for a single person over and over, there's no reason to pause before moving onto the next rule that I'm querying for. Unfortunately, we have no way to disambiguate between the two 401s and we're forced to either lock someone's account (ignoring 401s) or severely reduce their polling efficiency (acting on 401s). Best case would be to break these two error conditions out into separate error codes. Perhaps a 401 for bad credentials and a 402 for lack of authorization for a specific piece of content. Please let know if I've overlooked something that would help me disambiguate the use cases in the current system. Thanks! Eric
[twitter-dev] Please help. Cannot get verify_credentials.xml to work with seemingly correct request
Folks,
For some reason I ** cannot ** seem to make a request for /account/
verify_credentials.xml via an ASP-based request. I'm using
Server.CreateObject("Microsoft.XMLHTTP") and generating the following
URL:
http://twitter.com/account/verify_credentials.xml?oauth_consumer_key=GWLrrqixPNWscdvwpHGrSw&oauth_token=83692200-mJvKXGoqdZVZOj3lrYhBe2pKAMIEdgPBUp5VRE7G8&oauth_nonce=rtuddtjukxjp&oauth_timestamp=1261806964&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_signature=dIuA1bcXvF2rJ4LyJ2eE7%2B0qmIM%3D
Based on everything I've read this looks correct but gets back a 401/
unauthorized every time.
Can anyone see what is going wrong?
Thanks.
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Any resolution or news? On Nov 10, 11:07 pm, Eric Gilbert wrote: > Great. Thanks, Marcel. Looking forward to the answer. My guess: limit > on concurrent follows as countermeasure against bots? > > On Nov 10, 12:41 pm, Marcel Molina wrote: > > > Indeed something looks strange there. I've brought this to the > > attention of the team working on the lists backend. I'll let you know > > what they discover. > > > On Mon, Nov 9, 2009 at 10:20 PM, Eric Gilbert wrote: > > > > I'm developing an app that builds a few lists. Since it seems the only > > > way to add users to lists is one id per call (please let me know if > > > I'm mistaken), I experimented with populating the lists > > > asynchronously. Both seem to build the list fine, and of course async > > > is much faster. Here's the strange thing: although the lists created > > > with each method have the same membership list, the lists streams are > > > not the same. (Sync seems to be doing the right thing, but I haven't > > > verified this rigorously.) For example, see > > > >http://twitter.com/eegilbert/right vs > > >http://twitter.com/eegilbert/notsoright > > > > Strange. > > > > Cheers, > > > Eric > > > -- > > Marcel Molina > > Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Blocked Users on Lists
How is it possible no one from Twitter would respond to this? --ejw Eric Woodward Email: e...@nambu.com On Nov 16, 10:03 am, Eric Woodward wrote: > So, unless it has changed or I messed up test queries, users that I > have blocked still appear in Lists timelines when I request these > Lists from my authenticated account. Can someone else confirm or deny > this for me? > > Twitter, please confirm whether this is the desired behaviour going > forward, or a bug, or a development item yet to be completed. If need > be I will have to implement this client-side with a list of blocked > IDs, but no sense doing that if the API will do it at some point, > obviously. > > As Lists exist now it is impossible to follow a List that contains > someone you simply dont want to hear from. If this is a noisy > prominent well-known person it detracts from almost all Lists in > defined vertical segments. > > --ejw > > Eric Woodward > Email: e...@nambu.com
[twitter-dev] Blocked Users on Lists
So, unless it has changed or I messed up test queries, users that I have blocked still appear in Lists timelines when I request these Lists from my authenticated account. Can someone else confirm or deny this for me? Twitter, please confirm whether this is the desired behaviour going forward, or a bug, or a development item yet to be completed. If need be I will have to implement this client-side with a list of blocked IDs, but no sense doing that if the API will do it at some point, obviously. As Lists exist now it is impossible to follow a List that contains someone you simply dont want to hear from. If this is a noisy prominent well-known person it detracts from almost all Lists in defined vertical segments. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Great. Thanks, Marcel. Looking forward to the answer. My guess: limit on concurrent follows as countermeasure against bots? On Nov 10, 12:41 pm, Marcel Molina wrote: > Indeed something looks strange there. I've brought this to the > attention of the team working on the lists backend. I'll let you know > what they discover. > > > > On Mon, Nov 9, 2009 at 10:20 PM, Eric Gilbert wrote: > > > I'm developing an app that builds a few lists. Since it seems the only > > way to add users to lists is one id per call (please let me know if > > I'm mistaken), I experimented with populating the lists > > asynchronously. Both seem to build the list fine, and of course async > > is much faster. Here's the strange thing: although the lists created > > with each method have the same membership list, the lists streams are > > not the same. (Sync seems to be doing the right thing, but I haven't > > verified this rigorously.) For example, see > > >http://twitter.com/eegilbert/right vs > >http://twitter.com/eegilbert/notsoright > > > Strange. > > > Cheers, > > Eric > > -- > Marcel Molina > Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Yes. On Nov 10, 12:30 am, Tim Haines wrote: > Does creating the same list twice via sync'ed methods result in > duplicate streams? > > Sent from my iPhone > > On 10/11/2009, at 7:20 PM, Eric Gilbert wrote: > > > > > I'm developing an app that builds a few lists. Since it seems the only > > way to add users to lists is one id per call (please let me know if > > I'm mistaken), I experimented with populating the lists > > asynchronously. Both seem to build the list fine, and of course async > > is much faster. Here's the strange thing: although the lists created > > with each method have the same membership list, the lists streams are > > not the same. (Sync seems to be doing the right thing, but I haven't > > verified this rigorously.) For example, see > > >http://twitter.com/eegilbert/right vs > >http://twitter.com/eegilbert/notsoright > > > Strange. > > > Cheers, > > Eric
[twitter-dev] Blocking vs non-blocking list creation: list streams are different
I'm developing an app that builds a few lists. Since it seems the only way to add users to lists is one id per call (please let me know if I'm mistaken), I experimented with populating the lists asynchronously. Both seem to build the list fine, and of course async is much faster. Here's the strange thing: although the lists created with each method have the same membership list, the lists streams are not the same. (Sync seems to be doing the right thing, but I haven't verified this rigorously.) For example, see http://twitter.com/eegilbert/right vs http://twitter.com/eegilbert/notsoright Strange. Cheers, Eric
[twitter-dev] Re: Lists API for Subscriptions
Thanks for that. It would be great to combine them and reflect ownership in the response data set. This requires two API calls for what will be requested each time to show both sets together, which you on twitter.com. I assume others will tend to show both sets at the same time as well. --ejw Eric Woodward Email: e...@nambu.com On Oct 31, 3:01 pm, twittelator wrote: > Whoops - what I meant to say was: > > :user//lists/subscriptions.:format > > will get the lists a user has subscribed to > > Andrew Stone > Twitter / @twittelatorhttp://www.stone.com > got iPhone? > http://tinyurl.com/twitpro > http://tinyurl.com/intentionizer > http://tinyurl.com/gesture-buy > http://tinyurl.com/igraffiti > http://tinyurl.com/talkingpics > http://tinyurl.com/mobilemix > http://tinyurl.com/soundbite > http://tinyurl.com/icreated > http://tinyurl.com/pulsar-app > > On Oct 30, 5:52 pm, Eric Woodward wrote: > > > > > Anyone seeing an issue with a method to get a list of a user's list > > subscriptions? The following: > > > curl -u ejwc:[password] "http://twitter.com/ejwc/lists.xml"; > > > only returns the three test lists that I have created, while the same > > URL on Twitter's website: > > >https://twitter.com/ejwc/lists > > > returns my three test lists, and the 5+ lists I am following. > > > Any suggestions? I have only just started getting a response for the > > API methods in the last day or so and only getting familiar with them. > > Any help would be appreciated. > > > --ejw > > > Eric Woodward > > Email: e...@nambu.com
[twitter-dev] Lists API for Subscriptions
Anyone seeing an issue with a method to get a list of a user's list subscriptions? The following: curl -u ejwc:[password] "http://twitter.com/ejwc/lists.xml"; only returns the three test lists that I have created, while the same URL on Twitter's website: https://twitter.com/ejwc/lists returns my three test lists, and the 5+ lists I am following. Any suggestions? I have only just started getting a response for the API methods in the last day or so and only getting familiar with them. Any help would be appreciated. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Re: Twitter Lists: /user/list/members.xml returning only 20 at a time
Rich, I think you answered your own question there, the first one anyway. I would not expect a real answer to the second one. --ejw Eric Woodward Email: e...@nambu.com On Oct 26, 2:30 am, Rich wrote: > Seriously have we got a two tier dev system now, can we all have > access to the API please? > > On Oct 24, 10:18 pm, Dave Briccetti wrote: > > > > > How can I retrieve more than 20 at a time? > > > ?cursor=-1&count=200 has no effect
[twitter-dev] Re: Lists API
Hmm. Ok, thats is obviously fair enough, in theory. You obviously need to test and debug something with a subset of traffic. But Lists are operational now on twitter.com which serves millions, so it seems you are well down that road, yet no API, no draft API methods to review like we have for retweets, nothing. Services contact me to integrate services they developed on top of Lists meaning they have had access to the API for weeks, or more. Basically, you are rolling out critical platform improvements that many of us don't have access to. I am not sure what the point of being a Twitter developer is if you dont give us all fair access to key elements of the service. You have also created a small nightmare for those us that implemented a version of Lists/Groups that is now starting to confuse users. Basically, from what has been going on from the bit.ly transition to suggested users lists to preferential access to stream APIs to free advertising/endorsements for some to now giving access to the Lists API to selected people, I could write a book on how to not manage an ecosystem using Twitter as the prime example. Please please at least give us a draft API to review for Lists as you have done for Rewteets so we can at least *plan* a transition from our own Groups implementations, or how we will coordinate the two features based on the API methods. You have people building services on opt of the Lists API and pitching me to include it in Nambu, so it is obviously a lot further along you are letting on here. --ejw Eric Woodward Email: e...@nambu.com On Oct 15, 4:19 pm, Marcel Molina wrote: > We are rolling it out to a small set of users incrementally so that we > can load test and find bugs. We've been working on the API > documentation and will be rolling it out gradually. > > On Thu, Oct 15, 2009 at 4:10 PM, Eric Woodward wrote: > > > So, what is the plan for releasing the Lists API, if there is one? It > > is well known that selected people have access to them while the rest > > of us do not, which is creating a problem with users. Is there a plan > > to release these APIs to everyone soon? > > > Please respond. I am only asking. > > > --ejw > > > Eric Woodward > > Email: e...@nambu.com > > -- > Marcel Molina > Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Lists API
So, what is the plan for releasing the Lists API, if there is one? It is well known that selected people have access to them while the rest of us do not, which is creating a problem with users. Is there a plan to release these APIs to everyone soon? Please respond. I am only asking. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Preview Access to Lists API?
So, I am hearing from a few people that they have advanced preview access to the Lists API, the feature that was announced recently. It is a cool thing to see a steady stream of feature additions in the pipeline. I look forward to adding Lists to Nambu. First, please confirm that this is true, that some people have access to these APIs while the rest of us don't even know what the feature set actually is, and what we will be possible via the API. Second, if true, can Twitter please at least publish these APIs as beta specifications as you have done with the retweet APIs, so the rest of us second-tier developers can at least see what they will *exactly* be? With that we can at least prepare implementations. I all really want to know is what lists will *exactly* be as offered by the Twitter API. At the moment many of us that are not blessed services dont even know what they are, let alone have a chance to already build features on top of them, while those are that are blessed are already working on them. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Find twitter account from email address?
If I have an email address, can I query somehow to find a person's twitter page?
[twitter-dev] JQuery Full API Plugin - Help Needed Testing
Hey guys, I've been working on a full implementation of the twitter API through, primarily, jQuery, with a simple relay script server side for securely signing and keeping auth details. I've just finished the library, and am looking for some developers who know both the twitter API and jQuery to help test out this new plugin. If you would like to help with this project (currently named Jitter: Jquery Twitter), please send an email to gars...@gmail.com Thanks! [Cross Posted on the Twitter Dev and jQuery Lists]
[twitter-dev] Re: oauth/authenticate is redirecting me to oauth/authorize and giving a PIN
If you're using the twitter rubygem, the problem is detailed here http://groups.google.com/group/ruby-twitter-gem/browse_thread/thread/6e935089d55a92c2. Basically the twitter gem isn't using the newest oauth gem properly, and using an older version of the oauth gem seems to fix everything. Hopefully John, the author of the twitter gem, can confirm and get a new version out soon.
[twitter-dev] Re: oauth/authenticate is redirecting me to oauth/authorize and giving a PIN
I'm having the same problem--getting a PIN instead of being redirected at the end of the oauth flow. My application is set as a browser-type app, and I'm providing a callback url. Everything was working as expected for the past couple of weeks, the problem started when the API became available again after the ddos. On Aug 12, 10:56 am, Tony Amoyal wrote: > I am implementing some ruby on rails code tweet stuff for my users. I > am creating the proper oauth link...something like > > http://twitter.com/oauth/authenticate?oauth_token=y2RkuftYAEkbEuIF7zK... > > but Twitter redirects the user to oauth/authorize after he clicks > "Allow" which then gives him the 7 digit PIN! > > "You've successfully granted access to . Simply return to and enter > the following PIN to complete the process. 1234567" > > According to this articlehttp://apiwiki.twitter.com/Sign-in-with-Twitter > > Twitter should be redirecting the user to the callback URL I provided > in the application settings when I hit the /oauth/authenticate path > because that is saying that I am now a Desktop or iPhone app. Does > anyone know why this is happening?
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Any idea when the limit will be increased to 20,000? I'm sure myself as well as other sites are suffering a bit because of the limitation of API calls. On Aug 7, 4:54 pm, Chad Etzel wrote: > Hi Paul (and everyone), > > Thanks for your appreciation and your comments. > > On a personal note: I started my support role this week, which is > supposed to be part-time. Well, as you can imagine that went out the > window. I have all but abandoned my other work-related > responsibilities for the past two days in order to help with the API > communications with Twitter. > > As you noted, when your site goes down you get a lot of email. > Likewise, there is an amazing flood of emails coming into Twitter (not > counting this dev-list) all asking similar questions and demanding > answers. This has created a DDoS on the API Support team's time, in a > manner of speaking :) > > I think Ryan did a good job communicating what we do and don't know in > his email this morning, and we have tried to communicate things when > we can. > > During the course of this DDoS, the attackers have changed tactics and > so our Ops team have had to change their tactics in defense of the > attack. This is happening so often that we don't want to communicate > something out to the community that will be nullified by the next > move. Our opinion is, that would create more thrashing and frustration > from the community. We have been trying to communicate workarounds and > information that has become permanent or stable as a way to deal with > the attacks. > > As Peter noted, we have nothing new to share at the moment, except to > say that this thing is still ongoing, and we're having to ride it out > with you guys. We certainly know that the 3rd party apps make Twitter > great (I've had to tweak code on my personal apps as well), and we > don't want to alienate you. Unfortunately we don't have an ETA on > resolving all of the problems because we don't have an ETA on the DDoS > :) > > We will continue to post updates as we can. Again, we know this sucks > for you guys, and we really do appreciate everyone being patient with > us. > > Thanks, > -Chad > > On Fri, Aug 7, 2009 at 7:16 PM, Paul Kinlan wrote: > > > Hi Chad, > > > I think we all appreciate the pressure you are under and the flak that you > > are taking for events outside your control, and we all wish we could help > > more. > > > But for an open communications company that is postioning itself as the > > future platform for messaging - there has been so little communication and > > feedback to the developers in your community that it is simply shocking. > > > Little things such as statements that we as developers can use to pass to > > our users with regards to issues currently affecting the service would help > > immensly. I have spent my Friday night responding to over 150 emails asking > > why twollo is down - all I can say is I think it is related to current > > events and Twitter aren't telling us anything. This doesn't inspire > > confidence in users of my service and of twitters' > > > The situation is reminisent to the oauth situation the other month. Next to > > no communication at all. > > > We all love your service and want to build on top of it and help it grow and > > our own services too. > > > From my own, probably selfish point of view the app engine is completly > > blocked at the moment and as far as I can tell we have no indication if it > > is up yet - I can't tell correctly as I am in bed writing this. > > > Paul > > > On 7 Aug 2009, at 21:09, Chad Etzel wrote: > > >> Hello all, > > >> We have been flooded with emails asking why whitelisted IPs have been > >> reduced from the 20k rate-limit down to the normal 150 rate-limit. > >> This is a known issue and we are working as hard as we can on > >> resolving it. We thank you for your patience as we are dealing with > >> everything going on with the DDoS. > > >> Thanks, > >> -Chad
[twitter-dev] oAuth Token & JSON
Hey all, I'm working on a Javascript library for full API access with Twitter, and a current hickup in the system is fetching the oAuth token from Javascript. I'm new to the twitter API, so I'm not sure if I'm missing something, but I can't seem to get my API call to: http://twitter.com/oauth/request_token to return JSON to me. Is this something doable? (Ideally through a jsonp implementation)
[twitter-dev] iPhone Help
Is there another way to view friend's timeline without " https://username:passw...@twitter.com/statuses/friends_timeline.xml";? For some reason, the iPod Touch/iPhone won't recognize the URL when I try it out. I can still retrieve the Public timeline though because there isn't the " username:passw...@twitter.com " thing. Thanks!
[twitter-dev] Re: How to count to 140: or, characters vs. bytes vs. entities, third strike
I'd be interested to see a document that details the standards for this as well. On May 15, 12:01 pm, leoboiko wrote: > > On May 15, 2:03 pm, leoboiko wrote: > > while one with 71 UTF-8 > > bytes might not (if they’re all non-GSM, say, ‘ç’ repeated 71 times). > > Sorry, that was a bad example: 71 ‘ç’s take up 142 bytes in UTF-8, not > 71. > > Consider instead 71 ‘^’ (or ‘\’, ‘[’ &c.). These take one byte in > UTF-8, but their shortest encoding in SMS is two-byte (in GSM). So > the 71-byte UTF-8 string would take more than 140 bytes as SMS and not > fit an SMS. > > Why that matters? Consider a twitter update like this: > > @d00d: in the console, type "cat ~/file.sql | tr [:upper:] > [:lower:] | less". then you cand read the sql commands without the > annoying caps > > That looks like a perfectly reasonable 140-character UTF-8 string, so > Twitter won't truncate it or warn about sending a short version. But > its SMS encoding would take some 147 bytes, so the last words would be > truncated. > > -- > Leonardo Boikohttp://namakajiri.net
[twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PM PST and Monday, May 11th Noon-1PM PST
Another maintenance-related question - are things completely back up and running? I'm asking because I'm seeing inconsistent behavior. In my servers logs, I'm seeing a number of timeouts when talking to Twitter. Also, when I try to run curl commands from my servers to Twitter, they are _extremely_ slow, sometimes timing out. Some of my servers are systems that regularly communicate with Twitter while others rarely do so. However, when I run the same curl command from my desktop, it runs in a snap. I don't recall seeing anything like this in the past, where there would be such a consistent difference between the two environments. --Eric On May 8, 2009, at 6:41 PM, Doug Williams wrote: Eric, I was right next to Alex when he made the fix for Issue 300 and I remember seeing it deployed. I'll check into it. Thanks, Doug Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Fri, May 8, 2009 at 3:38 PM, Eric Blair wrote: Yeah, I filed 300 a while ago and it was marked as fixed, so I was surprised when I saw HTML. --Eric On May 8, 2009, at 6:08 PM, Doug Williams wrote: The issues tell the story: http://code.google.com/p/twitter-api/issues/list?can=1&q=maintenance&colspec=ID+Stars+Type+Status+Priority+Owner+Summary+Opened+Modified+Component&cells=tiles Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 2:46 PM, Eric Blair wrote: Any reason the API is serving up an HTML page instead of the normal error XML? --Eric On May 8, 2009, at 1:50 PM, Michael Bailey wrote: Thanks for the clarification Doug. Stock up on some RedBull and best of luck for a smooth upgrade to the team! Michael Bailey Doug Williams wrote: @Michael: Yes. The OAuth server makes use of the twitter.com web servers as well as the database backing store which is the focus of the maintenance. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 10:00 AM, Michael Bailey wrote: Which includes OAuth verification functionalities, yes? Michael Bailey Thought Leader and Serial Entrepreneur "Cultivating the landscape of the online multimedia community" Blog: http://www.mobasoft.com New Service: http://mobatalk.com Doug Williams wrote: Hi all. To clarify: the site will be down. twitter.com and search.twitter.com will fail to serve content while the back end changes are being made. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 7:31 AM, Nick Arnett wrote: On Thu, May 7, 2009 at 10:33 PM, Abraham Williams <4bra...@gmail.com> wrote: That is usually what "site maintenance" means... In my experience, a maintenance window means that the site could be down for any or all of that period. The way Doug wrote it, I'd imagine that they expect the site will only be down for a short time, but they're reserving an hour in case it takes longer for unanticipated reasons. We shall see... Nick
[twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PM PST and Monday, May 11th Noon-1PM PST
Yeah, I filed 300 a while ago and it was marked as fixed, so I was surprised when I saw HTML. --Eric On May 8, 2009, at 6:08 PM, Doug Williams wrote: The issues tell the story: http://code.google.com/p/twitter-api/issues/list?can=1&q=maintenance&colspec=ID+Stars+Type+Status+Priority+Owner+Summary+Opened+Modified+Component&cells=tiles Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 2:46 PM, Eric Blair wrote: Any reason the API is serving up an HTML page instead of the normal error XML? --Eric On May 8, 2009, at 1:50 PM, Michael Bailey wrote: Thanks for the clarification Doug. Stock up on some RedBull and best of luck for a smooth upgrade to the team! Michael Bailey Doug Williams wrote: @Michael: Yes. The OAuth server makes use of the twitter.com web servers as well as the database backing store which is the focus of the maintenance. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 10:00 AM, Michael Bailey wrote: Which includes OAuth verification functionalities, yes? Michael Bailey Thought Leader and Serial Entrepreneur "Cultivating the landscape of the online multimedia community" Blog: http://www.mobasoft.com New Service: http://mobatalk.com Doug Williams wrote: Hi all. To clarify: the site will be down. twitter.com and search.twitter.com will fail to serve content while the back end changes are being made. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 7:31 AM, Nick Arnett wrote: On Thu, May 7, 2009 at 10:33 PM, Abraham Williams <4bra...@gmail.com> wrote: That is usually what "site maintenance" means... In my experience, a maintenance window means that the site could be down for any or all of that period. The way Doug wrote it, I'd imagine that they expect the site will only be down for a short time, but they're reserving an hour in case it takes longer for unanticipated reasons. We shall see... Nick
[twitter-dev] Re: Planned site maintenance Friday, May 8th 2PM-3PM PST and Monday, May 11th Noon-1PM PST
Any reason the API is serving up an HTML page instead of the normal error XML? --Eric On May 8, 2009, at 1:50 PM, Michael Bailey wrote: Thanks for the clarification Doug. Stock up on some RedBull and best of luck for a smooth upgrade to the team! Michael Bailey Doug Williams wrote: @Michael: Yes. The OAuth server makes use of the twitter.com web servers as well as the database backing store which is the focus of the maintenance. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 10:00 AM, Michael Bailey wrote: Which includes OAuth verification functionalities, yes? Michael Bailey Thought Leader and Serial Entrepreneur "Cultivating the landscape of the online multimedia community" Blog: http://www.mobasoft.com New Service: http://mobatalk.com Doug Williams wrote: Hi all. To clarify: the site will be down. twitter.com and search.twitter.com will fail to serve content while the back end changes are being made. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 8, 2009 at 7:31 AM, Nick Arnett wrote: On Thu, May 7, 2009 at 10:33 PM, Abraham Williams <4bra...@gmail.com> wrote: That is usually what "site maintenance" means... In my experience, a maintenance window means that the site could be down for any or all of that period. The way Doug wrote it, I'd imagine that they expect the site will only be down for a short time, but they're reserving an hour in case it takes longer for unanticipated reasons. We shall see... Nick
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
Doug, I think using the same "URL" would work, but it might be nice to have an extra (or different) param added in order to determine the reason. For example, if a user revokes access from the web and Twitter notifies the "URL", the app may just be updating values in a DB, not displaying anything. Whereas if the user clicks Deny and is sent to the "URL", not only will DB updates be made, but a message provided to the user. Just a thought ;) On May 5, 10:36 am, Doug Williams wrote: > I'm trying to decide if this could easily be part of [1]? Any objections for > these to be one in the same? > > 1.http://code.google.com/p/twitter-api/issues/detail?id=545 > > Thanks, > Doug > -- > > Doug Williams > Twitter Platform Supporthttp://twitter.com/dougw > > On Tue, May 5, 2009 at 8:27 AM, jmathai wrote: > > > When the user clicks decline the flow is abruptly disrupted. I didn't > > see anything in the OAuth spec that specifies how a "decline" is > > handled. > > > It would be nice if there was a "decline" url that the application > > could specify which the user is redirected to. > >
[twitter-dev] Re: Default Device Notification
Damn. That was it. Thanks for the pointer. --Eric On Apr 22, 2009, at 7:58 PM, Matt Sanford wrote: Hi Eric, If you do a friendships/create?follow=true is will turn on notifications when the follower is added. Poorly named parameter, I know. — Matt On Apr 22, 2009, at 04:31 PM, Eric Blair wrote: Is there any condition that would result in device notification being active immediately after following somebody via friendship/ create? I have a user who's telling me they're getting SMS updates from new friends and following them in my app, but I don't see anything in my logs indicating the I called /notifications/follow. I've looked through the API docs and the settings on Twitter and nothing's jumped out at me. Thanks, --Eric
[twitter-dev] Default Device Notification
Is there any condition that would result in device notification being active immediately after following somebody via friendship/create? I have a user who's telling me they're getting SMS updates from new friends and following them in my app, but I don't see anything in my logs indicating the I called /notifications/follow. I've looked through the API docs and the settings on Twitter and nothing's jumped out at me. Thanks, --Eric
[twitter-dev] Re: public_timeline, invalid profile_image?
Alex - seems to still be an issue. Any updates on when we might see a fix? On Mar 30, 12:49 pm, Alex Payne wrote: > We're on this. Thanks for the reports. > > > > On Sun, Mar 29, 2009 at 18:27, Gary Zhao wrote: > > I'm seeing it too. > > > 2009/3/29 Günter Grodotzki > > >> since some days I am always getting: > > >>http://static.twitter.com/images/default_profile_normal.png > > >> as profile-image from the user via public-timeline (Data-mining-feed). > > >> I checked the announcement-google-group + twitter.com/twitterapi > >> (subscribed to feed anyway ;) ) but could not see any change. > > >> The site affected:www.geoheartbeat.com > > > -- > > Gary > >http://twitter.com/garyzhao > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Duplicate Tweets
Yeah, I'm hearing this from my users again as well. Looks to happen with timeouts and retries, same as my first email. http://twitter.com/josephcolon/status/1484146426 http://twitter.com/josephcolon/status/1484146432 plus a few more, some for that user and some for others. I've increased my posting timeout in code, but I've also filed a bug, since I'd expect Twitter's duplicate detection code to catch these cases. http://code.google.com/p/twitter-api/issues/detail?id=440 --Eric On Apr 9, 2009, at 3:01 PM, Chad Etzel wrote: Reviving old thread: Seeing duplicates again, and now have examples: http://twitter.com/ryanashleyscott/status/1485237579 http://twitter.com/ryanashleyscott/status/1485239348 same exact content, as far as i can tell, posted back-to-back by the user. ...apparently TweetGrid is scary :) -Chad On Thu, Apr 2, 2009 at 6:15 PM, Eric Blair wrote: That's what I was expecting to see. However, I have a user who's update made it to his timeline twice. I see that we sent the request twice, 5 seconds apart, because the first one didn't complete. The second request returned successful. The user's timeline is protected, but the messages are id 1440033342 and 1440033271. I log the ids of successful posts and, in my logs, I see the higher id (1440033342). --Eric On Apr 2, 2009, at 6:03 PM, Doug Williams wrote: If your application tries to update the status of the same account within a short period of time, Twitter will ignore the update. As the statuses/update method returns the status object, in the case where the message was ignored, the previously successful update (with the same) text will be returned. You can confirm this behavior yourself. Try to update an account's status with two requests back to back containing the same text: $ curl -u user:password -d "status=test" http://twitter.com/statuses/update.xml You will see that the first update is successful. The second request will then return the same status as the first update (verify by id). Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 2, 2009 at 11:58 AM, Eric Blair wrote: Just got a report from one of my users that a message he posted through our app made it through to his Twitter timeline twice. Looking at our server logs, I can see that when he posted, we got a timeout from Twitter and successfully tried to repost. My guess is that the timed-out post actually went through, as did our report. We don't want to be hitting Twitter with duplicate posts, which is why we're careful about when we retry. However, I've seen references to Twitter filtering out duplicates, so I was under the impression that Twitter would detect and reject the repost message in this case. [1] [1]: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fdaf7454be8f9006/acc5323f664a?lnk=gst&q=duplicate#acc5323f664a Am I understanding this correctly or should I be more concerned about duplicate posts making it through my retry code? --Eric
[twitter-dev] Re: Duplicate Tweets
That's what I was expecting to see. However, I have a user who's update made it to his timeline twice. I see that we sent the request twice, 5 seconds apart, because the first one didn't complete. The second request returned successful. The user's timeline is protected, but the messages are id 1440033342 and 1440033271. I log the ids of successful posts and, in my logs, I see the higher id (1440033342). --Eric On Apr 2, 2009, at 6:03 PM, Doug Williams wrote: > If your application tries to update the status of the same account > within a short period of time, Twitter will ignore the update. As > the statuses/update method returns the status object, in the case > where the message was ignored, the previously successful update > (with the same) text will be returned. > > You can confirm this behavior yourself. Try to update an account's > status with two requests back to back containing the same text: > > $ curl -u user:password -d "status=test" > http://twitter.com/statuses/update.xml > > You will see that the first update is successful. The second request > will then return the same status as the first update (verify by id). > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > On Thu, Apr 2, 2009 at 11:58 AM, Eric Blair > wrote: > > Just got a report from one of my users that a message he posted > through our app made it through to his Twitter timeline twice. Looking > at our server logs, I can see that when he posted, we got a timeout > from Twitter and successfully tried to repost. My guess is that the > timed-out post actually went through, as did our report. > > We don't want to be hitting Twitter with duplicate posts, which is why > we're careful about when we retry. However, I've seen references to > Twitter filtering out duplicates, so I was under the impression that > Twitter would detect and reject the repost message in this case. [1] > > [1]: > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fdaf7454be8f9006/acc5323f664a?lnk=gst&q=duplicate#acc5323f664a > > Am I understanding this correctly or should I be more concerned about > duplicate posts making it through my retry code? > > --Eric >
[twitter-dev] Duplicate Tweets
Just got a report from one of my users that a message he posted through our app made it through to his Twitter timeline twice. Looking at our server logs, I can see that when he posted, we got a timeout from Twitter and successfully tried to repost. My guess is that the timed-out post actually went through, as did our report. We don't want to be hitting Twitter with duplicate posts, which is why we're careful about when we retry. However, I've seen references to Twitter filtering out duplicates, so I was under the impression that Twitter would detect and reject the repost message in this case. [1] [1]: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fdaf7454be8f9006/acc5323f664a?lnk=gst&q=duplicate#acc5323f664a Am I understanding this correctly or should I be more concerned about duplicate posts making it through my retry code? --Eric
[twitter-dev] Re: HTTP Status 0
Steve's comment that he's seen this over the past few days over set
timespans - in our case, the problems are most prevalent between noon
and 6PM, eastern.
Also, here's my full traceroute:
Packets
Pings
Host Loss% Snt Last
Avg Best Wrst StDev
1. 209-20-64-2.slicehost.net 0.0% 35260.0
0.0 0.0 292.0 10.5
2. 209.20.79.225 0.6% 35260.0
0.0 0.0 252.0 8.0
3. ge-6-13-115.car1.StLouis1.Level3.net 0.2% 3526 196.0
10.1 0.0 304.0 35.5
4. ae-11-11.car2.StLouis1.Level3.net 0.7% 35260.0
13.4 0.0 328.0 41.4
5. ae-4-4.ebr2.Chicago1.Level3.net0.7% 35268.0
9.7 4.0 584.0 17.0
6. ae-2-56.edge3.Chicago3.Level3.net 0.6% 35264.0
9.5 4.0 304.0 21.8
7. 4.68.63.1980.5% 35264.0
23.5 4.0 360.0 46.9
8. xe-0-3-0.r21.chcgil09.us.bb.gin.ntt.net0.4% 35264.0
4.8 4.0 224.0 7.8
9. p64-7-0-3.r20.snjsca04.us.bb.gin.ntt.net 25.7% 3526 56.0
55.3 52.0 228.0 9.3
10. xe-1-3.r02.mlpsca01.us.bb.gin.ntt.net 11.1% 3526 52.0
68.6 52.0 564.0 44.5
11. mg-1.c00.mlpsca01.us.da.verio.net 0.4% 3526 56.0
73.2 52.0 4536. 92.4
12. 128.121.150.2050.6% 3526 52.0
53.4 52.0 356.0 12.2
13. 128.121.146.85 0.4% 3526 56.0
57.8 52.0 512.0 18.5
14. 128.121.146.1000.6% 3525 52.0
56.1 52.0 436.0 17.0
--Eric
On Feb 20, 2009, at 11:27 AM, Matt Sanford wrote:
>
> The times may help me do some network troubleshooting, what timezone
> is that?
>
> On Feb 20, 2009, at 08:13 AM, swggy wrote:
>
>>
>> I've been seeing the same thing - it started about 3 days ago. I
>> installed a q&d delay/retry loop to manage it and log the times on a
>> couple of API calls - rate_limit_status.json & test.json
>>
>> It seems to be mostly gone today - has only happened once so far at
>> 07:02:22.
>>
>> Yesterday this was a continual problem, with a solid burst locking me
>> out from 14:46:05 to 14:47:16 (I'm retrying every 3 seconds), and
>> ongoing from that point sporadically, at times replying with nothing
>> for 3 or 4 retries before getting a reasonable reply until 19:45:04 -
>> and other than the 1 today, no problems at all from that point.
>>
>>
>> On Feb 19, 4:53 pm, Chris wrote:
>>> Howdy,
>>>
>>> I am making API calls to Twitter using PHP ('Arc90 Twitter API
>>> Client'
>>> Library) to update a users status, and about 3 out of 10 times CURL
>>> returns a HTTP status code of 0 - with no other data returned.
>>>
>>> But if I try again and again it will usually work within a few
>>> repeats. Does anyone have any ideas about this?
>>>
>>> Thanks for your help,
>>>
>>> Chris.
>
Re: HTTP Status 0
I've been seeing that a bit the past few days as well (it looks like the email I sent to the list yesterday about curl multi was an HTTP Status 0 issue). We were outputting the curl output from our app to a file for a bit - it definitely seemed like the cases with status code 0 weren't communicating with Twitter - I've pasted some sample output at the end of the email. The log describes the following situation - we batched 4 requests and, in this case, 2 succeeded and 2 failed. In this case, the failures show up as Connection Timeout. I saw a few of these happen live in our logs and the timeout was definitely shorter than the value we set for CURLOPT_TIMEOUT. However, it might've been long enough to hit the limit set for CURLOPT_CONNECTTIMEOUT. We're increasing that value to see if improves the situation. In other cases, we saw Host Not Found instead of Connection Timeout, so I'm not certain if this will resolve the issue. One thing we did notice is that it looks like we're getting some major packet loss between our server and Twitter - one host was dropping 25% of packets and the next host was dropping 11%. We thought that seemed excessive and might've been contributing to the status 0 message. Here's a sample of the problematic portion of the traceroute: Packets Pings Loss% Snt LastAvg BestWrstStDev 8. xe-0-3-0.r21.chcgil09.us.bb.gin.ntt.net0.4% 35264.0 4.8 4.0 224.0 7.8 9. p64-7-0-3.r20.snjsca04.us.bb.gin.ntt.net 25.7% 3526 56.055.3 52.0228.0 9.3 10. xe-1-3.r02.mlpsca01.us.bb.gin.ntt.net 11.1% 352652.068.652.0 564.0 44.5 11. mg-1.c00.mlpsca01.us.da.verio.net 0.4% 352656.073.252.0 4536. 92.4 Here's the curl output - * About to connect() to www.twitter.com port 80 (#0) * Trying 128.121.146.100... * About to connect() to www.twitter.com port 80 (#1) * Trying 128.121.146.100... * About to connect() to www.twitter.com port 80 (#2) * Trying 128.121.146.100... * About to connect() to www.twitter.com port 80 (#3) * Trying 128.121.146.100... * Connected to www.twitter.com (128.121.146.100) port 80 (#2) * Server auth using Basic with user '**' > GET /direct_messages.xml?count=25&since=Mon+Feb+16+03%3A07%3A36+ %2B+2009 HTTP/1.1 * Connected to www.twitter.com (128.121.146.100) port 80 (#3) * Server auth using Basic with user '**' > GET /direct_messages/sent.xml?count=25&since=Mon+Feb +16+03%3A07%3A36+%2B+2009 HTTP/1.1 < HTTP/1.1 200 OK < Date: Thu, 19 Feb 2009 20:51:06 GMT < Server: hi < Last-Modified: Thu, 19 Feb 2009 20:51:06 GMT < Status: 200 OK < ETag: "8cbb8956513e515ff337bf304285829f" < Pragma: no-cache < Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 < Content-Type: application/xml; charset=utf-8 < Content-Length: 79 < Expires: Tue, 31 Mar 1981 05:00:00 GMT < X-Revision: d50813e1759a5b669840a0ae553da67b69c67caf < X-Transaction: 123507-28856-29642 < Set-Cookie: lang=en; path=/ < Set-Cookie: lang=en; path=/ < Set-Cookie: _twitter_sess = BAh7CToTcGFzc3dvcmRfdG9rZW4iLWRiNDcwZjgzYWFlNjU5YTk5YmM1MjY1 %250AZjE4OTM5MzUwNDA2NWJlMjA6CXVzZXJpA%252F5d5ToHaWQiJTIyMmVmZmVlMjFk %250ANWU4OWY0NGNmMWU1MzM2MTEzZWQ3IgpmbGFzaElDOidBY3Rpb25Db250cm9s %250AbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA --5bd0845e53637728605a15dd8c9fa4043cb5fea6; domain=.twitter.com; path=/ < Vary: Accept-Encoding < Connection: close < * Expire cleared * Closing connection #2 < HTTP/1.1 200 OK < Date: Thu, 19 Feb 2009 20:51:06 GMT < Server: hi < Last-Modified: Thu, 19 Feb 2009 20:51:06 GMT < Status: 200 OK < ETag: "8cbb8956513e515ff337bf304285829f" < Pragma: no-cache < Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 < Content-Type: application/xml; charset=utf-8 < Content-Length: 79 < Expires: Tue, 31 Mar 1981 05:00:00 GMT < X-Revision: d50813e1759a5b669840a0ae553da67b69c67caf < X-Transaction: 123507-55169-28378 < Set-Cookie: lang=en; path=/ < Set-Cookie: lang=en; path=/ < Set-Cookie: _twitter_sess = BAh7CToTcGFzc3dvcmRfdG9rZW4iLWRiNDcwZjgzYWFlNjU5YTk5YmM1MjY1 %250AZjE4OTM5MzUwNDA2NWJlMjA6CXVzZXJpA %252F5d5ToHaWQiJTUwYjUxMDg1OGE2 %250AY2ZlYWNhYzE2MDQ1ZjlmMWRjZDRkIgpmbGFzaElDOidBY3Rpb25Db250cm9s %250AbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- d1e252a95e502fa449339582429e1703159e5d2f; domain=.twitter.com; path=/ < Vary: Accept-Encoding < Connection: close < * Expire cleared * Closing connection #3 * Expire cleared * Expire cleared * Connection time-out * Closing connection #0 * Connection time-out
Accessing Twitter via PHP curl_multi
Any folks out there tried accessing Twitter via curl_multi in PHP? My
app is setup so that, when a user makes a requests, I ask Twitter for
the friends timeline, the reply timeline, the direct_message timeline
and the direct_message/sent timeline. Since I deployed the code, I've
been having problem where my requests have been failing - according to
curl_getInfo, they're failing with HTTP status code 0, which I'm
assuming means that curl's not even getting any data.
I build up the multi requests like this ($targets is an array
containing the URL path for each requests, along with some other data):
$mh = curl_multi_init();
foreach ($targets as $each_target) {
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "www.twitter.com" .
$each_target['path']);
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 2);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_AUTOREFERER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, 180);
curl_setopt($ch, CURLOPT_HTTPGET, 1);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 1);
curl_setopt($ch, CURLOPT_USERPWD, "$username:$password");
$chs[] = $ch;
curl_multi_add_handle($mh, $ch);
}
I then run through the responses like this
do {
$mrc = curl_multi_exec($mh, $active);
} while ($mrc == CURLM_CALL_MULTI_PERFORM);
if (CURLM_OK != $mrc) {
break;
}
while ($done = curl_multi_info_read($mh)) {
$handle_index = array_search($done['handle'], $chs);
if (false !== $handle_index) {
$response = curl_multi_getcontent($done['handle']);
$response_code = curl_getinfo($done['handle'],
CURLINFO_HTTP_CODE);
...
}
}
For calls that seem like they should otherwise be working, I'm getting
back connection failed, HTTP status 0.
Sometimes, the curl error is reported as timeout, which makes no sense
because it was happening almost immediately (I previously had a 3
minute timeout set and was seeing this issue - I reverted back to the
default curl timeout as an experiment). Other times, curl reports that
it "Couldn't connect to host"
Thanks,
--Eric
Re: calls for sent/received direct messages with since date parameter returning null
I believe the since parameter can only be used to go back 24 hours. From the docs: > • since. Optional. Narrows the resulting list of direct messages > to just those sent after the specified HTTP-formatted date, up to 24 > hours old. The same behavior is available by setting the If- > Modified-Since parameter in your HTTP request. Ex: > http://twitter.com/direct_messages.atom?since=Tue%2C+27+Mar+2007+22%3A55%3A48+GMT --Eric On Jan 31, 2009, at 6:52 PM, Dimebrain wrote: > > output of unit test (calling since with date prior twitter launch, > fails with closer dates as well) > > without since: http://twitter.com/direct_messages.json > with since: > http://twitter.com/direct_messages.json?since=Fri2c+27+Feb+2004+23%3a50%3a41+GMT > > 20 direct messages found without 'since' > 1 direct messages found with 'since' > > > On Jan 31, 4:27 pm, Alex Payne wrote: >> Sounds like we don't have direct messages for you since the date >> you're specifying :) >> >> On Sat, Jan 31, 2009 at 00:58, Dimebrain >> wrote: >> >>> I'm not able to make a call to get direct messages sent or >>> received by >>> the authenticating user if I add the "since" parameter, passing the >>> correctly formatted / url-encoded date. All I get back is "nil". >> >>> Even with the demo API call in the REST documentation, i.e.: >>> http://twitter.com/direct_messages/sent.xml?since=Tue%2C+27+Mar+2007+ >>> ... >> >>> I am getting a nil response. If I leave off the since parameter, I >>> get >>> all direct messages sent in the query above, including those later >>> than the example date. >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Inconsistent Response From verify_credentials
I've got one particular user of my application who gets inconsistent responses when we try to verify his credentials. A request to veryigy_credentials with a seemingly valid username and password will return an error message that the user cannot be authenticated. The same call made a few seconds later will succeed. We've seen this both from within our application and from attempting an authenticated call via curl on the command line. I've filed a bug against the behavior, but I was wondering if anybody else had hit this issue and had any ideas. --Eric
Test Method Failing
I'm getting a 301 error when I call the test method. I was using test as a check to see if Twitter was up before doing the bulk of my calls, so this threw my scripts for a bit of a loop. http://twitter.com/help/test.xml returns HTTP/1.1 301 Moved Permanently Date: Fri, 16 Jan 2009 23:44:50 GMT Server: Apache Location: http://help.twitter.com/ Cache-Control: max-age=300 Expires: Fri, 16 Jan 2009 23:49:50 GMT Vary: Accept-Encoding Content-Length: 232 Connection: close Content-Type: text/html; charset=iso-8859-1 301 Moved Permanently Moved Permanently The document has moved http://help.twitter.com/";>here. --Eric
