HI Matt,
Thanks for your response.
I tried using the oauth token and secret for the x_auth_username and
x_auth_password but that did not work for the 2 legged oauth that I am
trying to achieve using Twitter4J so that I don't get prompted for the
browser authorization that I am trying to avoid.I
See
http://code.google.com/p/oauth-python-twitter/source/browse/trunk/oauthtwitter.p
y?r=6 which extends python-twitter to include OAuth calls. I added a
method at a fork at http://github.com/hboon/oauthtwitter/ to include
the XAuth token exchange call.
--
Hwee-Boon
On Jun 13, 10:39 am,
Hi
I have a website that focuses on Twitter favorites ( http://favorious.com
) and I have tried to implement the new Link Wrapping guidelines using
entities. However ?include_entities=true is not working (I tried
getting a @raffi tweet that I have favorited). The documentation
(
Perhaps I'm missing something here, but I do not see any security in
this solution, except for the user not having to enter his Twitter
credentials in an app that only he uses anyway.
Open source means, well, open (readable and modifiable by anyone)
source. Meaning, your API Consumer Key is
I can't currently use asterisk characters in my app. If this is
included in a status update then I get an incorrect signature error
returned. In my signature base I'm encoding * as %252A and the status
update contains %2A. I'm doing similar syuff for other characters with
success but this just
Not quite sure what's going on but here's a successful run I just did:
POST body:
status=LOAD%20*,8,1
Signature base string:
POSThttp%3A%2F%2Fapi.twitter.com
Let's assume, we already have tokens of users, who logged into site
via normal OAuth process. Now, if we integrate Anywhere in our site
frontend, users are required to do a separate OAuth login for
following people via Anywhere hover cards. Is there a way to suppress
the second OAuth login, as we
No dice. I just tried creating a new app and using the new keys/token
to tweet. I'll go over my steps once more and see if I can track down
an issue somewhere...
On Jun 11, 8:53 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
xAuth in this case, I think, is unrelated to the issue.
The problem here is that Twitter wants to use OAuth to identify and
block abusive applications, but the OAuth standard was not designed to
be used in that manner. Regardless of whether an application's source
code is published, the consumer secret key will always be easily
accessible in desktop
Ok Thanks for the heads up, Hwee-Boon.
On Jun 13, 1:37 am, Hwee-Boon Yar hweeb...@gmail.com wrote:
Seehttp://code.google.com/p/oauth-python-twitter/source/browse/trunk/oau...
y?r=6 which extends python-twitter to include OAuth calls. I added a
method at a fork
On Jun 13, 5:07 pm, pythonista sitecontac...@gmail.com wrote:
Ok Thanks for the heads up, Hwee-Boon.
On Jun 13, 1:37 am, Hwee-Boon Yar hweeb...@gmail.com wrote:
Seehttp://code.google.com/p/oauth-python-twitter/source/browse/trunk/oau...
y?r=6 which extends python-twitter to include OAuth
Hi there - I'm trying to get set up with the new OAuth API for a
little app that I'm hosting on site5. When make a signed POST request
from the app on my home machine, it works just fine. When I have the
application do it on my host, the response to my curl request is a 413
Requet Entity Too large
Ok, so I believe my signature is correct because if I take out the
oauth_token parameter from the signature base I get an incorrect
signature error instead of the invalid/used nonce error. I am
definitely posting to the correct url: https://api.twitter.com/1/
statuses/update.xml because if I
Hello,
I am attempting to design a system to integrate into my website's news
management that will allow visitors to click a button/logo and
automatically tweet about it. I can't get past the authentication
step, however.
I'm using Andy Smith's PHP OAuth library to handle all my OAuth work,
and
14 matches
Mail list logo
