agreed - for future proofing purposes, make those calls against api.twitter.com/1.
have fun in C. On Tue, Dec 22, 2009 at 1:35 AM, shiplu <shiplu....@gmail.com> wrote: > If you get 302 it'll contain a Location header. > Make request to that location again. > > You are requesting to twitter.com. You should be using > api.twitter.com/1 instead. > > > Its better you use curl in C. > > Here is a code snippet for you http://pastie.org/752884 > Its generated by curl. > > > > -- > Shiplu Mokaddim > My talks, http://talk.cmyweb.net > Follow me, http://twitter.com/shiplu > SUST Programmers, http://groups.google.com/group/p2psust > Innovation distinguishes bet ... ... (ask Steve Jobs the rest) > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi