[twitter-dev] Twitter Basic Authentication
Hi, We are using basic authentication API method in our application (Which is already in appstore)for twitter login and for sharing the text...whether it will work fine after june 30th or we must have to give new update with oAuth API ...please give us guidance to resolve this issue..
Re: [twitter-dev] Twitter Basic Authentication
You must have the new oAuth API in place or your app with no longer work.. Twitter has given the drop-dead date for removal of the Basic Auth privileges for EVERYONE as June 30th. Sorry Jann On May 30, 2010, at 10:41 PM, Sakthi wrote: Hi, We are using basic authentication API method in our application (Which is already in appstore)for twitter login and for sharing the text...whether it will work fine after june 30th or we must have to give new update with oAuth API ...please give us guidance to resolve this issue..
Re: [twitter-dev] Annotations Hackfest wiki page
For those who could not make it to the Twitter office I snipped the introduction from the start and the demoes from the end: http://blog.abrah.am/2010/05/twitter-annotations-hackfest-highlights.html Abraham On Sat, May 29, 2010 at 12:32, Ryan Sarver rsar...@twitter.com wrote: Here is the page that we'll use to coordinate everything this weekend. Let us know if you have any questions. https://apiwiki.twitter.com/Annotations-Hackfest-May-25th Best, rs -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Uploading videos to Twitter using OAuth
Assuming you've already got the code for oauth itself working there isn't much more you need to do When you create an oauth request you are adding an Authorization header to the HTTP request that contains your oauth signatures. For oauth echo you need to generate that header as if you are making a GET request to Twitters verify_credentials endpoint. But instead of adding it to the Authorisation header, you add it to the x-verify- credentials-authorisation header and send it to twitted Howeveri think twitvids docs are wrong and you have to use hyphens instead of underscores On May 31, 4:51 am, Deepa deepapai0...@gmail.com wrote: Thanks for the reply. I am new to TwitVid APIs. I have gone through the documentation of TwitVid APIs and OAuth Echo. But, I could not understand the concept of x_verify_credentials_authorization as alternate for User name and password parameters. Also, could you please help me out in explaining how to get value of the parameter x_verify_credentials_authorization i.e OAuth Echo Authorization header. Is there any call in TwitVid library that allows to set the value of the parameter 'x_verify_credentials_authorization'? Thanks in advance. On May 29, 11:16 pm, Abraham Williams 4bra...@gmail.com wrote: x_verify_credentials_authorization: Required if no username/password sent. OAuth Echo Authorization header. Abraham On Sat, May 29, 2010 at 10:42, Deepa deepapai0...@gmail.com wrote: On May 29, 3:53 am, Abraham Williams 4bra...@gmail.com wrote: Twitvid supports OAuth Echo:http://twitvid.pbworks.com/authenticate But, according to thisocumentation the authentication mechanism needs user-name and password. But I cannot get the password. Because, I am using OAuth for authentication in which user is redirected to the web- page for entering user-name and password. I have used OAuth since Twitter is removing the of authentication mechanism which passes user- name and password as arguments. Thanks and regards, Deepa More info on Echo: http://mehack.com/oauth-echo-delegation-in-identity-verificatiohttp:/... You will have to ask Twitvid if their iPhone library supports Echo. Abraham On Fri, May 28, 2010 at 06:23, Deepa deepapai0...@gmail.com wrote: Hi, I am developing an iPhone app that uses Twitvid library for uploading videos to TwitVid. This library first authenticates the app using the user-name and password input parameters. Then it uploads the video. But, recently I switched to OAuth mechanism of authentication which leads to a web-page where user can enter the user-name and password. So, I cannot provide the input fields for user-name and password in my app for uploading video. Can someone help me out to solve this problem. Thanks and Regards, Deepa -- 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. -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: How long does it take to get approved with xAuth?
I consider it completely the opposite and that the oauth workflow is
more secure than the xauth one. To me seeing the Twitter website login
page shows me that only Twitter will see my login information and not
the client app itself
An xauth workflow the app should only pass it on in exchange for an
oauth token but there is nothing to stop them harvesting the
information in the meantime
Running the oauth workflow on the iPhone is not painful and can all be
done seamlessly from within your app itself. The user won't ben
confused either if you do it right
On May 30, 6:15 pm, Jann Gobble janngob...@gmail.com wrote:
Okay, please tell me you know that I can create an app with a UIWebView that
will take that password you type in faster than anything.
It is NOT secure. This is my problem with oAuth. The work-arounds cause a
false sense of security. oAuth was NEVER supposed to be used this way. If
the user does not trust the app, they should definitely not trust the
developer that puts a UIWebView in it -- it is too easy to do a
man-in-the-middle. oAuth fits in well with webapps, not iPhone apps.
Anyway, this was all hashed out internally to Twitter -- that is why they
came up with xAuth.
:)
Jann
On May 30, 2010, at 3:50 AM, Rich wrote:
You don't have to go from app to browser, embed a UIWebView and then
in
- (BOOL)webView:(UIWebView *)webView shouldStartLoadWithRequest:
(NSURLRequest *)request navigationType:
(UIWebViewNavigationType)navigationType {
Look for your callback URL and read the query string and you'll be
authorised, then just remove the UIWebView and use your application.
The user never has to leave your app.
Then the user gets MORE security that xAuth because they can see they
are logging in on Twitter.com and not giving their password to an
arbitrary application, which could still save their password without
their knowledge.
On May 30, 8:35 am, Jann Gobble janngob...@gmail.com wrote:
The requirement for users to go from app to browser to app is untenable
for many of my users. It is a major change to go from app to Safari and
back to app. Many users actually think that it the app is less secure
(rightly or wrongly) because they have to exit it -- and go to the web --
in order to login.
Indeed, many of them do not understand the permissions that the oAuth
system asks for when they get sent to the Twitter page. Unfortunately
with a phone like the iPhone you are dealing with many many users who are
new to mobile devices in general and just wish to use twitter from within
their favorite apps without the complications.
Would you say that oAuth is good enough for Twitterific or Chirpie,
Tweetie? Well, they are using xAuth. All I wish to do is to provide my
users with identical (and what they see is easy -- and safe) method of
using Twitter. xAuth provides this. oAuth does not. Many users prefer a
seamless experience to that of adopting a protocol that causes such a
jarring user experience -- regardless of the perceived safety of oAuth
over xAuth. Safety of one over the other comes down to how much you trust
the app. It no longer comes down to how much you trust Basic Auth.
I would have no problem if there was an even playing field where we could
all have our app signatures in the Tweet -- and all have the same user
experience where logins and permissions are concerned. This is not the
case.
Thanks for your input, though.
Jann
On May 30, 2010, at 12:03 AM, Rich wrote:
You don't need xAuth to develop an iPhone app, oAuth workflow works
just fine.
Indeed I though xAuth was designed for clients without a decent mobile
browser which isn't the case on the iPhone
On May 29, 2:08 am, Jann janngob...@gmail.com wrote:
I sent an email in to api@ this week. Got back a case # which, when
clicked, requires me to login. It then tells me that the case
#1008949does not exist.
So, I logged in under the twitter account that created the app and
created another ticket. Got another ticket #1009859. I am now
wondering how long this is supposed to take. (if the first one is
invalid, then my new support case is now over 900 cases farther down
in the queue. :(
Does anyone have any ideas? I have seen (when searching on google)
that some people say it takes upwards of a week to get the approval.
I am stuck however because I cannot even test my iPhone app using this
method. (I am usinghttp://aralbalkan.com/3133(xAuthTwitterEngine) to
implement and I can see no method to begin even testing using my own
account.
Shouldn't there be some way to (at least) test your app using the
username and password that was used to create the Application in
question?
Please give some insight. Maybe I am missing something stupid.
Thanks!
Jann
[twitter-dev] Re: Clock Ticking on Basic Authpocalypse
I posted such a list a week or so back I have successfully integrated: Twitpic Yfrog (they only allow the XML version of verify_credentials rather than json) Twitgoo Mobypicture Twitvid I believe pikchur also supports it but I haven't had the chance to test it yet On May 31, 1:30 am, Ron meerkat...@gmail.com wrote: With the clock ticking on Basic Authpocalypse (T-30 days and counting), what is the state of media hosting providers with regards to OAuth Echo compliance? Those of us developing mobile client apps need about two weeks to get our revised apps through the relevant approval processes, so we're down to about two weeks left before needing to submit something or risk our apps not working anymore. I have successfully tested with TwitPic and yFrog, but both seem to have lost Upload Post functionality when moving to OAuth Echo. Img.ly said they're still working on their implementation. Posterous is still a ? Can anyone share a list of providers ready to begin testing their new OAuth Echo functionality, along with a heads-up about any lost functionality resulting from the move? It's becoming increasingly important to find out who's going to be on the playing field with what functionality so we can revise our apps accordingly in advance of the approaching deadline.
[twitter-dev] Re: Clock Ticking on Basic Authpocalypse
Thanks for the reply. Yes, I did see your earlier post. I was hoping someone from Twitter would have greater insight into which media hosting services they were working with (assuming Twitter would most likely be involved at a corporate level with these other companies), and what features may be lost in the conversion. As I mentioned, I have already tested TwitPic and yFrog. But both no longer support Upload Post. Do the others you mentioned also lose that functionality? Img.ly is supposedly in the works. Is anything going on with Posterous? Is the loss of Upload Post a systemic OAuth issue for the time being? It's not easy for some of us to submit app revisions in rapid succession, and not including functionality in the first place is always better than taking it away later. Any help anyone can provide to help us get it (more right) the first time would be deeply appreciated by all. On May 31, 4:54 am, Rich rhyl...@gmail.com wrote: I posted such a list a week or so back I have successfully integrated: Twitpic Yfrog (they only allow the XML version of verify_credentials rather than json) Twitgoo Mobypicture Twitvid I believe pikchur also supports it but I haven't had the chance to test it yet On May 31, 1:30 am, Ron meerkat...@gmail.com wrote: With the clock ticking on Basic Authpocalypse (T-30 days and counting), what is the state of media hosting providers with regards to OAuth Echo compliance? Those of us developing mobile client apps need about two weeks to get our revised apps through the relevant approval processes, so we're down to about two weeks left before needing to submit something or risk our apps not working anymore. I have successfully tested with TwitPic and yFrog, but both seem to have lost Upload Post functionality when moving to OAuth Echo. Img.ly said they're still working on their implementation. Posterous is still a ? Can anyone share a list of providers ready to begin testing their new OAuth Echo functionality, along with a heads-up about any lost functionality resulting from the move? It's becoming increasingly important to find out who's going to be on the playing field with what functionality so we can revise our apps accordingly in advance of the approaching deadline.
[twitter-dev] Twitter API - Grab profile pic URL
Hey Guys, I am having trouble trying to grab my Profile Pic URL via the API. I am trying to grab it using the following path - http://twitter.com/statuses/user_timeline.xml?id=username but it returns the default profile picture (http://s.twimg.com/a/1274899949/ images/default_profile_2_normal.png) and not the custom profile pic which is displayed on my twitter homepage. Any ideas? Bruce
Re: [twitter-dev] Twitter API - Grab profile pic URL
Try using http://twitter.com/users/show/your user id or screen name.xml instead. The user objects in user_timeline may be stale. ---Mark http://twitter.com/mccv On Mon, May 31, 2010 at 4:40 AM, Bruce bruce...@gmail.com wrote: Hey Guys, I am having trouble trying to grab my Profile Pic URL via the API. I am trying to grab it using the following path - http://twitter.com/statuses/user_timeline.xml?id=username but it returns the default profile picture (http://s.twimg.com/a/1274899949/ images/default_profile_2_normal.png) and not the custom profile pic which is displayed on my twitter homepage. Any ideas? Bruce
Re: [twitter-dev] Re: How long does it take to get approved with xAuth?
On May 31, 2010, at 9:25 AM, Bernd Stramm wrote: In any case Jann, you have convinced me of something I strongly suspected - I really should get xauth for my application as well. If I have convinced one person today, I have done my job. I am used to that -- what with being a Mac user for decades. grin Be safe, You too! Jann
Re: [twitter-dev] Twitter API - Grab profile pic URL
There is also https://api.twitter.com/1/users/profile_image/abraham. Abraham On Mon, May 31, 2010 at 07:45, Mark McBride mmcbr...@twitter.com wrote: Even better, use http://api.twitter.com/1/users/show/your user id or screen name.xml. Using http://twitter.com for API calls is frowned upon these days. ---Mark http://twitter.com/mccv On Mon, May 31, 2010 at 7:45 AM, Mark McBride mmcbr...@twitter.com wrote: Try using http://twitter.com/users/show/your user id or screen name.xml instead. The user objects in user_timeline may be stale. ---Mark http://twitter.com/mccv On Mon, May 31, 2010 at 4:40 AM, Bruce bruce...@gmail.com wrote: Hey Guys, I am having trouble trying to grab my Profile Pic URL via the API. I am trying to grab it using the following path - http://twitter.com/statuses/user_timeline.xml?id=username but it returns the default profile picture (http://s.twimg.com/a/1274899949/ images/default_profile_2_normal.png) and not the custom profile pic which is displayed on my twitter homepage. Any ideas? Bruce -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: @Anywhere - Login - Custom HTML Button instead of Connect With Twitter
Hi, try connectButton(). Here is an exemplo: http://dev.twitter.com/anywhere/begin#auth-events On 31 maio, 02:33, smaira sameerma...@gmail.com wrote: Hi, I have made a similar post about this here : http://groups.google.com/group/twitter-development-talk/browse_thread... but I accidentally reported my own message as spam. (stupid, I know!) Anyway, here's the gist of what I'm trying to achieve. I basically need a way to render a custom html button instead of the Connect with Twitter button and make it work the same way. I'm not sure what Javascript call to make onclick() The @Anywhere docs mention a call to a Javascript function to Logout/ Signout from Twitter. button type=button onclick=twttr.anywhere.signOut();Sign out of Twitter/button Is there anything similar to sign in ? I've tried twttr.anywhere.signIn() , login() , signOn() Nothing works!
[twitter-dev] Haughin library and update_profile
Hey,
I'm developing a web application using the Haughin library. It works
quite cool.
Now I was trying to update the user profile: name, location, url and
description but I not getting it... I'm doing like:
$user = $this-twitter-call('account/update_profile', array('name' =
$name, 'url' = $web, 'location' = $location, 'description' =
$desc));
But I'm getting an empty response and the profile is not updated...
Any of you did this before?
[twitter-dev] Can you help in building this query
Hi Friends, Please can you help me in building Twitter search query: get tweets which are from user A and also get tweets which are from user B but contains 'happy' as keyword So all (as per the limit) tweets from user A. But only those tweets from user B that contains 'happy' as keyword. I'm trying something like this: http://search.twitter.com/search?q=from%3Achamonet_news+OR+from%3AMountain_Guides+photo I'm getting wrong results. Please can anyone help? Thanks Regards, Ashwani
[twitter-dev] Thoughts on annotations
This weekend's hackfest was at Twitter HQ was fun. About a couple dozen of us stayed awake for about 30 hours and still had enough to energy to present. Some pretty amazing things created and we helped identified a bunch of bugs. Now that I've had a chance to go home and catch up on some sleep, here is a brain dump of my thoughts. * One of the documented recommended types is place/location, but this data is similar to what we store in the geo fields. I'm not sure what issues we may run into privacy using it rather then storing the Geo fields (users can enable/disable geo and remove geo data from all previous status updates). * We will always have twitter clients that will not understand or look even look at our attributes. This means that we can't can't have annotations that change the meaning of a tweet or make the meaning of the tweet useless. This is basically graceful degradation, and not progressive enhancement. We joked that want to see tweets that say: This tweet can only be read in clients that support X annotations. Please upgrade your twitter client or try X client.. * You have to treat annotations as potentially hostile attack vectors. As was proved with some awesome cornfied and flashing unicorn injections this weekend, any raw data can be store in annotations. Just because you stored it there, anyone can do store any raw data and anyone can post tweets that copy your annotation format. Twitter may sanitize javascript injections, but it doesn't stop other types of injections from occurring if you don't check. It's extremely important to validate, html encode, or whatever you need to with the data stored in the annotations. As I did with my twitter remote shell execution example, I added my own signature and noance of my own into the twitter annotation to validate the sender had my secret. It may be one solution. * Attributes work at the time of creation because status updates are immutable. This may be obvious to most, but its a limitation that hits you a few times as you develop. Because of that we need to make sure that we can get most of the clients, including Twitter.com, support the most popular annotation formats. We can't fix update status updates after the fact so we have to get it right. (Adding annotations to new style retweets is in theory possible) * Can't remind people enough to switch from twitter.com to api.twitter.com. A bunch of little differences between the two that give you headaches. Our board of wasted time at the hackfest summed it up pretty well. * A good number of us spent a good deal of time on just getting past OAuth this weekend. We had a lot of people that understood the OAuth spec fairly well thankfully and @jmhodges was there to help (although not his area he deals with in the code). Since you update twitter with POST, it's optional to store the authentication data in the postdata instead of the authentication header according to the spec, and some our libraries were doing just that, but twitter only works with the Authentication header. We didn't know but this was documented on the Wiki and had to learned from trial and error. A bunch of us got caught up on using twitter.com instead of api.twitter.com. I think we all worked through it at about midnight late saturday. In the end it was pretty awesome. I want to thank @jonashuckestein for the the bookmarklet. It was awesome and saved us all time. http://jonashuckestein.github.com/Twitter.com-Annotations-Bookmarklet/ (see my stream with it http://twitpic.com/1st8sd ) I won't cover the bugs. I'll leave twitter to document those if and when they open up annotations to more developers. Thanks all! Zac Bowling @zbowling
[twitter-dev] Re: geo enabled tweets in the twitter stream
I have the same problem. I using the search API to find tweets near a geolocation. But I only want to receive results that are specifically geotagged with lat / lon coordinates. Is there a way to tell the API not t return anything that doesn't have LAT/LON? On May 26, 7:54 pm, John Kalucki j...@twitter.com wrote: Most users don't geotag their tweets. If they don't opt-in, the information isn't available. -John On Wed, May 26, 2010 at 10:34 AM, gm gmans...@gmail.com wrote: Hi, I am using the twitter stream api to access the sample of public tweets. For each tweet I need to know the latitude and longitude location from where the tweet was sent. I am looking up that information in the geo tag/field. But I observed that even if the geo_enabled field is set to true, the geo field is set to null for many tweets. Will appreciate if you can help me understand why this is the case. Also will appreciate if you can help me figure out if there is a better way to find the latitude and longitude location from where the tweet was sent by the user. thanks and I greatly appreciate your help with this! gm
[twitter-dev] Re: Thoughts on annotations
I was still waking up and recovering from yesterday when I wrote this so forgive the typos, grammar, and mixing up attributes as annotations. I also wanted to mention that I'm glad that twitter didn't confuse annotations by using the term namespace or providing some kind of mechanism that goes that direction. I originally was wondering about conflicting but this method is better. Namespace gives developers a sense of ownership with the data stored in that annotation type. You can easily still easily namespace your types if you want (possibly in the reverse DNS format used in Java) but you can't prevent other developers from using them and that needs to be conveyed. If you need to strongly store annotation data, you can use signatures, hashes, version markers, or whatever in the annotation that you want to provide that, but it's up to the developer to what they want to fit their needs. Also wanted to playfully rant that parking overnight on the weekend near Twitter HQ sucks, especially when there is a baseball game. The closest garages all close at night on the weekends, so I ended up moving my car 3 times. Next time I'm taking BART and riding my bike. :-) Also On May 31, 11:39 am, Zac Bowling zbowl...@gmail.com wrote: This weekend's hackfest was at Twitter HQ was fun. About a couple dozen of us stayed awake for about 30 hours and still had enough to energy to present. Some pretty amazing things created and we helped identified a bunch of bugs. Now that I've had a chance to go home and catch up on some sleep, here is a brain dump of my thoughts. * One of the documented recommended types is place/location, but this data is similar to what we store in the geo fields. I'm not sure what issues we may run into privacy using it rather then storing the Geo fields (users can enable/disable geo and remove geo data from all previous status updates). * We will always have twitter clients that will not understand or look even look at our attributes. This means that we can't can't have annotations that change the meaning of a tweet or make the meaning of the tweet useless. This is basically graceful degradation, and not progressive enhancement. We joked that want to see tweets that say: This tweet can only be read in clients that support X annotations. Please upgrade your twitter client or try X client.. * You have to treat annotations as potentially hostile attack vectors. As was proved with some awesome cornfied and flashing unicorn injections this weekend, any raw data can be store in annotations. Just because you stored it there, anyone can do store any raw data and anyone can post tweets that copy your annotation format. Twitter may sanitize javascript injections, but it doesn't stop other types of injections from occurring if you don't check. It's extremely important to validate, html encode, or whatever you need to with the data stored in the annotations. As I did with my twitter remote shell execution example, I added my own signature and noance of my own into the twitter annotation to validate the sender had my secret. It may be one solution. * Attributes work at the time of creation because status updates are immutable. This may be obvious to most, but its a limitation that hits you a few times as you develop. Because of that we need to make sure that we can get most of the clients, including Twitter.com, support the most popular annotation formats. We can't fix update status updates after the fact so we have to get it right. (Adding annotations to new style retweets is in theory possible) * Can't remind people enough to switch from twitter.com to api.twitter.com. A bunch of little differences between the two that give you headaches. Our board of wasted time at the hackfest summed it up pretty well. * A good number of us spent a good deal of time on just getting past OAuth this weekend. We had a lot of people that understood the OAuth spec fairly well thankfully and @jmhodges was there to help (although not his area he deals with in the code). Since you update twitter with POST, it's optional to store the authentication data in the postdata instead of the authentication header according to the spec, and some our libraries were doing just that, but twitter only works with the Authentication header. We didn't know but this was documented on the Wiki and had to learned from trial and error. A bunch of us got caught up on using twitter.com instead of api.twitter.com. I think we all worked through it at about midnight late saturday. In the end it was pretty awesome. I want to thank @jonashuckestein for the the bookmarklet. It was awesome and saved us all time. http://jonashuckestein.github.com/Twitter.com-Annotations-Bookmarklet/(see my stream with ithttp://twitpic.com/1st8sd) I won't cover the bugs. I'll leave twitter to document those if and when they open up annotations to more developers. Thanks
[twitter-dev] Bug on dev.twitter.com login page
Hi, As soon as I enter my credentials on Twitter's dev login page and press Sign In, the website is redirecting me to http://*dev.*dev.twitter.com/, instead of http://dev.twitter.com/. Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets.
Re: [twitter-dev] Bug on dev.twitter.com login page
Thanks. We'll have this fixed soon. For now, just remove the bonus subdomain. On Monday, May 31, 2010, Ernandes Jr. ernan...@gmail.com wrote: Hi, As soon as I enter my credentials on Twitter's dev login page and press Sign In, the website is redirecting me to http://dev.dev.twitter.com/, instead of http://dev.twitter.com/. Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets. -- Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: Uploading videos to Twitter using OAuth
Could you please suggest the link where I can ask for TwitVid library with OAuth support. On May 31, 9:01 am, Abraham Williams 4bra...@gmail.com wrote: I would think the TwitVid library would include the method but you will have to ask them. Abraham On Sun, May 30, 2010 at 20:51, Deepa deepapai0...@gmail.com wrote: Thanks for the reply. I am new to TwitVid APIs. I have gone through the documentation of TwitVid APIs and OAuth Echo. But, I could not understand the concept of x_verify_credentials_authorization as alternate for User name and password parameters. Also, could you please help me out in explaining how to get value of the parameter x_verify_credentials_authorization i.e OAuth Echo Authorization header. Is there any call in TwitVid library that allows to set the value of the parameter 'x_verify_credentials_authorization'? Thanks in advance. On May 29, 11:16 pm, Abraham Williams 4bra...@gmail.com wrote: x_verify_credentials_authorization: Required if no username/password sent. OAuth Echo Authorization header. Abraham On Sat, May 29, 2010 at 10:42, Deepa deepapai0...@gmail.com wrote: On May 29, 3:53 am, Abraham Williams 4bra...@gmail.com wrote: Twitvid supports OAuth Echo:http://twitvid.pbworks.com/authenticate But, according to thisocumentation the authentication mechanism needs user-name and password. But I cannot get the password. Because, I am using OAuth for authentication in which user is redirected to the web- page for entering user-name and password. I have used OAuth since Twitter is removing the of authentication mechanism which passes user- name and password as arguments. Thanks and regards, Deepa More info on Echo: http://mehack.com/oauth-echo-delegation-in-identity-verificatiohttp:/. .. You will have to ask Twitvid if their iPhone library supports Echo. Abraham On Fri, May 28, 2010 at 06:23, Deepa deepapai0...@gmail.com wrote: Hi, I am developing an iPhone app that uses Twitvid library for uploading videos to TwitVid. This library first authenticates the app using the user-name and password input parameters. Then it uploads the video. But, recently I switched to OAuth mechanism of authentication which leads to a web-page where user can enter the user-name and password. So, I cannot provide the input fields for user-name and password in my app for uploading video. Can someone help me out to solve this problem. Thanks and Regards, Deepa -- 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. -- 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. -- 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] Re: Uploading videos to Twitter using OAuth
http://www.twitvid.com/index.php?area=aboutaction=contact On Mon, May 31, 2010 at 21:19, Deepa deepapai0...@gmail.com wrote: Could you please suggest the link where I can ask for TwitVid library with OAuth support. On May 31, 9:01 am, Abraham Williams 4bra...@gmail.com wrote: I would think the TwitVid library would include the method but you will have to ask them. Abraham On Sun, May 30, 2010 at 20:51, Deepa deepapai0...@gmail.com wrote: Thanks for the reply. I am new to TwitVid APIs. I have gone through the documentation of TwitVid APIs and OAuth Echo. But, I could not understand the concept of x_verify_credentials_authorization as alternate for User name and password parameters. Also, could you please help me out in explaining how to get value of the parameter x_verify_credentials_authorization i.e OAuth Echo Authorization header. Is there any call in TwitVid library that allows to set the value of the parameter 'x_verify_credentials_authorization'? Thanks in advance. On May 29, 11:16 pm, Abraham Williams 4bra...@gmail.com wrote: x_verify_credentials_authorization: Required if no username/password sent. OAuth Echo Authorization header. Abraham On Sat, May 29, 2010 at 10:42, Deepa deepapai0...@gmail.com wrote: On May 29, 3:53 am, Abraham Williams 4bra...@gmail.com wrote: Twitvid supports OAuth Echo: http://twitvid.pbworks.com/authenticate But, according to thisocumentation the authentication mechanism needs user-name and password. But I cannot get the password. Because, I am using OAuth for authentication in which user is redirected to the web- page for entering user-name and password. I have used OAuth since Twitter is removing the of authentication mechanism which passes user- name and password as arguments. Thanks and regards, Deepa More info on Echo: http://mehack.com/oauth-echo-delegation-in-identity-verificatiohttp:/. .. You will have to ask Twitvid if their iPhone library supports Echo. Abraham On Fri, May 28, 2010 at 06:23, Deepa deepapai0...@gmail.com wrote: Hi, I am developing an iPhone app that uses Twitvid library for uploading videos to TwitVid. This library first authenticates the app using the user-name and password input parameters. Then it uploads the video. But, recently I switched to OAuth mechanism of authentication which leads to a web-page where user can enter the user-name and password. So, I cannot provide the input fields for user-name and password in my app for uploading video. Can someone help me out to solve this problem. Thanks and Regards, Deepa -- 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. -- 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. -- 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. -- 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.
