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,
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
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
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
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
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
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
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
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
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.
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
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
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
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
14 matches
Mail list logo
