[twitter-dev] Re: Incorrect Signature errors with both Tweepy and python-twitter
your welcome - glad you found a solution! -- 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: Incorrect Signature errors with both Tweepy and python-twitter
Here is what I see: send: u'GET /1/account/verify_credentials.json?oauth_nonce=85271670oauth_timestamp=1303621152oauth_consumer_key=...oauth_signature_method=HMAC-SHA1oauth_version=1.0oauth_token=...oauth_signature=... HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: api.twitter.com\r\nConnection: close\r\nUser-Agent: Python-urllib/2.7\r\n\r\n' reply: 'HTTP/1.1 200 OK\r\n' and then send looks identical to yours (order and fields) so that is telling me you may need to regenerate your tokens (especially since you are having issues with another lib.) Have you tried a test using that test twitter api page? I am drawing a blank on the link :( -- 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: trying to register a twitter dev account
Guess I'll answer part of my own question ... Was regenerating the OAuth keys I use for testing and noticed that the Connections part of the profile is what I was missing. So on a hunch I just went to /apps with my new account and bob's-your-uncle there was the magic page. Of course this *still* doesn't let me sign into the dev.twitter.com site - but I only wanted to do that to get to the register app page. How long has OAuth been in use and the documentation is still a mess? Sorry to be snarky but I can't imagine what someone new to twitter must go thru :/ -- 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] trying to register a twitter dev account
I go to http://dev.twitter.com/login?redirect_after_login=%2Fapps%2Fnew to try and get a new twitter account registered for a new app and I can't login as the twitter user. So I go to http://dev.twitter.com/start to see how to get that twitter id flagged as a developer and nothing but more sign-in pages. One link almost worked and got me all excited - but I ended up back at my twitter settings page with no way to register an application :( Where have you guys hidden the new-dev-signup page? -- 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] Pin via e-mail?
Is it possible to get PIN via e-mail? How long Auth Link lives? My desktop app will send clients authorization link Thet will click the link and get PIN e-mailed back to me What process to execute and data I need to store to finish authorization and get the keys? Thanks. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Looks like our application is DOA...
There's simple workaround for that. Just think about it and you'll figure it out ;-) -- 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] getting 404 error when trying to subscribe to a list
Using oAuth I am making the following call: POST /1/userid/3968155/subscribers.json where userid is the user whose oAuth tokens are in use and 3968155 is the id of the list i'm trying to subscribe to Twitter returns a stock 404 result I've even tried it with the slug id of the list, same result. I also know I have a valid oAuth environment because i'm getting the list information from a previous valid call to /1/userid/lists/ subscriptions.json and I always do /1/account/verify_credentials.json when i'm working on the library code. any clues? thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: getting 404 error when trying to subscribe to a list
On Aug 24, 9:27 pm, Matt Harris thematthar...@twitter.com wrote:
I agree this isn't clear in the docs so i'll get onto updating them.
The structure for this URL is:
POST /1/:user/:list_id/subscribers.{format}
where:
:user is the user_id or screen_name of the user who owns the list
:list_id is the ID or slug for the list owned by :user. This isn't
necessarily the display name of the list.
The method will then subscribe the user who you are authenticating as
to the list of subscribers.
For example if I want to subscribe to the world-leaders list created
by the @verified account I would use:
POST /1/verified/world-leaders/subscribers.json
oh my, now that is one not what I gathered from the doc and prior
use...
one set of api calls requires that :userid is the caller (I guess they
are pre-oauthcalypse) and the lists ones are not.
I can see why it would be that way from a REST point of view if I tilt
my head a bit - but yea, some rewording of the doc page is definitely
in order :)
thanks,
On success the method will return the details of of the list subscribed to.
Hope that helps
Matt
On Tue, Aug 24, 2010 at 6:12 PM, Matthew Terenzio mteren...@gmail.com wrote:
Try screen_name instead of userid. I'm not certain but it rings a bell. Not
that it shouldn't work with id, of course.
On Tue, Aug 24, 2010 at 8:49 PM, bear bea...@gmail.com wrote:
Using oAuth I am making the following call:
POST /1/userid/3968155/subscribers.json
where userid is the user whose oAuth tokens are in use and 3968155 is
the id of the list i'm trying to subscribe to
Twitter returns a stock 404 result
I've even tried it with the slug id of the list, same result. I also
know I have a valid oAuth environment because i'm getting the list
information from a previous valid call to /1/userid/lists/
subscriptions.json and I always do /1/account/verify_credentials.json
when i'm working on the library code.
any clues?
thanks
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
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
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] python oauth2 and twitter - invalid signature issue
I'm working on bringing the python-twitter library up to date with respect to using oAuth and i'm running into a brick wall... I've scanned the group postings and by far it seems that the most common issue when generating a request is that the order of items in the url param list is not the same as the order of items sent off to be signed *and* that said item list must be sorted. Using the debug key/secret values from the wiki, I generate the following: (debug output from python's urllib2, formatted to wrap so it's readable) GET /1/account/verify_credentials.json? oauth_nonce=26979601 oauth_timestamp=1281612120 oauth_consumer_key=GDdmIQH6jhtmLUypg82g oauth_signature_method=HMAC-SHA1 oauth_version=1.0 oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw oauth_signature=e82GTcQn9Rjir1QMNw19%2FwTkAYA%3D HTTP/1.1\r\n Accept-Encoding: identity\r\n Host: api.twitter.com\r\n Connection: close\r\n Authorization: OAuth realm=, oauth_nonce=26979601, oauth_timestamp=1281612120, oauth_consumer_key=GDdmIQH6jhtmLUypg82g, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw, oauth_signature=e82GTcQn9Rjir1QMNw19%2FwTkAYA%3D\r\n\r\n' and this is the raw data being signed: GEThttps%3A%2F%2Fapi.twitter.com%2F1%2Faccount %2Fverify_credentials.jsonoauth_consumer_key%3DGDdmIQH6jhtmLUypg82g %26oauth_nonce%3D26979601%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1281612120%26oauth_token%3D819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_version%3D1.0 First thing I notice is that the ordering of the oauth_* items is all over the place (i'll be sending a message to the python-oauth2 folks once I figure out where they are hanging out) but even when I correct for that and run it again, I *still* get an Invalid Signature error from Twitter! Here is the same debug run where all of the oauth_* items are sorted: (debug output from urllib2, formatted so it's readable) GET /1/account/verify_credentials.json? oauth_consumer_key=GDdmIQH6jhtmLUypg82g oauth_nonce=21793837 oauth_signature=5AQnyr09ZBcRz95SDPFOKizBEoo%3D oauth_signature_method=HMAC-SHA1 oauth_timestamp=1281612568 oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw oauth_version=1.0 HTTP/1.1\r\n Accept-Encoding: identity\r\n Host: api.twitter.com\r\n Connection: close\r\n Authorization: OAuth oauth_consumer_key=GDdmIQH6jhtmLUypg82g, oauth_nonce=21793837, oauth_signature=5AQnyr09ZBcRz95SDPFOKizBEoo %3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1281612568, oauth_token=819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw, oauth_version=1.0\r\n\r \n' raw data being signed: GEThttps%3A%2F%2Fapi.twitter.com%2F1%2Faccount %2Fverify_credentials.jsonoauth_consumer_key%3DGDdmIQH6jhtmLUypg82g %26oauth_nonce%3D21793837%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1281612568%26oauth_token%3D819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_version%3D1.0 looking for any clue-sticks, lifelines or hell, even a RTFM with a url - thanks!
[twitter-dev] Re: python oauth2 and twitter - invalid signature issue
On Aug 12, 7:57 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/12/10 1:33 PM, bear wrote: I'm working on bringing the python-twitter library up to date with respect to using oAuth and i'm running into a brick wall... I've scanned the group postings and by far it seems that the most common issue when generating a request is that the order of items in the url param list is not the same as the order of items sent off to be signed *and* that said item list must be sorted. Using the debug key/secret values from the wiki, I generate the following: (debug output from python's urllib2, formatted to wrap so it's readable) GET /1/account/verify_credentials.json? oauth_nonce=26979601 oauth_timestamp=1281612120 oauth_consumer_key=GDdmIQH6jhtmLUypg82g oauth_signature_method=HMAC-SHA1 oauth_version=1.0 oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw oauth_signature=e82GTcQn9Rjir1QMNw19%2FwTkAYA%3D HTTP/1.1\r\n Accept-Encoding: identity\r\n Host: api.twitter.com\r\n Connection: close\r\n Authorization: OAuth realm=, oauth_nonce=26979601, oauth_timestamp=1281612120, oauth_consumer_key=GDdmIQH6jhtmLUypg82g, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw, oauth_signature=e82GTcQn9Rjir1QMNw19%2FwTkAYA%3D\r\n\r\n' and this is the raw data being signed: GEThttps%3A%2F%2Fapi.twitter.com%2F1%2Faccount %2Fverify_credentials.jsonoauth_consumer_key%3DGDdmIQH6jhtmLUypg82g %26oauth_nonce%3D26979601%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1281612120%26oauth_token%3D819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_version%3D1.0 First thing I notice is that the ordering of the oauth_* items is all over the place (i'll be sending a message to the python-oauth2 folks once I figure out where they are hanging out) but even when I correct for that and run it again, I *still* get an Invalid Signature error from Twitter! Here is the same debug run where all of the oauth_* items are sorted: (debug output from urllib2, formatted so it's readable) GET /1/account/verify_credentials.json? oauth_consumer_key=GDdmIQH6jhtmLUypg82g oauth_nonce=21793837 oauth_signature=5AQnyr09ZBcRz95SDPFOKizBEoo%3D oauth_signature_method=HMAC-SHA1 oauth_timestamp=1281612568 oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw oauth_version=1.0 HTTP/1.1\r\n Accept-Encoding: identity\r\n Host: api.twitter.com\r\n Connection: close\r\n Authorization: OAuth oauth_consumer_key=GDdmIQH6jhtmLUypg82g, oauth_nonce=21793837, oauth_signature=5AQnyr09ZBcRz95SDPFOKizBEoo %3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1281612568, oauth_token=819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw, oauth_version=1.0\r\n\r \n' raw data being signed: GEThttps%3A%2F%2Fapi.twitter.com%2F1%2Faccount %2Fverify_credentials.jsonoauth_consumer_key%3DGDdmIQH6jhtmLUypg82g %26oauth_nonce%3D21793837%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1281612568%26oauth_token%3D819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_version%3D1.0 looking for any clue-sticks, lifelines or hell, even a RTFM with a url - thanks! Hi, Multiple things. * You don't have to send the oauth_* parameters in both the query and the Authorization: header. The library i'm using does that - not sure why. I'll explore removing all but oauth_signature in a bit. * The Base String seems fine, but you should not be using the keys on the wiki - they are random keys and will not work. (!) I used the wiki keys only because another post (oAuth and AppleScript) someone requested that they use those keys so that the signature value could be compared - I did the same. I get Invalid Signature when using keys that I've gotten back from Twitter. * The field order in the Authorization: header does not matter. Is it the order in the URL and the Signature then that is the magic ? I don't know which secrets you are using so I can't verify your signature generation, although I assume that it is correct. heck, i'm willing to post the key and secret so you can follow along - it is tied to a test app so I can blow them away at anytime. Tom thanks for the response
[twitter-dev] Re: python oauth2 and twitter - invalid signature issue
On Aug 12, 8:52 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/12/10 2:37 PM, bear wrote: On Aug 12, 7:57 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/12/10 1:33 PM, bear wrote: I'm working on bringing the python-twitter library up to date with respect to using oAuth and i'm running into a brick wall... I've scanned the group postings and by far it seems that the most common issue when generating a request is that the order of items in the url param list is not the same as the order of items sent off to be signed *and* that said item list must be sorted. Using the debug key/secret values from the wiki, I generate the following: (debug output from python's urllib2, formatted to wrap so it's readable) GET /1/account/verify_credentials.json? oauth_nonce=26979601 oauth_timestamp=1281612120 oauth_consumer_key=GDdmIQH6jhtmLUypg82g oauth_signature_method=HMAC-SHA1 oauth_version=1.0 oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw oauth_signature=e82GTcQn9Rjir1QMNw19%2FwTkAYA%3D HTTP/1.1\r\n Accept-Encoding: identity\r\n Host: api.twitter.com\r\n Connection: close\r\n Authorization: OAuth realm=, oauth_nonce=26979601, oauth_timestamp=1281612120, oauth_consumer_key=GDdmIQH6jhtmLUypg82g, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw, oauth_signature=e82GTcQn9Rjir1QMNw19%2FwTkAYA%3D\r\n\r\n' and this is the raw data being signed: GEThttps%3A%2F%2Fapi.twitter.com%2F1%2Faccount %2Fverify_credentials.jsonoauth_consumer_key%3DGDdmIQH6jhtmLUypg82g %26oauth_nonce%3D26979601%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1281612120%26oauth_token%3D819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_version%3D1.0 First thing I notice is that the ordering of the oauth_* items is all over the place (i'll be sending a message to the python-oauth2 folks once I figure out where they are hanging out) but even when I correct for that and run it again, I *still* get an Invalid Signature error from Twitter! Here is the same debug run where all of the oauth_* items are sorted: (debug output from urllib2, formatted so it's readable) GET /1/account/verify_credentials.json? oauth_consumer_key=GDdmIQH6jhtmLUypg82g oauth_nonce=21793837 oauth_signature=5AQnyr09ZBcRz95SDPFOKizBEoo%3D oauth_signature_method=HMAC-SHA1 oauth_timestamp=1281612568 oauth_token=819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw oauth_version=1.0 HTTP/1.1\r\n Accept-Encoding: identity\r\n Host: api.twitter.com\r\n Connection: close\r\n Authorization: OAuth oauth_consumer_key=GDdmIQH6jhtmLUypg82g, oauth_nonce=21793837, oauth_signature=5AQnyr09ZBcRz95SDPFOKizBEoo %3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1281612568, oauth_token=819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw, oauth_version=1.0\r\n\r \n' raw data being signed: GEThttps%3A%2F%2Fapi.twitter.com%2F1%2Faccount %2Fverify_credentials.jsonoauth_consumer_key%3DGDdmIQH6jhtmLUypg82g %26oauth_nonce%3D21793837%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1281612568%26oauth_token%3D819797- Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_version%3D1.0 looking for any clue-sticks, lifelines or hell, even a RTFM with a url - thanks! Hi, Multiple things. * You don't have to send the oauth_* parameters in both the query and the Authorization: header. The library i'm using does that - not sure why. I'll explore removing all but oauth_signature in a bit. Sorry if you misunderstood me. You should send all of them only once - either in the Authorization header or in the query. Ah - I did completely get what you were saying wrong. As soon as I removed it from the header everything started to work! amazing what happens when you pay attention ;) * The Base String seems fine, but you should not be using the keys on the wiki - they are random keys and will not work. (!) I used the wiki keys only because another post (oAuth and AppleScript) someone requested that they use those keys so that the signature value could be compared - I did the same. I get Invalid Signature when using keys that I've gotten back from Twitter That was me. Using this base string : GEThttps%3A%2F%2Fapi.twitter.com%2F1%2Faccount%2Fverify_credentials.jsono auth_consumer_key%3DGDdmIQH6jhtmLUypg82g%26oauth_nonce%3D26979601%26oauth_s ignature_method%3DHMAC-SHA1%26oauth_timestamp%3D1281612120%26oauth_token%3D 819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_version%3D1.0 Key: MCD8BKwGdgPHvAuvgvz4EQpqDAtx89grbuNMRd7Eh98J6zix3FfA9LofH0awS24M3HcBYXO5nI 1iYe8EfBA Signature: e82GTcQn9Rjir1QMNw19/wTkAYA= So that part is fine as well. * The field order in the Authorization: header does not matter. Is it the order in the URL and the Signature then that is the magic ? Ordering the fields is only necessary
[twitter-dev] Re: Python Twitter
On Jun 13, 5:07 pm, pythonista sitecontac...@gmail.com wrote: Ok Thanks for the heads up, Hwee-Boon. On Jun 13, 1:37 am, Hwee-Boon Yar hweeb...@gmail.com wrote: Seehttp://code.google.com/p/oauth-python-twitter/source/browse/trunk/oau... y?r=6 which extends python-twitter to include OAuth calls. I added a method at a fork athttp://github.com/hboon/oauthtwitter/toinclude the XAuth token exchange call. I am working on integrating Hwee-Boon's fork back into the trunk of python-twitter and should have it pushed to the repository early this week. Pending tests (and Twitter not changing things) I should be releasing a version that contains the new code. p.s. I'm not the core author of python-twitter but I'm working with them to make sure the library is updated and current. -- Hwee-Boon On Jun 13, 10:39 am, pythonista sitecontac...@gmail.com wrote: Hello, I am using the simplegeo fork of python-oauth2, and it is working fine. However, I then realize it doesn't contain API calls to actually send tweets. Anyone know of a particular Api wrapper that has updated its code, so that calls are made using the token/token secret that is now mandatory, or will be this month ? http://code.google.com/p/python-twitter/doesn'tseemto have been updated yet for making calls via oauth Thanks.
[twitter-dev] Stream API - which one to use
I'm getting some code ready for delivery to a customer and I need to settle on the best way to get twitter data into their app. I've been using the official Stream API up till now but that has all kinds of problems for me because it's basically the search results delivered as a stream, so I have to do all kinds of post processing on it to remove the extra stuff. During the Chirp conference I saw that there was a chirpstream preview of a user's data - has that been released to us non-sanfran devs yet? or is it still special? I'm also seeing in the dev group postings things like betastream, earlybird, and some others - is there any chance of even me being able to figure out which stream api will eventually get used at all? So yea, looking to get some answers on which stream api to use or if good old polling is still the best way to get clean, accurate user data?
[twitter-dev] Re: 404 Errors on friends and followers using cursors
I am now seeing this on some of my own accounts - has any movement or
fix been applied?
here is the url i'm trying:
curl http://twitter.com/statuses/friends/codebear.json -- returns
[]
curl http://twitter.com/statuses/friends/manta.json -- returns
{request:/statuses/friends/manta.json,error:Not found}
On Dec 28 2009, 2:42 pm, Mageuzi mage...@gmail.com wrote:
Sorry to keep bringing this up, but this is still causing problems for
me. Is there any follow-up as to what the issue is? Thanks in
advance.
On Dec 22, 10:06 pm, Mageuzi mage...@gmail.com wrote:
Is there an update to the status of this issue? A user of my program
reported a problem that ended up being this. While trying to iterate
through:http://api.twitter.com/1/statuses/friends/oevl.xml
Cursor 1274505087418535016 returned fine and contained a next_cursor
value of 1267920196862230269. That value returned a 404.
On Dec 8, 1:32 pm, Ammo Collector binhqtra...@gmail.com wrote:
If you get the following URLs and continue to using the next_cursor,
you receive incorrect 404s:
http://twitter.com/statuses/friends/debra_bee.xml?cursor=130554434315...
Any ideas?
[twitter-dev] Re: HTTP Server Error 503 No available server to handle this request
John, I'm going to be in San Fran the week of Nov 5th, I would love to meet with the Twitter Ops team on how we (we being Seesmic and possibly other large consumers of Twitter) can help you guys respond faster to these issues. If there was someone (or thing) to poke I could have given you guys early warning more than an hour before you updated the status blog as I was seeing a dramatic increase in the error rate trends. As it stands now all I can do is look at twitter, the IRC channel and this and wonder what's going on until someone remembers to update the status blog. On Oct 12, 3:49 pm, John Kalucki jkalu...@gmail.com wrote: We updated the status blog:http://status.twitter.com. On Oct 12, 12:44 pm, Dewald Pretorius dpr...@gmail.com wrote: It's now even on Mashable: http://mashable.com/2009/10/12/http-server-error-twitter/ On Oct 12, 4:36 pm, ryan alford ryanalford...@gmail.com wrote: Thanks Dewalt. I was beginning to think something was wrong with my app. Atleast I know I am not the only one seeing these slow downs. Ryan On Mon, Oct 12, 2009 at 3:26 PM, Dewald Pretorius dpr...@gmail.com wrote: Their system must just be overloaded at the moment. I have been seeing response times in the 10+ seconds region per simple API call since earlier this morning. Dewald On Oct 12, 3:56 pm, RTuosto ryantuo...@gmail.com wrote: I'm getting this error when looking athttp://www.twitter.comaswell as user pages. Whats the issue?
OAuth callback for local dev testing
Any chance of being allowed to use a callback URL that is local? http://localhost:4000/callback/ This would let me test using my local resources and not have to wrangle a server setup thanks,
Re: OAuth, the time has come.
this is like getting a call from your wife that a big box has been delivered to your house and you have no idea what it is... /me clicks refresh again /me clicks refresh On Feb 11, 6:46 pm, Matt Sanford m...@twitter.com wrote: And the first bugs is … That some of you are not seeing the new Connections tab. It looks like a minor bug in the code that does the beta access check (which was new, never done a closed beta before). We're working on a fix now and will send it out with tomorrows morning deploy. I'll update the list once it's out. Sorry about that; — Matt Sanford On Feb 11, 2009, at 02:16 PM, Matt Sanford wrote: And now for what I forgot, During this closed beta we recommend very strongly that you not do general software releases using the feature. If we find any security or performance problems we will need to turn off OAuth and I don't want to break your apps. Your app can sign up users who are not in the closed beta but since this is really a focus on getting feedback please try and limit the audience to people who you feel can provide some feedback. Thanks; — Matt Sanford On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote: Hello Everyone, Some of you are in the OAuth closed beta and some are not. I know that's frustrating but we need to start small so we aren't buried in feature requests and bugs all at once. Our intention is to discuss the OAuth progress on this main API Google group (http://groups.google.com/group/twitter-development-talk ). If the discussion gets in the way of the normal group operation please speak up and we can always move it off to a new Google group of its own. With all of that in mind we just launched the closed beta switch. If you're one of the 150 or so people included in the closed beta your settings page (http://twitter.com/account/settings) now contains a Connections tab. In the sidebar is a little information and a link to register your very own application. When you register a new application it will begin as suspended. You'll have the technical details (the key and secret) you need to get started but one of the Twitter admins will have to approve the application. It is not our intention to leave this in place forever but during these early application registrations we need to monitor things. Please use real descriptions and meaningful names, since that' what we'll have to go on. Especially meaningful names. During the closed beta we're looking for feedback. The Google group is good for discussing general issues and experiences but the Google code issues are the best place for bugs and enhancements (http://code.google.com/p/twitter-api/issues/list if you don't already know). I added a new milestone of OAuth, so please mark any bugs with the correct milestone. When you report issues try to be specific about the problem, especially in how to reproduce it. It would also save us some time reviewing if you mark enhancements with Type-Enhancementin the appropriate box. Thanks; — Matt Sanford / @mzsanford
