Re: [twitter-dev] Re: basic authentication not supported error
I haven't done much Flash coding -- I know there are a few approaches to coding in Flash and that there are OAuth libraries available. You might want to check out this library: http://code.google.com/p/oauth-as3/ Also, there's an AIR-based open source project called Spaz that you can look at, though it may be far from what you're wanting: https://github.com/funkatron/spaz-desktop-air @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 7:36 AM, nite21 shanebond1...@gmail.com wrote: hi taylor and paresh i am creating a slideshow of 40 users recent tweet one after another in flash now some of them show when i ctrl enter and some of them dont some of this give me this error errors error code=53Basic authentication is not supported/error /errors im using this code loadTwitterXML(http://api.twitter.com/1/statuses/user_timeline.xml? screen_name=+listArr[twitcount]); how to use oauth to show usertimeline thanks On Feb 10, 8:09 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: As Paresh mentioned, Your URL needs to be: a) pointed to the *api* subdomain b) versioned -- always *1* at this time c) specifying a format - usually either *json* or *xml* And should use: a) the screen_name parameter instead of an interpolated URI element to avoid issues with all-integer screen names. * * In your case you want to issue a GET to this URL instead: *http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=shane. .. * * * Taylor * * @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 3:30 AM, Paresh Nakhe paresh.na...@gmail.com wrote: Are you using twitteroauth library? Also, the url should be like http://api.twitter.com/1/statuses/user_timeline/sh...82 Atleast i am using this and it works for me. On Thu, Feb 10, 2011 at 3:44 PM, nite21 shanebond1...@gmail.com wrote: hi all im loading twitter xml data and showing it in flash when i load this xml to get data http://twitter.com/statuses/user_timeline/shanebond1982 i am getting this error basic authentication not supported error is there any other method to get the usertimeline data pls help thanks :) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- *What I have is not a dream, because I will make it a reality.* -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: basic authentication not supported error
hi taylor and paresh i am creating a slideshow of 40 users recent tweet one after another in flash now some of them show when i ctrl enter and some of them dont some of this give me this error errors error code=53Basic authentication is not supported/error /errors im using this code loadTwitterXML(http://api.twitter.com/1/statuses/user_timeline.xml? screen_name=+listArr[twitcount]); how to use oauth to show usertimeline thanks On Feb 10, 8:09 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: As Paresh mentioned, Your URL needs to be: a) pointed to the *api* subdomain b) versioned -- always *1* at this time c) specifying a format - usually either *json* or *xml* And should use: a) the screen_name parameter instead of an interpolated URI element to avoid issues with all-integer screen names. * * In your case you want to issue a GET to this URL instead: *http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=shane... * * * Taylor * * @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Thu, Feb 10, 2011 at 3:30 AM, Paresh Nakhe paresh.na...@gmail.comwrote: Are you using twitteroauth library? Also, the url should be like http://api.twitter.com/1/statuses/user_timeline/sh...82 Atleast i am using this and it works for me. On Thu, Feb 10, 2011 at 3:44 PM, nite21 shanebond1...@gmail.com wrote: hi all im loading twitter xml data and showing it in flash when i load this xml to get data http://twitter.com/statuses/user_timeline/shanebond1982 i am getting this error basic authentication not supported error is there any other method to get the usertimeline data pls help thanks :) -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- *What I have is not a dream, because I will make it a reality.* -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Basic authentication
i haven't implemented OAuth at the moment but i'm at the verge doing it. although it is complete nonsense for my closed circuit use of posting status updates from website to twitter by fixed set of 2 to 3 users which never change. i wish that Twitter would offer an alternative for scenarios like this. i just wanted to clarify this... On 20 Mai, 19:16, Lil Peck lilp...@gmail.com wrote: On Tue, May 18, 2010 at 2:13 PM, Eric wetr...@gmail.com wrote: We are using the Streaming API and will only be using our own credentials. Our experience with OAuth in other services has not been positive, so like TJ says huge hassle for no gain. Although I was able to finally adapt to Oauth (thanks for Abraham and thanks to Scott), I agree that for folks who have web apps that do not require them to collect other people's logins, or to give their own to a third party, that it does seem a shame that provisions haven't been made to let those apps continue as is. Sorta looks like fixing what aint broke.
[twitter-dev] Re: Basic authentication
Hey, I'm pretty sure that Twitter isn't going to like that very much. The whole point is that everyone uses it not tries to get around it... I can't imagine supertweet will maintain it's own oauth for very long... On May 20, 12:02 pm, Jef Poskanzer jef.poskan...@gmail.com wrote: Thanks to @mrblog and SuperTweet I now have a backup plan in case I don't get OAuth implemented by the time Basic Auth goes away. It's a Twitter proxy - you use Basic Auth to talk to the proxy, and it uses OAuth to talk to Twitter. Easy peasy. http://www.supertweet.net/
[twitter-dev] Re: Basic authentication
Twitter should offer a registration process for these cases. usually the posts aren't going to many accounts, so you could implement this registration with the Twitter user. the Twitter user could allow or disallow basic auth calls to his account. On May 21, 3:14 pm, Tammy Fennell tammykahnfenn...@gmail.com wrote: Hey, I'm pretty sure that Twitter isn't going to like that very much. The whole point is that everyone uses it not tries to get around it... I can't imagine supertweet will maintain it's own oauth for very long... On May 20, 12:02 pm, Jef Poskanzer jef.poskan...@gmail.com wrote: Thanks to @mrblog and SuperTweet I now have a backup plan in case I don't get OAuth implemented by the time Basic Auth goes away. It's a Twitter proxy - you use Basic Auth to talk to the proxy, and it uses OAuth to talk to Twitter. Easy peasy. http://www.supertweet.net/
Re: [twitter-dev] Re: Basic authentication
On Tue, May 18, 2010 at 1:23 AM, Rich rhyl...@gmail.com wrote: That argument is fine, except for one glaring issue... xAuth. I've seen plenty of iPhone clients for instance using xAuth but there is no good reason for them to be using xAuth as it's remarkably simple to use the oAuth workflow using UIWebView. For my iPhone push app http://2apn.com I've received many complains because user did not understand what they had to do (usint oauth+webview). I'm going xauth because I want to be able to do the UI I want.
[twitter-dev] Re: Basic authentication
Perhaps, but I think it's a mistake to shut supertweet down. It's solving a real-world problem, doing them a favor by doing something for twitter so they don't have to. It pushes all these corner cases off of their API front-end. It doesn't expose the user's Twitter passwords and users never expose their passwords to supertweet. Supertweet isn't so people can be lazy - people should still supprot oAuth and nobody should be using to make API calls on behalf of others (as in a normal Twitter user client). But it will really help PHP scripts and the like bridge over until their hosting service or whatever supports tools for OAuth. So again, I'd say http://www.supertweet.net is doing Twitter a favor. On May 21, 6:14 am, Tammy Fennell tammykahnfenn...@gmail.com wrote: Hey, I'm pretty sure that Twitter isn't going to like that very much. The whole point is that everyone uses it not tries to get around it... I can't imagine supertweet will maintain it's own oauth for very long... On May 20, 12:02 pm, Jef Poskanzer jef.poskan...@gmail.com wrote: Thanks to @mrblog and SuperTweet I now have a backup plan in case I don't get OAuth implemented by the time Basic Auth goes away. It's a Twitter proxy - you use Basic Auth to talk to the proxy, and it uses OAuth to talk to Twitter. Easy peasy. http://www.supertweet.net/
Re: [twitter-dev] Re: Basic authentication
On Tue, May 18, 2010 at 2:13 PM, Eric wetr...@gmail.com wrote: We are using the Streaming API and will only be using our own credentials. Our experience with OAuth in other services has not been positive, so like TJ says huge hassle for no gain. Although I was able to finally adapt to Oauth (thanks for Abraham and thanks to Scott), I agree that for folks who have web apps that do not require them to collect other people's logins, or to give their own to a third party, that it does seem a shame that provisions haven't been made to let those apps continue as is. Sorta looks like fixing what aint broke.
[twitter-dev] Re: Basic authentication
That argument is fine, except for one glaring issue... xAuth. I've seen plenty of iPhone clients for instance using xAuth but there is no good reason for them to be using xAuth as it's remarkably simple to use the oAuth workflow using UIWebView. I was under the belief that xAuth was designed either as a temporary conversion tool for old Basic Auth clients or clients that didn't have a decent embeddable browser on a mobile device? With xAuth the client is still asking for a username and password and what is to prevent them from storing that information, sure they aren't supposed to but what if they do, and how would Twitter know that that specific client was the one harvesting account information. On May 18, 7:49 am, Dave Sherohman d...@fishtwits.com wrote: On Mon, May 17, 2010 at 11:22:56AM -0700, Jef Poskanzer wrote: Have you considered keeping basic auth enabled, but only for https? This would be secure against packet sniffing and would probably use less resources than OAuth. The issue with Basic Auth isn't packet sniffing. The issue with Basic Auth is that you're giving your Twitter login credentials to a third party (i.e., some application that is not Twitter) and, in most cases, allowing that third party to store your Twitter login credentials for future use. This is Very Bad. General security best practice states that you should *never* give your login credentials for *any* system to *any* third party for *any* reason. To put it another way, how about if you just give me the username and password for your bank's website so that I can deposit some money for you? I won't use it to transfer money to my account, or to lock you out of your bank account, and I'll forget them as soon as the deposit has been made. Really. I promise. *That* is the problem with Basic Auth, regardless of whether I use https when I log in to your bank account or not. -- Dave Sherohman
[twitter-dev] Re: Basic authentication
For my command-line twitter applications there is no third party, just the end-user and twitter. Basic Auth + https would be just fine for that.
Re: [twitter-dev] Re: Basic authentication
On Tue, May 18, 2010 at 11:32 AM, Jef Poskanzer jef.poskan...@gmail.com wrote: For my command-line twitter applications there is no third party, just the end-user and twitter. Basic Auth + https would be just fine for that. +1 I don't access anyone's account information except my own. This is a huge hassle for no gain at all for me. Not that I expect that to change.
Re: [twitter-dev] Re: Basic authentication
If you are only working with your own account have a look at: http://dev.twitter.com/pages/oauth_single_token Abraham On Tue, May 18, 2010 at 11:28, TJ Luoma luo...@gmail.com wrote: On Tue, May 18, 2010 at 11:32 AM, Jef Poskanzer jef.poskan...@gmail.com wrote: For my command-line twitter applications there is no third party, just the end-user and twitter. Basic Auth + https would be just fine for that. +1 I don't access anyone's account information except my own. This is a huge hassle for no gain at all for me. Not that I expect that to change. -- 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: Basic authentication
We are using the Streaming API and will only be using our own credentials. Our experience with OAuth in other services has not been positive, so like TJ says huge hassle for no gain. +1 Thanks. -Eric On May 18, 9:28 am, TJ Luoma luo...@gmail.com wrote: On Tue, May 18, 2010 at 11:32 AM, Jef Poskanzer jef.poskan...@gmail.com wrote: For my command-line twitter applications there is no third party, just the end-user and twitter. Basic Auth + https would be just fine for that. +1 I don't access anyone's account information except my own. This is a huge hassle for no gain at all for me. Not that I expect that to change.
[twitter-dev] Re: Basic authentication with JQuery library ($.getJSON function)
hmm.
http://lmgtfy.com/?q=jquery+basic+authentication+
(not being a great javascript/jquery coder, i may recommend doing a
$.ajax call instead of the $.getJSON -- in the beforeSend callback do
a request.setRequestHeader with the basic auth headers as documented
at http://en.wikipedia.org/wiki/Basic_access_authentication -- but
what do i know)
Hi,
How i can do the basic authentication with $.getJSON function? I just
can get json file without authentication:
var url = 'http://search.twitter.com/search.json?
q=danielrqq=2callback=?'
$.getJSON(url, function(data){
$.each(data.results, function(i,item){});
but if i want this url http://twitter.com/statuses/
user_timeline.json i need to authenticate.
Can you help me on this?
best regards
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
