Re: [twitter-dev] @Anywhere communicate with PHP OAuth

2010-11-17 Thread Abraham Williams 
John,

It still works for me. My two suggestions is to make sure you are issuing a
POST request to oauth/access_token and check that oauth_bridge_code is
getting passed correctly.

You could use a tool like Charles Proxy to verify this information.
http://www.charlesproxy.com/

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Tue, Nov 16, 2010 at 20:57, John Barratt djo...@gmail.com wrote:

 On 6/10/10 7:17 AM, Abraham Williams wrote:

 The functionality is there just not officially supported.

 http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html

 I've had a go at implementing this with ruby  jnunemaker's twitter gem (
 https://github.com/jnunemaker/twitter), but to no avail.

 All other aspects of @anywhere access works fine for me, as does getting
 access through OAuth for use via the REST API.   Just can't get the token 
 secret for use with OAuth via @anywhere.

 Can anyone verify that this functionality does still work  is there any
 timeframe for it to be officially supported?

 Apart from the original slides by Matt  article by Abraham I can't find
 any more information on it.

 For reference I always get a 401, with the message Failed to validate
 oauth signature and token. FWIW my server time is fine, and all other OAuth
 interactions are working fine.

 I have tried many variants, but the basic code is :

 token=ABC;secret=DEF;oauth_bridge_code=GHI

 oauth = Twitter::OAuth.new(token, secret, :sign_in = true)

 access_token = oauth.request_token.get_access_token({}, :oauth_bridge_code
 = oauth_bridge_code)

 It's at this point that it 401's.

 I have verified that I am using valid token  secret, and what looks like a
 valid bridge code is also obtained  used.  But perhaps there is something I
 am missing here?

 Thanks,

 JB.


 Abraham
 -
 Abraham Williams | Hacker Advocate | http://abrah.am
 Update: http://blog.abrah.am/2010/10/organizing-my-life.html
 @abraham | http://projects.abrah.am | http://blog.abrah.am
 This email is: [ ] shareable [x] ask first [ ] private.



 On Tue, Oct 5, 2010 at 12:39, Krileon krile...@gmail.com
 mailto:krile...@gmail.com wrote:

I've been reading that it is planned, but is it ever going to happen?
Facebook does hits, Google Friend Connect does this (subsequently
provides Twitter login as well through their API), so why can't
twitters own API? Just pass a authorized key and secret with the
cookie so we can through it through the OAuth request. This is making
it an absolute nightmare to provide single sign-on for Twitter users
as can be done with Facebook connect. 99% sites out there can't only
superficially log users in with JS prettiness. They need to be
stored inside the database so access permissions and what have you may
function.

--
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 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

Re: [twitter-dev] @Anywhere communicate with PHP OAuth

2010-11-17 Thread John Barratt 

On 18/11/10 8:21 AM, Abraham Williams wrote:

It still works for me. My two suggestions is to make sure you are
issuing a POST request to oauth/access_token and check that
oauth_bridge_code is getting passed correctly.
Definitely a post, and the bridge code seems to be correct as well. 
I've tried a few variants in the way it is being sent as well to no avail.



You could use a tool like Charles Proxy to verify this information.
http://www.charlesproxy.com/

Might have to look into it.

Thanks for your help.

JB.


On Tue, Nov 16, 2010 at 20:57, John Barratt djo...@gmail.com
mailto:djo...@gmail.com wrote:

On 6/10/10 7:17 AM, Abraham Williams wrote:

The functionality is there just not officially supported.

http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html

I've had a go at implementing this with ruby  jnunemaker's twitter
gem (https://github.com/jnunemaker/twitter), but to no avail.

All other aspects of @anywhere access works fine for me, as does
getting access through OAuth for use via the REST API.   Just can't
get the token  secret for use with OAuth via @anywhere.

Can anyone verify that this functionality does still work  is there
any timeframe for it to be officially supported?

Apart from the original slides by Matt  article by Abraham I can't
find any more information on it.

For reference I always get a 401, with the message Failed to
validate oauth signature and token. FWIW my server time is fine,
and all other OAuth interactions are working fine.

I have tried many variants, but the basic code is :

token=ABC;secret=DEF;oauth_bridge_code=GHI

oauth = Twitter::OAuth.new(token, secret, :sign_in = true)

access_token = oauth.request_token.get_access_token({},
:oauth_bridge_code = oauth_bridge_code)

It's at this point that it 401's.

I have verified that I am using valid token  secret, and what looks
like a valid bridge code is also obtained  used.  But perhaps there
is something I am missing here?

Thanks,

JB.


Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
Update: http://blog.abrah.am/2010/10/organizing-my-life.html
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Tue, Oct 5, 2010 at 12:39, Krileon krile...@gmail.com
mailto:krile...@gmail.com
mailto:krile...@gmail.com mailto:krile...@gmail.com wrote:

I've been reading that it is planned, but is it ever going
to happen?
Facebook does hits, Google Friend Connect does this
(subsequently
provides Twitter login as well through their API), so why can't
twitters own API? Just pass a authorized key and secret with the
cookie so we can through it through the OAuth request. This
is making
it an absolute nightmare to provide single sign-on for
Twitter users
as can be done with Facebook connect. 99% sites out there
can't only
superficially log users in with JS prettiness. They need to be
stored inside the database so access permissions and what
have you may
function.

--
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 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

Re: [twitter-dev] @Anywhere communicate with PHP OAuth

2010-11-17 Thread Edward Hotchkiss 

Charles is awesssomeee. Best for Flash but this works too.

Best,

--
Edward H. Hotchkiss
http://www.edwardhotchkiss.com/
http://www.twitter.com/edwardhotchkiss/
--




On Nov 17, 2010, at 4:21 PM, Abraham Williams wrote:


John,

It still works for me. My two suggestions is to make sure you are  
issuing a POST request to oauth/access_token and check that  
oauth_bridge_code is getting passed correctly.


You could use a tool like Charles Proxy to verify this information. 
http://www.charlesproxy.com/

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Tue, Nov 16, 2010 at 20:57, John Barratt djo...@gmail.com wrote:
On 6/10/10 7:17 AM, Abraham Williams wrote:
The functionality is there just not officially supported.

http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html
I've had a go at implementing this with ruby  jnunemaker's twitter  
gem (https://github.com/jnunemaker/twitter), but to no avail.


All other aspects of @anywhere access works fine for me, as does  
getting access through OAuth for use via the REST API.   Just can't  
get the token  secret for use with OAuth via @anywhere.


Can anyone verify that this functionality does still work  is there  
any timeframe for it to be officially supported?


Apart from the original slides by Matt  article by Abraham I can't  
find any more information on it.


For reference I always get a 401, with the message Failed to  
validate oauth signature and token. FWIW my server time is fine,  
and all other OAuth interactions are working fine.


I have tried many variants, but the basic code is :

token=ABC;secret=DEF;oauth_bridge_code=GHI

oauth = Twitter::OAuth.new(token, secret, :sign_in = true)

access_token = oauth.request_token.get_access_token 
({}, :oauth_bridge_code = oauth_bridge_code)


It's at this point that it 401's.

I have verified that I am using valid token  secret, and what looks  
like a valid bridge code is also obtained  used.  But perhaps there  
is something I am missing here?


Thanks,

JB.


Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
Update: http://blog.abrah.am/2010/10/organizing-my-life.html
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Tue, Oct 5, 2010 at 12:39, Krileon krile...@gmail.com
mailto:krile...@gmail.com wrote:

   I've been reading that it is planned, but is it ever going to  
happen?

   Facebook does hits, Google Friend Connect does this (subsequently
   provides Twitter login as well through their API), so why can't
   twitters own API? Just pass a authorized key and secret with the
   cookie so we can through it through the OAuth request. This is  
making
   it an absolute nightmare to provide single sign-on for Twitter  
users
   as can be done with Facebook connect. 99% sites out there can't  
only

   superficially log users in with JS prettiness. They need to be
   stored inside the database so access permissions and what have  
you may

   function.

   --
   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 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
inline: edward.png

Re: [twitter-dev] @Anywhere communicate with PHP OAuth

2010-11-16 Thread John Barratt 

On 6/10/10 7:17 AM, Abraham Williams wrote:

The functionality is there just not officially supported.

http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html
I've had a go at implementing this with ruby  jnunemaker's twitter gem 
(https://github.com/jnunemaker/twitter), but to no avail.


All other aspects of @anywhere access works fine for me, as does getting 
access through OAuth for use via the REST API.   Just can't get the 
token  secret for use with OAuth via @anywhere.


Can anyone verify that this functionality does still work  is there any 
timeframe for it to be officially supported?


Apart from the original slides by Matt  article by Abraham I can't find 
any more information on it.


For reference I always get a 401, with the message Failed to validate 
oauth signature and token. FWIW my server time is fine, and all other 
OAuth interactions are working fine.


I have tried many variants, but the basic code is :

token=ABC;secret=DEF;oauth_bridge_code=GHI

oauth = Twitter::OAuth.new(token, secret, :sign_in = true)

access_token = oauth.request_token.get_access_token({}, 
:oauth_bridge_code = oauth_bridge_code)


It's at this point that it 401's.

I have verified that I am using valid token  secret, and what looks 
like a valid bridge code is also obtained  used.  But perhaps there is 
something I am missing here?


Thanks,

JB.



Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
Update: http://blog.abrah.am/2010/10/organizing-my-life.html
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Tue, Oct 5, 2010 at 12:39, Krileon krile...@gmail.com
mailto:krile...@gmail.com wrote:

I've been reading that it is planned, but is it ever going to happen?
Facebook does hits, Google Friend Connect does this (subsequently
provides Twitter login as well through their API), so why can't
twitters own API? Just pass a authorized key and secret with the
cookie so we can through it through the OAuth request. This is making
it an absolute nightmare to provide single sign-on for Twitter users
as can be done with Facebook connect. 99% sites out there can't only
superficially log users in with JS prettiness. They need to be
stored inside the database so access permissions and what have you may
function.

--
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

Re: [twitter-dev] @Anywhere communicate with PHP OAuth

2010-10-05 Thread Abraham Williams 
The functionality is there just not officially supported.

http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html

Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
Update: http://blog.abrah.am/2010/10/organizing-my-life.html
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Tue, Oct 5, 2010 at 12:39, Krileon krile...@gmail.com wrote:

 I've been reading that it is planned, but is it ever going to happen?
 Facebook does hits, Google Friend Connect does this (subsequently
 provides Twitter login as well through their API), so why can't
 twitters own API? Just pass a authorized key and secret with the
 cookie so we can through it through the OAuth request. This is making
 it an absolute nightmare to provide single sign-on for Twitter users
 as can be done with Facebook connect. 99% sites out there can't only
 superficially log users in with JS prettiness. They need to be
 stored inside the database so access permissions and what have you may
 function.

 --
 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