[twitter-dev] 401 unauthorized

My previous post is waiting to be moderated since I'm a newbie I think, but I was wrong. I thought it was a get vs. post issue, but it seems to be that my code works very intermittently. The error is always a 401 unauthorized in getting the access token from the request token. but once in a while

[twitter-dev] Re: OAuth and screen name

On 4/17/09 7:19 PM, Doug Williams wrote: Matt has done an amazing job this week. Just want to throw it out there that I'm super impressed. Now... to drop Sign in with Twitter around the web. It's now available on Twitter Karma! I'm still allowing folks to use their Twitter user/password and

[twitter-dev] Re: OAuth and screen name

Yeah Matt's the Donald Trump of releases. He looks a task or bug, right in the eye, points: "you're fired." On Apr 17, 2009, at 4:19 PM, Doug Williams wrote: Matt has done an amazing job this week. Just want to throw it out there that I'm super impressed. Now... to drop Sign in with Twitt

[twitter-dev] Re: What precisely does notification mean?

Allen, Notifications are for device notifications (like SMS or IM) if the user has them enabled. Following means that a user's updates are included in your timeline. Notifications mean that a user's updates appear in your timeline AND are sent to your enabled devices. Doug Williams Twitter API Sup

[twitter-dev] Re: OAuth and screen name

Matt has done an amazing job this week. Just want to throw it out there that I'm super impressed. Now... to drop Sign in with Twitter around the web. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 17, 2009 at 2:45 PM, Dossy Shiobara wrote: > > On 4/17/09 5:28 PM, Matt

[twitter-dev] Re: To link the @ or not to link the @, that is the question

On Fri, Apr 17, 2009 at 6:36 PM, Nick Arnett wrote: > > Perhaps it helps to think about a tool that extracts the tagged text from > links.  Would it make sense to end up with text that omits the @ sign?  Not > really, I disagree. There's really nothing useful about the @ sign except to signify

[twitter-dev] Re: To link the @ or not to link the @, that is the question

On Fri, Apr 17, 2009 at 7:21 AM, Chad Etzel wrote: > > A more lighthearted discussion to see where people stand on this > convention. > > We all know the convention of prefixing usernames with the @ symbol, > the interesting thing I notice is that different sites (and even > within tiwtter's site

[twitter-dev] Re: To link the @ or not to link the @, that is the question

This is something else that could go on a "best practices" page on the apiwiki. On Fri, Apr 17, 2009 at 15:50, Doug Williams wrote: > I agree. I'm all for convention... It helps users navigate and build > confidence in the Twitter experience, where ever it may be. > > Doug Williams > Twitter API

[twitter-dev] What precisely does notification mean?

Seeing all the posts here, I'm getting confused as to what the term notification means. Does it mean, for example: a) the person has it enabled to get email when someone starts following them b) the person has it enabled to notices sent to their mobile phone c) something else? Seriously, I'

[twitter-dev] Re: OAuth and screen name

On 4/17/09 5:28 PM, Matt Sanford wrote: It's working fine for me, and it sounds like for Abraham as well. Perhaps some more details about how you're calling it would help. Go ahead and fill out a bug report [1] with the headers and whatnot and I'll take a look. Done! Thanks. http://code

[twitter-dev] Re: OAuth and screen name

Hi Dossy, It's working fine for me, and it sounds like for Abraham as well. Perhaps some more details about how you're calling it would help. Go ahead and fill out a bug report [1] with the headers and whatnot and I'll take a look. Thanks; — Matt [1] - http://code.google.com/p/twit

[twitter-dev] Re: OAuth and screen name

On 4/17/09 4:58 PM, Matt Sanford wrote: Totally right, we just deployed the change. The method now calls the callback with the request token and that token can be exchanged for the existing access token. OMG awesome! Thank you SO much for the quick turn-around, Matt. Now, can someone help in

[twitter-dev] Re: Tweet Corpus creation for NLP research

Anything you can do to help people determine better the language of tweets, so search is more usable for international users. ;)) I am a bit curious about the mentioned 'costs of publishing in journals and conferences' - don't know about the journals. but none of the conferences I know of in Tech

[twitter-dev] Re: OAuth and screen name

Hello all, Totally right, we just deployed the change. The method now calls the callback with the request token and that token can be exchanged for the existing access token. I have been away from email getting the fix tested and deployed or I would have responded sooner. This fixes t

[twitter-dev] Re: To link the @ or not to link the @, that is the question

I agree. I'm all for convention... It helps users navigate and build confidence in the Twitter experience, where ever it may be. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 17, 2009 at 7:45 AM, Abraham Williams <4bra...@gmail.com> wrote: > I don't link the @ sign beca

[twitter-dev] Re: Tweet Corpus creation for NLP research

I've been collecting tweets for about a week for a project (http:// www.happn.in). Some characteristics of my current dataset: * Begin around April 10th 2009 * Collected from users who are located nearby 26 US cities * ~5,000,000 tweets * Growing at ~800,000 per day * ~900MB in mysql * ~375,000 u

[twitter-dev] Re: url as an input

The number of results you get is going to depend entirely on the url/users and does not indicate which services is better. On Fri, Apr 17, 2009 at 14:17, ParsePlz wrote: > > I have already tried with backtweets API, it works but give lesser > results than on-site search... > > On Apr 16, 12:45 a

[twitter-dev] Re: Tweet Corpus creation for NLP research

Part 1: http://drop.io/gmx85rd (tweetsgzaa) Part 2: http://drop.io/f5itrsx (tweetsgzab) Password (for the download): twitter The two parts need to be concatenated and then un-gzipped (naming the concatenated file tweets.gz would be appropriate). Nick The format is a tab-delimited text file.

[twitter-dev] Re: url as an input

I have already tried with backtweets API, it works but give lesser results than on-site search... On Apr 16, 12:45 am, ParsePlz wrote: > Hi, > > could someone please post an example API request, I mean the url as > input, which api request to be used. > > I tried withhttp://search.twitter.com/se

[twitter-dev] Re: OAuth and screen name

I'm going to bring this up just to put this out there, but it really seems to me that you should be using OpenID to authenticate the user and OAuth for authorizing access to a user's account. Given that any user can change their username at will, I worry that app developers will rely on and *trus

[twitter-dev] Re: Rate limit status's "remaining_hits" element scope

It is the number of hits you have left until the reset-time is hit. So it's part of that rolling window. 19933 2 2009-04-08T21:57:23+00:00 1239227843 Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 17, 2009 at 6:27 AM, Dimebrain wrote: > > I just realized I

[twitter-dev] Re: OAuth and screen name

You're such a tease! I'm assuming that it's going to change by you returning a request token and us exchanging it for the previous access token like usual... I understand you're probably not going to respond to that. (as an aside, we've implemented this in dev with a fallback so that if the aut

[twitter-dev] Re: Updating icon for OAuth applications

follow the link Matt included marked with "[1]" and fill out the form. On Fri, Apr 17, 2009 at 10:22, TweetPhoto wrote: > > Hi Matt, > > Not sure how to open a "Google Code issue [1]" to fix the logo image > issue. > > I will be more than happy to open it if you could let me know how. > > Thanks

[twitter-dev] Re: Updating icon for OAuth applications

Hi Matt, Not sure how to open a "Google Code issue [1]" to fix the logo image issue. I will be more than happy to open it if you could let me know how. Thanks a million for getting that fixed! Sean On Apr 16, 7:49 am, Matt Sanford wrote: > Hi Sean, > >      That's certainly a bug. We handle

[twitter-dev] Re: Tweet Corpus creation for NLP research

I'm splitting it and putting it on drop.io. Will take a little while to upload... I'll post when it's available. Nick On Fri, Apr 17, 2009 at 9:17 AM, djMax wrote: > > http://drop.io > > On Apr 17, 12:07 pm, Nick Arnett wrote: > > Michele, djMax and anybody else interested... It is a 128MB f

[twitter-dev] Re: 403 on valid request to friendships/create/ if friendship already exists

Woops, wrong 403 thread. My last two mails were about the search 403s. Sorry about that. — Matt On Apr 17, 9:31 am, Matt Sanford wrote: > Hi all, > >      The issue with random HTTP 403s on search (both API and web)   > should now be fixed. Similar to the employee password prompts a few   > day

[twitter-dev] Re: 403 on valid request to friendships/create/ if friendship already exists

Hi all, The issue with random HTTP 403s on search (both API and web) should now be fixed. Similar to the employee password prompts a few days ago we had a host unexpectedly join the search cluster. We want more capacity so bad we're actually convincing inanimate objects to join our ca

[twitter-dev] Re: Tweet Corpus creation for NLP research

On Fri, Apr 17, 2009 at 9:17 AM, djMax wrote: > > http://drop.io > The free version is limited to 100MB... I could split it, I guess. Any others with a higher limit? Nick

[twitter-dev] Re: 403 on valid request to friendships/create/ if friendship already exists

This could also just be a bug in the python code I'm using - maybe even something in urllib2 going wrong. Here is a bit of my code for reference, a function which makes an HTTP POST with a username & password. For an existing friendship, this will throw an exception printed out as: HTTP Error 40

[twitter-dev] Re: Tweet Corpus creation for NLP research

http://drop.io On Apr 17, 12:07 pm, Nick Arnett wrote: > Michele, djMax and anybody else interested...  It is a 128MB file after > gzipping (291MB uncompressed).  Any thoughts on a place to put it for > download?  I'm reluctant to sacrifice a lot of my own bandwidth for this and > off the top of

[twitter-dev] Re: Tweet Corpus creation for NLP research

Michele, djMax and anybody else interested... It is a 128MB file after gzipping (291MB uncompressed). Any thoughts on a place to put it for download? I'm reluctant to sacrifice a lot of my own bandwidth for this and off the top of my head, I can't think of a good place to share it. Nick

[twitter-dev] Re: 403 on valid request to friendships/create/ if friendship already exists

Hi all, We're not seeing the 403s in our normal logs but we've seen a few in responses. We're looking into the issue and I'll send out more info when I have it. — Matt On Apr 17, 2009, at 07:27 AM, Abraham Williams wrote: This seems to indicate it too. The 403 Forbidden HTTP status

[twitter-dev] Re: Getting Source Parameter in Java from XML returns "<"

On Thu, Apr 16, 2009 at 11:11 PM, Travis James wrote: > > Can anyone show me how I would parse this? > I am not exactly sure how I would go about doing this. Here is the > parsing code I have. > Why not just use the java-twitter API? http://code.google.com/p/java-twitter/ -steve

[twitter-dev] Re: API - getting info about user is blocked

http://code.google.com/p/twitter-api/issues/detail?id=9 On Fri, Apr 17, 2009 at 09:59, kkapron wrote: > > Hello, > > I'm developing a Twitter client application and I have a small > problem. > > In the Twitter API are methods for blocking and unblocking users, but > I can't use them in efficient

[twitter-dev] Getting HTTP 500 from statuses/followers using OAuth

I'm using the HTTP Authorization header to pass along the OAuth signature, and getting HTTP 500 errors back. I know that the signature is correct, because if I intentionally perturb the Authorization header I'm sending with junk, I get HTTP 401 responses saying "Failed to validate oauth sign

[twitter-dev] Re: Sign in with Twitter

It would be nice to support applications that merely authenticate, never authorize. That is, they don't ask for permission to access Twitter on the user's behalf. Such an application would never direct a user to /oauth/authorize, and thus would never get a token secret from the authorization flo

[twitter-dev] Re: Fail Whale

Will do Doug, thanks a lot for your help. Just to let you know, we're launching TweetPhoto on April 27th so our volume of API requests/calls is going to sky rocket from current levels. Thanks you for the support and help! Sean On Apr 7, 8:44 am, Doug Williams wrote: > Ouch. When you start to

[twitter-dev] API - getting info about user is blocked

Hello, I'm developing a Twitter client application and I have a small problem. In the Twitter API are methods for blocking and unblocking users, but I can't use them in efficient way because it's missing the method for checikng if a user is blocked by "me" (authorized user). I haven't found any

[twitter-dev] Re: OAuth and screen name

Hello again, Let me be more specific that my previous mails. This will be changing. Let me emphasize that: ⚠ The new authenticate method will be changing in a way that breaks the current behavior. At this point it is only a matter of time until I can get the new code reviewed an

[twitter-dev] Re: OAuth and screen name

On Fri, Apr 17, 2009 at 07:01, Dossy Shiobara wrote: > > On 4/17/09 2:51 AM, Abraham Williams wrote: > >> They correct flow is: >> 1) get request token from twitter. >> 2) send user to twitter with oauth_token for the first time. >> > > Send the user to Twitter how, though? oauth/authorize? How

[twitter-dev] Re: OAuth and screen name

I believe this flow is not secure (or not "as" secure) because that URL that is "transmitted" via the browser is permanently reusable by anyone to login to my service as that twitter user. In the authorization flow, I don't believe any such URL ever goes through the browser. So basically I think

[twitter-dev] Re: OAuth Authentication - clarification needed

This thread is kind of a dupe of http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a27298269b429a15 I'd suggest we move the convo over there? My last post in that thread describes why I think the current flow is not secure, which is essentially what Dossy says I think

[twitter-dev] Re: To link the @ or not to link the @, that is the question

I don't link the @ sign because 1) I don't like how it looks and 2) Twitter.com does not. On Fri, Apr 17, 2009 at 09:21, Chad Etzel wrote: > > A more lighthearted discussion to see where people stand on this > convention. > > We all know the convention of prefixing usernames with the @ symbol, >

[twitter-dev] Re: 403 on valid request to friendships/create/ if friendship already exists

This seems to indicate it too. The *403 Forbidden* HTTP status > code indicates > that the client was able to communicate with the server, but the server > doesn't let the user access

[twitter-dev] To link the @ or not to link the @, that is the question

A more lighthearted discussion to see where people stand on this convention. We all know the convention of prefixing usernames with the @ symbol, the interesting thing I notice is that different sites (and even within tiwtter's site itself) decide to link or not link the @ symbol along with it.

[twitter-dev] Re: OAuth Authentication - clarification needed

I think the thinking is, the first time a user authenticates using our app, we get the access token and it's up to us to persist the secret. Then we can use the authenticate approach, get back the user's token (it should be the same one we have), and then match it up to the access token paired to

[twitter-dev] Re: Sign in with Twitter

Hi all, This behavior (i.e. which token is returned) is likely to change soon. Once again, stay tuned for updates. — Matt On Apr 17, 2009, at 01:02 AM, Abraham Williams wrote: The oauth_token returned from oauth/authenticate is the key from the users access tokens. as long as you stor

[twitter-dev] Re: update_profile_image api issues

Hi Raghu, This issue [1] , like any other in Google Code can be 'starred' so you receive updates. Visit the issues in question [1], Sign in with your Google account, and then click on the star next to the title. When we update the issue you'll get an email. Thanks; — Matt Sanford /

[twitter-dev] Rate limit status's "remaining_hits" element scope

I just realized I don't know whether the remaining_hits element returned for /account/rate_limit_status is a static number from the beginning of the current hour, or if it is the remaining hits on a rolling sixty minute cycle. Does anyone know?

[twitter-dev] 403 on valid request to friendships/create/ if friendship already exists

Hi, Twitter returns a HTTP 403 if you make a properly authorized follow request to a user already followed. That seems like the wrong kind of response. It should return 200, with data saying the friendship already existed, no? Ivan http://tipjoy.com

[twitter-dev] Re: OAuth and screen name

On 4/17/09 2:51 AM, Abraham Williams wrote: They correct flow is: 1) get request token from twitter. 2) send user to twitter with oauth_token for the first time. Send the user to Twitter how, though? oauth/authorize? How do you know if this is the user's first time or not? 3) user return

[twitter-dev] Re: OAuth Authentication - clarification needed

On 4/16/09 10:56 PM, Dimebrain wrote: It should be no different than if you persisted the access token yourself and went to call the API a few weeks after doing so, you should be able to trust that your token won't expire. But this still leaves the question of "how do I get and/or know the to

[twitter-dev] Re: OAuth Authentication - clarification needed

On 4/16/09 9:46 PM, djMax wrote: That's where I'm confused:what do I do next? If I try to turn that OAuth Token into an access token, it fails, assumedly because it already is an auth token. Right, the oauth/authenticate returns the user to your callback URL with an AccessToken, not the orig

[twitter-dev] Re: Search API throwing 404's

Hi, I've experienced a few 404's on search.json this morning. Sometimes works, sometimes doesn't can't seem to pinpoint any particular pattern to it happening. -- Leu On Apr 17, 5:11 am, Chad Etzel wrote: > Just a quick update: > > The problem as popped up again. Doug is aware of this problem

[twitter-dev] Re: sending DM to all followers?

2009/4/17 Nicole Simon > On Fri, Apr 17, 2009 at 12:04 AM, Jesse Stay wrote: > > >> How do I switch off receiving DMs? I get DMs no matter what. I can turn >> off notifications, but not DMs. >> > > Twitter really has not a lot of options. If you do not know how to do that, > you obviously neve

[twitter-dev] Re: multiple tokens for the same user/application

On Thu, Apr 16, 2009 at 9:46 PM, Mario Menti wrote: > On Thu, Apr 16, 2009 at 8:17 PM, Doug Williams wrote: > >> Marlo, >> You should currently only have one working token per user per application. >> There is an open issue [1] that will allow multiple tokens per user per >> application. >> >> 1

[twitter-dev] Re: Sign in with Twitter

The oauth_token returned from oauth/authenticate is the key from the users access tokens. as long as you store the access tokens you can match the returned oauth_token with what is in your database. On Fri, Apr 17, 2009 at 01:35, John Kristian wrote: > > I'm having trouble using /oauth/authentic

[twitter-dev] Re: OAuth and screen name

It would make more sense to me, too, to use the same protocol flow for oauth/authorize and /authenticate. On Apr 16, 11:51 pm, Abraham Williams <4bra...@gmail.com> wrote: > It seems like it would make more sense to use the same work flow for both > oauth/authorize and oauth/authenticate. Then the

[twitter-dev] Re: Sign in with Twitter

I'm having trouble using /oauth/authenticate, too. After authenticating, Twitter redirects back to my consumer with a different oauth_token than the one I sent to initiate authentication. Twitter APIs don't accept either token. Sending the original request token to /oauth/access_token elicits H

[twitter-dev] Re: Sign in with Twitter

It just dawned on me: it looks like /oauth/authenticate is designed to merely deliver a user's ID and screen_name to a application, not to authorize the application to access Twitter on the user's behalf. Is that so? A suggestion: treat the user ID and screen_name as a resource that's protected