Re: [twitter-dev] Problem - SSL CA cert
Dear George, Firstly, Embeded board doesnt support any accesstokens. You should build a kind of proxy which does your Xauth and call back to the embded board apps. Regards, -Mukesh Kumar Srivastav. On Thu, Nov 25, 2010 at 5:55 PM, Georgooty varghese wrote: > Dear Twitter, > > I have developed a twitter application in C language using Libcurl. I have > used xAuth authentication.The application was working in PC as fine. I am > special thanks to twitter engineers for helping to me successfully > completion of twitter application in PC. Now I am facing a critical issue. > My C code is inegrating into embedded environment (board), I got SSL > certification pblm when query accesstoken(HTTPS). I can't get the > accesstoken. > What certificates do I need when I use SSL?. > What certification need twitter for SSL(HTTPS).? How to get the secure SSL > certificate? > > Could u 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-dev] Searching recent tweets?
Hi
There seems to be a problem with searching tweets. I can see the tweet
online but the search returns no results. Am I missing something? I
follow @twitterapi and @support so I monitor what is happening to the
feed. There doesn't seem to be any issues at the moment.
The string I'm using is:
http://search.twitter.com/search.json?q=%23flashmodfiresale
This returns the following:
{"results":[],"max_id":10256807192694784,"since_id":0,"refresh_url":"?
since_id=10256807192694784&q=%23flashmodfiresale","results_per_page":
15,"page":1,"completed_in":
0.00782,"since_id_str":"0","max_id_str":"10256807192694784","query":"%23flashmodfiresale"}
Best regards
Andre
--
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 rate limiting restricting my implementation
Hello, I am implementing an application which will download users' friends & followers as csv so that they can have backup of their data but when I am making the API call, users API call limit is getting to zero as that user is having more than 100 friends and followers and limit of 350 is getting over in one shot. I am making two API calls at a time. One is friends/ids for retrieving friends' ids and form that I am fetching users details via users/show. Is there any other way in which I can be able to retrieve the list using streaming API or something else or increasing my limit? Also users/show function is retrieving data very much slow. I am getting stuck at this point. Please help me. Thank 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] Twitter rate limiting restricting my implementation
Hello. You may try to get your app whitelisted to bump up the limits: http://dev.twitter.com/pages/rate-limiting#whitelisting On Thu, Dec 2, 2010 at 6:57 PM, computerzworld wrote: > Hello, > I am implementing an application which will download users' > friends & followers as csv so that they can have backup of their data > but when I am making the API call, users API call limit is getting to > zero as that user is having more than 100 friends and followers and > limit of 350 is getting over in one shot. I am making two API calls at > a time. One is friends/ids for retrieving friends' ids and form that I > am fetching users details via users/show. Is there any other way in > which I can be able to retrieve the list using streaming API or > something else or increasing my limit? Also users/show function is > retrieving data very much slow. I am getting stuck at this point. > Please help me. Thank 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 > -- 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] whitelist Approval refusal!!!!
Why the approval is not but I don't know ㅜㅜ continuous refusal Nothing answer back ! Did my application form go wrong? help me!! (Application Form) @fcsearch This is company of Korea operating portal website name of freechal.com We offering news, video, blog, mail, game, p2p and search engine. We are interested in your twitter service it means we prepare to use that service from December of 2010. We would like to display same keyword that result of tweets, ids, and profile images from twitter when users searching some words. This service has already provided by many websites of Korea (Naver, Daum, Nate, etc.) and they permitted white list by twitter. Also we are developing to provide that service such as other websites. It is going to be updated as often as we can also we will save data that Koreans wrote during the latest 3days. To provide near real-time services, we are using the REST API, the data is cached. ‘Oauth’ will be used for authentication, ‘twitter4J’ library is expected to be used. In this process we expect 3,000 requests per an hour the number of API calls that means it will be exceed API Limit. In that reason, we want to white list the IP address and to reduce collection cycle of tweets. We expect that will be very important part of our new service, it’s going to open December of this year. Kind Regards, The features in current use are as follows: Data for example. Features 1) Request for the all Korean users following information, & Their twitts : friends_timeline(Real-time) 2) Request for the all Korean user IDs, status(image data, etc.) : statuses/friends -- 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: Twitter rate limiting restricting my implementation
Hi, Thanks for your response. I have made a request before a week but its still not get approved. Is Twitter ignoring all requests? Or any other way can I make this work? Thanks. On Dec 2, 6:31 pm, Igor Kharin wrote: > Hello. You may try to get your app whitelisted to bump up the > limits:http://dev.twitter.com/pages/rate-limiting#whitelisting > > On Thu, Dec 2, 2010 at 6:57 PM, computerzworld wrote: > > Hello, > > I am implementing an application which will download users' > > friends & followers as csv so that they can have backup of their data > > but when I am making the API call, users API call limit is getting to > > zero as that user is having more than 100 friends and followers and > > limit of 350 is getting over in one shot. I am making two API calls at > > a time. One is friends/ids for retrieving friends' ids and form that I > > am fetching users details via users/show. Is there any other way in > > which I can be able to retrieve the list using streaming API or > > something else or increasing my limit? Also users/show function is > > retrieving data very much slow. I am getting stuck at this point. > > Please help me. Thank 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 -- 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] hot to get all friend list
dear friend,
need helpp, :)... im nubiiee in here
i want get all friend list, and i confuse how to pupulate friend from
paging..
this my code:
$cursor = -1;
if($cursor == -1 ){
$followers = $connection->get('statuses/friends',
array('id' =>
$getUserId[0] ,'cursor' =>$cursor));
}
do
{
$cursornya .= $followers->next_cursor.",";
$followers2 = $connection->get('statuses/friends',
array('id' =>
$getUserId[0] ,'cursor' => $followers->next_cursor));
echo "something";
}while($followers->next_cursor > -1 );
--
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] Searching recent tweets?
The Search Index does not include all tweets that are created on Twitter.
See this help desk article for more information:
http://support.twitter.com/articles/66018-my-tweets-or-hashtags-are-missing-from-search
Taylor
On Thu, Dec 2, 2010 at 2:55 AM, abruton wrote:
> Hi
>
> There seems to be a problem with searching tweets. I can see the tweet
> online but the search returns no results. Am I missing something? I
> follow @twitterapi and @support so I monitor what is happening to the
> feed. There doesn't seem to be any issues at the moment.
>
> The string I'm using is:
> http://search.twitter.com/search.json?q=%23flashmodfiresale
>
> This returns the following:
>
> {"results":[],"max_id":10256807192694784,"since_id":0,"refresh_url":"?
> since_id=10256807192694784&q=%23flashmodfiresale","results_per_page":
> 15,"page":1,"completed_in":
>
> 0.00782,"since_id_str":"0","max_id_str":"10256807192694784","query":"%23flashmodfiresale"}
>
> Best regards
>
> Andre
>
> --
> 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] Re: Twitter rate limiting restricting my implementation
Well, I'm pretty sure you can use multiple accounts. So that when user account limits gets exhausted you can switch to you app's one and fetch the rest. On Thu, Dec 2, 2010 at 8:57 PM, computerzworld wrote: > Hi, > Thanks for your response. I have made a request > before a week but its still not get approved. Is Twitter ignoring all > requests? Or any other way can I make this work? > > Thanks. > > On Dec 2, 6:31 pm, Igor Kharin wrote: >> Hello. You may try to get your app whitelisted to bump up the >> limits:http://dev.twitter.com/pages/rate-limiting#whitelisting >> >> On Thu, Dec 2, 2010 at 6:57 PM, computerzworld wrote: >> > Hello, >> > I am implementing an application which will download users' >> > friends & followers as csv so that they can have backup of their data >> > but when I am making the API call, users API call limit is getting to >> > zero as that user is having more than 100 friends and followers and >> > limit of 350 is getting over in one shot. I am making two API calls at >> > a time. One is friends/ids for retrieving friends' ids and form that I >> > am fetching users details via users/show. Is there any other way in >> > which I can be able to retrieve the list using streaming API or >> > something else or increasing my limit? Also users/show function is >> > retrieving data very much slow. I am getting stuck at this point. >> > Please help me. Thank 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 > > -- > 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] hot to get all friend list
You are using 'statuses/friends'. That requires OAuth, only returns
100 results at a time, and also returns the most recent tweet for each
user. That is slow, bulky, and quickly gets rate limited.
I use 'friends/ids', if all I need is a list of all friends. That
doesn't need any authentication and returns 5,000 results at a time.
Here is the PHP code I use to get all friends for a specific user. It
should be readable enough to rewrite into any language.
$http_code = 200;
$cursor = -1;
$api_call = 'http://api.twitter.com/1/friends/ids.json?user_id=' .
$target_user_id . '&cursor=';
while (($cursor != 0) && ($http_code == 200)) {
$url = $api_call . $cursor;
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_USERAGENT, "user lookup" );
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
$api = json_decode(curl_exec($ch));
$results = $api->ids;
$cursor = $api->next_cursor_str;
$header = curl_getinfo($ch);
$http_code = $header['http_code'];
if ($http_code == 200) {
foreach($results as $index => $user_id) {
// code to store friend's user_id somewhere
}
} else {
// code to log or email error report
}
}
--
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev
On Thu, Dec 2, 2010 at 3:50 AM, putri wrote:
> dear friend,
>
> need helpp, :)... im nubiiee in here
> i want get all friend list, and i confuse how to pupulate friend from
> paging..
>
> this my code:
>
> $cursor = -1;
> if($cursor == -1 ){
> $followers = $connection->get('statuses/friends',
> array('id' =>
> $getUserId[0] ,'cursor' =>$cursor));
> }
>
> do
> {
> $cursornya .= $followers->next_cursor.",";
> $followers2 = $connection->get('statuses/friends',
> array('id' =>
> $getUserId[0] ,'cursor' => $followers->next_cursor));
>
> echo "something";
>
> }while($followers->next_cursor > -1 );
>
> --
> 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] Re: Twitter rate limiting restricting my implementation
Hi computerzworld, You probably don't need whitelisting and should rethink your implementation instead. Using multiple accounts is not the right answer to get around rate limits, unless those accounts represent users engaged in your service and you are acting directly on their behalf. The quickest path to outputting a list of friends and followers to a CSV file is using the friends/ids and followers/ids API methods. For most users, each of these methods will require a single request. You then pipeline those results into users/lookup, which allows you to get the equivalent of users/show for up to 100 user ids at a time. With this pipeline, you can certainly provide CSVs of followers and followings for the majority of your users within 350 requests. If it would take more than 350 requests it's a very exceptional situation. The answer to that situation is not whitelisting. It's recognizing that some of your users will take longer to process than others. They might not get their CSV within an hour. Thanks, Taylor On Thu, Dec 2, 2010 at 7:26 AM, Igor Kharin wrote: > Well, I'm pretty sure you can use multiple accounts. So that when user > account limits gets exhausted you can switch to you app's one and > fetch the rest. > > On Thu, Dec 2, 2010 at 8:57 PM, computerzworld wrote: > > Hi, > >Thanks for your response. I have made a request > > before a week but its still not get approved. Is Twitter ignoring all > > requests? Or any other way can I make this work? > > > > Thanks. > > > > On Dec 2, 6:31 pm, Igor Kharin wrote: > >> Hello. You may try to get your app whitelisted to bump up the limits: > http://dev.twitter.com/pages/rate-limiting#whitelisting > >> > >> On Thu, Dec 2, 2010 at 6:57 PM, computerzworld > wrote: > >> > Hello, > >> > I am implementing an application which will download users' > >> > friends & followers as csv so that they can have backup of their data > >> > but when I am making the API call, users API call limit is getting to > >> > zero as that user is having more than 100 friends and followers and > >> > limit of 350 is getting over in one shot. I am making two API calls at > >> > a time. One is friends/ids for retrieving friends' ids and form that I > >> > am fetching users details via users/show. Is there any other way in > >> > which I can be able to retrieve the list using streaming API or > >> > something else or increasing my limit? Also users/show function is > >> > retrieving data very much slow. I am getting stuck at this point. > >> > Please help me. Thank 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 > > > > -- > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > API updates via Twitter: http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter rate limiting restricting my implementation
Just a note on this, but you can save one of the queries by using statuses/friends and statuses/followers rather then selecting friends/ids and followers/ids first and then doing users/lookup on batches of it, as statuses/friends will include the user information (though you will have to cursor through the list. On Thu, Dec 2, 2010 at 8:22 AM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > Hi computerzworld, > > You probably don't need whitelisting and should rethink your implementation > instead. Using multiple accounts is not the right answer to get around rate > limits, unless those accounts represent users engaged in your service and > you are acting directly on their behalf. > > The quickest path to outputting a list of friends and followers to a CSV > file is using the friends/ids and followers/ids API methods. For most users, > each of these methods will require a single request. You then pipeline those > results into users/lookup, which allows you to get the equivalent of > users/show for up to 100 user ids at a time. > > With this pipeline, you can certainly provide CSVs of followers and > followings for the majority of your users within 350 requests. If it would > take more than 350 requests it's a very exceptional situation. The answer to > that situation is not whitelisting. It's recognizing that some of your users > will take longer to process than others. They might not get their CSV within > an hour. > > Thanks, > Taylor > > > On Thu, Dec 2, 2010 at 7:26 AM, Igor Kharin wrote: > >> Well, I'm pretty sure you can use multiple accounts. So that when user >> account limits gets exhausted you can switch to you app's one and >> fetch the rest. >> >> On Thu, Dec 2, 2010 at 8:57 PM, computerzworld >> wrote: >> > Hi, >> >Thanks for your response. I have made a request >> > before a week but its still not get approved. Is Twitter ignoring all >> > requests? Or any other way can I make this work? >> > >> > Thanks. >> > >> > On Dec 2, 6:31 pm, Igor Kharin wrote: >> >> Hello. You may try to get your app whitelisted to bump up the limits: >> http://dev.twitter.com/pages/rate-limiting#whitelisting >> >> >> >> On Thu, Dec 2, 2010 at 6:57 PM, computerzworld >> wrote: >> >> > Hello, >> >> > I am implementing an application which will download users' >> >> > friends & followers as csv so that they can have backup of their data >> >> > but when I am making the API call, users API call limit is getting to >> >> > zero as that user is having more than 100 friends and followers and >> >> > limit of 350 is getting over in one shot. I am making two API calls >> at >> >> > a time. One is friends/ids for retrieving friends' ids and form that >> I >> >> > am fetching users details via users/show. Is there any other way in >> >> > which I can be able to retrieve the list using streaming API or >> >> > something else or increasing my limit? Also users/show function is >> >> > retrieving data very much slow. I am getting stuck at this point. >> >> > Please help me. Thank 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 >> > >> > -- >> > 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] Re: Searching recent tweets?
Thank you. Didn't know about this. This seriously affects my new
venture... will have to rethink it...
Damm. Any way to include a person in the index? Search enough times
will include it? Or something similar?
Thanks
Andre
On Dec 2, 4:58 pm, Taylor Singletary
wrote:
> The Search Index does not include all tweets that are created on Twitter.
> See this help desk article for more
> information:http://support.twitter.com/articles/66018-my-tweets-or-hashtags-are-m...
>
> Taylor
>
>
>
>
>
>
>
> On Thu, Dec 2, 2010 at 2:55 AM, abruton wrote:
> > Hi
>
> > There seems to be a problem with searching tweets. I can see the tweet
> > online but the search returns no results. Am I missing something? I
> > follow @twitterapi and @support so I monitor what is happening to the
> > feed. There doesn't seem to be any issues at the moment.
>
> > The string I'm using is:
> >http://search.twitter.com/search.json?q=%23flashmodfiresale
>
> > This returns the following:
>
> > {"results":[],"max_id":10256807192694784,"since_id":0,"refresh_url":"?
> > since_id=10256807192694784&q=%23flashmodfiresale","results_per_page":
> > 15,"page":1,"completed_in":
>
> > 0.00782,"since_id_str":"0","max_id_str":"10256807192694784","query":"%23fla
> > shmodfiresale"}
>
> > Best regards
>
> > Andre
>
> > --
> > 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] Re: Searching recent tweets?
Hi Andre,
You may find the Streaming API more suitable for this:
http://dev.twitter.com/pages/streaming_api
The streaming API allows you to 'track' words and have the Tweets which match
streamed directly to you. That way, as long as you have an open connection to
the Streaming API, Tweets will be streamed to you almost the instant they are
created.
Hope that helps,
@themattharris
On Dec 2, 2010, at 9:41, abruton wrote:
> Thank you. Didn't know about this. This seriously affects my new
> venture... will have to rethink it...
>
> Damm. Any way to include a person in the index? Search enough times
> will include it? Or something similar?
>
> Thanks
>
> Andre
>
> On Dec 2, 4:58 pm, Taylor Singletary
> wrote:
>> The Search Index does not include all tweets that are created on Twitter.
>> See this help desk article for more
>> information:http://support.twitter.com/articles/66018-my-tweets-or-hashtags-are-m...
>>
>> Taylor
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Dec 2, 2010 at 2:55 AM, abruton wrote:
>>> Hi
>>
>>> There seems to be a problem with searching tweets. I can see the tweet
>>> online but the search returns no results. Am I missing something? I
>>> follow @twitterapi and @support so I monitor what is happening to the
>>> feed. There doesn't seem to be any issues at the moment.
>>
>>> The string I'm using is:
>>> http://search.twitter.com/search.json?q=%23flashmodfiresale
>>
>>> This returns the following:
>>
>>> {"results":[],"max_id":10256807192694784,"since_id":0,"refresh_url":"?
>>> since_id=10256807192694784&q=%23flashmodfiresale","results_per_page":
>>> 15,"page":1,"completed_in":
>>
>>> 0.00782,"since_id_str":"0","max_id_str":"10256807192694784","query":"%23fla
>>> shmodfiresale"}
>>
>>> Best regards
>>
>>> Andre
>>
>>> --
>>> 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: User_Timeline - include_rts not working
I'm having the same problem. This doesn't make much sense. It also seems to still count deleted tweets, which seems like lousy behavior. I assume they do this cut down on query paramters and thus server overload, but it still stinks, especially since there is no user- available programatic way to detect that this happening and thus compensating for it. -- 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] Re: User_Timeline - include_rts not working
Hi, Can you share the full URL you are requesting so I can take a closer look. Thanks. --- @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Dec 2, 2010 at 10:30 AM, dt wrote: > I'm having the same problem. This doesn't make much sense. It also > seems to still count deleted tweets, which seems like lousy behavior. > I assume they do this cut down on query paramters and thus server > overload, but it still stinks, especially since there is no user- > available programatic way to detect that this happening and thus > compensating for it. > > -- > 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] whitelist Approval refusal!!!!
This looks like something you could implement using the Streaming API, using REST and Search to fill in the missing pieces. If you're working in PHP, have a look at Adam Green's open source library at http://140dev.com/free-twitter-api-source-code-library/ and the Phirehose library. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb "A mathematician is a device for turning coffee into theorems." - Paul Erdos Quoting moneekun : Why the approval is not but I don't know ㅜㅜ continuous refusal Nothing answer back ! Did my application form go wrong? help me!! (Application Form) @fcsearch This is company of Korea operating portal website name of freechal.com We offering news, video, blog, mail, game, p2p and search engine. We are interested in your twitter service it means we prepare to use that service from December of 2010. We would like to display same keyword that result of tweets, ids, and profile images from twitter when users searching some words. This service has already provided by many websites of Korea (Naver, Daum, Nate, etc.) and they permitted white list by twitter. Also we are developing to provide that service such as other websites. It is going to be updated as often as we can also we will save data that Koreans wrote during the latest 3days. To provide near real-time services, we are using the REST API, the data is cached. ‘Oauth’ will be used for authentication, ‘twitter4J’ library is expected to be used. In this process we expect 3,000 requests per an hour the number of API calls that means it will be exceed API Limit. In that reason, we want to white list the IP address and to reduce collection cycle of tweets. We expect that will be very important part of our new service, it’s going to open December of this year. Kind Regards, The features in current use are as follows: Data for example. Features 1) Request for the all Korean users following information, & Their twitts : friends_timeline(Real-time) 2) Request for the all Korean user IDs, status(image data, etc.) : statuses/friends -- 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] whitelist Approval refusal!!!!
mabey your computer is slow On Thu, Dec 2, 2010 at 15:08, M. Edward (Ed) Borasky < zn...@borasky-research.net> wrote: > This looks like something you could implement using the Streaming API, > using REST and Search to fill in the missing pieces. If you're working in > PHP, have a look at Adam Green's open source library at > http://140dev.com/free-twitter-api-source-code-library/ and the Phirehose > library. > > -- > M. Edward (Ed) Borasky > http://borasky-research.net http://twitter.com/znmeb > > "A mathematician is a device for turning coffee into theorems." - Paul > Erdos > > > Quoting moneekun : > > Why the approval is not but I don't know ㅜㅜ >> continuous refusal >> Nothing answer back ! >> Did my application form go wrong? >> help me!! >> >> >> (Application Form) >> @fcsearch >> >> This is company of Korea operating portal website name of >> freechal.com >> We offering news, video, blog, mail, game, p2p and search engine. >> >> We are interested in your twitter service it means we prepare to use >> that service from December of 2010. >> >> We would like to display same keyword that result of tweets, ids, and >> profile images from twitter when users searching some words. >> >> This service has already provided by many websites of Korea (Naver, >> Daum, Nate, etc.) and they permitted white list by twitter. Also we >> are developing to provide that service such as other websites. >> >> It is going to be updated as often as we can also we will save data >> that Koreans wrote during the latest 3days. >> >> To provide near real-time services, we are using the REST API, the >> data is cached. >> ‘Oauth’ will be used for authentication, ‘twitter4J’ library is >> expected to be used. >> In this process we expect 3,000 requests per an hour the number of API >> calls that means it will be exceed API Limit. In that reason, we want >> to white list the IP address and to reduce collection cycle of >> tweets. >> >> We expect that will be very important part of our new service, it’s >> going to open December of this year. >> Kind Regards, >> >> The features in current use are as follows: Data for example. >> >> Features >> 1) Request for the all Korean users following information, & Their >> twitts : friends_timeline(Real-time) >> 2) Request for the all Korean user IDs, status(image data, etc.) : >> statuses/friends >> >> -- >> 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] Display tweets according to the design guidelines
Hi there, I want to use the Twitter search API and display tweets formatted according to http://dev.twitter.com/pages/display_guidelines How do I go from a tweet in JSON format to the specified format without having to do the string manipulation myself? Is there a javascript tool that can do this? 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] oAuth still working for everyone.?
I noticed I've just started getting 401's for all my oAuth requests. Seems to be happening on more than one site for me.. My application keys and status still look good.. Just wondering if anyone else is having an issue..? -- 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] Display tweets according to the design guidelines
I do this with a combination of text templates containing HTML and CSS. You can use PHP on a server to take JSON data from the API and place it into the HTML template. Then embed it into a web page and format the tweets with CSS. On the client side you can use Javascript to allow the user to pull in more tweets, and display a count of new tweets since the page was loaded. This gives you the SEO benefit of having the tweets in your original Web page, and the interactive UI with Javascript. What you don't want to do is call the Twitter API directly from Javascript in the web page. That is slower, and the tweets are invisible to Google. I have an open source framework for this model of tweet display at: http://140dev.com/free-twitter-api-source-code-library/twitter-display/ The documentation page on code architecture will show you how all the steps work together. You can contact me if you have any questions about setting it up. On Thu, Dec 2, 2010 at 4:00 PM, Daniel wrote: > Hi there, > > I want to use the Twitter search API and display tweets formatted > according to http://dev.twitter.com/pages/display_guidelines > > How do I go from a tweet in JSON format to the specified format > without having to do the string manipulation myself? Is there a > javascript tool that can do this? > > 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 > -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- 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: oAuth still working for everyone.?
I'm seeing a lot of invalid/expired token errors. On Dec 2, 9:21 pm, Dave-twiends wrote: > I noticed I've just started getting 401's for all my oAuth requests. > Seems to be happening on more than one site for me.. My application > keys and status still look good.. > > Just wondering if anyone else is having an issue..? -- 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] Re: oAuth still working for everyone.?
We've corrected a number of long-standing OAuth-related bug fixes -- mainly in areas where we more liberal than we should have been when verifying signatures. Here are a few things to verify: * Verify that you are using your consumer key where the consumer key is supposed to go. Compare this to what you see for you app on dev.twitter.com * Likewise, verify that you are using your consumer secret where it is supposed to go. Compare this to what you see for you app on dev.twitter.com * Laugh at the obviousness and absurdity of a check like that. Cry a little because we already know some people were doing the wrong thing here, especially on end points that didn't require authentication. * Verify that your timestamps are in range * If you're sending a request to a resource that doesn't require authentication but you're including OAuth credentials: - we used to just give you a free pass even if the credentials were incorrect. Hey, it doesn't require auth, so why bother checking? - now we check this. if you pass us an OAuth header or anything that looks like an OAuth-based request, we will check it for validity, even if it's a resource that doesn't require auth. We haven't changed anything about our actual core signature validation code -- what was a valid signature before should be a valid one now. We're just checking the validity in more use cases than we were previously, and checking other validity points we were flexible with previously. Taylor On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger wrote: > I'm seeing a lot of invalid/expired token errors. > > On Dec 2, 9:21 pm, Dave-twiends wrote: > > I noticed I've just started getting 401's for all my oAuth requests. > > Seems to be happening on more than one site for me.. My application > > keys and status still look good.. > > > > Just wondering if anyone else is having an issue..? > > -- > 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: oAuth still working for everyone.?
Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months ago, before most of the libraries were out, so there could be anything wrong. It's probably not 100% spec compliant, which is probably why it broke. I've tracked down the issue to the access_token exchange part of the process. The access token's that I have from before are still working, just can't get new ones. I've noticed I'm not passing oauth_verifier back in the request, which could be causing the issue.. Will let you guys know how I get on... Thanks for the pointers Dave On Dec 2, 9:57 pm, Taylor Singletary wrote: > We've corrected a number of long-standing OAuth-related bug fixes -- mainly > in areas where we more liberal than we should have been when verifying > signatures. > > Here are a few things to verify: > > * Verify that you are using your consumer key where the consumer key is > supposed to go. Compare this to what you see for you app on dev.twitter.com > * Likewise, verify that you are using your consumer secret where it is > supposed to go. Compare this to what you see for you app on dev.twitter.com > * Laugh at the obviousness and absurdity of a check like that. Cry a little > because we already know some people were doing the wrong thing here, > especially on end points that didn't require authentication. > * Verify that your timestamps are in range > * If you're sending a request to a resource that doesn't require > authentication but you're including OAuth credentials: > - we used to just give you a free pass even if the credentials were > incorrect. Hey, it doesn't require auth, so why bother checking? > - now we check this. if you pass us an OAuth header or anything that > looks like an OAuth-based request, we will check it for validity, even if > it's a resource that doesn't require auth. > > We haven't changed anything about our actual core signature validation code > -- what was a valid signature before should be a valid one now. We're just > checking the validity in more use cases than we were previously, and > checking other validity points we were flexible with previously. > > Taylor > > On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger wrote: > > > > > > > > > I'm seeing a lot of invalid/expired token errors. > > > On Dec 2, 9:21 pm, Dave-twiends wrote: > > > I noticed I've just started getting 401's for all my oAuth requests. > > > Seems to be happening on more than one site for me.. My application > > > keys and status still look good.. > > > > Just wondering if anyone else is having an issue..? > > > -- > > 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: oAuth still working for everyone.?
I am using this library on all my sites: https://github.com/jmathai/twitter-async, all of which are now broken and fail to let anyone log in. Any way this can be rolled back until all the various oAuth libraries people are using are brought up to date? Lee On Dec 2, 5:35 pm, Dave-twiends wrote: > Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months > ago, before most of the libraries were out, so there could be anything > wrong. It's probably not 100% spec compliant, which is probably why it > broke. > > I've tracked down the issue to the access_token exchange part of the > process. The access token's that I have from before are still working, > just can't get new ones. I've noticed I'm not passing oauth_verifier > back in the request, which could be causing the issue.. > > Will let you guys know how I get on... > > Thanks for the pointers > Dave > > On Dec 2, 9:57 pm, Taylor Singletary > wrote: > > > We've corrected a number of long-standing OAuth-related bug fixes -- mainly > > in areas where we more liberal than we should have been when verifying > > signatures. > > > Here are a few things to verify: > > > * Verify that you are using your consumer key where the consumer key is > > supposed to go. Compare this to what you see for you app on dev.twitter.com > > * Likewise, verify that you are using your consumer secret where it is > > supposed to go. Compare this to what you see for you app on dev.twitter.com > > * Laugh at the obviousness and absurdity of a check like that. Cry a little > > because we already know some people were doing the wrong thing here, > > especially on end points that didn't require authentication. > > * Verify that your timestamps are in range > > * If you're sending a request to a resource that doesn't require > > authentication but you're including OAuth credentials: > > - we used to just give you a free pass even if the credentials were > > incorrect. Hey, it doesn't require auth, so why bother checking? > > - now we check this. if you pass us an OAuth header or anything that > > looks like an OAuth-based request, we will check it for validity, even if > > it's a resource that doesn't require auth. > > > We haven't changed anything about our actual core signature validation code > > -- what was a valid signature before should be a valid one now. We're just > > checking the validity in more use cases than we were previously, and > > checking other validity points we were flexible with previously. > > > Taylor > > > On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger > > wrote: > > > > I'm seeing a lot of invalid/expired token errors. > > > > On Dec 2, 9:21 pm, Dave-twiends wrote: > > > > I noticed I've just started getting 401's for all my oAuth requests. > > > > Seems to be happening on more than one site for me.. My application > > > > keys and status still look good.. > > > > > Just wondering if anyone else is having an issue..? > > > > -- > > > 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] Re: oAuth still working for everyone.?
Waiting doesn't help solve the issue. The spec hasn't changed, the API is just a bit more watching for the mistakes which some developers tend to make. I'd recommend diving into the code and fixing the errors, instead of asking the Twitter API team to accept your "broken" OAuth implementations. :-) Tom On 12/2/10 11:42 PM, LeeS - @semel wrote: I am using this library on all my sites: https://github.com/jmathai/twitter-async, all of which are now broken and fail to let anyone log in. Any way this can be rolled back until all the various oAuth libraries people are using are brought up to date? Lee On Dec 2, 5:35 pm, Dave-twiends wrote: Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months ago, before most of the libraries were out, so there could be anything wrong. It's probably not 100% spec compliant, which is probably why it broke. I've tracked down the issue to the access_token exchange part of the process. The access token's that I have from before are still working, just can't get new ones. I've noticed I'm not passing oauth_verifier back in the request, which could be causing the issue.. Will let you guys know how I get on... Thanks for the pointers Dave On Dec 2, 9:57 pm, Taylor Singletary wrote: We've corrected a number of long-standing OAuth-related bug fixes -- mainly in areas where we more liberal than we should have been when verifying signatures. Here are a few things to verify: * Verify that you are using your consumer key where the consumer key is supposed to go. Compare this to what you see for you app on dev.twitter.com * Likewise, verify that you are using your consumer secret where it is supposed to go. Compare this to what you see for you app on dev.twitter.com * Laugh at the obviousness and absurdity of a check like that. Cry a little because we already know some people were doing the wrong thing here, especially on end points that didn't require authentication. * Verify that your timestamps are in range * If you're sending a request to a resource that doesn't require authentication but you're including OAuth credentials: - we used to just give you a free pass even if the credentials were incorrect. Hey, it doesn't require auth, so why bother checking? - now we check this. if you pass us an OAuth header or anything that looks like an OAuth-based request, we will check it for validity, even if it's a resource that doesn't require auth. We haven't changed anything about our actual core signature validation code -- what was a valid signature before should be a valid one now. We're just checking the validity in more use cases than we were previously, and checking other validity points we were flexible with previously. Taylor On Thu, Dec 2, 2010 at 1:32 PM, Twitlongerwrote: I'm seeing a lot of invalid/expired token errors. On Dec 2, 9:21 pm, Dave-twiends wrote: I noticed I've just started getting 401's for all my oAuth requests. Seems to be happening on more than one site for me.. My application keys and status still look good.. Just wondering if anyone else is having an issue..? -- 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] Re: oAuth still working for everyone.?
Hi Folks, We're going to rollback a subset of these changes for now. Before we give this another try, we'll let everyone know the specific pain points and give some time to adjust to them. In the meantime, those who experienced trouble today will want to verify that their libraries are doing the right thing in regard to the bullet points I posted above. Also useful is making sure that you don't send additional headers related to basic auth in an OAuth request, that you're using the proper, versioned api-subdomain end points, etc. Dave: It's pretty crucial that you send an oauth_verifier on the access token step. It's not valid OAuth 1.0a without it. Sorry about the mess folks. We should never have let these bugs persist for so long. Taylor On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > Waiting doesn't help solve the issue. The spec hasn't changed, the API is > just a bit more watching for the mistakes which some developers tend to > make. > > I'd recommend diving into the code and fixing the errors, instead of asking > the Twitter API team to accept your "broken" OAuth implementations. :-) > > Tom > > > > On 12/2/10 11:42 PM, LeeS - @semel wrote: > >> I am using this library on all my sites: >> https://github.com/jmathai/twitter-async, >> all of which are now broken and fail to let anyone log in. >> >> Any way this can be rolled back until all the various oAuth libraries >> people are using are brought up to date? >> >> Lee >> >> On Dec 2, 5:35 pm, Dave-twiends wrote: >> >>> Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months >>> ago, before most of the libraries were out, so there could be anything >>> wrong. It's probably not 100% spec compliant, which is probably why it >>> broke. >>> >>> I've tracked down the issue to the access_token exchange part of the >>> process. The access token's that I have from before are still working, >>> just can't get new ones. I've noticed I'm not passing oauth_verifier >>> back in the request, which could be causing the issue.. >>> >>> Will let you guys know how I get on... >>> >>> Thanks for the pointers >>> Dave >>> >>> On Dec 2, 9:57 pm, Taylor Singletary >>> wrote: >>> >>> We've corrected a number of long-standing OAuth-related bug fixes -- mainly in areas where we more liberal than we should have been when verifying signatures. >>> >>> Here are a few things to verify: >>> >>> * Verify that you are using your consumer key where the consumer key is supposed to go. Compare this to what you see for you app on dev.twitter.com * Likewise, verify that you are using your consumer secret where it is supposed to go. Compare this to what you see for you app on dev.twitter.com * Laugh at the obviousness and absurdity of a check like that. Cry a little because we already know some people were doing the wrong thing here, especially on end points that didn't require authentication. * Verify that your timestamps are in range * If you're sending a request to a resource that doesn't require authentication but you're including OAuth credentials: - we used to just give you a free pass even if the credentials were incorrect. Hey, it doesn't require auth, so why bother checking? - now we check this. if you pass us an OAuth header or anything that looks like an OAuth-based request, we will check it for validity, even if it's a resource that doesn't require auth. >>> >>> We haven't changed anything about our actual core signature validation code -- what was a valid signature before should be a valid one now. We're just checking the validity in more use cases than we were previously, and checking other validity points we were flexible with previously. >>> >>> Taylor >>> >>> On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger>>> >wrote: >>> >>> I'm seeing a lot of invalid/expired token errors. > >>> On Dec 2, 9:21 pm, Dave-twiends wrote: > >> I noticed I've just started getting 401's for all my oAuth requests. >> Seems to be happening on more than one site for me.. My application >> keys and status still look good.. >> > >>> Just wondering if anyone else is having an issue..? >> > >>> -- > 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-ta
[twitter-dev] Re: oAuth still working for everyone.?
That may be so but a little warning would have been nice. Obviously you knew people were using the wrong practice in mass scale. Educating people that they were doing so before you made the change would have been nice. -- 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: oAuth still working for everyone.?
Thanks, I'm up again, looks like it was just oauth_verifier that I was missing... Phew.. I'll take some time this week to read the spec in detail and make sure I'm not missing anything else.. Thanks Dave On Dec 2, 10:59 pm, Taylor Singletary wrote: > Hi Folks, > > We're going to rollback a subset of these changes for now. Before we give > this another try, we'll let everyone know the specific pain points and give > some time to adjust to them. In the meantime, those who experienced trouble > today will want to verify that their libraries are doing the right thing in > regard to the bullet points I posted above. > > Also useful is making sure that you don't send additional headers related to > basic auth in an OAuth request, that you're using the proper, versioned > api-subdomain end points, etc. > > Dave: It's pretty crucial that you send an oauth_verifier on the access > token step. It's not valid OAuth 1.0a without it. > > Sorry about the mess folks. We should never have let these bugs persist for > so long. > > Taylor > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > > > > > > > > > Waiting doesn't help solve the issue. The spec hasn't changed, the API is > > just a bit more watching for the mistakes which some developers tend to > > make. > > > I'd recommend diving into the code and fixing the errors, instead of asking > > the Twitter API team to accept your "broken" OAuth implementations. :-) > > > Tom > > > On 12/2/10 11:42 PM, LeeS - @semel wrote: > > >> I am using this library on all my sites: > >>https://github.com/jmathai/twitter-async, > >> all of which are now broken and fail to let anyone log in. > > >> Any way this can be rolled back until all the various oAuth libraries > >> people are using are brought up to date? > > >> Lee > > >> On Dec 2, 5:35 pm, Dave-twiends wrote: > > >>> Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months > >>> ago, before most of the libraries were out, so there could be anything > >>> wrong. It's probably not 100% spec compliant, which is probably why it > >>> broke. > > >>> I've tracked down the issue to the access_token exchange part of the > >>> process. The access token's that I have from before are still working, > >>> just can't get new ones. I've noticed I'm not passing oauth_verifier > >>> back in the request, which could be causing the issue.. > > >>> Will let you guys know how I get on... > > >>> Thanks for the pointers > >>> Dave > > >>> On Dec 2, 9:57 pm, Taylor Singletary > >>> wrote: > > >>> We've corrected a number of long-standing OAuth-related bug fixes -- > mainly > in areas where we more liberal than we should have been when verifying > signatures. > > >>> Here are a few things to verify: > > >>> * Verify that you are using your consumer key where the consumer key is > supposed to go. Compare this to what you see for you app on > dev.twitter.com > * Likewise, verify that you are using your consumer secret where it is > supposed to go. Compare this to what you see for you app on > dev.twitter.com > * Laugh at the obviousness and absurdity of a check like that. Cry a > little > because we already know some people were doing the wrong thing here, > especially on end points that didn't require authentication. > * Verify that your timestamps are in range > * If you're sending a request to a resource that doesn't require > authentication but you're including OAuth credentials: > - we used to just give you a free pass even if the credentials were > incorrect. Hey, it doesn't require auth, so why bother checking? > - now we check this. if you pass us an OAuth header or anything that > looks like an OAuth-based request, we will check it for validity, even > if > it's a resource that doesn't require auth. > > >>> We haven't changed anything about our actual core signature validation > code > -- what was a valid signature before should be a valid one now. We're > just > checking the validity in more use cases than we were previously, and > checking other validity points we were flexible with previously. > > >>> Taylor > > >>> On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger >wrote: > > >>> I'm seeing a lot of invalid/expired token errors. > > >>> On Dec 2, 9:21 pm, Dave-twiends wrote: > > >> I noticed I've just started getting 401's for all my oAuth requests. > >> Seems to be happening on more than one site for me.. My application > >> keys and status still look good.. > > >>> Just wondering if anyone else is having an issue..? > > >>> -- > > 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/twi
[twitter-dev] Re: oAuth still working for everyone.?
The open source library I was using omitted oauth_verifier, which apparently was not required for oauth to work previously. Thanks to Dave & Taylor for pointing this out. Lee On Dec 2, 6:09 pm, Dave-twiends wrote: > Thanks, I'm up again, looks like it was just oauth_verifier that I was > missing... Phew.. > > I'll take some time this week to read the spec in detail and make sure > I'm not missing anything else.. > > Thanks > Dave > > On Dec 2, 10:59 pm, Taylor Singletary > wrote: > > > Hi Folks, > > > We're going to rollback a subset of these changes for now. Before we give > > this another try, we'll let everyone know the specific pain points and give > > some time to adjust to them. In the meantime, those who experienced trouble > > today will want to verify that their libraries are doing the right thing in > > regard to the bullet points I posted above. > > > Also useful is making sure that you don't send additional headers related to > > basic auth in an OAuth request, that you're using the proper, versioned > > api-subdomain end points, etc. > > > Dave: It's pretty crucial that you send an oauth_verifier on the access > > token step. It's not valid OAuth 1.0a without it. > > > Sorry about the mess folks. We should never have let these bugs persist for > > so long. > > > Taylor > > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > > > > Waiting doesn't help solve the issue. The spec hasn't changed, the API is > > > just a bit more watching for the mistakes which some developers tend to > > > make. > > > > I'd recommend diving into the code and fixing the errors, instead of > > > asking > > > the Twitter API team to accept your "broken" OAuth implementations. :-) > > > > Tom > > > > On 12/2/10 11:42 PM, LeeS - @semel wrote: > > > >> I am using this library on all my sites: > > >>https://github.com/jmathai/twitter-async, > > >> all of which are now broken and fail to let anyone log in. > > > >> Any way this can be rolled back until all the various oAuth libraries > > >> people are using are brought up to date? > > > >> Lee > > > >> On Dec 2, 5:35 pm, Dave-twiends wrote: > > > >>> Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months > > >>> ago, before most of the libraries were out, so there could be anything > > >>> wrong. It's probably not 100% spec compliant, which is probably why it > > >>> broke. > > > >>> I've tracked down the issue to the access_token exchange part of the > > >>> process. The access token's that I have from before are still working, > > >>> just can't get new ones. I've noticed I'm not passing oauth_verifier > > >>> back in the request, which could be causing the issue.. > > > >>> Will let you guys know how I get on... > > > >>> Thanks for the pointers > > >>> Dave > > > >>> On Dec 2, 9:57 pm, Taylor Singletary > > >>> wrote: > > > >>> We've corrected a number of long-standing OAuth-related bug fixes -- > > mainly > > in areas where we more liberal than we should have been when verifying > > signatures. > > > >>> Here are a few things to verify: > > > >>> * Verify that you are using your consumer key where the consumer key is > > supposed to go. Compare this to what you see for you app on > > dev.twitter.com > > * Likewise, verify that you are using your consumer secret where it is > > supposed to go. Compare this to what you see for you app on > > dev.twitter.com > > * Laugh at the obviousness and absurdity of a check like that. Cry a > > little > > because we already know some people were doing the wrong thing here, > > especially on end points that didn't require authentication. > > * Verify that your timestamps are in range > > * If you're sending a request to a resource that doesn't require > > authentication but you're including OAuth credentials: > > - we used to just give you a free pass even if the credentials were > > incorrect. Hey, it doesn't require auth, so why bother checking? > > - now we check this. if you pass us an OAuth header or anything that > > looks like an OAuth-based request, we will check it for validity, even > > if > > it's a resource that doesn't require auth. > > > >>> We haven't changed anything about our actual core signature validation > > code > > -- what was a valid signature before should be a valid one now. We're > > just > > checking the validity in more use cases than we were previously, and > > checking other validity points we were flexible with previously. > > > >>> Taylor > > > >>> On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger > >wrote: > > > >>> I'm seeing a lot of invalid/expired token errors. > > > >>> On Dec 2, 9:21 pm, Dave-twiends wrote: > > > >> I noticed I've just started getting 401's for all my oAuth requests. > > >> Seems to be happening on more than one site for me.. My application > > >> keys and status still look good.. > > > >>>
Re: [twitter-dev] Re: oAuth still working for everyone.?
Hey Taylor, Thanks for rolling this back. It seems odd that you'd push this out without notice when you know it will break apps. Or was there notice somewhere? Can you deploy your new code to a test endpoint so people (myself included) can test that their new code complies with your new requirements? Cheers, Tim. On Fri, Dec 3, 2010 at 7:59 AM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > Hi Folks, > > We're going to rollback a subset of these changes for now. Before we give > this another try, we'll let everyone know the specific pain points and give > some time to adjust to them. In the meantime, those who experienced trouble > today will want to verify that their libraries are doing the right thing in > regard to the bullet points I posted above. > > Also useful is making sure that you don't send additional headers related > to basic auth in an OAuth request, that you're using the proper, versioned > api-subdomain end points, etc. > > Dave: It's pretty crucial that you send an oauth_verifier on the access > token step. It's not valid OAuth 1.0a without it. > > Sorry about the mess folks. We should never have let these bugs persist for > so long. > > Taylor > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > >> Waiting doesn't help solve the issue. The spec hasn't changed, the API is >> just a bit more watching for the mistakes which some developers tend to >> make. >> >> I'd recommend diving into the code and fixing the errors, instead of >> asking the Twitter API team to accept your "broken" OAuth implementations. >> :-) >> >> Tom >> >> >> >> On 12/2/10 11:42 PM, LeeS - @semel wrote: >> >>> I am using this library on all my sites: >>> https://github.com/jmathai/twitter-async, >>> all of which are now broken and fail to let anyone log in. >>> >>> Any way this can be rolled back until all the various oAuth libraries >>> people are using are brought up to date? >>> >>> Lee >>> >>> On Dec 2, 5:35 pm, Dave-twiends wrote: >>> Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months ago, before most of the libraries were out, so there could be anything wrong. It's probably not 100% spec compliant, which is probably why it broke. I've tracked down the issue to the access_token exchange part of the process. The access token's that I have from before are still working, just can't get new ones. I've noticed I'm not passing oauth_verifier back in the request, which could be causing the issue.. Will let you guys know how I get on... Thanks for the pointers Dave On Dec 2, 9:57 pm, Taylor Singletary wrote: We've corrected a number of long-standing OAuth-related bug fixes -- > mainly > in areas where we more liberal than we should have been when verifying > signatures. > Here are a few things to verify: > * Verify that you are using your consumer key where the consumer key is > supposed to go. Compare this to what you see for you app on > dev.twitter.com > * Likewise, verify that you are using your consumer secret where it is > supposed to go. Compare this to what you see for you app on > dev.twitter.com > * Laugh at the obviousness and absurdity of a check like that. Cry a > little > because we already know some people were doing the wrong thing here, > especially on end points that didn't require authentication. > * Verify that your timestamps are in range > * If you're sending a request to a resource that doesn't require > authentication but you're including OAuth credentials: >- we used to just give you a free pass even if the credentials were > incorrect. Hey, it doesn't require auth, so why bother checking? >- now we check this. if you pass us an OAuth header or anything that > looks like an OAuth-based request, we will check it for validity, even > if > it's a resource that doesn't require auth. > We haven't changed anything about our actual core signature validation > code > -- what was a valid signature before should be a valid one now. We're > just > checking the validity in more use cases than we were previously, and > checking other validity points we were flexible with previously. > Taylor > On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger >wrote: > I'm seeing a lot of invalid/expired token errors. >> > On Dec 2, 9:21 pm, Dave-twiends wrote: >> >>> I noticed I've just started getting 401's for all my oAuth requests. >>> Seems to be happening on more than one site for me.. My application >>> keys and status still look good.. >>> >> Just wondering if anyone else is having an issue..? >>> >> -- >> Twitter developer documentation and resources: >> http://dev.twitter.com/doc >> API updates via Twitter
[twitter-dev] Re: oAuth still working for everyone.?
I am using TwitterEPI library. Mine was out of date. Uploaded the newest version and my app now works. Mark On Dec 2, 7:06 pm, Tim Haines wrote: > Hey Taylor, > > Thanks for rolling this back. It seems odd that you'd push this out without > notice when you know it will break apps. Or was there notice somewhere? > > Can you deploy your new code to a test endpoint so people (myself included) > can test that their new code complies with your new requirements? > > Cheers, > > Tim. > > On Fri, Dec 3, 2010 at 7:59 AM, Taylor Singletary < > > taylorsinglet...@twitter.com> wrote: > > Hi Folks, > > > We're going to rollback a subset of these changes for now. Before we give > > this another try, we'll let everyone know the specific pain points and give > > some time to adjust to them. In the meantime, those who experienced trouble > > today will want to verify that their libraries are doing the right thing in > > regard to the bullet points I posted above. > > > Also useful is making sure that you don't send additional headers related > > to basic auth in an OAuth request, that you're using the proper, versioned > > api-subdomain end points, etc. > > > Dave: It's pretty crucial that you send an oauth_verifier on the access > > token step. It's not valid OAuth 1.0a without it. > > > Sorry about the mess folks. We should never have let these bugs persist for > > so long. > > > Taylor > > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > > >> Waiting doesn't help solve the issue. The spec hasn't changed, the API is > >> just a bit more watching for the mistakes which some developers tend to > >> make. > > >> I'd recommend diving into the code and fixing the errors, instead of > >> asking the Twitter API team to accept your "broken" OAuth implementations. > >> :-) > > >> Tom > > >> On 12/2/10 11:42 PM, LeeS - @semel wrote: > > >>> I am using this library on all my sites: > >>>https://github.com/jmathai/twitter-async, > >>> all of which are now broken and fail to let anyone log in. > > >>> Any way this can be rolled back until all the various oAuth libraries > >>> people are using are brought up to date? > > >>> Lee > > >>> On Dec 2, 5:35 pm, Dave-twiends wrote: > > Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months > ago, before most of the libraries were out, so there could be anything > wrong. It's probably not 100% spec compliant, which is probably why it > broke. > > I've tracked down the issue to the access_token exchange part of the > process. The access token's that I have from before are still working, > just can't get new ones. I've noticed I'm not passing oauth_verifier > back in the request, which could be causing the issue.. > > Will let you guys know how I get on... > > Thanks for the pointers > Dave > > On Dec 2, 9:57 pm, Taylor Singletary > wrote: > > We've corrected a number of long-standing OAuth-related bug fixes -- > > mainly > > in areas where we more liberal than we should have been when verifying > > signatures. > > Here are a few things to verify: > > * Verify that you are using your consumer key where the consumer key is > > supposed to go. Compare this to what you see for you app on > > dev.twitter.com > > * Likewise, verify that you are using your consumer secret where it is > > supposed to go. Compare this to what you see for you app on > > dev.twitter.com > > * Laugh at the obviousness and absurdity of a check like that. Cry a > > little > > because we already know some people were doing the wrong thing here, > > especially on end points that didn't require authentication. > > * Verify that your timestamps are in range > > * If you're sending a request to a resource that doesn't require > > authentication but you're including OAuth credentials: > > - we used to just give you a free pass even if the credentials were > > incorrect. Hey, it doesn't require auth, so why bother checking? > > - now we check this. if you pass us an OAuth header or anything that > > looks like an OAuth-based request, we will check it for validity, even > > if > > it's a resource that doesn't require auth. > > We haven't changed anything about our actual core signature validation > > code > > -- what was a valid signature before should be a valid one now. We're > > just > > checking the validity in more use cases than we were previously, and > > checking other validity points we were flexible with previously. > > Taylor > > On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger > >wrote: > > I'm seeing a lot of invalid/expired token errors. > > On Dec 2, 9:21 pm, Dave-twiends wrote: > > >>> I noticed I've just started getting 401's for all my oAuth requests. > >>> Seems to be happening on more than one site for me.. My application > >>> keys and status sti
[twitter-dev] Twitter's OAuth provider ... what happened?
Getting this error back from Twitter -- /oauth/access_token?oauth_consumer_key=((elided))&oauth_nonce=((elided))&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1291335791&oauth_token=((elided))&oauth_version=1.0&oauth_signature=((elided)) Invalid / expired Token This is on newly "Allow"'ed tokens from Twitter's OAuth. What gives? -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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] Twitter's OAuth provider ... what happened?
Also, getting this error response, too: /oauth/access_token?oauth_consumer_key=((elided))&oauth_nonce=((elided))&oauth_signature_method=((elided))&oauth_timestamp=((elided))&oauth_token=((elided))&oauth_version=((elided))&oauth_signature=((elided)) Invalid oauth_verifier parameter On 12/2/10 7:25 PM, Dossy Shiobara wrote: > Getting this error back from Twitter -- > > > > /oauth/access_token?oauth_consumer_key=((elided))&oauth_nonce=((elided))&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1291335791&oauth_token=((elided))&oauth_version=1.0&oauth_signature=((elided)) > Invalid / expired Token > > > This is on newly "Allow"'ed tokens from Twitter's OAuth. What gives? > -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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: oAuth still working for everyone.?
Yep - oauth_verifier broke it here. Previously, if one was using the callback flow you had to make the verifier blank in order for it to work. Patched my custom Obj-C OAuth flow to put it back in place. - B. On Dec 2, 7:19 pm, kprobe wrote: > I am using TwitterEPI library. Mine was out of date. Uploaded the > newest version and my app now works. > Mark > > On Dec 2, 7:06 pm, Tim Haines wrote: > > > > > Hey Taylor, > > > Thanks for rolling this back. It seems odd that you'd push this out without > > notice when you know it will break apps. Or was there notice somewhere? > > > Can you deploy your new code to a test endpoint so people (myself included) > > can test that their new code complies with your new requirements? > > > Cheers, > > > Tim. > > > On Fri, Dec 3, 2010 at 7:59 AM, Taylor Singletary < > > > taylorsinglet...@twitter.com> wrote: > > > Hi Folks, > > > > We're going to rollback a subset of these changes for now. Before we give > > > this another try, we'll let everyone know the specific pain points and > > > give > > > some time to adjust to them. In the meantime, those who experienced > > > trouble > > > today will want to verify that their libraries are doing the right thing > > > in > > > regard to the bullet points I posted above. > > > > Also useful is making sure that you don't send additional headers related > > > to basic auth in an OAuth request, that you're using the proper, versioned > > > api-subdomain end points, etc. > > > > Dave: It's pretty crucial that you send an oauth_verifier on the access > > > token step. It's not valid OAuth 1.0a without it. > > > > Sorry about the mess folks. We should never have let these bugs persist > > > for > > > so long. > > > > Taylor > > > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > > > >> Waiting doesn't help solve the issue. The spec hasn't changed, the API is > > >> just a bit more watching for the mistakes which some developers tend to > > >> make. > > > >> I'd recommend diving into the code and fixing the errors, instead of > > >> asking the Twitter API team to accept your "broken" OAuth > > >> implementations. > > >> :-) > > > >> Tom > > > >> On 12/2/10 11:42 PM, LeeS - @semel wrote: > > > >>> I am using this library on all my sites: > > >>>https://github.com/jmathai/twitter-async, > > >>> all of which are now broken and fail to let anyone log in. > > > >>> Any way this can be rolled back until all the various oAuth libraries > > >>> people are using are brought up to date? > > > >>> Lee > > > >>> On Dec 2, 5:35 pm, Dave-twiends wrote: > > > Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months > > ago, before most of the libraries were out, so there could be anything > > wrong. It's probably not 100% spec compliant, which is probably why it > > broke. > > > I've tracked down the issue to the access_token exchange part of the > > process. The access token's that I have from before are still working, > > just can't get new ones. I've noticed I'm not passing oauth_verifier > > back in the request, which could be causing the issue.. > > > Will let you guys know how I get on... > > > Thanks for the pointers > > Dave > > > On Dec 2, 9:57 pm, Taylor Singletary > > wrote: > > > We've corrected a number of long-standing OAuth-related bug fixes -- > > > mainly > > > in areas where we more liberal than we should have been when verifying > > > signatures. > > > Here are a few things to verify: > > > * Verify that you are using your consumer key where the consumer key > > is > > > supposed to go. Compare this to what you see for you app on > > > dev.twitter.com > > > * Likewise, verify that you are using your consumer secret where it is > > > supposed to go. Compare this to what you see for you app on > > > dev.twitter.com > > > * Laugh at the obviousness and absurdity of a check like that. Cry a > > > little > > > because we already know some people were doing the wrong thing here, > > > especially on end points that didn't require authentication. > > > * Verify that your timestamps are in range > > > * If you're sending a request to a resource that doesn't require > > > authentication but you're including OAuth credentials: > > > - we used to just give you a free pass even if the credentials were > > > incorrect. Hey, it doesn't require auth, so why bother checking? > > > - now we check this. if you pass us an OAuth header or anything > > > that > > > looks like an OAuth-based request, we will check it for validity, even > > > if > > > it's a resource that doesn't require auth. > > > We haven't changed anything about our actual core signature validation > > > code > > > -- what was a valid signature before should be a valid one now. We're > > > just > > > checking the validity in more use cases than
[twitter-dev] Re: Twitter's OAuth provider ... what happened?
I'm getting the same error since this afternoon, any ideas??? 401:Authentication credentials were missing or incorrect. Invalid oauth_verifier parameter /oauth/access_token -- 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: oAuth still working for everyone.?
Anyone using PHP can use https://github.com/abraham/twitteroauth . It supports the oauth_verifier (as of its most recent update). Earlier versions of twitteroauth didn't support it and had a different parameter order for making requests, so if you're updating, be sure to check those things out. This guide will help those looking to be walked through a bit too - http://blancer.com/tutorials/73877/how-to-authenticate-users-with-twitter-oauth/ On Dec 2, 7:19 pm, kprobe wrote: > I am using TwitterEPI library. Mine was out of date. Uploaded the > newest version and my app now works. > Mark > > On Dec 2, 7:06 pm, Tim Haines wrote: > > > > > > > > > Hey Taylor, > > > Thanks for rolling this back. It seems odd that you'd push this out without > > notice when you know it will break apps. Or was there notice somewhere? > > > Can you deploy your new code to a test endpoint so people (myself included) > > can test that their new code complies with your new requirements? > > > Cheers, > > > Tim. > > > On Fri, Dec 3, 2010 at 7:59 AM, Taylor Singletary < > > > taylorsinglet...@twitter.com> wrote: > > > Hi Folks, > > > > We're going to rollback a subset of these changes for now. Before we give > > > this another try, we'll let everyone know the specific pain points and > > > give > > > some time to adjust to them. In the meantime, those who experienced > > > trouble > > > today will want to verify that their libraries are doing the right thing > > > in > > > regard to the bullet points I posted above. > > > > Also useful is making sure that you don't send additional headers related > > > to basic auth in an OAuth request, that you're using the proper, versioned > > > api-subdomain end points, etc. > > > > Dave: It's pretty crucial that you send an oauth_verifier on the access > > > token step. It's not valid OAuth 1.0a without it. > > > > Sorry about the mess folks. We should never have let these bugs persist > > > for > > > so long. > > > > Taylor > > > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > > > >> Waiting doesn't help solve the issue. The spec hasn't changed, the API is > > >> just a bit more watching for the mistakes which some developers tend to > > >> make. > > > >> I'd recommend diving into the code and fixing the errors, instead of > > >> asking the Twitter API team to accept your "broken" OAuth > > >> implementations. > > >> :-) > > > >> Tom > > > >> On 12/2/10 11:42 PM, LeeS - @semel wrote: > > > >>> I am using this library on all my sites: > > >>>https://github.com/jmathai/twitter-async, > > >>> all of which are now broken and fail to let anyone log in. > > > >>> Any way this can be rolled back until all the various oAuth libraries > > >>> people are using are brought up to date? > > > >>> Lee > > > >>> On Dec 2, 5:35 pm, Dave-twiends wrote: > > > Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months > > ago, before most of the libraries were out, so there could be anything > > wrong. It's probably not 100% spec compliant, which is probably why it > > broke. > > > I've tracked down the issue to the access_token exchange part of the > > process. The access token's that I have from before are still working, > > just can't get new ones. I've noticed I'm not passing oauth_verifier > > back in the request, which could be causing the issue.. > > > Will let you guys know how I get on... > > > Thanks for the pointers > > Dave > > > On Dec 2, 9:57 pm, Taylor Singletary > > wrote: > > > We've corrected a number of long-standing OAuth-related bug fixes -- > > > mainly > > > in areas where we more liberal than we should have been when verifying > > > signatures. > > > Here are a few things to verify: > > > * Verify that you are using your consumer key where the consumer key > > is > > > supposed to go. Compare this to what you see for you app on > > > dev.twitter.com > > > * Likewise, verify that you are using your consumer secret where it is > > > supposed to go. Compare this to what you see for you app on > > > dev.twitter.com > > > * Laugh at the obviousness and absurdity of a check like that. Cry a > > > little > > > because we already know some people were doing the wrong thing here, > > > especially on end points that didn't require authentication. > > > * Verify that your timestamps are in range > > > * If you're sending a request to a resource that doesn't require > > > authentication but you're including OAuth credentials: > > > - we used to just give you a free pass even if the credentials were > > > incorrect. Hey, it doesn't require auth, so why bother checking? > > > - now we check this. if you pass us an OAuth header or anything > > > that > > > looks like an OAuth-based request, we will check it for validity, even > > > if > > > it's a resource that doesn't require auth. > > >
Re: [twitter-dev] Re: oAuth still working for everyone.?
My library is also OAuth 1.0a compliant: https://github.com/themattharris/tmhOAuth @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Dec 2, 2010 at 4:55 PM, Mike Davis (mcdavis) wrote: > Anyone using PHP can use https://github.com/abraham/twitteroauth . > It supports the oauth_verifier (as of its most recent update). > Earlier versions of twitteroauth didn't support it and had a different > parameter order for making requests, so if you're updating, be sure to > check those things out. > > This guide will help those looking to be walked through a bit too - > > http://blancer.com/tutorials/73877/how-to-authenticate-users-with-twitter-oauth/ > > On Dec 2, 7:19 pm, kprobe wrote: > > I am using TwitterEPI library. Mine was out of date. Uploaded the > > newest version and my app now works. > > Mark > > > > On Dec 2, 7:06 pm, Tim Haines wrote: > > > > > > > > > > > > > > > > > Hey Taylor, > > > > > Thanks for rolling this back. It seems odd that you'd push this out > without > > > notice when you know it will break apps. Or was there notice > somewhere? > > > > > Can you deploy your new code to a test endpoint so people (myself > included) > > > can test that their new code complies with your new requirements? > > > > > Cheers, > > > > > Tim. > > > > > On Fri, Dec 3, 2010 at 7:59 AM, Taylor Singletary < > > > > > taylorsinglet...@twitter.com> wrote: > > > > Hi Folks, > > > > > > We're going to rollback a subset of these changes for now. Before we > give > > > > this another try, we'll let everyone know the specific pain points > and give > > > > some time to adjust to them. In the meantime, those who experienced > trouble > > > > today will want to verify that their libraries are doing the right > thing in > > > > regard to the bullet points I posted above. > > > > > > Also useful is making sure that you don't send additional headers > related > > > > to basic auth in an OAuth request, that you're using the proper, > versioned > > > > api-subdomain end points, etc. > > > > > > Dave: It's pretty crucial that you send an oauth_verifier on the > access > > > > token step. It's not valid OAuth 1.0a without it. > > > > > > Sorry about the mess folks. We should never have let these bugs > persist for > > > > so long. > > > > > > Taylor > > > > > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt > wrote: > > > > > >> Waiting doesn't help solve the issue. The spec hasn't changed, the > API is > > > >> just a bit more watching for the mistakes which some developers tend > to > > > >> make. > > > > > >> I'd recommend diving into the code and fixing the errors, instead of > > > >> asking the Twitter API team to accept your "broken" OAuth > implementations. > > > >> :-) > > > > > >> Tom > > > > > >> On 12/2/10 11:42 PM, LeeS - @semel wrote: > > > > > >>> I am using this library on all my sites: > > > >>>https://github.com/jmathai/twitter-async, > > > >>> all of which are now broken and fail to let anyone log in. > > > > > >>> Any way this can be rolled back until all the various oAuth > libraries > > > >>> people are using are brought up to date? > > > > > >>> Lee > > > > > >>> On Dec 2, 5:35 pm, Dave-twiends wrote: > > > > > Thanks Taylor, yip unfortunately I wrote my oauth code about 18 > months > > > ago, before most of the libraries were out, so there could be > anything > > > wrong. It's probably not 100% spec compliant, which is probably > why it > > > broke. > > > > > I've tracked down the issue to the access_token exchange part of > the > > > process. The access token's that I have from before are still > working, > > > just can't get new ones. I've noticed I'm not passing > oauth_verifier > > > back in the request, which could be causing the issue.. > > > > > Will let you guys know how I get on... > > > > > Thanks for the pointers > > > Dave > > > > > On Dec 2, 9:57 pm, Taylor Singletary > > > > wrote: > > > > > We've corrected a number of long-standing OAuth-related bug fixes > -- > > > > mainly > > > > in areas where we more liberal than we should have been when > verifying > > > > signatures. > > > > > Here are a few things to verify: > > > > > * Verify that you are using your consumer key where the consumer > key is > > > > supposed to go. Compare this to what you see for you app on > > > > dev.twitter.com > > > > * Likewise, verify that you are using your consumer secret where > it is > > > > supposed to go. Compare this to what you see for you app on > > > > dev.twitter.com > > > > * Laugh at the obviousness and absurdity of a check like that. > Cry a > > > > little > > > > because we already know some people were doing the wrong thing > here, > > > > especially on end points that didn't require authentication. > > > > * Verify that your timestamps are in range > > > > * If you're sending a request to a resource that doesn
Re: [twitter-dev] Re: Twitter's OAuth provider ... what happened?
Looking at your examples it looks like you don't have the oauth_verifier included in your request. The oauth_verifier can be found in the request parameters of the callback we make to you. Try adding the parameter in to see if that resolves the issue. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Dec 2, 2010 at 4:46 PM, Hector wrote: > > I'm getting the same error since this afternoon, any ideas??? > > 401:Authentication credentials were missing or incorrect. Invalid > oauth_verifier parameter /oauth/access_token > > -- > 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: oAuth still working for everyone.?
Does anyone using twitter4j solve the oauth_verifier issue? 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] Re: oAuth still working for everyone.?
Update to the latest version. oauth_verifier was added earlier this month. On Dec 2, 3:41 pm, "LeeS - @semel" wrote: > The open source library I was using omitted oauth_verifier, which > apparently was not required for oauth to work previously. > > Thanks to Dave & Taylor for pointing this out. > > Lee > > On Dec 2, 6:09 pm, Dave-twiends wrote: > > > Thanks, I'm up again, looks like it was just oauth_verifier that I was > > missing... Phew.. > > > I'll take some time this week to read the spec in detail and make sure > > I'm not missing anything else.. > > > Thanks > > Dave > > > On Dec 2, 10:59 pm, Taylor Singletary > > wrote: > > > > Hi Folks, > > > > We're going to rollback a subset of these changes for now. Before we give > > > this another try, we'll let everyone know the specific pain points and > > > give > > > some time to adjust to them. In the meantime, those who experienced > > > trouble > > > today will want to verify that their libraries are doing the right thing > > > in > > > regard to the bullet points I posted above. > > > > Also useful is making sure that you don't send additional headers related > > > to > > > basic auth in an OAuth request, that you're using the proper, versioned > > > api-subdomain end points, etc. > > > > Dave: It's pretty crucial that you send an oauth_verifier on the access > > > token step. It's not valid OAuth 1.0a without it. > > > > Sorry about the mess folks. We should never have let these bugs persist > > > for > > > so long. > > > > Taylor > > > > On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt wrote: > > > > > Waiting doesn't help solve the issue. The spec hasn't changed, the API > > > > is > > > > just a bit more watching for the mistakes which some developers tend to > > > > make. > > > > > I'd recommend diving into the code and fixing the errors, instead of > > > > asking > > > > the Twitter API team to accept your "broken" OAuth implementations. :-) > > > > > Tom > > > > > On 12/2/10 11:42 PM, LeeS - @semel wrote: > > > > >> I am using this library on all my sites: > > > >>https://github.com/jmathai/twitter-async, > > > >> all of which are now broken and fail to let anyone log in. > > > > >> Any way this can be rolled back until all the various oAuth libraries > > > >> people are using are brought up to date? > > > > >> Lee > > > > >> On Dec 2, 5:35 pm, Dave-twiends wrote: > > > > >>> Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months > > > >>> ago, before most of the libraries were out, so there could be anything > > > >>> wrong. It's probably not 100% spec compliant, which is probably why it > > > >>> broke. > > > > >>> I've tracked down the issue to the access_token exchange part of the > > > >>> process. The access token's that I have from before are still working, > > > >>> just can't get new ones. I've noticed I'm not passing oauth_verifier > > > >>> back in the request, which could be causing the issue.. > > > > >>> Will let you guys know how I get on... > > > > >>> Thanks for the pointers > > > >>> Dave > > > > >>> On Dec 2, 9:57 pm, Taylor Singletary > > > >>> wrote: > > > > >>> We've corrected a number of long-standing OAuth-related bug fixes -- > > > mainly > > > in areas where we more liberal than we should have been when > > > verifying > > > signatures. > > > > >>> Here are a few things to verify: > > > > >>> * Verify that you are using your consumer key where the consumer key > > > >>> is > > > supposed to go. Compare this to what you see for you app on > > > dev.twitter.com > > > * Likewise, verify that you are using your consumer secret where it > > > is > > > supposed to go. Compare this to what you see for you app on > > > dev.twitter.com > > > * Laugh at the obviousness and absurdity of a check like that. Cry a > > > little > > > because we already know some people were doing the wrong thing here, > > > especially on end points that didn't require authentication. > > > * Verify that your timestamps are in range > > > * If you're sending a request to a resource that doesn't require > > > authentication but you're including OAuth credentials: > > > - we used to just give you a free pass even if the credentials > > > were > > > incorrect. Hey, it doesn't require auth, so why bother checking? > > > - now we check this. if you pass us an OAuth header or anything > > > that > > > looks like an OAuth-based request, we will check it for validity, > > > even > > > if > > > it's a resource that doesn't require auth. > > > > >>> We haven't changed anything about our actual core signature > > > >>> validation > > > code > > > -- what was a valid signature before should be a valid one now. We're > > > just > > > checking the validity in more use cases than we were previously, and > > > checking other validity points we were flexible with previ
Re: [twitter-dev] Re: Twitter's OAuth provider ... what happened?
Looks like that was it ... updated my OAuth consumer and now things are working again. Was this announced somewhere and I totally missed it? On 12/2/10 8:07 PM, Matt Harris wrote: > Looking at your examples it looks like you don't have the > oauth_verifier included in your request. The oauth_verifier can be > found in the request parameters of the callback we make to you. > > Try adding the parameter in to see if that resolves the issue. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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: randomly 401 error
Hello Matt, I've try the case without basic Auth, but still 401 http://9.share.photo.xuite.net/u9011022/19d3103/4424859/171517288_x.jpg On 12月1日, 上午9時57分, Matt Harris wrote: > Hi Alvin, > > I notice in your request that you are sending a Basic Authentication header > in addition to the OAuth. Specifically the line: > Authorization: Basic > > When using OAuth this is not required and will be confusing the request. > Specifically you are sending OAuth in the request but telling the API to > authorise using Basic Auth. What you should do is either drop the > Authorization header completley, or move the OAuth parameters into the > Authorization header. > > A possible reason why some of your requests are working and others are > failing is that some methods do not require authentication. In those cases > the failing authentication details you are sending are being ignored and the > request is most likely running unauthenticated. > > Best, > @themattharris > Developer Advocate, Twitterhttp://twitter.com/themattharris > > 2010/11/30 Alvin Wang > > > > > > > > > Hey, > > > still same. > >http://9.share.photo.xuite.net/u9011022/19d31e2/4424859/171241799_x.jpg > > > On 11月30日, 上午2時39分, themattharris wrote: > > > Hi Alvin, > > > > The error in that response tells me your signature is incorrect. > > > Double check you are generating your signature using the algorithm > > > described here: > > >http://dev.twitter.com/auth#signing-requests > > > > In particular I notice the parameters in your GET request are not in > > > lexicographical order, and so I wonder if they may not be in order in > > > your signature base string. > > > > Best, > > > Matt > > > > On Nov 24, 10:10 pm, Alvin Wang wrote: > > > > > hello, Matt > > > > > After removing the symbol "&" and parameter realm, the frequency of > > > > 401 is lower. > > > > But it becomes the problem as I attach below > > > > >http://9.share.photo.xuite.net/u9011022/19d319b/4424859/170775808_x.jpg > > > > > On 11月25日, 上午2時32分, Matt Harris wrote: > > > > > > Hey Alvin, > > > > > > Your URL looks badly formed as it includes > > > > > .../home_timeline.json?&count=5 I would expect to see > > > > > .../home_timeline.json?count=5... > > > > > (so no & after the ?). You also have realm in your query string when > > it > > > > > isn't needed. Realm is optional and when used, is only used in the > > > > > Authorization header. When using OAuth in the query string you > > shouldn't > > > > > pass realm. Your parameters should also be in lexicographical order. > > > > > > In your case I would have expected your URL to look like this: > > >http://api.twitter.com/1/statuses/home_timeline.json?count=5&oauth_co... > > > > > &page=1 > > > > > > You can read more about signing requests on our developer resources > > site: > > > > >http://dev.twitter.com/pages/auth#signing-requests > > > > > > Best > > > > > @themattharris > > > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > 2010/11/23 Alvin Wang > > > > > > > hello Matt, > > > > > > here is the image when 401 occurs. > > > > > > >http://dl.dropbox.com/u/162763/1.png > > > > > > > On 11月23日, 下午2時17分, Matt Harris wrote: > > > > > > > Hey Alvin, > > > > > > > > So the community and developers can help you we'll need to know a > > little > > > > > > bit > > > > > > > more about the error you are receiving. Things like the API > > request you > > > > > > are > > > > > > > making, the request basestring, and the full response you get > > back are > > > > > > good > > > > > > > things to include. > > > > > > > > Be careful to not include any passwords or OAuth secrets in > > anything you > > > > > > > share. > > > > > > > > Best, > > > > > > > @themattharris > > > > > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > > 2010/11/22 Alvin Wang > > > > > > > > > Are there any other solutions? Retry will still got > > 401randomly. Just > > > > > > > > wondering is there any twitter tech person can help? > > > > > > > > > On 11月23日, 上午3時28分, Nick Bradbury > > wrote: > > > > > > > > > I also ran into this problem, even though I knew the > > signature was > > > > > > > > > fine. This post from a Twitter "Developer Advocate" > > indicates that > > > > > > > > a401may be due to Twitter being stressed: > > >http://www.devcomments.com/re-intermittent-401-and-502-during-oauth-p... > > > > > > > > > > In my case, ignoring the401and resending the request a little > > later > > > > > > > > > solved the problem the majority of the time. > > > > > > > > > > On Nov 22, 2:43 am, Alvin Wang wrote: > > > > > > > > > > > Hi, > > > > > > > > > > I am currently developing an application using twitter api. > > > > > > > > > > However, i will ramdomly receive401error (invalid > > signature). > > > > > > > > > > Sometime it's working fine but sometime are not. > > > > > > > > > > Can you please help us to resolve this problem? > > > > > > > > > > > BR, > > > > > > > > > > Alvin-
[twitter-dev] Re: oAuth still working for everyone.?
Hi, I had confirmed the error message several hours ago and was looking into it. And somehow I don't see the error now. Please give it a try once again. If the problem persists, please post the exception stacktrace to twitte...@googlegroups.com. http://twitter4j.org/en/index.html#mailingList Thanks, Yusuke On Dec 3, 10:09 am, Hector wrote: > Does anyone using twitter4j solve the oauth_verifier issue? > > 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
Re: [twitter-dev] Re: randomly 401 error
Hi Alvin, It looks like your oauth_signature is not URL encoded. For example you have + in your signature when it should be %2B. Double check you are URL encoding the your parameters correctly. Best, @themattharris On Dec 2, 2010, at 22:10, Alvin Wang wrote: > Hello Matt, > > I've try the case without basic Auth, but still 401 > > http://9.share.photo.xuite.net/u9011022/19d3103/4424859/171517288_x.jpg > > On 12月1日, 上午9時57分, Matt Harris wrote: >> Hi Alvin, >> >> I notice in your request that you are sending a Basic Authentication header >> in addition to the OAuth. Specifically the line: >>Authorization: Basic >> >> When using OAuth this is not required and will be confusing the request. >> Specifically you are sending OAuth in the request but telling the API to >> authorise using Basic Auth. What you should do is either drop the >> Authorization header completley, or move the OAuth parameters into the >> Authorization header. >> >> A possible reason why some of your requests are working and others are >> failing is that some methods do not require authentication. In those cases >> the failing authentication details you are sending are being ignored and the >> request is most likely running unauthenticated. >> >> Best, >> @themattharris >> Developer Advocate, Twitterhttp://twitter.com/themattharris >> >> 2010/11/30 Alvin Wang >> >> >> >> >> >> >> >>> Hey, >> >>> still same. >>> http://9.share.photo.xuite.net/u9011022/19d31e2/4424859/171241799_x.jpg >> >>> On 11月30日, 上午2時39分, themattharris wrote: Hi Alvin, >> The error in that response tells me your signature is incorrect. Double check you are generating your signature using the algorithm described here: http://dev.twitter.com/auth#signing-requests >> In particular I notice the parameters in your GET request are not in lexicographical order, and so I wonder if they may not be in order in your signature base string. >> Best, Matt >> On Nov 24, 10:10 pm, Alvin Wang wrote: >> > hello, Matt >> > After removing the symbol "&" and parameter realm, the frequency of > 401 is lower. > But it becomes the problem as I attach below >> > http://9.share.photo.xuite.net/u9011022/19d319b/4424859/170775808_x.jpg >> > On 11月25日, 上午2時32分, Matt Harris wrote: >> >> Hey Alvin, >> >> Your URL looks badly formed as it includes >> .../home_timeline.json?&count=5 I would expect to see >> .../home_timeline.json?count=5... >> (so no & after the ?). You also have realm in your query string when >>> it >> isn't needed. Realm is optional and when used, is only used in the >> Authorization header. When using OAuth in the query string you >>> shouldn't >> pass realm. Your parameters should also be in lexicographical order. >> >> In your case I would have expected your URL to look like this: >> >>> http://api.twitter.com/1/statuses/home_timeline.json?count=5&oauth_co... >> &page=1 >> >> You can read more about signing requests on our developer resources >>> site: >> http://dev.twitter.com/pages/auth#signing-requests >> >> Best >> @themattharris >> Developer Advocate, Twitterhttp://twitter.com/themattharris >> >> 2010/11/23 Alvin Wang >> >>> hello Matt, >>> here is the image when 401 occurs. >> >>> http://dl.dropbox.com/u/162763/1.png >> >>> On 11月23日, 下午2時17分, Matt Harris wrote: Hey Alvin, >> So the community and developers can help you we'll need to know a >>> little >>> bit more about the error you are receiving. Things like the API >>> request you >>> are making, the request basestring, and the full response you get >>> back are >>> good things to include. >> Be careful to not include any passwords or OAuth secrets in >>> anything you share. >> Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris >> 2010/11/22 Alvin Wang >> > Are there any other solutions? Retry will still got >>> 401randomly. Just > wondering is there any twitter tech person can help? >> > On 11月23日, 上午3時28分, Nick Bradbury >>> wrote: >> I also ran into this problem, even though I knew the >>> signature was >> fine. This post from a Twitter "Developer Advocate" >>> indicates that > a401may be due to Twitter being stressed: >> >>> http://www.devcomments.com/re-intermittent-401-and-502-during-oauth-p... >> >> In my case, ignoring the401and resending the request a little >>> later >> solved the problem the majority of the time. >> >> On Nov 22, 2:43 am, Alvin Wang wrote: >> >>> Hi, >>> I am currently developing an application using twitter api. >>> However, i will ramdomly receive401error (invalid >>> signature). >>> Sometime it's working fine but
[twitter-dev] Re: oAuth still working for everyone.?
Seems that Twitter rolled back some of the changes a few hours ago, right now is working. On Dec 3, 12:13 am, Yusuke wrote: > Hi, > > I had confirmed the error message several hours ago and was looking > into it. > And somehow I don't see the error now. > > Please give it a try once again. > If the problem persists, please post the exception stacktrace to > twitte...@googlegroups.com.http://twitter4j.org/en/index.html#mailingList > > Thanks, > Yusuke > > On Dec 3, 10:09 am, Hector wrote: > > > Does anyone using twitter4j solve the oauth_verifier issue? > > > 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] API for TOP Tweets
I wonder which API to use to get TOP Tweets as shown on twitter home page without login. Any sugession ? Thank 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
[twitter-dev] Can't connect with @anywhere.
Hello everyone, I'm trying to develop a little something for myself using @anywhere. It was kinda sorta working until yesterday when I just couldn't connect anymore via the connect button. I've try resetting my credential on my app's page, but I still get the same error: One the ' https://oauth.twitter.com/2/authorize ' page asking me to allow my application, firebug console logs a 403 to get 'base- lite.js' , then when I click 'connect' I get a "Sorry but something went technically wrong". I guess it's on the @anywhere side, since I did some testing earlier this week and everything worked... Any clue of what's going on? -- 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
