[twitter-dev] Re: 401 unauthorized
Correction. Switching to HTTP does remove the issue, so I'm making that a configurable setting in our app as a temporary workaround. -- 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: 401 unauthorized
I'd like to add another confirmation of this issue. I am the lead developer for a commercial application that has started receiving reports of Twitter sign-in failures over the last couple days and I was able to reliably reproduce the 15-second workaround before I came across this thread. I'm using the Hammock (.NET) library, against the api.twitter.com URLs over SSL, but I found the problem persists when I tried over HTTP and/or directed to the regular twitter.com URLs. -- 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] is streaming API read-only?
Hi, I have an impression that streaming API (for example, user stream API) is read-only. I can obtain statuses but I won't be able to update, such as add follows to a user account. Is it correct? Thanks, Gary -- 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] twitter_oauth gem problem
Having a problem with the twitter_oauth gem. It seems to work fine for the
update method and others, e.g.
chan = Jobchannel.find(:last, :conditions => ['access_token IS NOT NULL'])
client = TwitterOAuth::Client.new(
:consumer_key => SAFETWEET_CONSUMER_KEY,
:consumer_secret => SAFETWEET_CONSUMER_SECRET,
:token => chan.safetweet_access_token,
:secret => chan.safetweet_access_secret
)
ret = client.update('test')
but when I use the update profile method, I get this:
ret = client.update_profile(:description => 'test')
JSON::ParserError: 665: unexpected token at '
/1/account/update_profile
Could not authenticate with OAuth.
'
from
/home/deploy/.gem/ruby/1.8/gems/json_pure-1.2.2/lib/json/common.rb:
from
/home/deploy/.gem/ruby/1.8/gems/json_pure-1.2.2/lib/json/common.rb:
from
/opt/ruby/lib/ruby/gems/1.8/gems/twitter_oauth-0.4.3/lib/twitter_oa
from
/opt/ruby/lib/ruby/gems/1.8/gems/twitter_oauth-0.4.3/lib/twitter_oa
from (irb):12
Any ideas?
Thanks,
Gary Zukowski
TweetMyJOBS.com
@garyzukowski
@tweetmyjobs
LinkedIn <http://www.linkedin.com/profile/view?id=414054>
704-544-9370
Listen to the TweetMyJOBS Holiday Album at http://www.tweetmyjobs.com/album
Check out TweetMyJOBS on MSNBC's Dylan Ratigan Show:
http://www.msnbc.msn.com/id/31510813/#39313587
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. If you are not the intended recipient, you are
notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.
From: Dean Collins [mailto:d...@cognation.net]
Sent: Wednesday, January 05, 2011 11:00 AM
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] RE: New twitter in ie8 broken again
Huh well that IS interesting.
I have no idea why but someone just emailed me to answer my question about
New Twitter being broken for IE8.
They told me if you turn on "InPrivate" browsing on IE8 that new twitter
works.. Just tried it for my account http://www.Twitter.com/LiveNascarChat
came up perfect.
Can someone from twitter explain what in their code broke this morning at
8am that is negated by inprivate browsing?
Cheers,
Dean
_
From: Dean Collins
Sent: Wednesday, January 05, 2011 8:23 AM
To: twitter-development-talk@googlegroups.com
Subject: New twitter in ie8 broken again
New twitter in ie8 is broken again, works great in firefox but started
failing in ie8 about 8am this morning.
Cheers,
Dean
--
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] Where is join date on #newtwitter
Does anyone know where the "Join Date" is on a user in #NewTwitter? Thanks, Gary Zukowski -- 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] Twitter authentication on/off behavior
Hi all, I have a desktop application using xAuth. Usually, everything works fine. But occasionally, for a period of several days or more, the authentication fails returning invalid-signature error. And then, a few days later, it starts working again without any change on my side. Is there something happening at Twitter, that anyone knows about, that would cause this to happen? Thanks, Gary -- 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] TwitterOauth
I'm getting the following error when trying to do a simple update_profile: client.update_profile(:url => '') JSON::ParserError: 665: unexpected token at ' /1/account/update_profile Could not authenticate with OAuth. ' Any ideas? Thanks, Gary Zukowski -- 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] TwitterOauth
We've started seeing some errors using TwitteOauth. Specifically, we get an "Incorrect signature" error when trying to use the followers_ids method. This method worked 3 days ago. Has something changed? Thanks, Gary Zukowski -- 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: Failed to Auth on Japanese OS
Yes. That worked. The timezone was incorrect. Thank you. On Nov 1, 1:02 pm, Taylor Singletary wrote: > When producing an oauth_timestamp for any method requiring authentication, > the time needs to be indicated in seconds since the "UTC epoch" -- some > programming languages have Date & Time classes that deal with epoch time > easily for you, others require more work. In any case, when generating an > oauth_timestamp, you need to take your local time, convert it to UTC, and > then calculate epoch seconds in that timezone. Further, the timestamp needs > to be within ~ 5 minutes of Twitter's server clock. Our server clock is > reported in the "Date" HTTP header response to each of your requests. > > Taylor > > On Mon, Nov 1, 2010 at 12:54 PM, Gary wrote: > > The system date-time is in sync with local date-time. Exactly what > > the English OS is. I'm not sure what timezone it is set to, though. > > What else should I take under consideration? Could it be that the > > timezone is set to Japan yet the date-time is set to local? (It's not > > easy to find my way around this system being that I don't speak/write > > Japanese.) > > > By the way, I have no trouble running two similar apps (on this > > machine) that talk with YouTube and Facebook apis. > > > On Oct 30, 6:10 pm, nischalshetty wrote: > > > @Gary oAuth takes the current time into consideration, so that really > > > needs to be in sync. > > > > -N > > > > On Oct 31, 2:56 am, Gary wrote: > > > > > I checked and all characters are utf-8 - the auth header and the post > > > > body. I tried installing an English OS on the same machine so it's > > > > not machine specific. I also added charset=utf-8 to the content type > > > > header: application/x-www-form-urlencoded; charset=utf-8. Still I get > > > > the "Failed to validate oauth signature and token". > > > > > I'm not sure what the system clock would have to do with it. > > > > > On Oct 29, 1:24 pm, Taylor Singletary > > > > wrote: > > > > > > Are there any other environmental issues, such as the system clock > > that > > > > > might be different? Are you absolutely sure that all characters are > > UTF-8 in > > > > > both environments, regardless of language? > > > > > > Taylor > > > > > > On Fri, Oct 29, 2010 at 1:04 PM, Gary wrote: > > > > > > I should add that there are no Japanese characters in the message. > > > > > > It's all English. In fact I did try adding Japanese characters > > using > > > > > > the Engllish OS and that worked fine. Even when I used a Japanese > > > > > > character password, the English OS authenticated correctly. > > > > > > > On Oct 29, 1:01 pm, Gary wrote: > > > > > > > Hi, > > > > > > > > I've had great success with the Twitter API until I tried it on a > > > > > > > Japanese version of Windows. It fails to "...validate oauth > > signature > > > > > > > and token". I have captured the output using wireshark and the > > > > > > > outgoing message is identical to the English version of Windows. > > This > > > > > > > does not happen on all Japanese OS machines, though. > > > > > > > > Is there a known problem in this area? > > > > > > > -- > > > > > > 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: Failed to Auth on Japanese OS
The system date-time is in sync with local date-time. Exactly what the English OS is. I'm not sure what timezone it is set to, though. What else should I take under consideration? Could it be that the timezone is set to Japan yet the date-time is set to local? (It's not easy to find my way around this system being that I don't speak/write Japanese.) By the way, I have no trouble running two similar apps (on this machine) that talk with YouTube and Facebook apis. On Oct 30, 6:10 pm, nischalshetty wrote: > @Gary oAuth takes the current time into consideration, so that really > needs to be in sync. > > -N > > On Oct 31, 2:56 am, Gary wrote: > > > I checked and all characters are utf-8 - the auth header and the post > > body. I tried installing an English OS on the same machine so it's > > not machine specific. I also added charset=utf-8 to the content type > > header: application/x-www-form-urlencoded; charset=utf-8. Still I get > > the "Failed to validate oauth signature and token". > > > I'm not sure what the system clock would have to do with it. > > > On Oct 29, 1:24 pm, Taylor Singletary > > wrote: > > > > Are there any other environmental issues, such as the system clock that > > > might be different? Are you absolutely sure that all characters are UTF-8 > > > in > > > both environments, regardless of language? > > > > Taylor > > > > On Fri, Oct 29, 2010 at 1:04 PM, Gary wrote: > > > > I should add that there are no Japanese characters in the message. > > > > It's all English. In fact I did try adding Japanese characters using > > > > the Engllish OS and that worked fine. Even when I used a Japanese > > > > character password, the English OS authenticated correctly. > > > > > On Oct 29, 1:01 pm, Gary wrote: > > > > > Hi, > > > > > > I've had great success with the Twitter API until I tried it on a > > > > > Japanese version of Windows. It fails to "...validate oauth signature > > > > > and token". I have captured the output using wireshark and the > > > > > outgoing message is identical to the English version of Windows. This > > > > > does not happen on all Japanese OS machines, though. > > > > > > Is there a known problem in this area? > > > > > -- > > > > 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: Failed to Auth on Japanese OS
I checked and all characters are utf-8 - the auth header and the post body. I tried installing an English OS on the same machine so it's not machine specific. I also added charset=utf-8 to the content type header: application/x-www-form-urlencoded; charset=utf-8. Still I get the "Failed to validate oauth signature and token". I'm not sure what the system clock would have to do with it. On Oct 29, 1:24 pm, Taylor Singletary wrote: > Are there any other environmental issues, such as the system clock that > might be different? Are you absolutely sure that all characters are UTF-8 in > both environments, regardless of language? > > Taylor > > On Fri, Oct 29, 2010 at 1:04 PM, Gary wrote: > > I should add that there are no Japanese characters in the message. > > It's all English. In fact I did try adding Japanese characters using > > the Engllish OS and that worked fine. Even when I used a Japanese > > character password, the English OS authenticated correctly. > > > On Oct 29, 1:01 pm, Gary wrote: > > > Hi, > > > > I've had great success with the Twitter API until I tried it on a > > > Japanese version of Windows. It fails to "...validate oauth signature > > > and token". I have captured the output using wireshark and the > > > outgoing message is identical to the English version of Windows. This > > > does not happen on all Japanese OS machines, though. > > > > Is there a known problem in this area? > > > -- > > 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] Failed to Auth on Japanese OS
Hi, I've had great success with the Twitter API until I tried it on a Japanese version of Windows. It fails to "...validate oauth signature and token". I have captured the output using wireshark and the outgoing message is identical to the English version of Windows. This does not happen on all Japanese OS machines, though. Is there a known problem in this area? -- 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: Failed to Auth on Japanese OS
I should add that there are no Japanese characters in the message. It's all English. In fact I did try adding Japanese characters using the Engllish OS and that worked fine. Even when I used a Japanese character password, the English OS authenticated correctly. On Oct 29, 1:01 pm, Gary wrote: > Hi, > > I've had great success with the Twitter API until I tried it on a > Japanese version of Windows. It fails to "...validate oauth signature > and token". I have captured the output using wireshark and the > outgoing message is identical to the English version of Windows. This > does not happen on all Japanese OS machines, though. > > Is there a known problem in this area? -- 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: can email be accepted when using OAuth?
This now works. I can pass the email address in place of screen name. On Oct 5, 2:28 pm, Tom van der Woerdt wrote: > I just did a quick check in my own application, it failed. So, unless > Taylor, Matt or John says otherwise, you should consider the definite > answer to be a No. > > Tom > > On 10/5/10 11:25 PM, Gary wrote: > > > Hi Tom, > > > These are thebasestrings with fictitious username, password and > > consumer key and so they will not pass through the validator. I have > > checked the actualbasestrings and they check-out ok. > > > Anyway, what I'm looking for is a definite yes or no as to whether > >emailaddresses-login is supported or not. Is there somewhere I could > > get this info? > > > Thanks, > > Gary > > > On Oct 5, 12:27 pm, Tom van der Woerdt wrote: > >> Those aren'tbasestrings. > > >> Use the OAuthBaseString validator @ <http://quonos.nl/oauthTester/> > > >> By the way: I'm not sure about logging in with E-Mail addresses. It may > >> work, and it may not. > > >> Tom > > >> On 10/5/10 8:27 PM, Gary wrote: > > >>> Hi, > > >>> I'm also having this problem. I cannot login using the user'semail. > >>> AFAIK, I am encoding according to the documentation. I encode the > >>> post body and then encode again when I create thesignaturebase > >>> string. > > >>> Assume: > >>> screen name: myscrname > >>> password: m...@password <--- note I added @ to the password just > >>> to see if there was something about @ which was causing the problem > >>>email: m...@somewhere.com > > >>> === > >>> Using the screen name to login works fine: > > >>> Post body > >>> --- > >>> x_auth_mode=client_auth&x_auth_password=my > >>> %40password&x_auth_username=myscrname > > >>> Sigbasestring > >>> -- > >>> oauth_consumer_key%3Da%26oauth_nonce > >>> %3D3u988u37Acy3GkQWd6tJKrY3fPTefe2QYIL2WXb1R3gWP > >>> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > >>> %3D1286237702%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth > >>> %26x_auth_password%3Dmy%2540password%26x_auth_username%3Dmyscrname > > >>> === > >>> Using theemailto login fails: > > >>> Post body > >>> --- > >>> x_auth_mode=client_auth&x_auth_password=my > >>> %40password&x_auth_username=me%40somewhere.com > > >>> Sigbasestring > >>> -- > >>> oauth_consumer_key%3Da%26oauth_nonce > >>> %3Dwwsim7hj1bfMylHARpmLwQerWjJJu4Y7kgzz8jCdY3Cv6%26oauth_signature_method > >>> %3DHMAC-SHA1%26oauth_timestamp%3D1286237782%26oauth_version > >>> %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy%2540password > >>> %26x_auth_username%3Dme%2540somewhere.com > > >>> On Aug 30, 7:17 am, Taylor Singletary > >>> wrote: > >>>> Hi Joe, > > >>>> Emailcan be accepted, as long as it is properly encoded. A URL encoded > >>>> POST > >>>> body by definition means that you'll already have to escape characters > >>>> like > >>>> the "@" symbol for your POST body -- then for yoursignaturebasestring, > >>>> it'll have to be encoded again. > > >>>> Most Twitter users sign in with their screen name and password. Do you > >>>> have > >>>> a use case where users are predominantly using theiremailaddress? > > >>>> Taylor > > >>>> On Mon, Aug 30, 2010 at 1:10 AM, joe wrote: > >>>>> Hi guys, > > >>>>> I have a question about getting access token. > >>>>> Can I useemailaddress as the username? When x_auth_username = > >>>>> "x...@xxx.com", always a error msg returned: "Failed to validate oauth > >>>>> signatureand token". But if user input username, there is no problem > >>>>> at all. > >>>>> So can anybody tell whetheremailaddress is accepted? Thanks a lot. > > >>>>> Joe > > >>>>> -- > >>>>> 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?hl=en -- 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: can email be accepted when using OAuth?
Here are the post body and base strings where the fictitious credentials are cooked into the base string so it should pass the validator: x_auth_mode=client_auth&x_auth_password=my %40password&x_auth_username=me%40somewhere.com POST&https%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_token&oauth_consumer_key%3D8Oe4VT3GUKwyfMfB4LfQ9h %26oauth_nonce %3DmEd5z1pdth4fAIZ7BQdamQOKkVOqmOYerp6oR2ChhsdB8%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1286314415%26oauth_version %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy%2540password %26x_auth_username%3Dme%2540somewhere.com On Oct 5, 12:27 pm, Tom van der Woerdt wrote: > Those aren'tbasestrings. > > Use the OAuthBaseString validator @ <http://quonos.nl/oauthTester/> > > By the way: I'm not sure about logging in with E-Mail addresses. It may > work, and it may not. > > Tom > > On 10/5/10 8:27 PM, Gary wrote: > > > Hi, > > > I'm also having this problem. I cannot login using the user'semail. > > AFAIK, I am encoding according to the documentation. I encode the > > post body and then encode again when I create thesignaturebase > > string. > > > Assume: > > screen name: myscrname > > password: m...@password <--- note I added @ to the password just > > to see if there was something about @ which was causing the problem > >email: m...@somewhere.com > > > === > > Using the screen name to login works fine: > > > Post body > > --- > > x_auth_mode=client_auth&x_auth_password=my > > %40password&x_auth_username=myscrname > > > Sigbasestring > > -- > > oauth_consumer_key%3Da%26oauth_nonce > > %3D3u988u37Acy3GkQWd6tJKrY3fPTefe2QYIL2WXb1R3gWP > > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > > %3D1286237702%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth > > %26x_auth_password%3Dmy%2540password%26x_auth_username%3Dmyscrname > > > === > > Using theemailto login fails: > > > Post body > > --- > > x_auth_mode=client_auth&x_auth_password=my > > %40password&x_auth_username=me%40somewhere.com > > > Sigbasestring > > -- > > oauth_consumer_key%3Da%26oauth_nonce > > %3Dwwsim7hj1bfMylHARpmLwQerWjJJu4Y7kgzz8jCdY3Cv6%26oauth_signature_method > > %3DHMAC-SHA1%26oauth_timestamp%3D1286237782%26oauth_version > > %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy%2540password > > %26x_auth_username%3Dme%2540somewhere.com > > > On Aug 30, 7:17 am, Taylor Singletary > > wrote: > >> Hi Joe, > > >>Emailcan be accepted, as long as it is properly encoded. A URL encoded POST > >> body by definition means that you'll already have to escape characters like > >> the "@" symbol for your POST body -- then for yoursignaturebasestring, > >> it'll have to be encoded again. > > >> Most Twitter users sign in with their screen name and password. Do you have > >> a use case where users are predominantly using theiremailaddress? > > >> Taylor > > >> On Mon, Aug 30, 2010 at 1:10 AM, joe wrote: > >>> Hi guys, > > >>> I have a question about getting access token. > >>> Can I useemailaddress as the username? When x_auth_username = > >>> "x...@xxx.com", always a error msg returned: "Failed to validate oauth > >>>signatureand token". But if user input username, there is no problem > >>> at all. > >>> So can anybody tell whetheremailaddress is accepted? Thanks a lot. > > >>> Joe > > >>> -- > >>> 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?hl=en -- 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: can email be accepted when using OAuth?
Hi Tom, These are the base strings with fictitious username, password and consumer key and so they will not pass through the validator. I have checked the actual base strings and they check-out ok. Anyway, what I'm looking for is a definite yes or no as to whether email addresses-login is supported or not. Is there somewhere I could get this info? Thanks, Gary On Oct 5, 12:27 pm, Tom van der Woerdt wrote: > Those aren'tbasestrings. > > Use the OAuthBaseString validator @ <http://quonos.nl/oauthTester/> > > By the way: I'm not sure about logging in with E-Mail addresses. It may > work, and it may not. > > Tom > > On 10/5/10 8:27 PM, Gary wrote: > > > Hi, > > > I'm also having this problem. I cannot login using the user'semail. > > AFAIK, I am encoding according to the documentation. I encode the > > post body and then encode again when I create thesignaturebase > > string. > > > Assume: > > screen name: myscrname > > password: m...@password <--- note I added @ to the password just > > to see if there was something about @ which was causing the problem > >email: m...@somewhere.com > > > === > > Using the screen name to login works fine: > > > Post body > > --- > > x_auth_mode=client_auth&x_auth_password=my > > %40password&x_auth_username=myscrname > > > Sigbasestring > > -- > > oauth_consumer_key%3Da%26oauth_nonce > > %3D3u988u37Acy3GkQWd6tJKrY3fPTefe2QYIL2WXb1R3gWP > > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > > %3D1286237702%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth > > %26x_auth_password%3Dmy%2540password%26x_auth_username%3Dmyscrname > > > === > > Using theemailto login fails: > > > Post body > > --- > > x_auth_mode=client_auth&x_auth_password=my > > %40password&x_auth_username=me%40somewhere.com > > > Sigbasestring > > -- > > oauth_consumer_key%3Da%26oauth_nonce > > %3Dwwsim7hj1bfMylHARpmLwQerWjJJu4Y7kgzz8jCdY3Cv6%26oauth_signature_method > > %3DHMAC-SHA1%26oauth_timestamp%3D1286237782%26oauth_version > > %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy%2540password > > %26x_auth_username%3Dme%2540somewhere.com > > > On Aug 30, 7:17 am, Taylor Singletary > > wrote: > >> Hi Joe, > > >>Emailcan be accepted, as long as it is properly encoded. A URL encoded POST > >> body by definition means that you'll already have to escape characters like > >> the "@" symbol for your POST body -- then for yoursignaturebasestring, > >> it'll have to be encoded again. > > >> Most Twitter users sign in with their screen name and password. Do you have > >> a use case where users are predominantly using theiremailaddress? > > >> Taylor > > >> On Mon, Aug 30, 2010 at 1:10 AM, joe wrote: > >>> Hi guys, > > >>> I have a question about getting access token. > >>> Can I useemailaddress as the username? When x_auth_username = > >>> "x...@xxx.com", always a error msg returned: "Failed to validate oauth > >>>signatureand token". But if user input username, there is no problem > >>> at all. > >>> So can anybody tell whetheremailaddress is accepted? Thanks a lot. > > >>> Joe > > >>> -- > >>> 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?hl=en -- 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: can email be accepted when using OAuth?
Hi, I'm also having this problem. I cannot login using the user's email. AFAIK, I am encoding according to the documentation. I encode the post body and then encode again when I create the signature base string. Assume: screen name: myscrname password: m...@password<--- note I added @ to the password just to see if there was something about @ which was causing the problem email: m...@somewhere.com === Using the screen name to login works fine: Post body --- x_auth_mode=client_auth&x_auth_password=my %40password&x_auth_username=myscrname Sig base string -- oauth_consumer_key%3Da%26oauth_nonce %3D3u988u37Acy3GkQWd6tJKrY3fPTefe2QYIL2WXb1R3gWP %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1286237702%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth %26x_auth_password%3Dmy%2540password%26x_auth_username%3Dmyscrname === Using the email to login fails: Post body --- x_auth_mode=client_auth&x_auth_password=my %40password&x_auth_username=me%40somewhere.com Sig base string -- oauth_consumer_key%3Da%26oauth_nonce %3Dwwsim7hj1bfMylHARpmLwQerWjJJu4Y7kgzz8jCdY3Cv6%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1286237782%26oauth_version %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy%2540password %26x_auth_username%3Dme%2540somewhere.com On Aug 30, 7:17 am, Taylor Singletary wrote: > Hi Joe, > > Email can be accepted, as long as it is properly encoded. A URL encoded POST > body by definition means that you'll already have to escape characters like > the "@" symbol for your POST body -- then for your signature base string, > it'll have to be encoded again. > > Most Twitter users sign in with their screen name and password. Do you have > a use case where users are predominantly using their email address? > > Taylor > > On Mon, Aug 30, 2010 at 1:10 AM, joe wrote: > > Hi guys, > > > I have a question about getting access token. > > Can I use email address as the username? When x_auth_username = > > "x...@xxx.com", always a error msg returned: "Failed to validate oauth > > signature and token". But if user input username, there is no problem > > at all. > > So can anybody tell whether email address is accepted? Thanks a lot. > > > Joe > > > -- > > 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?hl=en -- 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: XAuth - bad request
Thank you. Now it works. So what is needed was a single HTTP header with name Authorization and value is the comma delimited string with quoted values as shown in the example. In other words... POST /oauth/authorize HTTP/1.1 Authorization: OAuth oauth_nonce="n7NBq1mCqoinPQzQ23FRFOo6imP5Qh7l51QMi0tlO5GnW", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1285086393", oauth_consumer_key="", oauth_signature="wykLrYGLUBkiq9s3VPIXi%2FGH1bk%3D", oauth_version="1.0" Content-Type: application/x-www-form-urlencoded x_auth_mode=client_auth&x_auth_password=twitter- xauth&x_auth_username=oauth_test_exec On Sep 21, 2:23 am, Tom van der Woerdt wrote: > First, let me start by saying that xAuth is only an extension to OAuth > and that you will have to implement OAuth as well. > > The problem with your request is that you send all oauth_* parameters as > header. That's wrong: the correct syntax is "Authorization: OAuth > oauth_nonce="nonce", oauth_signature="sig",etc" > > Tom > > On 9/21/10 2:19 AM, Gary wrote: > > > Hello, > > > I am developing a desktop application using C++ and QT. (I'm not > > using QAuth because I don't want to have to encorporate QCA and > > OpenSLL into my app.) > > > I am attempting to perform xAuth and I'm getting 400 (bad request). > > Here are the details (data taken fromhttp://dev.twitter.com/pages/xauth) > > > Base string: > > POST&https%3A%2F%2Fapi.twitter.com%2Foauth > > %2Faccess_token&oauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA > > %26oauth_nonce%3D6AN2dKRzxyGhmIXUKSmp1JcB4pckM8rD3frKMTmVAo > > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > > %3D1284565601%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth > > %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec > > > oauth_signature: > > 1L1oXQmawZAkQ47FHLwcOV%2Bkjwc%3D > > > Post body: > > x_auth_mode=client_auth&x_auth_password=twitter- > > xauth&x_auth_username=oauth_test_exec > > > I sent the data to a bogus (non secure) server so I could see what was > > going out in wireshark. Below is the outgoing message. Why is this > > resulting in 400? What am I missing? (Assume this is really going to > >https://api.twitter.com/oauth/access_token) > > > POST /oauth/authorize HTTP/1.1 > > OAuth oauth_nonce: 6AN2dKRzxyGhmIXUKSmp1JcB4pckM8rD3frKMTmVAo > > oauth_signature_method: HMAC-SHA1 > > oauth_timestamp: 1284565601 > > oauth_consumer_key: JvyS7DO2qd6NNTsXJ4E7zA > > oauth_signature: 1L1oXQmawZAkQ47FHLwcOV%2Bkjwc%3D > > oauth_version: 1.0 > > Content-Type: application/x-www-form-urlencoded > > Content-Length: 85 > > Connection: Keep-Alive > > Accept-Encoding: gzip > > accept-language: en,* > > User-Agent: Mozilla/5.0 > > Host: twitter.com > > > x_auth_mode=client_auth&x_auth_password=twitter- > > xauth&x_auth_username=oauth_test_exec -- 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?hl=en
[twitter-dev] XAuth - bad request
Hello, I am developing a desktop application using C++ and QT. (I'm not using QAuth because I don't want to have to encorporate QCA and OpenSLL into my app.) I am attempting to perform xAuth and I'm getting 400 (bad request). Here are the details (data taken from http://dev.twitter.com/pages/xauth) Base string: POST&https%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_token&oauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA %26oauth_nonce%3D6AN2dKRzxyGhmIXUKSmp1JcB4pckM8rD3frKMTmVAo %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1284565601%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth %26x_auth_password%3Dtwitter-xauth%26x_auth_username%3Doauth_test_exec oauth_signature: 1L1oXQmawZAkQ47FHLwcOV%2Bkjwc%3D Post body: x_auth_mode=client_auth&x_auth_password=twitter- xauth&x_auth_username=oauth_test_exec I sent the data to a bogus (non secure) server so I could see what was going out in wireshark. Below is the outgoing message. Why is this resulting in 400? What am I missing? (Assume this is really going to https://api.twitter.com/oauth/access_token) POST /oauth/authorize HTTP/1.1 OAuth oauth_nonce: 6AN2dKRzxyGhmIXUKSmp1JcB4pckM8rD3frKMTmVAo oauth_signature_method: HMAC-SHA1 oauth_timestamp: 1284565601 oauth_consumer_key: JvyS7DO2qd6NNTsXJ4E7zA oauth_signature: 1L1oXQmawZAkQ47FHLwcOV%2Bkjwc%3D oauth_version: 1.0 Content-Type: application/x-www-form-urlencoded Content-Length: 85 Connection: Keep-Alive Accept-Encoding: gzip accept-language: en,* User-Agent: Mozilla/5.0 Host: twitter.com x_auth_mode=client_auth&x_auth_password=twitter- xauth&x_auth_username=oauth_test_exec -- 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?hl=en
[twitter-dev] TwitterOauth
Is anyone else having problem with TwitterOauth and friends?
I'm trying to create friends with:
ret = @client.friend("twittername")
And the response I get is a null ret and "test" show up on the console.
Any ideas?
Thanks,
Gary Zukowski
--
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?hl=en
[twitter-dev] since_id not getting since_id :)
Hi, I've got a question about since_id and if it actually works. The API states - since_id: returns tweets with status ids greater than the given id. So when I get a list of 100 twitter messages, I store the maximum id in that group, which I get from the id property after stripping out "tag:search.twitter.com,2005:" and use that id for my since_id the next time I run the query. The problem is I've noticed I get back id's that I've already seen in previous requests when using since_id. It is fine for me I just ignore them I just thought I'd bring it to the attention of you guys, unless I've misinterpreted this functionality. Thanks, Gary
RE: [twitter-dev] Re: Twitter Platform blog post
We tweet jobs for customers to not only our accounts, but to their branded accounts as well. Companies like this because they can outsource this mechanism to a third party without getting their IT groups involved. We don't do any advertising within the tweet, other than provide a bit.ly link that takes jobseekers to more detail about the job. Are these considered ads? Is this considered a violation? In the past, the folks at Twitter have told me that we're OK, but has this changed with the new TOC? If so, there's going to be a lot of upset brand-name companies. Thanks, Gary Zukowski TweetMyJOBS.com This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -Original Message- From: Liz [mailto:nwjersey...@gmail.com] Sent: Tuesday, May 25, 2010 6:36 AM To: Twitter Development Talk Subject: [twitter-dev] Re: Twitter Platform blog post Thanks for the clarification, Ryan. This distinction isn't clear in the original blog post. I also wasn't sure what the difference was between me posting a message that I love Reebok shoes and Starbucks posting they have a special on Frappuccinos. If advertising was prohibited from Tweets, it would apply to commercial accounts as well as individual ones. But you say that's not the case. At this point, I'm not sure what services DO fall under the prohibition guidelines but I guess they are ones where the users have given advertisers blanket control to post whatever they want on their Tweetstream. In effect, this sounds like advertising spam with a third party taking over individual users' accounts. Liz nwjersey...@yahoo.com
RE: [twitter-dev] Oauth authenticated user
Dean, Exactly the same concern I have. We're going to store the access tokens in the db under their user profile, and some of our users have multiple Twitter accounts. We feel that some of them may see the big "allow" button, click it, and not realize that they are allowing the wrong Twitter account to be linked to their TMJ account. Any way around this? Thanks, Gary Zukowski TweetMyJOBS.com @garyzukowski @tweetmyjobs 704-544-9370 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. From: Dean Collins [mailto:d...@cognation.net] Sent: Wednesday, May 19, 2010 8:53 AM To: twitter-development-talk@googlegroups.com Subject: RE: [twitter-dev] Oauth authenticated user This question has been raised before. We have the same issue for our sports chat sites. I would have preferred to have the user log in each time an oauth request is made as it's frustrating when people contat us at support because their "in chat" twitter posts aren't appearing only to find the posts are being made but to someone else twitter accounts who was using the computer before and even though the browser was closed Twitter automatically sued this account when we sent the oauth requests. It's a big problem and a choice should be offered to the developer to force logout before an oauth call if this is the process flow they want to implement. Cheers, Dean _ From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of srikanth reddy Sent: Wednesday, May 19, 2010 8:46 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Oauth authenticated user I do not think forcing the user to logout is a good idea. Isn't this a security breach? Twitter will any how ask the user to signout if the user does not wish to connect to your app with the logged in account.Then he will be shown the login page and after successful authentication user will be redirected back to your app (like normal flow) On Wed, May 19, 2010 at 6:01 PM, Gary Zukowski wrote: So there's no way to automatically do this? I have to ask the user to log out? Thanks, Gary Zukowski TweetMyJOBS.com @garyzukowski @tweetmyjobs 704-544-9370 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. From: Roee A. [mailto:roe...@gmail.com] Sent: Wednesday, May 19, 2010 8:28 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Oauth authenticated user add to your code "If you are not " please log out. Then you will connect him again with the right credentials. Regards, On Wed, May 19, 2010 at 3:19 PM, Gary Zukowski wrote: What does "adf" mean? I want to force the logout and present the Twitter login when doing the authentication.. Thanks, Gary Zukowski TweetMyJOBS.com @garyzukowski @tweetmyjobs 704-544-9370 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action
RE: [twitter-dev] Oauth authenticated user
So there's no way to automatically do this? I have to ask the user to log out? Thanks, Gary Zukowski TweetMyJOBS.com @garyzukowski @tweetmyjobs 704-544-9370 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. From: Roee A. [mailto:roe...@gmail.com] Sent: Wednesday, May 19, 2010 8:28 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Oauth authenticated user add to your code "If you are not " please log out. Then you will connect him again with the right credentials. Regards, On Wed, May 19, 2010 at 3:19 PM, Gary Zukowski wrote: What does "adf" mean? I want to force the logout and present the Twitter login when doing the authentication.. Thanks, Gary Zukowski TweetMyJOBS.com @garyzukowski @tweetmyjobs 704-544-9370 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. From: Roee Aizman [mailto:roe...@gmail.com] Sent: Wednesday, May 19, 2010 7:41 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Oauth authenticated user U can adf the if you are not log out Then log again with his righr cridentials Sent by IPhone On 19/05/2010, at 14:28, "Gary Zukowski" wrote: How do I force a user to log in to Twitter during the Oauth dance, even though he/she may already be logged in to Twitter via the web? Our users may have more than one Twitter account they want to authenticate/register, and I want to make sure they are forced to put the correct credentials, and not just click "accept" for the currently logged in account. Thanks, Gary Zukowski -- Roee Aizman, CTO E: roe...@gmail.com M: +972-542345222 Amigos-Online.com Friends have never been so close
RE: [twitter-dev] Oauth authenticated user
What does “adf” mean? I want to force the logout and present the Twitter login when doing the authentication…. Thanks, Gary Zukowski TweetMyJOBS.com @garyzukowski @tweetmyjobs 704-544-9370 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. From: Roee Aizman [mailto:roe...@gmail.com] Sent: Wednesday, May 19, 2010 7:41 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Oauth authenticated user U can adf the if you are not log out Then log again with his righr cridentials Sent by IPhone On 19/05/2010, at 14:28, "Gary Zukowski" wrote: How do I force a user to log in to Twitter during the Oauth dance, even though he/she may already be logged in to Twitter via the web? Our users may have more than one Twitter account they want to authenticate/register, and I want to make sure they are forced to put the correct credentials, and not just click “accept” for the currently logged in account. Thanks, Gary Zukowski
[twitter-dev] Oauth authenticated user
How do I force a user to log in to Twitter during the Oauth dance, even though he/she may already be logged in to Twitter via the web? Our users may have more than one Twitter account they want to authenticate/register, and I want to make sure they are forced to put the correct credentials, and not just click "accept" for the currently logged in account. Thanks, Gary Zukowski
[twitter-dev] oAuth Usage Question
Hello, I just want to be clear I've understood how the oAuth works, I have setup an oauth app on twitter and have enabled my twitter account on it. When I authenticate with twitter I can call http://twitter.com/statuses/friends_timeline.xml and get the timeline. However, if I try to execute that request again, I get a 401 unauthorized saying the token has expired. Is it a correct assumption that whenever I want to access http://twitter.com/statuses/friends_timeline.xml the user has to go through the "An application would like to connect to your account" process each time? If not what do I need to store to make requests on this resource without user interaction? I'm developing this in C# but any code sample would be handy, Gary
[twitter-dev] Re: How to add an open source project into wiki?
Could you add my project into the open source project list? http://code.google.com/p/twitterbeis/ Thanks Gary On Thu, Apr 2, 2009 at 10:24 AM, Alex Payne wrote: > > Just let us know what you'd like to add. Unfortunately, we haven't > been able to run the wiki "in the open" due to PBwiki's lack of spam > protection. > > On Wed, Apr 1, 2009 at 19:51, Gary Zhao wrote: > > http://apiwiki.twitter.com/Libraries and > > http://apiwiki.twitter.com/Open-source > > > > Thanks > > -- > > Gary > > http://twitter.com/garyzhao > > > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x > -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: http://twitter.com/direct_messages/new.json failed
Exactly. It's my overlook. Thanks Alex and Doug. On Fri, Apr 10, 2009 at 9:25 AM, Doug Williams wrote: > Gary, > direct_messages/new requires a HTTP POST request. I can see from the URL > you pasted in the post that you have a query string. If you are sending a > POST request you would have no query string. > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > > On Thu, Apr 9, 2009 at 10:21 PM, Alex Payne wrote: > >> >> 400 is the response code we return for rate limiting. Are you sure >> you're making the request using an HTTP POST? What was the body of the >> response? >> >> On Thu, Apr 9, 2009 at 18:22, Gary Zhao wrote: >> > http://twitter.com/direct_messages/new.json?user=qinqi7&text=test >> > I got "The remote server returned an error: (400) Bad Request." Anything >> > wrong with this API invocation? >> > Thanks >> > >> > -- >> > Gary >> > http://twitter.com/garyzhao >> > >> >> >> >> -- >> Alex Payne - API Lead, Twitter, Inc. >> http://twitter.com/al3x >> > > -- Gary http://twitter.com/garyzhao
[twitter-dev] http://twitter.com/direct_messages/new.json failed
http://twitter.com/direct_messages/new.json?user=qinqi7&text=test I got "The remote server returned an error: (400) Bad Request." Anything wrong with this API invocation? Thanks -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: Freelance Twitter API Dev directory?
Name: Gary ZhaoTwitter: @garyzhao Email: garyz...@gmail.com Website: twitterbeis.cloudapp.net C#, Silverlight 3, Windows Azure 2009/3/31 delgaudio > > Name: Diogo Del Gaudio > > Twitter: @diogodelgaudio > Email: diogo.delgau...@gmail.com > MSN Messenger: diogo.delgau...@hotmail.com > Gtalk: diogo.delgaudio > > SqlWindows, C# and ASP.NET programmer and ruby on rails noob xD. > -- Gary http://twitter.com/garyzhao
[twitter-dev] Fwd: Your request for a Twitter source parameter has been rejected
Is there a way to change source parameter? Thanks -- Forwarded message -- From: Twitter Date: Fri, Apr 3, 2009 at 5:52 PM Subject: Your request for a Twitter source parameter has been rejected To: garyz...@gmail.com TW1TTERBEIS: Thanks for requesting a source parameter link for your application, TwitterBEIS Unfortunately, we've rejected your request. Here's why: twitterbeis is already taken, please reapply with a unique parameter Please address the issues above and submit another request if appropriate. Thanks for your interest and good luck! -- Gary http://twitter.com/garyzhao
[twitter-dev] http://twitter.com/statuses/user_timeline.json returns others tweets
I'm using http://twitter.com/statuses/user_timeline.json to retrieve my latest tweets (without any parameters, specify username and password), but the weired thing is it returns others tweets. Mine: http://twitter.com/garyzhao It returns: http://twitter.com/rejon -- Gary http://twitter.com/garyzhao
[twitter-dev] How to add an open source project into wiki?
http://apiwiki.twitter.com/Libraries and http://apiwiki.twitter.com/Open-source Thanks -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: profile_image_url in public timeline is always the static image
Same here. must be bug. On Sun, Mar 29, 2009 at 4:58 AM, CodeWarden wrote: > > Hello, > > Why is the profile_image_url in the public timeline now only ever > pointing to the image that is used if you don't set an avatar? > > I have verified that this is the case with both the JSON and XML > formats through the api, they all only point to > > http://static.twitter.com/images/default_profile_normal.png > > -Paul > -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: public_timeline, invalid profile_image?
I'm seeing it too. 2009/3/29 Günter Grodotzki > > since some days I am always getting: > > http://static.twitter.com/images/default_profile_normal.png > > as profile-image from the user via public-timeline (Data-mining-feed). > > I checked the announcement-google-group + twitter.com/twitterapi > (subscribed to feed anyway ;) ) but could not see any change. > > The site affected: www.geoheartbeat.com > > -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: Which site to show the link to my application?
Thanks a lot. 2009/3/20 Abraham Williams <4bra...@gmail.com> > Twitter.com. If your application interacts with the API and uses the source > parameter the it will show up on individual tweets like: > https://twitter.com/poseurtech/status/1356664112. See "about 17 hours ago > from Identica". The highlighted part would be replaced with TwitterBEIS. > > The pbwiki site is community based and anybody can add their application to > the list. > > > On Fri, Mar 20, 2009 at 08:21, Gary Zhao wrote: > >> I received the following email after source parameter approved. My >> question is which site is referred by the highlighted part. I checked >> http://twitter.pbwiki.com/Apps, but couldn't find my app. >> Thanks >> >> -- Forwarded message -- >> From: Twitter >> Date: 2009/3/18 >> Subject: Your request for a Twitter source parameter has been approved >> To: garyz...@gmail.com >> >> >> TW1TTERBEIS: >> >> Thanks for requesting a source parameter link for your application, >> TwitterBEIS >> >> Please have your application send a parameter named "source" >> with a value of "twitterbeis" when you POST updates to the Twitter API. >> >> The link to your application should show up on the Twitter site >> in the next 24 to 48 hours. >> >> Thanks much, and good luck with your application! >> >> >> >> -- >> Gary >> http://twitter.com/garyzhao >> > > > > -- > Abraham Williams | http://the.hackerconundrum.com > Web608 | Community Evangelist | http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from: Madison WI United States. -- Gary http://twitter.com/garyzhao
[twitter-dev] Which site to show the link to my application?
I received the following email after source parameter approved. My question is which site is referred by the highlighted part. I checked http://twitter.pbwiki.com/Apps, but couldn't find my app. Thanks -- Forwarded message -- From: Twitter Date: 2009/3/18 Subject: Your request for a Twitter source parameter has been approved To: garyz...@gmail.com TW1TTERBEIS: Thanks for requesting a source parameter link for your application, TwitterBEIS Please have your application send a parameter named "source" with a value of "twitterbeis" when you POST updates to the Twitter API. The link to your application should show up on the Twitter site in the next 24 to 48 hours. Thanks much, and good luck with your application! -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: Direct message appearing and disappearing on each refresh
Where is the right place to file bugs? On Thu, Mar 19, 2009 at 8:42 AM, Sean Spencer wrote: > I'm assuming the recent disappearing tweets issue is a known bug as well? > I filed it anyway, but it seems to be widespread enough to have already > attracted attention... > > > On Thu, Mar 19, 2009 at 11:32 AM, benjackson wrote: > >> >> Seems like Twitterfone is fine (I assume it's using different params >> as it archives locally). Though Tweetie is also FUBAR. >> >> On Mar 18, 7:53 pm, Alex Payne wrote: >> > Very much so. >> > >> > On Wed, Mar 18, 2009 at 14:43, benjackson wrote: >> > >> > > We're seeing an issue where the latest direct message is cut out of >> > > the list when refreshing, and then included/cut again upon each >> > > refresh. >> > >> > > Is this a known issue? >> > >> > -- >> > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >> > > -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: Friendship.create is confusing
Why not categorize them in three roles?I would rather consider a friend is
whom you are following and he/she follows you as well. For example, if
someone I follow but he doesn't follow me, I can't send direct messages to
him. How can I consider him as a friend? A friend should be someone you can
communicate with without boundaries. Make sense?
On Tue, Mar 17, 2009 at 1:21 PM, TjL wrote:
>
> "Follower" is clear (someone you follow)
>
> "Friend" is (kinda) clear if you know what "Follower" means
>
> ("If a Follower is someone who follows you, then a Friend must be
> someone you follow.")
>
> I understand the desire to move away from the term "Friend" as
> "Someone You Follow" (as it can be confusing) but what's the better
> word for it? Has anyone come up with one?
>
> "Followees" isn't it but it's as close as I've come.
>
>
> "Attention Getters" (those who get my attention) vs "Attention Givers"
> (those who give their attention to me) would be another way of putting
> it, but both seem too long :-)
>
> TjL
>
--
Gary
http://twitter.com/garyzhao
[twitter-dev] Re: Friendship.create is confusing
Things still confusing. As per the article, The New Terminology Things are now decidedly simpler: you follow other users, and other users follow you. You can turn notifications on and off on a per-user basis. So looks like Friendship.create is to follow someone and Notification.follow is to turn on notifications. My question is what "turn on/off" means. I found the only option on twitter.com is to follow/unfollow a user. Can I follow a user but turn off notifications? or it can only be done in program? What's your suggestion if I want to simply follow a person. Friendship.create and Notification.follow, which one should I use? Thanks Gary On Tue, Mar 17, 2009 at 1:04 PM, Doug Williams wrote: > > Gary, > Alex wrote this a while back and it suddenly seems relevant [1]. > > [1] - http://apiwiki.twitter.com/Migrating-to-followers-terminology > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > > On Tue, Mar 17, 2009 at 3:42 PM, Gary Zhao wrote: > > Hi all > > I'm sort of confused with this API. On twitter.com, my understanding is > a > > friend is someone you follow. However, there is a parameter "follow" for > > this API. That means he/she can be your friend, but you don't follow. > What > > does this mean? A friend you don't follow is what? > > Another question is when you use Notification.follow API, will the > > user specified becomes your friend automatically? Or is it possible that > you > > follow someone who's not your friend? > > Thanks > > -- > > Gary > > > > > -- Gary
[twitter-dev] Friendship.create is confusing
Hi all I'm sort of confused with this API. On twitter.com, my understanding is a friend is someone you follow. However, there is a parameter "follow" for this API. That means he/she can be your friend, but you don't follow. What does this mean? A friend you don't follow is what? Another question is when you use Notification.follow API, will the user specified becomes your friend automatically? Or is it possible that you follow someone who's not your friend? Thanks -- Gary
[twitter-dev] Re: Freelance Twitter API Dev directory?
Twitter Username: @garyc_guru URL: http://www.compgurus.net Email: com...@gmail.com Technology: PHP, CFML, JS, SQL, Python Quite Happy to hack on twitter as well. On Feb 23, 10:33 am, Alex Payne wrote: > There isn't one that I'm aware of, but if people would like to post > their contact info in this thread (Twitter username, URL, email, > whatever) I'm happy to collect them on the API Wiki. > > On Sat, Feb 21, 2009 at 18:00, Chad Etzel wrote: > > > Hi All, > > > I have been getting a few requests here and there for twitter API > > development work. I cannot take on any such projects at the moment, > > but I always feel bad for leaving them in the lurch. Is there a list > > or directory anywhere of Twitter API developers that work freelance > > that I can send to them when this happens? I'm happy to forward on > > such requests. > > > -Chad > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
