Re: [twitter-dev] Incorrect signature while getting user time line
They look fine, and since the rest of the requests work fine (which you said), I have to assume that it's not the signature generation. Also, since you're not the only one to mention this in the past 12 hours, I have to leave open the possibility of Twitter being the issue. However, before looking at that, please double check that the Base String matches what you are actually doing! Tom On 12/16/10 7:25 AM, Georgooty varghese wrote: Thanks twitter for your quick reply. I have make only one modification into my code. Other code changes do only when I get your reply. I have changed url for user time line http to https. Here I have copied my user time line base url and signature and base string. Please suggest to me a correct way for this. *Base URL* :oauth_consumer_key=*oauth_nonce=EF2k_xwovJInFfqoauth_signature_method=HMAC-SHA1oauth_timestamp=1292480095oauth_token=*oauth_version=1.0page=1screen_name=Sanoop_SP * Signature*:FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324REpV1owATZgqcsx3R6FaM0qGilyBRkkP95zwNVosGoSnc *Base string*:GEThttps%3A%2F%2Fapi.twitter.com http://2Fapi.twitter.com%2F1%2Fstatuses%2Fuser_timeline.jsonoauth_consumer_key%%26oauth_nonce%3DEF2k_xwovJInFfq%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1292480095%26oauth_token%**%26oauth_version%3D1.0%26page%3D1%26screen_name%3DSanoop_SP What mistake I have made in this. Please reply. I am waiting for your reply. Regards, George On Wed, Dec 15, 2010 at 11:21 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Hi George, There have been some changes to Twitter's API and while not all of them have been activated yet, some of them may apply to you. Incorrect signature usually means that your signature is bad. This can mean a lot of things, but if only your user_timeline part is broken, you can start by looking at these : * Make sure that the URL in the Base String does not contain the query part of an URL (= anything after (and including) the ? part of the URL) - Good: https://api.twitter.com/1/statuses/user_timeline.json - Bad: https://api.twitter.com/1/statuses/user_timeline.json?count=200 Of course, this only applies to the Base String. Making a GET request is still fine. * Make sure that you specify the correct method in the Base String. - If you are making a GET request, put GET in the Base String. * Make sure that you properly URL-encode all values in the Base String - Good: Hello%20Twitter - Bad: Hello+Twitter - (This does not really apply to user_timeline) If you checked the above and the issue is still there, please show us a sample Base String and a dump of the request you make to the Twitter API. Tom On 12/15/10 6:06 PM, Georgooty varghese wrote: Dear Twitter, I have been created a twitter application. I got xauth token for my application. I have implemented twitter functionalities like home tweets, user info, follower details, following details, user time line. These functionalities working smoothly. Also get each user time line . But Todat, usser time url is not working right now. I got incorrect signature exception.. Though usertime line qury is not working yesterday. I have no change any line code. If any change need to my coding? Anybody please help me.. I am waiting for your reply. Regards, George -- 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-dev] BUG? in_reply_to_status_id not matching in_reply_to_status_id_str
eg:
http://twitter.com/status/show/15268326762614784.json
{
retweeted: false,
created_at: Thu Dec 16 04:53:47 + 2010,
place: null,
id_str: 15268326762614784,
truncated: false,
source: a href=\http://www.echofon.com/\; rel=\nofollow
\Echofon/a,
geo: null,
favorited: false,
in_reply_to_status_id: 15265857135443968,
in_reply_to_screen_name: jbreach,
in_reply_to_status_id_str: 15265857135443969,
coordinates: null,
user: {
verified: false,
created_at: Thu Apr 02 00:45:52 + 2009,
description: Socialite. Sports Nut. Political Junkie.
\nChristian. Conservative. Patriot. \nwww.PunditLeague.us,
friends_count: 638,
profile_link_color: FF,
is_translator: false,
show_all_inline_media: false,
geo_enabled: false,
profile_sidebar_border_color: F2E195,
id_str: 28240319,
contributors_enabled: false,
location: Indianapolis,
profile_use_background_image: true,
followers_count: 914,
profile_image_url: http://a0.twimg.com/profile_images/
1187962408/aprildgregory_normal.jpg,
follow_request_sent: null,
profile_background_color: BADFCD,
url: http://HoosierAccess.com;,
notifications: null,
profile_background_image_url: http://s.twimg.com/a/1292022067/
images/themes/theme12/bg.gif,
favourites_count: 35,
screen_name: aprildgregory,
lang: en,
statuses_count: 7556,
protected: false,
profile_text_color: 0C3E53,
name: April D Gregory,
listed_count: 70,
profile_sidebar_fill_color: FFF7CC,
id: 28240319,
following: null,
profile_background_tile: false,
time_zone: Eastern Time (US Canada),
utc_offset: -18000
},
in_reply_to_user_id: 14754469,
contributors: null,
retweet_count: 0,
id: 15268326762614784,
in_reply_to_user_id_str: 14754469,
text: @jbreach Awesome! Thanks...Intern ;)
}
The in_reply_to_status_id_str is different to in_reply_to_status_id.
This can make building threaded conversations . tricky.
Andrew Horn
--
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] BUG? in_reply_to_status_id not matching in_reply_to_status_id_str
I was about to say :
I was about to say Check your parser but then I noticed that you are
right. Checked with a 64bit parser.
in_reply_to_status_id: 15265857135443968
in_reply_to_status_id_str: 15265857135443969
But then I noticed it in the source :
in_reply_to_status_id:15265857135443969,in_reply_to_status_id_str:15265857135443969
So I'm definitely going to say: Check your parser. :-)
Tom
On 12/16/10 6:39 AM, Andrew Horn wrote:
eg:
http://twitter.com/status/show/15268326762614784.json
{
retweeted: false,
created_at: Thu Dec 16 04:53:47 + 2010,
place: null,
id_str: 15268326762614784,
truncated: false,
source: a href=\http://www.echofon.com/\; rel=\nofollow
\Echofon/a,
geo: null,
favorited: false,
in_reply_to_status_id: 15265857135443968,
in_reply_to_screen_name: jbreach,
in_reply_to_status_id_str: 15265857135443969,
coordinates: null,
user: {
verified: false,
created_at: Thu Apr 02 00:45:52 + 2009,
description: Socialite. Sports Nut. Political Junkie.
\nChristian. Conservative. Patriot. \nwww.PunditLeague.us,
friends_count: 638,
profile_link_color: FF,
is_translator: false,
show_all_inline_media: false,
geo_enabled: false,
profile_sidebar_border_color: F2E195,
id_str: 28240319,
contributors_enabled: false,
location: Indianapolis,
profile_use_background_image: true,
followers_count: 914,
profile_image_url: http://a0.twimg.com/profile_images/
1187962408/aprildgregory_normal.jpg,
follow_request_sent: null,
profile_background_color: BADFCD,
url: http://HoosierAccess.com;,
notifications: null,
profile_background_image_url: http://s.twimg.com/a/1292022067/
images/themes/theme12/bg.gif,
favourites_count: 35,
screen_name: aprildgregory,
lang: en,
statuses_count: 7556,
protected: false,
profile_text_color: 0C3E53,
name: April D Gregory,
listed_count: 70,
profile_sidebar_fill_color: FFF7CC,
id: 28240319,
following: null,
profile_background_tile: false,
time_zone: Eastern Time (US Canada),
utc_offset: -18000
},
in_reply_to_user_id: 14754469,
contributors: null,
retweet_count: 0,
id: 15268326762614784,
in_reply_to_user_id_str: 14754469,
text: @jbreach Awesome! Thanks...Intern ;)
}
The in_reply_to_status_id_str is different to in_reply_to_status_id.
This can make building threaded conversations . tricky.
Andrew Horn
x
--
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] Streaming API - Multiple connections on 1 IP?
Hello everyone, Just a simple question: can I launch multiple connections to Streaming API using different accounts, but on the same machine? The official document seems don't say this clearly: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. Many thanks for the help! epomqo -- 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: getUserTimeline failing error 401 - getFriendsTimeline and getHomeTimeline still work
Heh! That's funny. I've experienced the same: getting 401 on user_timeline.json while the same call/implementation in my client was working some days ago. I just looked into it this morning and figured out that I broke my OAuth call (forgot to sort the parameters alphabetically.) After sorting them for this specific call, it was working again. Could it be that the OAuth checking for user_timeline was somehow NOT working before and accepted calls with wrong OAuth signatures? @janole On 16 Dez., 00:24, Taylor Singletary taylorsinglet...@twitter.com wrote: Can you share the exact URL you are hitting when this fails? Can you provide an example of how you are presenting your authentication (all of the request headers of your request would be helpful) -- in addition, it would be helpful if you could provide an OAuth signature basestring, and the HTTP headers sent to you in the response. Thanks, Taylor On Wed, Dec 15, 2010 at 3:18 PM, Joey joeybl...@gmail.com wrote: Hi, My twitter app, that has been working up until the last couple of days, stopped being able to retrieve the user timeline. I can hit many other pieces of the api, with Oauth authentication, and everything there works fine. It is only failing on the getting of the user timeline. Anyone having the same problems? Looks like there are some trending google searches for it the last couple of days. Thanks in advance, Joey -- 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] Error: Could not authenticate you.
What am I doing wrong here? trying to tweet a text to an account. #!/usr/bin/perl use Net::Twitter; use Net::Twitter; my $nt = Net::Twitter-new(legacy = 0); my $nt = Net::Twitter-new( traits = [qw/OAuth API::REST/], consumer_key= $consumer_key, consumer_secret = $consumer_secret, access_token= $token, access_token_secret = $token_secret, ); my $res = $nt-update(Hello World!); I am getting the error Error: Could not authenticate you. -- 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] Streaming API - Multiple connections on 1 IP?
Yes you can. On Thu, Dec 16, 2010 at 8:23 AM, epomqo wenzi0...@gmail.com wrote: Hello everyone, Just a simple question: can I launch multiple connections to Streaming API using different accounts, but on the same machine? The official document seems don't say this clearly: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. Many thanks for the help! epomqo -- 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: Streaming API - Multiple connections on 1 IP?
Many thanks! On Dec 16, 12:18 pm, Augusto Santos augu...@gemeos.org wrote: Yes you can. On Thu, Dec 16, 2010 at 8:23 AM, epomqo wenzi0...@gmail.com wrote: Hello everyone, Just a simple question: can I launch multiple connections to Streaming API using different accounts, but on the same machine? The official document seems don't say this clearly: Each account may create only one standing connection to the Streaming API. Subsequent connections from the same account may cause previously established connections to be disconnected. Excessive connection attempts, regardless of success, will result in an automatic ban of the client's IP address. Continually failing connections will result in your IP address being blacklisted from all Twitter access. Many thanks for the help! epomqo -- 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] Incorrect signature while getting user time line
Ok. Thanks Tom. What wrong I have made in this. I didn't find any issue. Could u please check the issue. I am waiting for your reply. Regards, George On Thu, Dec 16, 2010 at 1:58 PM, Tom van der Woerdt i...@tvdw.eu wrote: They look fine, and since the rest of the requests work fine (which you said), I have to assume that it's not the signature generation. Also, since you're not the only one to mention this in the past 12 hours, I have to leave open the possibility of Twitter being the issue. However, before looking at that, please double check that the Base String matches what you are actually doing! Tom On 12/16/10 7:25 AM, Georgooty varghese wrote: Thanks twitter for your quick reply. I have make only one modification into my code. Other code changes do only when I get your reply. I have changed url for user time line http to https. Here I have copied my user time line base url and signature and base string. Please suggest to me a correct way for this. *Base URL* :oauth_consumer_key=*oauth_nonce=EF2k_xwovJInFfqoauth_signature_method=HMAC-SHA1oauth_timestamp=1292480095oauth_token=*oauth_version=1.0page=1screen_name=Sanoop_SP * Signature*:FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324REpV1owATZgqcsx3R6FaM0qGilyBRkkP95zwNVosGoSnc *Base string*:GEThttps%3A%2F%2Fapi.twitter.com http://2Fapi.twitter.com %2F1%2Fstatuses%2Fuser_timeline.jsonoauth_consumer_key%%26oauth_nonce%3DEF2k_xwovJInFfq%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1292480095%26oauth_token%**%26oauth_version%3D1.0%26page%3D1%26screen_name%3DSanoop_SP What mistake I have made in this. Please reply. I am waiting for your reply. Regards, George On Wed, Dec 15, 2010 at 11:21 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Hi George, There have been some changes to Twitter's API and while not all of them have been activated yet, some of them may apply to you. Incorrect signature usually means that your signature is bad. This can mean a lot of things, but if only your user_timeline part is broken, you can start by looking at these : * Make sure that the URL in the Base String does not contain the query part of an URL (= anything after (and including) the ? part of the URL) - Good: https://api.twitter.com/1/statuses/user_timeline.json - Bad: https://api.twitter.com/1/statuses/user_timeline.json?count=200 Of course, this only applies to the Base String. Making a GET request is still fine. * Make sure that you specify the correct method in the Base String. - If you are making a GET request, put GET in the Base String. * Make sure that you properly URL-encode all values in the Base String - Good: Hello%20Twitter - Bad: Hello+Twitter - (This does not really apply to user_timeline) If you checked the above and the issue is still there, please show us a sample Base String and a dump of the request you make to the Twitter API. Tom On 12/15/10 6:06 PM, Georgooty varghese wrote: Dear Twitter, I have been created a twitter application. I got xauth token for my application. I have implemented twitter functionalities like home tweets, user info, follower details, following details, user time line. These functionalities working smoothly. Also get each user time line . But Todat, usser time url is not working right now. I got incorrect signature exception.. Though usertime line qury is not working yesterday. I have no change any line code. If any change need to my coding? Anybody please help me.. I am waiting for your reply. Regards, George -- 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-dev] search.twitter.com on IE
Hi, I have a problem accessing search.twitter.com from IE. My website is a Flash site (pure AS3 project). everything works fine on OS X and Safari, Firefox, Chrome and on windows Firefox. Is this a known problem? Something to do with the crossdomain.xml many thanks GA -- 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] Unauthorized 401
Hi,
I am trying to establish my first connection to twitter using .NET. I
get the following error when I use the demo project from internet that
is using a webrequest: Unauthorized.
{http://twitter.com/oauth/request_token?oauth_callback=http://
localhostoauth_consumer_key=#keyvalue#oauth_nonce=#keyvalue#oauth_signature_method=HMAC-
SHA1oauth_timestamp=#keyvalue#oauth_version=1.0oauth_signature=#keyvalue#}
(I replaced the real values by #keyvalue# )
I created my app in dev.twitter.com and used the consumer key and
consumer secret from there.
Anybody knows what could be the reason. I read somewhere I would need
authorization by sending a mail to a...@twitter.com. Is this true? Or
could the reason be something else?
Thank you very much in advance for any response,
Erik
--
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] Unauthorized 401
No, you don't need authorization for that.
To help you debug these issues, we need these values :
* Your request (it's safe to include everything you replaced with
#keyvalue#, just don't include any secrets (keys are fine))
* The Base String used to generate the signature
Tom
On 12/16/10 5:26 PM, Erik Bloem wrote:
Hi,
I am trying to establish my first connection to twitter using .NET. I
get the following error when I use the demo project from internet that
is using a webrequest: Unauthorized.
{http://twitter.com/oauth/request_token?oauth_callback=http://
localhostoauth_consumer_key=#keyvalue#oauth_nonce=#keyvalue#oauth_signature_method=HMAC-
SHA1oauth_timestamp=#keyvalue#oauth_version=1.0oauth_signature=#keyvalue#}
(I replaced the real values by #keyvalue# )
I created my app in dev.twitter.com and used the consumer key and
consumer secret from there.
Anybody knows what could be the reason. I read somewhere I would need
authorization by sending a mail to a...@twitter.com. Is this true? Or
could the reason be something else?
Thank you very much in advance for any response,
Erik
--
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 XAuth issues
Hi I have been attempting to implement Twitter using XAuth in an upcoming PS3 title but I am having a lot of issues with authentication, roughly 90% of my requests fail with 401 : Failed to validate oauth signature and token. I have already ruled out the usual suspect of dodgy timestamp and retry using the timestamp provided in the response headers. I have also had no issues generating matching signatures using the test data in the Twitter XAuth documentation. Any help on the matter would be most welcome. Thanks Jason Post body: x_auth_mode=client_authx_auth_password=Xx_auth_username=XX Authorisation header params: oauth_consumer_key=Xoauth_nonce=MTYyOTkxMDE4MDcxNDc5OTMwNDEyNDM0MzExNTY2NjExODQ3OTQ3oauth_signature_method=HMAC- SHA1oauth_timestamp=1292503073oauth_version=1.0x_auth_mode=client_authx_auth_password=Xx_auth_username=XX URL encoded authorisation header params: oauth_consumer_key %3DX%26oauth_nonce %3DMTYyOTkxMDE4MDcxNDc5OTMwNDEyNDM0MzExNTY2NjExODQ3OTQ3%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1292503073%26oauth_version %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3DX %26x_auth_username%3DXX Signature base string: POSThttps%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_tokenoauth_consumer_key%3DX %26oauth_nonce %3DMTYyOTkxMDE4MDcxNDc5OTMwNDEyNDM0MzExNTY2NjExODQ3OTQ3%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1292503073%26oauth_version %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3DX %26x_auth_username%3DXX Signature key: X oAuth signature: yyUGFCB4zTWHXyb73422Qgxqbgw= URL encoded oauth signature: yyUGFCB4zTWHXyb73422Qgxqbgw%3D Authorisation header: OAuth oauth_nonce=MTYyOTkxMDE4MDcxNDc5OTMwNDEyNDM0MzExNTY2NjExODQ3OTQ3, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1292503073, oauth_consumer_key=X, oauth_signature=yyUGFCB4zTWHXyb73422Qgxqbgw%3D, oauth_version=1.0 Post body: x_auth_username=XXx_auth_password=Xx_auth_mode=client_auth -- 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] Usage of site streams in production projects.
Hi, Maybe this question is asked before but I was unable to find it in the post history. At the moment we are developing an application that needs to get the timelines of many users in real time. The are many possibilities to create this solution but I think twitters site stream API looks like the perfect solution for our problem. We can setup one or maybe a few connections that enables us to get this information much easier than when using the user stream API. I played around with it for the last couple of weeks and I very enthusiastic about it to use in our current project. I wondering if it is advisable to use twitters site stream API for production applications because this is in BETA at this moment. Is there some kind of road map available for the site stream API? It will take at least a couple of months before we will release the first version of the application so the BETA it's not a problem at this moment but if there's no indication of when the BETA period will end and the site streams will go into production is it than available to use it our to still use the user stream as alternative. I hope someone can help me with this? Kind Regards, Melvin -- 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] Cell phone tower information
Hi, If tweet is posted from a cell phone. Is there a cell phone tag information when I search it using twitter Stream API? 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
[twitter-dev] .Security.Permissions.SecurityPermission,mscorlib, Version=2.0.0.0, Culture=neutral,PublicKeyToken=b77a5c561934e089'
My development environment is MS Visual Studio 2010, using VB.NET. All I need to do is post a Tweet for some of the identified status changes within my web application. I don't need user verification as the app is designed to automatically post the status change Tweet whenever it occurs. I added all 4 required values, ConsumerKey, ConsumerSecret, OAuthToken, and OAuthTokenSecret to the web.config file in the appSettings section of the configuration section. appSettings !-- Twitter and BitLy access keys -- add key=ConsumerKey value=MYCONSUMERKEY / add key=ConsumerSecret value=MYCONSUMERSECRETKEY / add key=OAuthToken value=MYAPPSOAUTHTOKENKEY / add key=OAuthTokenSecret value=MYAPPSOAUTHTOKENSECRETKEY / /appSettings I found that by going to twitter.com and signing into the account that is using the application, then go to the Settings page, go to the bottom of the page and click on the API menu option. Once the API page appears you will click on the button 2, Register An App. On the right side on the new page, you will see a button View Your Applications. If you have previously registered your app, click this button, If not fill out the application for a new app. Now at the View your Applications page, select the app you want to get the authorization keys for where is says Edit Details. Now click on the button to the right that says, Application Detail. Here you will find your Consumer Key and your Consumer Secret Key. On the right side of this page you will see the menu option My Access Token, click it and you will find your oauth_token and your oauth_token_secret keys! Now that you have all the keys, put them in the appSettings section of the web.config file. I add Dim twConn As New TwitterVB2.TwitterAPI at the top of the code behind web page. I then created a subroutine where I pass in the Tweet: Public Sub PostOnTwitter(ByVal Tweet As String) 'Retrieve Keys from web.config Dim twitterKey As String = System.Configuration.ConfigurationManager.AppSettings(ConsumerKey) Dim twitterSecret As String = System.Configuration.ConfigurationManager.AppSettings(ConsumerSecret) Dim twitterOAuthToken As String = System.Configuration.ConfigurationManager.AppSettings(OAuthToken) Dim twitterOAuthTokenSecret As String = System.Configuration.ConfigurationManager.AppSettings(OAuthTokenSecret) Try twConn.AuthenticateWith(twitterKey, twitterSecret, twitterOAuthToken, twitterOAuthTokenSecret) twConn.Update(Trim(Tweet)) Catch ex As Exception lblError.Text = Twitter Returned: ex.Message End Try End Sub This code works great on my local development, an environment that allows Full trust level. However it appears when I publish my application to my host, Rackspace.com which uses an environment of Cloud Hosting , the Trust Level is less than Full and I get an error. Twitter Returned: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. Can you tell me what I am doing wrong, and what I need to do to fix the problem? 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
[twitter-dev] List Statuses: 401 - Incorrect signature
Hey there, I've had a site up and running for quite some time now (July 2010) since Dec 14, and a little after 2:30 (Mountain) we stopped receiving tweets from that service call. After checking in on it today I discovered I was receiving a 401: Incorrect signature error. Here is my request /1/mdcpartnerssite/lists/executives/statuses.json? oauth_consumer_key=KQSwCfwSi2QEW9l6Yu8bgoauth_nonce=caf8db043f02f2612675cfc2b64755c1oauth_signature=hA6%2FA0VtOSyFAxk3Qa4InU %2FrAdo%3Doauth_signature_method=HMAC- SHA1oauth_timestamp=1292540218oauth_token=154351009-8yk6Cl0bqA9VzomDPrFsS2JmfnGgox1UHo6eZAOdoauth_version=1.0page=1per_page=200since_id=9996331253 Here is my base string GEThttp%3A%2F%2Fapi.twitter.com%2F%2F1%2Fmdcpartnerssite%2Flists %2Fexecutives%2Fstatuses.jsonoauth_consumer_key %3DKQSwCfwSi2QEW9l6Yu8bg%26oauth_nonce %3Dcaf8db043f02f2612675cfc2b64755c1%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1292540218%26oauth_token %3D154351009-8yk6Cl0bqA9VzomDPrFsS2JmfnGgox1UHo6eZAOd%26oauth_version %3D1.0%26page%3D1%26per_page%3D200%26since_id%3D9996331253 Please let me know if there is any other information you need that would help in this manner. Did something change on twitter's end that required some more strict checking, that I might not be adhering to? I've also noticed a few other's mailing in about 401 issues. Any help would be greatly appreciated. Thank you! Brian Wigginton Interactive Developer Crispin Porter + Bogusky -- 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] Hugeurl
Can someone from Twitter please confirm we can use the following undocumented API call: http://search.twitter.com/hugeurl?url=http://tinyurl.com/[alias] - [original URL] It is a very helpful tool for expanding urls return by the search api (since they don't come with entities). Thanks much in advance, @_ado -- 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] Please check you are using the correct API and host
Hey Developers, We recently reviewed a sample of your API requests, emails and support tickets and found that some of you were not using the correct domains. While undocumented domains and endpoints may respond with data, you should avoid using them as they may be disabled or changed without notice. Our network infrastructure is also updated from time to time. These changes are required for capacity planning or load balancing, but are generally transparent to you if you use the correct API host. To avoid problems or outages with your applications you need to ensure you are using the correct hosts (and base paths) for the Twitter API you want to use. Even if your code is working now, you should check the hosts match those listed below: REST API: http://api.twitter.com/1/RESOURCE OAuth: http://api.twitter.com/oauth/RESOURCE Streaming (Track): http://stream.twitter.com/1/RESOURCE Userstreams: http://userstream.twitter.com/2/user.json SiteStreams Beta: http://betastream.twitter.com/2b/site.json Search: http://search.twitter.com/search.json Tweet Button: http://platform.twitter.com/widgets.js @anywhere: http://platform.twitter.com/anywhere.js Web Widgets: http://widgets.twimg.com/j/2/widget.js Some common errors include: * Incorrectly using http://twitter.com instead of http://api.twitter.com/1/ * Incorrectly using requests like http://api.twitter.com/account/verify_credentials.json instead of http://api.twitter.com/1/account/verify_credentials.json * Incorrectly directing users to http://twitter.com/oauth/authorizeinstead of http://api.twitter.com/oauth/authorize * Incorrectly querying http://199.16.156.11/search.json instead of http://search.twitter.com/search.json You can find the documented endpoints on our developer resources site: http://dev.twitter.com Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris -- 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] Please check you are using the correct API and host
https should be preferred on many of these especially anything that is transferring protected data. 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 Thu, Dec 16, 2010 at 16:54, Matt Harris thematthar...@twitter.comwrote: Hey Developers, We recently reviewed a sample of your API requests, emails and support tickets and found that some of you were not using the correct domains. While undocumented domains and endpoints may respond with data, you should avoid using them as they may be disabled or changed without notice. Our network infrastructure is also updated from time to time. These changes are required for capacity planning or load balancing, but are generally transparent to you if you use the correct API host. To avoid problems or outages with your applications you need to ensure you are using the correct hosts (and base paths) for the Twitter API you want to use. Even if your code is working now, you should check the hosts match those listed below: REST API: http://api.twitter.com/1/RESOURCE OAuth: http://api.twitter.com/oauth/RESOURCE Streaming (Track): http://stream.twitter.com/1/RESOURCE Userstreams: http://userstream.twitter.com/2/user.json SiteStreams Beta: http://betastream.twitter.com/2b/site.json Search: http://search.twitter.com/search.json Tweet Button: http://platform.twitter.com/widgets.js @anywhere: http://platform.twitter.com/anywhere.js Web Widgets: http://widgets.twimg.com/j/2/widget.js Some common errors include: * Incorrectly using http://twitter.com instead of http://api.twitter.com/1/ * Incorrectly using requests like http://api.twitter.com/account/verify_credentials.json instead of http://api.twitter.com/1/account/verify_credentials.json * Incorrectly directing users to http://twitter.com/oauth/authorizeinstead of http://api.twitter.com/oauth/authorize * Incorrectly querying http://199.16.156.11/search.json instead of http://search.twitter.com/search.json You can find the documented endpoints on our developer resources site: http://dev.twitter.com Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris -- 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] Unauthorized 401 http://twitter.com/friends/ids.json
I keep getting unauthorized 401 error. I have been running my twitter application for months. But past couple of days, I was able to retieve very few friends information. Since Dec. 15, 6pm, I haven't been able to retrieve any. My search url is : http://twitter.com/friends/ids.json?user_id= -- 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: Different crossdomains for a0.twimg.com a2.twimg.com, a3 etc
Hi Matt, I appreciate you jumping into this thread and I look forward to your response. -Ben On Dec 16, 2:07 pm, Matt Harris thematthar...@twitter.com wrote: Thanks for letting us know about this. I've asked the team to if this file should be as restrictive as it currently is. Best @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Dec 16, 2010 at 11:16 AM, WildFoxMedia wildfoxme...@gmail.comwrote: Super, they are all returning the same thing now, which is blocking access from any non-twitter domain which you can see below: cross-domain-policy xsi:noNamespaceSchemaLocation=http:// www.adobe.com/xml/schemas/PolicyFile.xsd allow-access-from domain=twitter.com/ allow-access-from domain=api.twitter.com/ allow-access-from domain=search.twitter.com/ allow-access-from domain=static.twitter.com/ site-control permitted-cross-domain-policies=master-only/ allow-http-request-headers-from domain=*.twitter.com headers=* secure=true/ /cross-domain-policy What is Twitters official stance on this? Are Flash developers SOL and required to use a server-side proxy to grab images, or are we supposed to be able to grab profile images from *.twimg? On Dec 15, 5:57 pm, John Adams j...@twitter.com wrote: a0 through a4 should offer identical crossdomain.xml files. They are all going through a CDN, so it might be the case that the CDN endpoint you are hitting has a stale file. I just checked all of the CDN endpoints from here and they are returning the same data. Try again? -john On Wed, Dec 15, 2010 at 5:20 PM, WildFoxMedia wildfoxme...@gmail.com wrote: Im currently seeing the same issue, however, in completely reverse. As of this moment, a0 a1 are not allowing other domains and a2 a3 are allowing all domains. The other day, all 4 were not allowing other domains. Is there any reason or rhyme for this and more importantly, what is the expectation? Are we supposed to be able to make calls from Flash for profile images or not? On Nov 28, 3:57 pm, stephen sno...@bcm.com.au wrote: Hey, It appears the crossdomains for a2, a3, etc are different and are preventing flash from accessing profile images on these domains. a0 and a1 are fine, however the api returns profile image urls using all of these domains (a0 - a?). Are the crossdomains suppose to be all the same or are we suppose to target only the first two? From the few that I've tested, it seems all profile images are accessible through the a0 or a1 domains despite what the api returns. Crossdomains http://a0.twimg.com/crossdomain.xmlhttp://a1.twimg.com/crossdomain.xm. .. Stephen -- 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
