[twitter-dev] Changing an app from Client mode to Browser mode.
I'm currently writing a twitter-enabled Flash game using the tweetr library. The library only seems to support Client mode, so I started out writing the game to work that way, but pasting a PIN isn't really an ideal thing to ask a player to do in the world of browser games, so now that it's working I'd try to extend the library a bit and get Browser mode working. The problem is, when I change my app's settings to Browser mode, when I request authentication, I still get sent to the PIN page instead of the callback URL I set. Is this a bug? Do I need to delete the application and re-create it in Browser mode? Or am I just not understanding what the difference is between Client and Browser mode?
Re: [twitter-dev] Sorry, your query is too complex. Please reduce complexity and try again.
> I keep getting the message: Sorry, your query is too complex. Please > reduce complexity and try again. > > Is there a way around this? Post your query, perhaps? In general, no. You might have to combine two less complicated searches into a single set on your end rather than expecting the Search API to do it. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Backup not found. Abort, Retry, Vomit, Panic, Write Resume File? ---
[twitter-dev] Sorry, your query is too complex. Please reduce complexity and try again.
I keep getting the message: Sorry, your query is too complex. Please reduce complexity and try again. Is there a way around this?
[twitter-dev] Re: Out-of-band/PIN Code Authentication not working?
i think i forgot to take out my app credentials from my previous post,
my app keys have been reset though
On May 22, 6:58 pm, ramy wrote:
> Hi, I have a desktop application using libcurl that has "oob" as the
> call back
>
> I am making an Authorization: header and appending all the required
> items, but when i send my request, i get nothing back - curl just
> waits for a response from the server for ever, here's a snippet, this
> is to get a request token btw:
>
> signatureBaseString = getSignatureBaseString();
> key = consumerSecret + "&";
> signature = format::encrypt(signatureBaseString, key);
>
> basicHeader.push_back("oauth_nonce=\"" + format::encode( noonce,
> curl ) + "\", ");
> basicHeader.push_back("oauth_callback=\"" + format::encode( callBack,
> curl ) + "\", ");
> basicHeader.push_back("oauth_signature_method=\"" +
> format::encode( signatureMethod, curl ) + "\", ");
> basicHeader.push_back("oauth_timestamp=\"" +
> format::encode( timeStamp, curl ) + "\", ");
> basicHeader.push_back("oauth_consumer_key=\"" +
> format::encode( consumerKey, curl ) +"\", ");
> basicHeader.push_back("oauth_signature=\"" +
> format::encode( signature, curl ) + "\", ");
> basicHeader.push_back("oauth_version=\"" +
> format::encode( oauthVersion, curl ) + "\"");
>
> postData = format::vectorToString(basicHeader);
> postData = "Authorization: OAuth " + postData;
> headers = curl_slist_append(headers, postData.c_str() );
>
> std::cout << "postdata: " << postData << std::endl;
>
> post(headers, requestTokenUrl);
>
> postData would look like this (consumer key censored):
> Authorization: OAuth oauth_nonce="vmhufwrwnjdkaupa",
> oauth_callback="oob", oauth_signature_method="HMAC-SHA1",
> oauth_timestamp="1274568595",
> oauth_consumer_key="XxXXXxxXXxxXXXxxXXx",
> oauth_signature="v8EdkEk3V3XijCwdsoTIk5x9Z3w%3D", oauth_version="1.0"
>
> the post function looks like this
>
> curl_easy_setopt(curl, CURLOPT_HTTPHEADER, headers);
> curl_easy_setopt(curl, CURLOPT_CAINFO, "./
> VeriSignClass3ExtendedValidationSSLCA");
> curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, writer);
> curl_easy_setopt(curl, CURLOPT_WRITEDATA, &curlapiPageBuffer);
> curl_easy_setopt(curl, CURLOPT_POST, 1);
> curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1);
> curl_easy_setopt(curl, CURLOPT_COOKIE, curlCookie.c_str() );
> curl_easy_setopt(curl, CURLOPT_URL, url.c_str() );
>
> curlResult = curl_easy_perform(curl);
> std::cout << curlapiPageBuffer << std::endl;
>
> is anyone seeing any mistakes here?
>
> thanks
[twitter-dev] Re: Out-of-band/PIN Code Authentication not working?
i have some more data for anyone willing to help, this is the output
of the curl debug, the last part is the most important
== Info: About to connect() to api.twitter.com port 443 (#0)
== Info: Trying 168.143.171.93... == Info: connected
== Info: Connected to api.twitter.com (168.143.171.93) port 443 (#0)
== Info: successfully set certificate verify locations:
== Info: CAfile: ./VeriSignClass3ExtendedValidationSSLCA
CApath: /etc/ssl/certs
== Info: SSLv3, TLS handshake, Client hello (1):
<= Send SSL data, 108 bytes (0x6c)
: ...h..K./s.H.&..A&...O\.aal..U..&.9.8.5...3.2./.
0040: .api.twitter.com
== Info: SSLv3, TLS handshake, Server hello (2):
<= Recv SSL data, 74 bytes (0x4a)
: ...f..k@..b*!|=..c7s.B'42u6.W5..7. ..FB...[.x..8...b./.J...
0040: Rs{.5.
== Info: SSLv3, TLS handshake, CERT (11):
<= Recv SSL data, 853 bytes (0x355)
: ...Q..N..K0..G0.0...*.H0Z1.0...UUS1.0...
0040: UEquifax Secure Inc.1-0+..U...$Equifax Secure Global eBusine
0080: ss CA-10...090526121457Z..100727061016Z0..1.0...UUS1.0...U..
00c0: ..*.twitter.com1.0...UGT57932074110/..U...(See www.rapidssl.
0100: com/resources/cps (c)091/0-..U...&Domain Control Validated - Rap
0140: idSSL(R)1.0...U*.twitter.com0..0...*.H0...g.
0180: B..W"@.k/c._1r_e..v!.C7 ..{%w.\Q...c..?..a.].2.;.f
01c0: ..Cy~.v!.|.;.g.-...-...@..p.f.-.8./M6.7...*.O+...n.e..._{/_+...
0200: .0..0...U...0...U..`.Qt.Ov.0;..U...4
0240: 0200...,.*http://crl.geotrust.com/crls/globalca1.crl0...U.#..0..
0280: trPkD..#.Wkhl0...U.%..0...+.+...0...U...
02c0: 0.0...*.H..ZQ.X2.CH`..N.>~.AJ..9aF.p...I.. =
0300: .-.Tx).o..#.B.}...h..K..."H=.>M.vy..(zN.D./.y7..O..
0340: andw.?.o.~@.e./$.
== Info: SSLv3, TLS handshake, Server finished (14):
<= Recv SSL data, 4 bytes (0x4)
:
== Info: SSLv3, TLS handshake, Client key exchange (16):
<= Send SSL data, 134 bytes (0x86)
: ..U2..{..E&G".y1.b#...J.L:.P%.RmH.}.?.A).7H
0040: ..T.[_. x.h...W..E>.x...j./"U..<..DM.[...((...H)U.I..9..
0080: ..=;.\
== Info: SSLv3, TLS change cipher, Client hello (1):
<= Send SSL data, 1 bytes (0x1)
: .
== Info: SSLv3, TLS handshake, Finished (20):
<= Send SSL data, 16 bytes (0x10)
: .H;.
== Info: SSLv3, TLS change cipher, Client hello (1):
<= Recv SSL data, 1 bytes (0x1)
: .
== Info: SSLv3, TLS handshake, Finished (20):
<= Recv SSL data, 16 bytes (0x10)
: .P.3.Uv:
== Info: SSL connection using AES256-SHA
== Info: Server certificate:
== Info: subject: C=US, O=*.twitter.com, OU=GT57932074, OU=See
www.rapidssl.com/resources/cps (c)09, OU=Domain Control Validated -
RapidSSL(R), CN=*.twitter.com
== Info: start date: 2009-05-26 12:14:57 GMT
== Info: expire date: 2010-07-27 06:10:16 GMT
== Info: common name: *.twitter.com (matched)
== Info: issuer: C=US, O=Equifax Secure Inc., CN=Equifax Secure
Global eBusiness CA-1
== Info: SSL certificate verify ok.
=> Send header, 424 bytes (0x1a8)
: POST /oauth/request_token HTTP/1.1
0024: Host: api.twitter.com
003b: Accept: */*
0048: Cookie: ./cookies.txt
005f: Authorization: OAuth oauth_nonce="vevztawimsxgfjpc", oauth_callb
009f: ack="oob", oauth_signature_method="HMAC-SHA1", oauth_timestamp="
00df: 1274651066", oauth_consumer_key="KPheeTlyurIeJfp2zC5bQg", oauth_
011f: signature="0Mbdd6%2B5sARJmMF5ZieBQqYxBQk%3D", oauth_version="1.0
015f: "
0162: Content-Length: 0
0175: Content-Type: application/x-www-form-urlencoded
01a6:
so clearly the Authorization header is getting sent appropriately as
per the documentation here: http://dev.twitter.com/pages/auth#request-token,
but after that point, everything just stops, and waits without end.
i'm hopping someone has an idea of what might be wrong?
r.d.
On May 22, 6:58 pm, ramy wrote:
> Hi, I have a desktop application using libcurl that has "oob" as the
> call back
>
> I am making an Authorization: header and appending all the required
> items, but when i send my request, i get nothing back - curl just
> waits for a response from the server for ever, here's a snippet, this
> is to get a request token btw:
>
> signatureBaseString = getSignatureBaseString();
> key = consumerSecret + "&";
> signature = format::encrypt(signatureBaseString, key);
>
> basicHeader.push_back("oauth_nonce=\"" + format::encode( noonce,
> curl ) + "\", ");
> basicHeader.push_back("oauth_callback=\"" + format::encode( callBack,
> curl ) + "\", ");
> basicHeader.push_back("oauth_signature_method=\"" +
> format::encode( signatureMethod, curl ) + "\", ");
> basicHeader.push_back("oauth_timestamp=\"" +
> format::encode( timeStamp, curl ) + "\", ");
> basicHeader.push_back("oauth_consumer_key=\"" +
> format::encode( consumerKey, curl ) +"\", ");
> basicHea
Re: [twitter-dev] Hard lesson learned
Hey Miguel, Long time :-) OAuth 1.0a spec lays it out clearly for hmac/sha1 signatures. Has all the specific details. Soon though with OAuth WRAP/2.0 it will make it much easier by just leaving it all up the transport layer and using ssl/tls. Hope mono is doing well! Zac Sent from my iPad On May 23, 2010, at 2:52 PM, Miguel de Icaza wrote: > Hello guys, > >Perhaps the most frustrating piece in dealing with the OAuth > configuration is that the twitter OAuth page talks casually about > "urlEncode". You need to "urlEncode this" and "urlEncode that". What > the page does not say is that "urlEncode" is not a standard > urlEncoding system that web developers are used to. The urlEncode > required by OAuth signatures is actually "percent encode" and it is > *required* that you use percent encoding for anything but a small > subset of characters. > >The only characters that do not require percent encoding are: > > unreserved = a through z, A through Z, 0 through 9 and '-', '.', '_', > '~' > > Miguel
[twitter-dev] TwitterOAuth, two authentication calls, one works, one fails... why?
I've been trying to get my application to work with TwitterOAuth for several weeks now. Here’s a brief history: I need to authorize user requests of three different types. For that purpose I’ve got two scripts (I’ll call them #1 and #2), and #2 is invoked in two places. Several weeks ago I got script #1 to work with an old version of TwitterOAuth, which did not support specifying a callback URL for each call. I then tried to migrate to a newer version (beta-0.2.0), which would support specifying a callback URL, and script #1 ceased to work. Everything seemed OK up to the point where I tested the access token by performing a verify_credentials operation; then I got back an error that said “could not authenticate you.” I had no luck identifying the problem, so today I fell back to the old version of TwitterOAuth. Now script #1 works again, but script #2 does not. It returns the same error, “could not authenticate you.” I've inserted echo statements in both scripts to show the parameters and result of every call to TwitterOAuth. The sequences of calls are identical, and as far as I can tell the parameters and results are identical in every respect that they should be. Yet one call succeeds and the other fails. I've been beating may head against this thing for weeks, and I'm stumped. I'm open to any sort of advice on what the problem might be, or how to identify it, or how to work around it without identifying it.
[twitter-dev] Re: Favorite create API which is the right one?
Actually the correct one is: http://api.twitter.com/1/favorites/create/:id.json Cheers Georgios http://favorious.com On May 21, 12:24 pm, wibblefish wrote: > I would imagine this one as it is on dev which is more up to date and > seems more in keeping with their other REST formats. > > http://api.twitter.com/version/favorites/:id/create.format > > On May 21, 6:21 am, Jebu Ittiachen wrote: > > > > > As per apiwiki.twitter.com create favorite is > > >http://api.twitter.com/1/favorites/create/*id*.*format* > > dev.twitter.com says > > itshttp://api.twitter.com/*version*/favorites/:id/create.*format > > > *So which is the right one? > > > -- > > Jebu Ittiachen > > jebu.ittiac...@gmail.com
[twitter-dev] Re: Newbie question - please help.
Hi Gustavo Favorious ( http://favorious.com";>http://favorious.com ), which is a website I have recently launched, can do exactly what you want. Cheers Georgios On May 23, 11:17 pm, gus wrote: > result_type=popular won't do it for my project. This criterion is very > restrictive. Even if one searches for a widely used hashtag such as > #cerati, no results or very few results will show up as popular. In > fact, if you search for "twitter" you get only a couple of "popular" > tweets! > > Furthermore, the problem with result_type=popular is that you cannot > measure exactly how popular any of the results are. You can't order > them by popularity either. How many times have they been RT? How many > times have they been favorited? It's a black box. > > What I would like to do is to query the API in such a way that I can > get, for instance, "all tweets that have been favorited at least 5 > times for a given hashtag". > > What I am doing right now is: > - search for all tweets that include the hashtag > - count how many times each of them have been favorited by the > (~1,500) followers of my account. (For this I use the "favorite" API > method). > > What I would like to achieve is: > - find out how many times each of those tweets has been favorited by > any users (not just my followers). But it seems this can't be done. > - query the API in a simpler way (right now I have to constantly check > the tweets that have been favorited by each of my 1,500 followers just > to see if they happen to have favorited any of the tweets that contain > the hashtag in question). > > Thanks, > > Gustavo > > On May 23, 10:22 am, bum wrote: > > > > > Has anyone gotten result_type=popular to work in the search api? I > > must be doing something silly since for the life of me I can't get it > > to return any results. > > > On May 22, 11:52 pm, gus wrote: > > > > Thanks, I'll try that. > > > > On May 22, 12:35 pm, Abraham Williams <4bra...@gmail.com> wrote: > > > > > Try using the popular feature of the search > > > > method:http://dev.twitter.com/doc/get/search > > > > > Abraham > > > > > On Thu, May 20, 2010 at 15:28, gus wrote: > > > > > Hello, > > > > > > I want to develop a web-based application that will search for the > > > > > most favorited tweets for a given hashtag. For example, a user may > > > > > type "cerati" in a textbox and the application will return the tweets > > > > > that contain the hashtag #cerati and have been favorited more than x > > > > > (3, 4, 5) times. > > > > > > My questions are: > > > > > - Is this possible? > > > > > - If so, what method should I use? > > > > > > It appears to me that if I use the search API I don't get a > > > > > favourite_count among the results. And I can't specify something like > > > > > "minimum amount of times tweet was favorited" as a parameter. > > > > > > Or maybe I can use the search API to get the tweets that contain the > > > > > hashtag and then iterate thorugh the list to obtain the number of > > > > > times each tweet was favorited? > > > > > > Another alternative: instead of doing this with the public timeline > > > > > (ideal solution) do it for all tweets by the users a person is > > > > > following. Can this be done? > > > > > > Thanks for your help. > > > > > > Gustavo > > > > > -- > > > > Abraham Williams | Developer for hire |http://abrah.am > > > > @abraham |http://projects.abrah.am|http://blog.abrah.am > > > > This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Newbie question - please help.
result_type=popular won't do it for my project. This criterion is very restrictive. Even if one searches for a widely used hashtag such as #cerati, no results or very few results will show up as popular. In fact, if you search for "twitter" you get only a couple of "popular" tweets! Furthermore, the problem with result_type=popular is that you cannot measure exactly how popular any of the results are. You can't order them by popularity either. How many times have they been RT? How many times have they been favorited? It's a black box. What I would like to do is to query the API in such a way that I can get, for instance, "all tweets that have been favorited at least 5 times for a given hashtag". What I am doing right now is: - search for all tweets that include the hashtag - count how many times each of them have been favorited by the (~1,500) followers of my account. (For this I use the "favorite" API method). What I would like to achieve is: - find out how many times each of those tweets has been favorited by any users (not just my followers). But it seems this can't be done. - query the API in a simpler way (right now I have to constantly check the tweets that have been favorited by each of my 1,500 followers just to see if they happen to have favorited any of the tweets that contain the hashtag in question). Thanks, Gustavo On May 23, 10:22 am, bum wrote: > Has anyone gotten result_type=popular to work in the search api? I > must be doing something silly since for the life of me I can't get it > to return any results. > > On May 22, 11:52 pm, gus wrote: > > > > > Thanks, I'll try that. > > > On May 22, 12:35 pm, Abraham Williams <4bra...@gmail.com> wrote: > > > > Try using the popular feature of the search > > > method:http://dev.twitter.com/doc/get/search > > > > Abraham > > > > On Thu, May 20, 2010 at 15:28, gus wrote: > > > > Hello, > > > > > I want to develop a web-based application that will search for the > > > > most favorited tweets for a given hashtag. For example, a user may > > > > type "cerati" in a textbox and the application will return the tweets > > > > that contain the hashtag #cerati and have been favorited more than x > > > > (3, 4, 5) times. > > > > > My questions are: > > > > - Is this possible? > > > > - If so, what method should I use? > > > > > It appears to me that if I use the search API I don't get a > > > > favourite_count among the results. And I can't specify something like > > > > "minimum amount of times tweet was favorited" as a parameter. > > > > > Or maybe I can use the search API to get the tweets that contain the > > > > hashtag and then iterate thorugh the list to obtain the number of > > > > times each tweet was favorited? > > > > > Another alternative: instead of doing this with the public timeline > > > > (ideal solution) do it for all tweets by the users a person is > > > > following. Can this be done? > > > > > Thanks for your help. > > > > > Gustavo > > > > -- > > > Abraham Williams | Developer for hire |http://abrah.am > > > @abraham |http://projects.abrah.am|http://blog.abrah.am > > > This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Hard lesson learned
Miguel, This 'lesson' has been 'learned' and re-learned many times over, here on the Twitter dev list and on the oauth list. One would hope that at some point this issue would rise to enough prominence to get people in charge of implementation, and sig participants in general, to do something about it. The common developer these days is not a super savvy geek, and even the super savvy geeks among us waste time on this issue, again and again. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Sun, May 23, 2010 at 5:52 PM, Miguel de Icaza wrote: > Hello guys, > >Perhaps the most frustrating piece in dealing with the OAuth > configuration is that the twitter OAuth page talks casually about > "urlEncode". You need to "urlEncode this" and "urlEncode that". What > the page does not say is that "urlEncode" is not a standard > urlEncoding system that web developers are used to. The urlEncode > required by OAuth signatures is actually "percent encode" and it is > *required* that you use percent encoding for anything but a small > subset of characters. > >The only characters that do not require percent encoding are: > > unreserved = a through z, A through Z, 0 through 9 and '-', '.', '_', > '~' > > Miguel >
[twitter-dev] Hard lesson learned
Hello guys, Perhaps the most frustrating piece in dealing with the OAuth configuration is that the twitter OAuth page talks casually about "urlEncode". You need to "urlEncode this" and "urlEncode that". What the page does not say is that "urlEncode" is not a standard urlEncoding system that web developers are used to. The urlEncode required by OAuth signatures is actually "percent encode" and it is *required* that you use percent encoding for anything but a small subset of characters. The only characters that do not require percent encoding are: unreserved = a through z, A through Z, 0 through 9 and '-', '.', '_', '~' Miguel
Re: [twitter-dev] @anywhere follow button width
Quoting Fabien Penso : Hi, May I suggest being able to have a small version of the follow button (a bit like the like button of Farcebook), or begin able to change its title/width? This is way too large for some website design. Thanks. +1 - I have to be careful where I put it on most WordPress themes.
[twitter-dev] @anywhere follow button width
Hi, May I suggest being able to have a small version of the follow button (a bit like the like button of Farcebook), or begin able to change its title/width? This is way too large for some website design. Thanks.
[twitter-dev] 403 status BUT i'm not posting anything
I've been using the twitter4j library in Processing to explore what is
possible with twitter as a large source of data. I've been conducting
searches and displaying the results with their location without
problem for a few weeks. A few days ago, everything stopped working. I
was unable to search twitter and received only the following twitter
exception
Couldn't connect: TwitterException{statusCode=403, retryAfter=0,
rateLimitStatus=null}
This has been going on for days now.
I don't fully understand the API's rules and the OAuth system. It
doesn't seem like I should need to register with them as I'm not
really developing a free-standing app that anyone could download and
use. But, everything I've read about the status code 403 sounds like
it was a preventative measure made by twitter to stop spammers from
POSTING things too quickly. I'm not posting anything, so have I done
something wrong? Have I been blacklisted? The program did conduct its
searches rather frequently. Could I have passed the traffic
limitations? How could i check or have this corrected?
[twitter-dev] The difference between status_id and user_id
Hi: I intend to use the twitter search API (search method) to get the tweet from a user with a specific user_id, however, it seems that the search method only provides two options related with the ids, e.g.: 1) max_id option (returns tweets with status ids less than the given id) and 2) since_id option (returns tweets with status ids greater than the given id). I am not sure whether the status_id is the same as user_id? Can anyone explain this for me? So many thanks Guangchen
[twitter-dev] Re: Newbie question - please help.
Has anyone gotten result_type=popular to work in the search api? I must be doing something silly since for the life of me I can't get it to return any results. On May 22, 11:52 pm, gus wrote: > Thanks, I'll try that. > > On May 22, 12:35 pm, Abraham Williams <4bra...@gmail.com> wrote: > > > > > Try using the popular feature of the search > > method:http://dev.twitter.com/doc/get/search > > > Abraham > > > On Thu, May 20, 2010 at 15:28, gus wrote: > > > Hello, > > > > I want to develop a web-based application that will search for the > > > most favorited tweets for a given hashtag. For example, a user may > > > type "cerati" in a textbox and the application will return the tweets > > > that contain the hashtag #cerati and have been favorited more than x > > > (3, 4, 5) times. > > > > My questions are: > > > - Is this possible? > > > - If so, what method should I use? > > > > It appears to me that if I use the search API I don't get a > > > favourite_count among the results. And I can't specify something like > > > "minimum amount of times tweet was favorited" as a parameter. > > > > Or maybe I can use the search API to get the tweets that contain the > > > hashtag and then iterate thorugh the list to obtain the number of > > > times each tweet was favorited? > > > > Another alternative: instead of doing this with the public timeline > > > (ideal solution) do it for all tweets by the users a person is > > > following. Can this be done? > > > > Thanks for your help. > > > > Gustavo > > > -- > > Abraham Williams | Developer for hire |http://abrah.am > > @abraham |http://projects.abrah.am|http://blog.abrah.am > > This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Twitter APP Development
Hey..How are you doing? Steel Sendras Group is an organisation with various non-profit & for-profit services. We are still in our early development stage. As a part of our services, we want to develop a feature rich twitter app for mobile, PC & MAC platform. We want to make this app as rich as TweetDeck or Tweetie. For this app development we need people & help; as much as possible. So, we are requesting everyone, who wants to help to join us on this mission. Kindly, remember that, this app development will be held under our non- profit service; we won't use it for making money. For more details, follow us on twitter @SteelSendras Remember, it's not any kind of spam. It's a kind request to all! Thanks all...
[twitter-dev] Lists and Replies
We operate an aggregation site that used to grab status updates directly through individual rss feeds, when lists appeared we took the opportunity to integrate with them instead to decrease the overall number of calls to the API it would take to update a few hundred accounts on our lists... we recently noticed that some tweets are missing from the list XML that are in the personal RSS feed?!?!? The missing tweets seem to be @ replies BUT the odd thing is that some @ replies are coming through -- so after some research we think that the list API is returning tweets with @ replies that are to other people in the list? Is that the case? If so, ummm why and more importantly how do we get around that so we see complete status updates in the list or do we have to go back to running the old method and pounding on the API? Please advise. Thanks!
[twitter-dev] Out-of-band/PIN Code Authentication not working?
Hi, I have a desktop application using libcurl that has "oob" as the
call back
I am making an Authorization: header and appending all the required
items, but when i send my request, i get nothing back - curl just
waits for a response from the server for ever, here's a snippet, this
is to get a request token btw:
signatureBaseString = getSignatureBaseString();
key = consumerSecret + "&";
signature = format::encrypt(signatureBaseString, key);
basicHeader.push_back("oauth_nonce=\"" + format::encode( noonce,
curl ) + "\", ");
basicHeader.push_back("oauth_callback=\"" + format::encode( callBack,
curl ) + "\", ");
basicHeader.push_back("oauth_signature_method=\"" +
format::encode( signatureMethod, curl ) + "\", ");
basicHeader.push_back("oauth_timestamp=\"" +
format::encode( timeStamp, curl ) + "\", ");
basicHeader.push_back("oauth_consumer_key=\"" +
format::encode( consumerKey, curl ) +"\", ");
basicHeader.push_back("oauth_signature=\"" +
format::encode( signature, curl ) + "\", ");
basicHeader.push_back("oauth_version=\"" +
format::encode( oauthVersion, curl ) + "\"");
postData = format::vectorToString(basicHeader);
postData = "Authorization: OAuth " + postData;
headers = curl_slist_append(headers, postData.c_str() );
std::cout << "postdata: " << postData << std::endl;
post(headers, requestTokenUrl);
postData would look like this (consumer key censored):
Authorization: OAuth oauth_nonce="vmhufwrwnjdkaupa",
oauth_callback="oob", oauth_signature_method="HMAC-SHA1",
oauth_timestamp="1274568595",
oauth_consumer_key="XxXXXxxXXxxXXXxxXXx",
oauth_signature="v8EdkEk3V3XijCwdsoTIk5x9Z3w%3D", oauth_version="1.0"
the post function looks like this
curl_easy_setopt(curl, CURLOPT_HTTPHEADER, headers);
curl_easy_setopt(curl, CURLOPT_CAINFO, "./
VeriSignClass3ExtendedValidationSSLCA");
curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, writer);
curl_easy_setopt(curl, CURLOPT_WRITEDATA, &curlapiPageBuffer);
curl_easy_setopt(curl, CURLOPT_POST, 1);
curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1);
curl_easy_setopt(curl, CURLOPT_COOKIE, curlCookie.c_str() );
curl_easy_setopt(curl, CURLOPT_URL, url.c_str() );
curlResult = curl_easy_perform(curl);
std::cout << curlapiPageBuffer << std::endl;
is anyone seeing any mistakes here?
thanks
[twitter-dev] Problems with users/search and blocks/exists api calls
I've been having problems trying to figure out why users/search and
blocks/exists keeps returning back to me an invalid signature (401
code). I can make calls to other api urls without any issue.
Using the web based Twurl console, users/search when I put in a
parameter/value of q=noradio (for example) the returning result is
{
"request": "/1/users/search.json",
"error": "Client must provide a 'q' parameter with a value."
}
Doing the same for blocks/exists returns
{
"request": "/1/blocks/exists.json",
"error": "Not found"
}
Using Twurl on my linux machine the calls work fine. I am totally lost
as to what is going on.
Re: [twitter-dev] @anywhere in Safari4/Mac - wont work
Am 13.05.2010 um 07:51 schrieb Dan Webb: > It looks to me like your hovercards are not finding a screen name > rather than it being a browser issue. The Unsafe javascript attempt > is a warning and does not effect operation. Sorry for late answer, but i think i found the error reason now: anywhere.js loads https://api.twitter.com/xd_receiver.html, which gives the following JavaScript Code: var url = "http://localhost:/dist/server/xd_receiver.js";; if (document.location.host == 'api.twitter.com') { url = "https://twitter-any.s3.amazonaws.com/server/production/xd_receiver.js";; } if (document.location.host.match(/^api-staging/)) { url = "https://twitter-any.s3.amazonaws.com/server/staging/xd_receiver.js";; } document.write('