Re: [twitter-dev] Leveraging the Twitter API and scraping out tweets to only include tweets with links
(this will become easier once we can roll out entities into the XML/JSON payload) On Fri, May 14, 2010 at 5:21 AM, Abraham Williams 4bra...@gmail.com wrote: You could just do a check to see if the status contains a http:// or https://. You might miss a few that don't include the protocol but it would be a pretty small amount. Abraham On Thu, May 13, 2010 at 15:15, Mrs. Tillman katlen.till...@gmail.comwrote: I am working on a project for a client and I am looking into using the Twitter API to feed in tweets from those users who opt-in to have their twitter feed brought in. One thing that I wanted to do to customize the feed is to only show those tweets that have a link included. Does anyone have any details on how to do this and whether it's pretty straight-forward to do? I am not a developer. Thanks! -- 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. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Uploading to Media Services / OAuth
Hi Guys Whilst our desktop app has been desktop OAuth-based since launch, the media uploading has been username / password based (yfrog, twitpic etc). With basic auth going the way of the dodo next month, I just wanted to check to see what folks are doing for media uploads to services that use Twitter creds. Raffi's talked about the delegated OAuth etc, however I'm a little confused on the status of this new- fangled method - and whether it's something developers can work with right now. Apologies if this *has* been covered elsewhere, however I just wanted to bring this up and ask what the recommended method is for clients wanting to make sure things like yfrog / twitpic uploading continue to work. Cheers! Nik (@nikf)
[twitter-dev] Re: parsing out entities from tweets (a.k.a. parsing out hashtags is hard!)
Yes, this would be very cool. Any ideas on when this would be rolled out? 1) It would be nice to have the profile_image_url in it as well. I can imagine a lot of nice visual enhancements with that. 2) +1 for making it optional. A lot of people are suggesting additional stuff, so maybe it would even be nicer to not just have a include/don't include param, but to be able to specify which data you would like to have included... jarón On May 14, 6:29 am, Rich rhyl...@gmail.com wrote: +1 for it being optional as well. Whilst I will probably use it, it's nice to be able to keep the bandwidth download to a minimum for scenarios where it's not needed On May 14, 1:52 am, Naveen Ayyagari nav...@getsocialscope.com wrote: +1 on the additional parameter to optionally request the data. Every byte counts for mobile device battery life and download time. --Naveen Ayyagari @knight9 On May 13, 8:13 pm, Dewald Pretorius dpr...@gmail.com wrote: Raffi, This is all good, but can you please make the inclusion in the tweet payload optional? Meaning, only include it if it is requested by an additional parameter? I, and I'm sure a lot of others, are already parsing the tweet text. This is just going to consume additional bandwidth and not add any value for us. It will add value for folks who are not already doing the parsing or don't know how. So, they can just request this additional payload.
Re: [twitter-dev] Read/Unread field?
Love the idea - pretty hard to do. Want to doit. Not sure when :p On Friday, May 14, 2010, Adam v0id@gmail.com wrote: I'm not sure if this has been asked before, but I was wondering about the inclusion of a read/unread field included with a status. So many applications conduct their own methods of knowing whether a tweet has been read, but it would be really good if this could be unified on Twitter. I'm not completely sure how it would work, maybe have a new API function to set the read/unread status, and tweets seen on Twitter.com itself would never set this status, only applications would use this function. This is just an idea though, what do you think? -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Illegal XML is returned for user timeline
Very often illegal XML is returned by a call to http://api.twitter.com/1/statuses/user_timeline.rss . The value is twitter:source is not XML encoded. E.g. twitter:source a href=http://www.google.com/support/youtube/bin/answer.py? hl=enanswer=164577 rel=nofollowGoogle/a /twitter:source It should be twitter:source a href=http://www.google.com/support/youtube/bin/answer.py? hl=enamp;answer=164577 rel=nofollowGoogle/a /twitter:source
[twitter-dev] Re: Read/Unread field?
Wouldn't that be something for the upcoming Annotations? Ole -- Jan Ole Suhr s...@mobileways.de On Twitter: http://twitter.com/janole On 14 Mai, 12:45, Raffi Krikorian ra...@twitter.com wrote: Love the idea - pretty hard to do. Want to doit. Not sure when :p On Friday, May 14, 2010, Adam v0id@gmail.com wrote: I'm not sure if this has been asked before, but I was wondering about the inclusion of a read/unread field included with a status. So many applications conduct their own methods of knowing whether a tweet has been read, but it would be really good if this could be unified on Twitter. I'm not completely sure how it would work, maybe have a new API function to set the read/unread status, and tweets seen on Twitter.com itself would never set this status, only applications would use this function. This is just an idea though, what do you think? -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Search results limitation
Hi, I am developing an application where i want to get twitter updates (follow-ups, tweets etc.) based on keywords straightaway into my application. I am using twitter4j for that purpose. The problem is that the search results are quite outdated as compared to the ones gotten through twitter directly. Is it a restriction imposed by twitter? In case it is, if there is any other API to resolve the issue or some customization sort of paid service provide by twitter or whatever the solution can be. Please respond. Thanks Amit
[twitter-dev] Re: parsing out entities from tweets (a.k.a. parsing out hashtags is hard!)
+1 for making this optional. It's faster for mobile apps to do this themselves than download it. Besides, if this is the library used for web, you're not doing it right. :) For example, to mention URL parsing only, you don't check for valid domain names (e.g. www.test.failure is matched as URL), some characters are not recognized as part of a link (e.g. | in http://translate.google.com/?hl=en#auto|en|bonjour)...
[twitter-dev] How to address different groups of followers?
People, help me out with this one. I'm twitting about CATS and DOGS. I have followers who are interested about CATS or DOGS, but not both. How do I send my tweets about cats to only those followers who needs to know about cats, and send the dogs updates only to the subscribers interested in dogs? Creating two separate accounts is not preferable. Thanks!
Re: [twitter-dev] Re: parsing out entities from tweets (a.k.a. parsing out hashtags is hard!)
Besides, if this is the library used for web, you're not doing it right. :) For example, to mention URL parsing only, you don't check for valid domain names (e.g. www.test.failure is matched as URL), some characters are not recognized as part of a link (e.g. | in http://translate.google.com/?hl=en#auto|en|bonjour)... all we're trying to do is help people standardize on how they parse stuff. making sure you can represent what is a hash tag, a url, a username, etc., in the same way that twitter.com does it, can be difficult. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Read/Unread field?
annotations are immutable along with the tweet. you create annotations when you create a tweet, and they are stored with that tweet. On Fri, May 14, 2010 at 12:37 PM, janole s...@mobileways.de wrote: Wouldn't that be something for the upcoming Annotations? Ole -- Jan Ole Suhr s...@mobileways.de On Twitter: http://twitter.com/janole On 14 Mai, 12:45, Raffi Krikorian ra...@twitter.com wrote: Love the idea - pretty hard to do. Want to doit. Not sure when :p On Friday, May 14, 2010, Adam v0id@gmail.com wrote: I'm not sure if this has been asked before, but I was wondering about the inclusion of a read/unread field included with a status. So many applications conduct their own methods of knowing whether a tweet has been read, but it would be really good if this could be unified on Twitter. I'm not completely sure how it would work, maybe have a new API function to set the read/unread status, and tweets seen on Twitter.com itself would never set this status, only applications would use this function. This is just an idea though, what do you think? -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Search results limitation
Results from the Search API should be delayed only by a few seconds during normal operations. If there's some operational issue, search can get behind, but this should be fairly rare. The lowest latency API is the Streaming API. Results are often available here before they are published onto timelines, and generally before Search. But, we're talking by hundreds of milliseconds or low seconds. This shouldn't matter for most applications. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Thu, May 13, 2010 at 11:18 PM, Amit saksena...@gmail.com wrote: Hi, I am developing an application where i want to get twitter updates (follow-ups, tweets etc.) based on keywords straightaway into my application. I am using twitter4j for that purpose. The problem is that the search results are quite outdated as compared to the ones gotten through twitter directly. Is it a restriction imposed by twitter? In case it is, if there is any other API to resolve the issue or some customization sort of paid service provide by twitter or whatever the solution can be. Please respond. Thanks Amit
Re: [twitter-dev] Re: Read/Unread field?
Read-until is naturally stored with, or in relation-to, the User object. Due to temporary infrastructure limitations, that is database issues, it's not really feasible to add additional high-velocity columns on Users for a little while. Once this limitation is sorted out, the Platform team can do all sorts of interesting things. There's a whole team of folks dedicated to working on this infrastructure. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, May 14, 2010 at 5:48 AM, Raffi Krikorian ra...@twitter.com wrote: annotations are immutable along with the tweet. you create annotations when you create a tweet, and they are stored with that tweet. On Fri, May 14, 2010 at 12:37 PM, janole s...@mobileways.de wrote: Wouldn't that be something for the upcoming Annotations? Ole -- Jan Ole Suhr s...@mobileways.de On Twitter: http://twitter.com/janole On 14 Mai, 12:45, Raffi Krikorian ra...@twitter.com wrote: Love the idea - pretty hard to do. Want to doit. Not sure when :p On Friday, May 14, 2010, Adam v0id@gmail.com wrote: I'm not sure if this has been asked before, but I was wondering about the inclusion of a read/unread field included with a status. So many applications conduct their own methods of knowing whether a tweet has been read, but it would be really good if this could be unified on Twitter. I'm not completely sure how it would work, maybe have a new API function to set the read/unread status, and tweets seen on Twitter.com itself would never set this status, only applications would use this function. This is just an idea though, what do you think? -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: parsing out entities from tweets (a.k.a. parsing out hashtags is hard!)
I understand. And I don't have anything against it (even if it will be default), as long as it will be optional. And we're all appreciating the library (and its Java implementation: http://github.com/mzsanford/twitter-text-java). On May 14, 3:47 pm, Raffi Krikorian ra...@twitter.com wrote: all we're trying to do is help people standardize on how they parse stuff. making sure you can represent what is a hash tag, a url, a username, etc., in the same way that twitter.com does it, can be difficult. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Search results limitation
Use since and until parameters to specify the time period for which you would like to see the results. For each day you can retrieve a maximum of 1500 tweets per search term. On Fri, May 14, 2010 at 11:48 AM, Amit saksena...@gmail.com wrote: Hi, I am developing an application where i want to get twitter updates (follow-ups, tweets etc.) based on keywords straightaway into my application. I am using twitter4j for that purpose. The problem is that the search results are quite outdated as compared to the ones gotten through twitter directly. Is it a restriction imposed by twitter? In case it is, if there is any other API to resolve the issue or some customization sort of paid service provide by twitter or whatever the solution can be. Please respond. Thanks Amit
[twitter-dev] Re: parsing out entities from tweets (a.k.a. parsing out hashtags is hard!)
+1 for it being optional as well -- keep the bandwidth to a minimum for scenarios where it's not needed. +1 for having short URLs' original (long) URL provided (perhaps also an option?)
Re: [twitter-dev] Re: parsing out entities from tweets (a.k.a. parsing out hashtags is hard!)
Disambiguating short URLs and delivering the true URL and title would be a real plus, not just for developers, but for the target of a URL. While it does add a load to twitter's servers, it will save many, many useless hits to the target. Imagine 100,000 Twitter apps resolving each short URL found in a tweet. All of them doing it within seconds of the tweet arriving via the streaming API. It would be an automatic DOS against every site mentioned in a tweet. If this sounds hyperbolic, read the APIwiki docs that say 2,000 followers is an expected max. Ha! On Fri, May 14, 2010 at 9:15 AM, Zhami stu...@yellowhelium.com wrote: +1 for it being optional as well -- keep the bandwidth to a minimum for scenarios where it's not needed. +1 for having short URLs' original (long) URL provided (perhaps also an option?)
Re: [twitter-dev] Re: Read/Unread field?
Ahh I see. Yeah, didn't think about it like that. Thanks for the reply. Maybe in the future eh? Adam On Fri, May 14, 2010 at 9:54 PM, John Kalucki j...@twitter.com wrote: Read-until is naturally stored with, or in relation-to, the User object. Due to temporary infrastructure limitations, that is database issues, it's not really feasible to add additional high-velocity columns on Users for a little while. Once this limitation is sorted out, the Platform team can do all sorts of interesting things. There's a whole team of folks dedicated to working on this infrastructure. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, May 14, 2010 at 5:48 AM, Raffi Krikorian ra...@twitter.com wrote: annotations are immutable along with the tweet. you create annotations when you create a tweet, and they are stored with that tweet. On Fri, May 14, 2010 at 12:37 PM, janole s...@mobileways.de wrote: Wouldn't that be something for the upcoming Annotations? Ole -- Jan Ole Suhr s...@mobileways.de On Twitter: http://twitter.com/janole On 14 Mai, 12:45, Raffi Krikorian ra...@twitter.com wrote: Love the idea - pretty hard to do. Want to doit. Not sure when :p On Friday, May 14, 2010, Adam v0id@gmail.com wrote: I'm not sure if this has been asked before, but I was wondering about the inclusion of a read/unread field included with a status. So many applications conduct their own methods of knowing whether a tweet has been read, but it would be really good if this could be unified on Twitter. I'm not completely sure how it would work, maybe have a new API function to set the read/unread status, and tweets seen on Twitter.com itself would never set this status, only applications would use this function. This is just an idea though, what do you think? -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: parsing out entities from tweets (a.k.a. parsing out hashtags is hard!)
Raffi, A bit advanced request. Would it be possible to attach list of significant words and phrases present in the tweet. We could then use this info to categorize tweets and even build a trends list on the tweets aggregated by our apps. In one of our apps, we use Yahoo Terms Extraction service to extract phrases from tweets. Thanks, Karthik
Re: [twitter-dev] Searching date limitations
Hi Miles, You're right in that we don't go back very far with search right now. We want to improve that. There's no timeline right now, but it's certainly something we're looking at. There are so many tweets. We want you to have them all. Some day. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 13, 2010 at 6:34 PM, Miles Parker milespar...@gmail.com wrote: This is one of those questions where I'm pretty sure I know the answer, but I'd really like to be wrong. :) There doesn't seem to be anyway to get tweets past ~7 days. Which sort of makes me wonder what the point of the since and until params are -- for the usages where only being able to search back 7 days makes sense, it seems like you'd want more granularity. So my deeper question is whether this is simply a matter of not being able to *store* all of the data (seems highly unlikely) or just not being able to adequately *serve* that data through an open http interface? It would be really nice for research purposes to be able to have access to that data...
[twitter-dev] No oauth_verifier in custom URI (Desktop)
Hi, I am trying to use a callback URL with my desktop client. Twitter added twittia://oauth_token/ as my callback url but when I try to use it and open the http://twitter.com/oauth/authorize?oauth_token=mDu9cZQBVCm0yrZufUAKujduyIxl7OoFwAlEM3q7rg resource in the browser, the user authorizes the app and should be send back to the url: twittia://oauth_token/ But it never gets. If I look on the websites HTML code I just see: meta http-equiv=refresh content=0;url=twittia:///? oauth_token=DEZzXy9JBF5YtUdoUdQCPhHtVHiWHUUj6uaDBMLOE You see no oauth_verifier which I need to proceed. Does someone know what I am doing wrong? /Jeena
Re: [twitter-dev] No oauth_verifier in custom URI (Desktop)
Hi Jeena, I'll investigate this and let you know what I figure out. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, May 14, 2010 at 9:09 AM, Jeena jeenaparad...@gmail.com wrote: Hi, I am trying to use a callback URL with my desktop client. Twitter added twittia://oauth_token/ as my callback url but when I try to use it and open the http://twitter.com/oauth/authorize?oauth_token=mDu9cZQBVCm0yrZufUAKujduyIxl7OoFwAlEM3q7rg resource in the browser, the user authorizes the app and should be send back to the url: twittia://oauth_token/ But it never gets. If I look on the websites HTML code I just see: meta http-equiv=refresh content=0;url=twittia:///? oauth_token=DEZzXy9JBF5YtUdoUdQCPhHtVHiWHUUj6uaDBMLOE You see no oauth_verifier which I need to proceed. Does someone know what I am doing wrong? /Jeena
[twitter-dev] Errors on http://dev.twitter.com/doc
If this thread is a duplicate, feel free to point me to the correct thread. I found some documentation that isn't correct. On http://dev.twitter.com/doc/post/favorites/:id/create the documentation state that you should send a post to https://api.twitter.com/1/favorites/insert-id/create.json, but that doesn't work. If a call https://api.twitter.com/1/favorites/create/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/favorites/destroy the documentation state that you should send a post to https://api.twitter.com/1/favorites/destroy.json with the id as parameter, but that doesn't work. If a call https://api.twitter.com/1/favorites/destroy/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/saved_searches/destroy the documentation state that you should send a post to https://api.twitter.com/1/saved_searches/destroy.json with the id as parameter, but that doesn't work. If a call https://api.twitter.com/1/saved_searches/destroy/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/direct_messages/new there is a optional parameter called user. On all other methods this parameter is called id, which is very confusing.
[twitter-dev] Re: No oauth_verifier in custom URI (Desktop)
Ok great, looking forward to it. On May 14, 6:19 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Jeena, I'll investigate this and let you know what I figure out. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, May 14, 2010 at 9:09 AM, Jeena jeenaparad...@gmail.com wrote: Hi, I am trying to use a callback URL with my desktop client. Twitter added twittia://oauth_token/ as my callback url but when I try to use it and open the http://twitter.com/oauth/authorize?oauth_token=mDu9cZQBVCm0yrZufUAKuj... resource in the browser, the user authorizes the app and should be send back to the url: twittia://oauth_token/ But it never gets. If I look on the websites HTML code I just see: meta http-equiv=refresh content=0;url=twittia:///? oauth_token=DEZzXy9JBF5YtUdoUdQCPhHtVHiWHUUj6uaDBMLOE You see no oauth_verifier which I need to proceed. Does someone know what I am doing wrong? /Jeena
Re: [twitter-dev] Errors on http://dev.twitter.com/doc
Hi Tijs, I'm actually working on these errors now. It's more of a systematic thing than anything -- quirks. When in doubt, the API wiki is still up and running and can give clarity until the plumbing on this is fixed. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, May 14, 2010 at 9:17 AM, Tijs Verkoyen t...@verkoyen.eu wrote: If this thread is a duplicate, feel free to point me to the correct thread. I found some documentation that isn't correct. On http://dev.twitter.com/doc/post/favorites/:id/create the documentation state that you should send a post to https://api.twitter.com/1/favorites/insert-id/create.json, but that doesn't work. If a call https://api.twitter.com/1/favorites/create/ insert-id.json through POST it works. On http://dev.twitter.com/doc/post/favorites/destroy the documentation state that you should send a post to https://api.twitter.com/1/favorites/destroy.json with the id as parameter, but that doesn't work. If a call https://api.twitter.com/1/favorites/destroy/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/saved_searches/destroy the documentation state that you should send a post to https://api.twitter.com/1/saved_searches/destroy.json with the id as parameter, but that doesn't work. If a call https://api.twitter.com/1/saved_searches/destroy/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/direct_messages/new there is a optional parameter called user. On all other methods this parameter is called id, which is very confusing.
[twitter-dev] Re: oauth and embedded microcontrollers
Thanks. As I note, that is a non-trivial project/barrier. FWIW, I'm putting together a generic service for this application, where a user can oAuth to the site and then create proxy credentials that can be used to tweet etc. http://www.supertweet.net/ Feedback welcome. On May 12, 7:35 am, John Kalucki j...@twitter.com wrote: Why not have the controller proxy through a full-featured webserver that can oAuth in to Twitter? -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, May 12, 2010 at 2:03 AM, glenn gillen gl...@rubypond.com wrote: oAuth is a big burden for microcontroller based devices like this - OAuthcalypse will probably simply kill this app. It seems like way too much overhead to push oAuth code into this little chip. oAuth alone would probably exceed all the rest of the application code on the device combined. I couldn't find anything on the blog or the related sites given examples of the code being used to run this GarageBot other than it was running on uClinux. What code/libraries (if any) are you presently using to connect to the API? The curl guys are working on building oauth support direct into curl, so that should provide a fallback for these kind of apps. You could probably use curl now provided you had a way of generating the oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). If you could divulge a little more about your setup, and what kind of constraints you have to work within, we might be lucky enough to have someone in this group that can think of a solution. -- Glenn Gillen http://glenngillen.com/
[twitter-dev] Re: oauth and embedded microcontrollers
Hi Glenn, FWIW, the application and platform is extremely small and lightweight - there is nothing as powerful or huge as 'curl' there. It is all raw C code, stripped down libraries, etc. measured in K-bytes, not Megabytes, to say nothing of Gigabytes. For example, the current 'tweet' code binary is 18K bytes. If you can add oAuth in 100K bytes or less, that might work, but that one function would then still be bigger than the entire rest of the application. In fact, the entire file system ROM image, with all the binaries and data is 114K bytes. On May 12, 2:03 am, glenn gillen gl...@rubypond.com wrote: oAuth is a big burden for microcontroller based devices like this - OAuthcalypse will probably simply kill this app. It seems like way too much overhead to push oAuth code into this little chip. oAuth alone would probably exceed all the rest of the application code on the device combined. I couldn't find anything on the blog or the related sites given examples of the code being used to run this GarageBot other than it was running on uClinux. What code/libraries (if any) are you presently using to connect to the API? The curl guys are working on building oauth support direct into curl, so that should provide a fallback for these kind of apps. You could probably use curl now provided you had a way of generating the oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). If you could divulge a little more about your setup, and what kind of constraints you have to work within, we might be lucky enough to have someone in this group that can think of a solution. -- Glenn Gillenhttp://glenngillen.com/
[twitter-dev] Re: Issues getting started with xAuth
SOLVED!
The moral of the story is to keep your nonce values SIMPLE.
We were generating a random value:
Base64.encode('1:' + counter++ + ':' + random + Date.now());
which most of the time resulted in a string that contained an equals
sign character, which then gets urlencoded to %3D.
It appears the % character was confusing the server and so we kept
getting 401s.
Our solution is to make a simpler, non-Base64-encoded nonce. NO
PERCENTS!!! And all is now well.
-dwf
On May 12, 3:30 pm, DWF dwfr...@pivotallabs.com wrote:
Taylor: Here's what we're sending now. The signature looks like the
correct length. But we're getting the same error.
POST /oauth/access_token HTTP/1.1
Host: api.twitter.com
Authorization: OAuth oauth_signature_method=HMAC-SHA1,
oauth_nonce=MToxOjQyOTY0NzEyNzM3MDMzMzQwMTU%3D,
oauth_timestamp=1273703334,
oauth_consumer_key=WFKpuxJsIdVbesPtUAN6w, oauth_version=1.0,
oauth_signature=NU%2BLWGJ7lDm2DmPYKkT8P45YsZA%3D
Accept: application/json
Content-Length: 93
Content-Type: application/x-www-form-urlencoded
x%5Fauth%5Fusername=Xx%5Fauth%5Fpassword=Xx%5Fauth
%5Fmode=client%5Fauth
HTTP/1.1 401 Unauthorized
Date: Wed, 12 May 2010 22:29:11 GMT
Server: hi
Status: 401 Unauthorized
X-Transaction: 1273703351-32476-1016
Last-Modified: Wed, 12 May 2010 22:29:11 GMT
X-Runtime: 0.01211
Content-Type: text/html; charset=utf-8
Content-Length: 44
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=74.207.226.80.1273703350241947; path=/; expires=Wed, 19-
May-10 22:29:10 GMT; domain=.twitter.com
Set-Cookie: guest_id=127370335144417010; path=/; expires=Fri, 11 Jun
2010 22:29:11 GMT
Set-Cookie:
_twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCJXEoo4oAToRdHJhbnNfcHJvbXB0MDoHaWQi
%250AJWUwNmRiODNlMDlmY2FhNzk3YTE1YWNlODFiMzllZDVjIgpmbGFzaElDOidB
%250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
a76c125e0d8422759ab95667e37db1decdc56861; domain=.twitter.com; path=/
Vary: Accept-Encoding
Connection: close
Failed to validate oauth signature and token
On May 12, 2:56 pm,DWFdwfr...@pivotallabs.com wrote:
It turns out that we have a base64 encoding problem, which means our
signature actually is bad.
Working on it now.
--dwf
On May 12, 1:06 pm,DWFdwfr...@pivotallabs.com wrote:
We just coded up a simple Ruby script to make the same request,
building our post body by hand into a string to ensure the escaping
(or not) of the params.
So we know that going into Net::HTTP the underscores are underscores
and NOT %5F's.
Same response from the server.
--dwf
On May 12, 11:14 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Just eyeballing this: your POST body is over-URL encoded. Your POST body
should be simply:
x_auth_username=Xx_auth_password=Xx_auth_mode=client_auth
But the values of each key should be URL escaped (so if there's an email
address, username, or password with non-URL safe characters, they would
be
URL encoded -- and double URL encoded in your signature base string)
Otherwise, at first glance anyway, this looks pretty close to right.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, May 12, 2010 at 10:58 AM,DWFdwfr...@pivotallabs.com wrote:
We're trying this out now think we're approved. But we're still
seeing 401s when requesting a user token.
(username password hidden with XX below)
Here's our base string:
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_tokenoauth_consumer_key%3DWFKpuxJsIdVbesPtUAN6w
%26oauth_nonce%3DMTowOjk1NDE2ODEyNzM2ODY1OTM4Mjc%3D
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1273686593%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
%26x_auth_password%3DX%26x_auth_username%3DX
Here's our POST (using hurl.it as it looks like twurl doesn't support
this API endpoint yet):
-
POST /oauth/access_token HTTP/1.1
Host: api.twitter.com
Authorization: OAuth oauth_signature_method=HMAC-SHA1,
oauth_nonce=MToxOjEyMzcxNzEyNzM2ODY1OTM4Mjc%3D,
oauth_timestamp=1273686593,
oauth_consumer_key=WFKpuxJsIdVbesPtUAN6w, oauth_version=1.0,
oauth_signature=4f23193590c2b66c5ea23ce5deae9c767998a902
Accept: application/json
Content-Length: 93
Content-Type: application/x-www-form-urlencoded
x%5Fauth%5Fusername=Xx%5Fauth%5Fpassword=Xx%5Fauth
%5Fmode=client%5Fauth
-
And we're getting this response (sad panda):
-
HTTP/1.1 401 Unauthorized
Date: Wed, 12 May 2010 17:52:11 GMT
Server: hi
Status: 401 Unauthorized
X-Transaction: 1273686731-92894-17698
Last-Modified: Wed, 12 May 2010 17:52:11 GMT
X-Runtime: 0.03752
Content-Type: text/html; charset=utf-8
RE: [twitter-dev] Re: oauth and embedded microcontrollers
Mr Blog wrote: For example, the current 'tweet' code binary is 18K bytes. If you can add oAuth in 100K bytes or less, that might work, but that one function would then still be bigger than the entire rest of the application. In fact, the entire file system ROM image, with all the binaries and data is 114K bytes. How large is your TLS stack and root CA certificate database? Regards, Brian
[twitter-dev] need Screen Name of person doing a retweet from statuses/retweets_of_me not originating tweeter
I have an application that executes the statuses/retweets_of_me.format api method. The call works just fine and my app receives the retweets. But the user section of the statuses returned contains the original tweeter not of the user that posted the retweet. I can use the status id in another call to the api to get the user object. but if there are multiple retweets that increases the number of calls to the API almost exponentially. I have tried sending a comma delimited list of status ids to the api call, statuses/id/retweeted_by_id.format, and that does return a list of users. However there may or not be the retweet status id in the user object to know what user goes with what retweet status id. I know that the twitter user interface does provide the retweeter id in the retweets of me display. But the api does not appear to have that call available. The status/mentions.format does have the user that posted the mention. So my question is has anybody had this problem? if so what have you done to resolve it?
[twitter-dev] Unexpected search results from search.twitter.com and API
Hello, I have seen this a few times in the last couple of days and did not see it mentioned on the list. If it is a duplicate report I apologize. A simple search is on a keyword, the first result does not contain the keyword at all, here is a screen shot displaying the behavior on search.twitter.com website. http://dl.dropbox.com/u/27113/search_wierdness.jpg I have seen this strange behavior via the api as well and it is a bit confusing. --Naveen Ayyagari SocialScope @knight9
Re: [twitter-dev] Unexpected search results from search.twitter.com and API
Naveen, I saw a case with one of my searches this morning where a bit.ly url appeared to have been expanded before Twitter Search matched on the tweet. Tim Haines said this morning on Twitter he had seen something similar. So, for the first tweet: $ curl -I http://bit.ly/cMsa7U; HTTP/1.1 301 Moved Server: nginx/0.7.42 Date: Fri, 14 May 2010 20:32:14 GMT Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: _bit=4bedb34e-00080-050e7-b4a08fa8;domain=.bit.ly;expires=Wed Nov 10 15:32:14 2010;path=/; HttpOnly Location: http://feedproxy.google.com/~r/TheBoyGeniusReport/~3/95JeYV6zcMk/?utm_source=SocialScopeutm_medium=SocialScopeutm_campaign=SocialScopeutm_term=SocialScopeutm_content=SocialScope MIME-Version: 1.0 Content-Length: 443 The expanded bit.ly link contains 'SocialScope'. -damon -- http://twitter.com/damon http://blog.damonc.com On Fri, May 14, 2010 at 3:14 PM, Naveen Ayyagari nav...@getsocialscope.com wrote: Hello, I have seen this a few times in the last couple of days and did not see it mentioned on the list. If it is a duplicate report I apologize. A simple search is on a keyword, the first result does not contain the keyword at all, here is a screen shot displaying the behavior on search.twitter.com website. http://dl.dropbox.com/u/27113/search_wierdness.jpg I have seen this strange behavior via the api as well and it is a bit confusing. --Naveen Ayyagari SocialScope @knight9
[twitter-dev] Getting 401 when using one access token with OAuth
I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hess http://www.getharvest.com
[twitter-dev] Re: Announcing Twurl: OAuth-enabled curl for the Twitter API
On May 15, 12:41 am, kuhkatz kuhk...@googlemail.com wrote: so i suppose i am doing things wrong. i followed your instructions, but when i apply the diff, i get this: $ patch -i twurldiff Close. You can do either one of patch -p 1 -i twurldiff or git apply twurldiff Faried.
[twitter-dev] Re: Unexpected search results from search.twitter.com and API
Yes, we do match parts of the expanded URL on searches. That currently includes query parameters, but we'll be removing that soon. On May 14, 1:35 pm, Damon Clinkscales sca...@pobox.com wrote: Naveen, I saw a case with one of my searches this morning where a bit.ly url appeared to have been expanded before Twitter Search matched on the tweet. Tim Haines said this morning on Twitter he had seen something similar. So, for the first tweet: $ curl -I http://bit.ly/cMsa7U; HTTP/1.1 301 Moved Server: nginx/0.7.42 Date: Fri, 14 May 2010 20:32:14 GMT Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: _bit=4bedb34e-00080-050e7-b4a08fa8;domain=.bit.ly;expires=Wed Nov 10 15:32:14 2010;path=/; HttpOnly Location:http://feedproxy.google.com/~r/TheBoyGeniusReport/~3/95JeYV6zcMk/?utm... MIME-Version: 1.0 Content-Length: 443 The expanded bit.ly link contains 'SocialScope'. -damon --http://twitter.com/damonhttp://blog.damonc.com On Fri, May 14, 2010 at 3:14 PM, Naveen Ayyagari nav...@getsocialscope.com wrote: Hello, I have seen this a few times in the last couple of days and did not see it mentioned on the list. If it is a duplicate report I apologize. A simple search is on a keyword, the first result does not contain the keyword at all, here is a screen shot displaying the behavior on search.twitter.com website. http://dl.dropbox.com/u/27113/search_wierdness.jpg I have seen this strange behavior via the api as well and it is a bit confusing. --Naveen Ayyagari SocialScope @knight9
[twitter-dev] Doc Bug: statuses/mentions claims to NOT require authentication, but it does
http://dev.twitter.com/doc/get/statuses/mentions This API doesn't take a parameter for a username so it's only available via an auth call. We tried to hit http://api.twitter.com/1/statuses/mentions.json via Hurl.it and got a 401. Which means that the doc is wrong wrt auth URL. --dwf
[twitter-dev] Twitter detection in the client
Hello, I am implementing an auto login feature in my web application. What I want to do is detect the presence of twitter. If it is present (open) then I want to do an auto-login which will send a callback to my server to initiate the login. What I want to know is: How can I detect the presence of the twitter app in my browser so that I can initiate the auto login process? I believe that this would have to be done via cookies as I cannot get the apps via normal browser resources such as Window object, etc. Any help would be appreciated. Regards.
[twitter-dev] Problem with status encoding... I guess
I have an app using OAuth (actaully xAuth) and it is working well... or almost well. I had a few bugs with encoding, I was not using UTF8 and now I do, so I am able to tweet stauff like Peñarol á é í ó ú (spanish lang characters). I was making some tests and I noticed that if I want to set '!' as my status (just the exclamation mark) it dos not work... I get an Incorrect signature error message. I tried moving stuff around but my actual config works in most cases. I can even twit 'é' as my status and it works! :S Can anybody point me in the right direction... most samples I've seen online don't care about UTF8 encoding, probably because most of them are built in the US :( Thanks. Regards, Seba
[twitter-dev] Oauth not redirecting back to site
We've been running Oauth Twitter redirect to our site for months now (www.society.me). All of the sudden the sign in page won't redirect back to our URL. It works with a different product we offer (different domain). Has anyone else seen this bug? The app works fine otherwise (people who signed in before this problem can still publish via our app, etc.) but no new users can sign in because the redirect is broken. Thanks, Leonard
Re: [twitter-dev] Oauth not redirecting back to site
Hi Leonard, Are you explicitly setting your oauth_callback in the request_token step or are you relying on a callback pre-registered in your application record on Twitter? In either case, what's the value set to when it fails? What happens on the failed redirect? We haven't changed code in this area for awhile, so it's a curious case. Thanks, Taylor On Friday, May 14, 2010, Leonard Speiser speiser2...@gmail.com wrote: We've been running Oauth Twitter redirect to our site for months now (www.society.me). All of the sudden the sign in page won't redirect back to our URL. It works with a different product we offer (different domain). Has anyone else seen this bug? The app works fine otherwise (people who signed in before this problem can still publish via our app, etc.) but no new users can sign in because the redirect is broken. Thanks, Leonard -- Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
Re: [twitter-dev] Doc Bug: statuses/mentions claims to NOT require authentication, but it does
Will fix, thanks. On Friday, May 14, 2010, DWF dwfr...@pivotallabs.com wrote: http://dev.twitter.com/doc/get/statuses/mentions This API doesn't take a parameter for a username so it's only available via an auth call. We tried to hit http://api.twitter.com/1/statuses/mentions.json via Hurl.it and got a 401. Which means that the doc is wrong wrt auth URL. --dwf -- Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] alert() in anywhere.js
I just came across a coworker's browser that triggered an alert() call from anywhere.js. While okay for development, the use of alert() is not friendly for production websites. Could these be converted console.log() or some other benign mechanism? Grepping through anywhere.js I found two instances of alert(): alert(To set up @anywhere, please provide a client ID); alert(No version matching +Z); Cheers Larry
Re: [twitter-dev] alert() in anywhere.js
Both of which are issues that will pretty much stop @Anywhere from working and need to be noticed as soon as possible at installation. Hiding them in console.log will make it more likely that @Anywhere will be installe improperly and the admins will only find out when users complain. Abraham On Fri, May 14, 2010 at 15:57, Larry la...@topsy.com wrote: I just came across a coworker's browser that triggered an alert() call from anywhere.js. While okay for development, the use of alert() is not friendly for production websites. Could these be converted console.log() or some other benign mechanism? Grepping through anywhere.js I found two instances of alert(): alert(To set up @anywhere, please provide a client ID); alert(No version matching +Z); Cheers Larry -- 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] Problem with status encoding... I guess
I'm working on a Japanese twitter app and have had similar challenges with encoding (i.e. the OAuth lib I used didnt support Japanese). I'll have a bit of a look and see if I have the same ! problem as you and let you know. Adam On Sat, May 15, 2010 at 7:22 AM, @sebagomez sebastiangomezcor...@gmail.comwrote: I have an app using OAuth (actaully xAuth) and it is working well... or almost well. I had a few bugs with encoding, I was not using UTF8 and now I do, so I am able to tweet stauff like Peñarol á é í ó ú (spanish lang characters). I was making some tests and I noticed that if I want to set '!' as my status (just the exclamation mark) it dos not work... I get an Incorrect signature error message. I tried moving stuff around but my actual config works in most cases. I can even twit 'é' as my status and it works! :S Can anybody point me in the right direction... most samples I've seen online don't care about UTF8 encoding, probably because most of them are built in the US :( Thanks. Regards, Seba
Re: [twitter-dev] Re: Announcing Twurl: OAuth-enabled curl for the Twitter API
Hi, Faried - I tried it too, since I have Linux 10.04, and it also has a problem at the patching part, even provided your two ways to execute the diff. I'm also new to Ruby stuff. $ patch -i twurldiff patching file Rakefile Hunk #1 FAILED at 2. Hunk #2 FAILED at 69. 2 out of 2 hunks FAILED -- saving rejects to file Rakefile.rej patching file lib/twurl.rb Hunk #1 FAILED at 4. 1 out of 1 hunk FAILED -- saving rejects to file lib/twurl.rb.rej patching file test/rcfile_test.rb Hunk #1 FAILED at 138. 1 out of 1 hunk FAILED -- saving rejects to file test/rcfile_test.rb.rej Just feedback. Patrick On Sat, May 15, 2010 at 4:40 AM, Faried Nawaz far...@gmail.com wrote: On May 15, 12:41 am, kuhkatz kuhk...@googlemail.com wrote: so i suppose i am doing things wrong. i followed your instructions, but when i apply the diff, i get this: $ patch -i twurldiff Close. You can do either one of patch -p 1 -i twurldiff or git apply twurldiff Faried.
