Other question too.
When i tried those codes form www.twitterapime.com ,
once my program caught an exception(however now I forgot what that
exception was) and sometime says could not verify(according to my
program, I displayed could not verify while verifyCredential()
returned false).
Is that
I request this URL :
http://stream.twitter.com/1/statuses/firehose.json
i get this message on my compiler :
WARNING 2010-09-11 07:31:30,447 urlfetch_stub.py:284] Stripped
prohibited headers from URLFetch request: ['Host']
i think something is wrong with my permission.
I read this doc.
This is
Hi
I have a question for the API team. I notice that display_url doesn't
contain the protocol e.g. http:// or https:// yet expanded_url does.
Would I be safe to assume that a urlhttp://t.co/xx/url would
always contain an expanded_url as well as a display_url?
Richard
--
Twitter developer
I think the best debugging process is to reproduce your problem in curl,
then show the curl -v output (passwords elided, naturally). If curl works
and your home-rolled client does not, then you can use tcpdump(1) or some
other packet sniffer and work out the deltas between the working solution
and
Please show your Base String. A lot of issues are related to the Base
String.
Also, to answer your question: yes, you need to combine both secrets.
consumersecretusersecret = your signing key.
Tom
On 9/12/10 12:09 AM, DK wrote:
I keep getting this when I try to update status. I am using xAuth
You need to re-authorize the app. A pair of credentials is either
read/write or readonly, and for security reasons it can't change.
Tom
On 9/12/10 1:22 AM, tomz wrote:
I've changed my app to Read and Write, but I am still getting the
following:
(401): Unauthorized - Read-only application
Estimados,
Creo hace falta una opción para activar/desactivar los twitters de las
personas que uno sigue sin que signifique bloquearlo. Es para cuando
uno esta siguiendo a muchas personas poder discriminar cuáles ver en
un determinado momento, y no tener tantos twitters que realmente uno
no puede
See if this chain of calls and the ratelimit remaining make any
sense...
API callReturned Ratelimit Remaining
Verify Credentials 188
Followers IDs181
Direct Messages 171
The request to verify credentials established that I have 188 calls
