date:20100616

Re: [twitter-dev] What can be done with twitter data?

2010-06-16 Thread kuhkatz


Am 15.06.2010 21:36, schrieb ckell...@gmail.com:

What can be done with the twitter api? What can be done with data? What kind of 
output is useful to the general public? So far I have found twitter to be a 
public version of text messages. I have ideas for twitter such as twitter 
dating and twitter chatrooms is this something that the twitter api could be 
used for to develop such a program?

-Chris
ckel...@aol.com
Sent on the Sprint® Now Network from my BlackBerry®


dating... i dont know.
i also dont know if i want my dating approaches to be visible for anyone 
and indexed by google, etc.


chat... maybe?
if you setup one account per chatchannel / room, people can DM that 
account, and a bot would DM anyone who is registered for that room.

it is possible, i suppose.

if its not via DM chatting people would spam other peoples timelines, 
at least i would see it that way.

Re: [twitter-dev] Rate limits, bad gateway, etc.

2010-06-16 Thread Matt Harris

Hi Bhushan,

You can find specific information about rate limiting on our dev site [1].
The main reason for seeing a rate-limit is that you, or your IP, have made
too many requests over the measured time.

One of many reasons for this happening is if you are using shared hosting.
It could be that somebody else with your IP is also making requests from
Twitter.

One way of approaching this is to use authenticated calls. This way your
application is identifiable over any other request on the same IP.

Hope that helps explain what could be happening.

Matt

1. http://dev.twitter.com/pages/rate-limiting

On Wed, Jun 16, 2010 at 12:23 AM, Bhushan Garud garud.bhus...@gmail.comwrote:

 Hi Taylor,

 I am using [Tweetr APIs] for my application. I want to get user's public
 feeds. However, i am facing a GET request rate limit problem. I am wondering
 even if i make one or two request, it is giving me 400 error [rate-limit
 reached]. If you can explain me the reason or any workaround for this
 problem, it will be great

 Thanks  regards,
 Bhushan

 On Wed, Jun 9, 2010 at 12:41 AM, Taylor Singletary 
 taylorsinglet...@twitter.com wrote:

 Hi Ed,

 I think you're doing the best that you can do to be fault tolerant in this
 case. We generally recommend exponential back-off in the face of continued
 error.. perhaps waiting 5 seconds before retrying after the first failed
 request, then widening to a longer duration, and so on with each subsequent
 error. It is recommended that you implement this kind of behavior, as in
 times of high error rates, those applications that are ignoring error codes
 and retrying the same requests most aggressively are candidates for
 temporary blacklisting (to relieve the unproductive stress on the system as
 it recovers from error states).

 Your normal operation behavior also seems to be the correct one to
 utilize. Though if you want to implement additional waiting time, that's up
 to you. Dynamically handling rate limiting is a good idea, as one shouldn't
 really expect the rate limiting to a constant function/rate (though they
 generally are today).

 Taylor Singletary
 Developer Advocate, Twitter
 http://twitter.com/episod



 On Tue, Jun 8, 2010 at 11:36 AM, M. Edward (Ed) Borasky 
 zn...@borasky-research.net wrote:

 I have a Perl script that downloads historical tweets using the
 user_timeline REST API call. I'm running into 503 - Bad Gateway -
 Twitter / Over capacity errors when I run it. Questions:

 1. When I run into an error, I'm waiting 45 seconds before retrying.
 Should I wait longer? Is there a shorter recommended wait time after an
 Over capacity error? Do I need to wait at all?

 2. In normal operation, I'm using the returned rate limit header
 information to pace the request rate so that I never run out of calls. This
 can generate a call as soon as I've completed processing of the previous
 data. Should I insert a non-zero wait time here? I've tested explicit wait
 times as high as 20 seconds here and they don't seem to be reducing the
 incidence of Over capacity errors.






-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Who retweeted?

2010-06-16 Thread Ken

Maybe not a dev question, but I keep wanting to click on retweeted by
you and one other to know who that was!

[twitter-dev] Re: Who retweeted?

2010-06-16 Thread Ken

To clarify, I know how to find out, I just expect that text to be
clickable.

Re: [twitter-dev] Trouble generating OAuth signature

2010-06-16 Thread Matt Harris

Hi Felipe,

Taking a quick look at your code you've got a few things which will be
causing you problems.

With your signature generation you're correct in using hash_hmac but you've
missed out the base64 encoding. It also looks like you won't be getting the
raw signature from your hash_hmac function. Looking at the docs for that
function you need to append 'true' to the end.

You also want to make sure your parameters are lexicographically ordered
before and after you generate the signature. In your case the sign part is
in order, but your authorization header is not.

You may have done this already but if not, take a look at the Authenticating
Requests page of dev.twitter.com [1] for an overview of the steps you need
to follow. There are also a couple of libraries which do the heavy lifting
for you when generating the signatures so they act as good references if you
want to create your own. We have a list of those on the dev site too [2]

1. http://dev.twitter.com/pages/auth#signing-requests
2. http://dev.twitter.com/pages/oauth_libraries#php

Hope that helps, you know where we are if you still have trouble getting it
all to work,
Matt

On Tue, Jun 15, 2010 at 5:58 PM, Felipe Sodré Silva fso...@gmail.comwrote:

 Hello all.

 I'm trying to write a simple application that sends an update Hello World
 on behalf of my own twitter account. Therefore, I got my access token and
 secret in my dev.twitter webpage and hardcoded it into the code (which I
 hided for making it public): http://pastebin.com/n6Ba5nrW

 However, I keep getting the following response:

 {request:/1/statuses/update.json,error:Incorrect signature}

 I'm doing the whole process by reading this guide:
 http://dev.twitter.com/pages/auth
 But I just cannot get it to work. What am I doing wrong during the
 signature assembly ?

 Thanks in advance!

 Felipe




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Re: Repeat Tweets

2010-06-16 Thread themattharris

Thanks for letting us know about these Andy. As Taylor was saying the
instabilities the other day are likely to have been the cause for
these getting through. It shouldn't happen now but anything that did
get through will still be there.

Matt

On Jun 15, 6:39 pm, Andy Matsubara andymatsub...@gmail.com wrote:
Taylor,

There's a sample of six consecutive
tweets.http://twitter.com/AppleWalker/status/16204554355http://twitter.com/AppleWalker/status/16204551280http://twitter.com/AppleWalker/status/16204548302http://twitter.com/AppleWalker/status/16204545368http://twitter.com/AppleWalker/status/16204542279http://twitter.com/AppleWalker/status/16204539134

Andy Matsubara

On Wed, Jun 16, 2010 at 4:21 AM, methnen meth...@gmail.com wrote:
Can you provide some links to the repeated tweets? While things were at
their worse last night, it was very easy for duplicate updates to get
processed but that shouldn't be the case now.

We manually deleted them and it now appears to have stopped.

Are you sure that the client you were using isn't trying to re-post tweets
on your behalf, thinking they haven't been posted yet?

At first I thought it might be on our end. As we use the API to make
tweets via a custom script in our CMS. However, the script records
successful posts and then stops posting and the repeating tweet was
recorded as a successful post and our system never sent it to Twitter
again.

65 matches

Mail list logo