I believe sometimes the IP address can be user-based, even for white-
listed IPs. E.G., if the user himself has a whitelisted IP.
On Aug 10, 7:57 pm, Dewald Pretorius dpr...@gmail.com wrote:
Jim,
I don't know exactly what you're looking at and how you get to that
answer.
My system is
On Mon, 10 Aug 2009 22:01:16 -0700 (PDT)
hansamann sven.hai...@googlemail.com wrote:
Can someone post a link to some online resources explaining more about
geometric back-offs? Did a search, did not find a whole lot.
Retry intervals grow in a geometric progression:
Come on.
For its auto-follow, tweetlater.com specifically states: [w]e have
limits in place to ensure that your daily following remains well
within the limits imposed by Twitter. So you are presumably touching
the rate limit then going back -1, -2, -3, or whatever. How is that
different than
Just wanted to report that we are back up and running for the most
part as well, BUT quite a number of our servers are still experiencing
some BlackOut periods where twitter fails to respond and connections
time out. They seem to last about 5-10 minutes each. We are running
quite a few
My thoughts
OAuth wasn't meant for Desktop apps. Its for third party apps (consumers)
who try to request a protected resource from a service provider on behalf
of end users. Typically a consumer offers one kind of service and a service
provider offers a different service. As you know the
The originating post is total speculation.
If you think that bulk unfollowing is the sole culprit to suspensions,
then you're not following Twitter closely enough. It takes two to
tango. In this case, churn can correctly be described as the process
of blind bulk/auto following and blind
No, my nonce is definately new every time. Surely if there was
something wrong with the way it was being generated it would error
during requestToken/accessToken/VerifyCredentials too?? All the code
ive looked through is doing it exactly the same way. Is the 'status'
parameter being used just
how does it work now?
On 8月3日, 下午1时21分, Ryan McGrath ryan.mcgra...@gmail.com wrote:
Hey,
I figured it's worth dropping a note here about a name change of
aPythonlibrary I wrote to wrap Twitter'sAPI, as some people from this
list took some interest in it when I first announced it. *shrug*
Also, the 'reset-time' is increasing with every request. My reset time
below was taken at 7:57 UTC:
?xml version=1.0 encoding=UTF-8?
hash
remaining-hits type=integer2/remaining-hits
hourly-limit type=integer2/hourly-limit
reset-time-in-seconds type=integer1249981041/reset-time-in-
Hi there,
I'm doing statuses/user_timeline requests via JS, and sometimes due to
faulty user input, I query statuses/user_timeline for nonexisting
users. The statuses/user_timeline API endpoint returns correct data
(for example, `callbackFunction({request:\/statuses\/user_timeline\/
On Aug 11, 3:11 am, TFT Media tftmedia1...@gmail.com wrote:
For its auto-follow, tweetlater.com specifically states: [w]e have
limits in place to ensure that your daily following remains well
within the limits imposed by Twitter. So you are presumably touching
the rate limit then going back
I follow a simple principle in TweetLater.
Where Twitter rules are clearly spelled out, such as for spam, I give
the users a hammer and caution them, Carefully read the rules because
you can drive a nail into wood, but you can also smash your thumb to a
pulp with this thing.
Where Twitter rules
The most common one I've seen used is tweetmeme. Check out
http://tweetmeme.com/about/retweet_button for more details.
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of genshu
Sent: Tuesday, August 11, 2009
Yep. In my experience calling a user that doesn't exist does yield a
404. You'll have to handle the errors on this.
I guess 404 does make sense here, as the user is not found.
dave
On Aug 11, 5:40 am, Carlo Zottmann czottm...@gmail.com wrote:
Hi there,
I'm doing statuses/user_timeline
Ryan,
I am now doing geometric backoffs on 502s and connection refuses.
I did not do exact math, but I seem to be getting between 2 and 5
connection refuses and 502s (combined) per second, and 95%+ of those
requests get a 200 OK at the first retry.
I think it's really good performance given
IDOLPeeps,
I feel you're being overly alarmist and haven't painted the situation
properly.
You can unfollow anyone you want. The issue is a quick follow and then
unfollowing if not reciprocated. You're *supposed* to follow someone
because you want to hear what they are saying, not because you
Ive only been trying since friday...do you have any problems calling
verifyCredentials or any other methods??
On Aug 10, 4:43 pm, Rob O'Brien r...@zepoid.com wrote:
I'm getting the same response. All weekend, I chalked it up to being an
issue during recovery of the systems, but I'm still
At least, it's pretty straightforward to have a link to the web
interface with some text already pasted in. All people have to do then
is to hit the update button. The advantage is that you don't need
the user's login credentials... .
For example, http://twitter.com/home?status=Your%20Text
-M
Hi
I am making small Twitter client in Java. Currently I make option
'farourite status' and I have a strange problem.
I always use format of url like this (for example for 'follow user'):
http://twitter.com/friendships/create.json?id=
It works well in almost all cases. However it doesn't
For our app, we successfully call request_token from our server. When
we then call statuses/update from the client, we get a 401 'Invalid /
used nonce' response. If the request_token call comes directly from
the client, the update call succeeds.
The nonces have been sanity checked and are
We have also been seeing similar behaviour for our iPhone app based on
MGTwitterEngine-1.0.8-OAuth.
If we call request_token from the client followed by statuses/update,
everything works ok. However, if we send the request_token from our
server, then statuses/update from the client, a 401
David,
For me it is not about regimes or dictatorships. For me it is about
not giving users a tool when they cannot get any clear and
authoritative guidance on safely using that tool.
Some folks are charging them money for courses and ebooks that teach
them how to do following churn, and they
While i haven't done scientific testing of this, I was able to run up
to 3-4 instances of my search script prior at a time before it told me
to enhance my calm. Now I'm barely able to run one without hitting the
limit. I can put delays in my code to slow it down, but I'm wondering
if this is just
Srikanth,
Thank you for your thoughts -- good ones. Responses:
snip
But what if the app was developed by some thirdparty devs? you never
know whether the password is stored or logged some where.
/snip
I'm not sure who the third party is relative to -- if you are the
user of an iPhone app,
On Tue, Aug 11, 2009 at 10:30 AM, David Fishertib...@gmail.com wrote:
While i haven't done scientific testing of this, I was able to run up
to 3-4 instances of my search script prior at a time before it told me
to enhance my calm. Now I'm barely able to run one without hitting the
limit. I
Hi,
we currently built a twitter client into our application, but we are
having trouble to get this to work.
The setup:
- registered OAuth client
- our app is registered as read and write
- I think we added the oauth_access_type=write*
We have been testing for a couple of days now. Now the
I agree my comparison to dictatorships is a stretch, but I was in a
poetic mood and trying to emphasize the point that clarity is better
than ambiguity. Twitter is obviously doing a tremendous job dealing
with their explosive growth and dynamic nature of this new medium
they've created. That
On Aug 11, 11:48 am, IDOLpeeps belm...@grandcentralholdings.com
wrote:
Would be very helpful to know the definition of quick as relates to
following churn suspensions.
As Cameron pointed out earlier, as soon as they do that, the following
churners will adjust their methods to be just inside
I'm developing a Twitter Directory that is saving tweets locally via a
cron that's making authenticated calls to friends_timeline every 10
minutes. Ideally, I'd like to update the directory more frequently.
Is there a way to get a firehose feed for a single account, or some
other way to approach
On Mon, Aug 10, 2009 at 8:31 PM, IDOLpeeps belm...@grandcentralholdings.com
wrote:
Lots of community members and developers are leaving Twitter because
of what appears to them to be arbitrary suspension of accounts they've
invested considerable time and good citizenship developing only to
You probably want either the follow streaming api or if you have a couple
more users the shadow
http://apiwiki.twitter.com/Streaming-API-Documentation#follow
http://apiwiki.twitter.com/Streaming-API-Documentation#followshadow
See birddog above. Allows following up to 50,000 users.
URL:
We're having the same issue in our app, occurs sporadically in our
logs - but I believe the cause with us is that:
We're generating nonce values as a timestamp seeded sequence of random
numbers
We're creating an instance of the Oauth class that does this for each
logged in user for the app
By third party i meant some one like 'TwitViewer' (some one who would pay
and register their app in appstore and trick the users to believe in them
but who do not work the way they were expected to )
You are still keying in your password within the app, in code that the
developer of this
An update on this thread: we have an inquiry out to our spam team to get
more information about the metrics they use when policing
mass-following/unfollowing.
On Mon, Aug 10, 2009 at 15:12, IDOLpeeps
belm...@grandcentralholdings.comwrote:
Twitter recently started suspending accounts which bulk
For the case of a dedicated application on a rich mobile platform like
iPhone, I agree that OAuth does not offer a particularly different user
experience. It does, however, provide us at Twitter the information we need
to provide detailed usage analytics back to developers, as well as the data
we
Even if passing id as a parameter works, it's not the documented behavior
and isn't guaranteed to be supported indefinitely. Please specify IDs
in-URL.
On Tue, Aug 11, 2009 at 02:37, Mariusz mariusz...@gmail.com wrote:
Hi
I am making small Twitter client in Java. Currently I make option
The user agent for each search request is the same. I'm using the Ruby
Twitter API wrapper, so sending anything else with search requests
isn't possible unless that is now deprecated.
dave
On Aug 11, 10:36 am, Andrew Badera and...@badera.us wrote:
On Tue, Aug 11, 2009 at 10:30 AM, David
One of the projects on our list is a continuous testing system, running from
a machine outside our cluster. We have the test suite built to do it, just
not the production-safe fixture data.
On Mon, Aug 10, 2009 at 10:20, Dewald Pretorius dpr...@gmail.com wrote:
Does the API team have a test
Very cool! Thanks much. I've added it to
http://apiwiki.twitter.com/Libraries#Ruby
On Mon, Aug 10, 2009 at 10:18, Wynn Netherland wynn.netherl...@gmail.comwrote:
I'd like to thank those of you who have released your own APIs for the
apps you've built on top of Twitter. If you're using Ruby,
Would be very helpful to know the definition of quick
as relates to following churn suspensions.
As Cameron pointed out earlier, as soon as they do that,
the following churners will adjust their methods to be
just inside that definition of OK.
This seems like a really short-sighted
This entire debate focuses on the wrong side of the coin.
Follow churn exists as a side effect of the improper Twitter culture of
reciprocating follows blindly.
If users paid due diligence to those they follow and only followed those
people who demonstrate some value to them, follower churn would
Thanks for your library, Josh! I've added it to
http://apiwiki.twitter.com/Libraries#Python
On Mon, Aug 10, 2009 at 09:50, Josh Roesslein jroessl...@gmail.com wrote:
Hello twitter developers:
Just posting here to announce a library for python I have been putting
together.
It supports pretty
And a 'X people blocked this person' next to their details in the
follows notification would help to identify which are spammers.
ATB
Neil
On 11 Aug 2009, at 18:55, Kevin Mesiab wrote:
This entire debate focuses on the wrong side of the coin.
Follow churn exists as a side effect of the
Follower churn wouldn't exist, but getting hundreds of spam emails
(about being followed) would still exist.
I've got over 12,000 emails in my inbox about being followed on
Twitter. Dozens of those are from the same users. Some weeks the same
users unfollow and refollow me nonstop to try to get
If users paid due diligence to those they follow and only
followed those people who demonstrate some value to them,
follower churn would not exist. Period.
Obviously they won't so maybe it's time to deal with reality
rather than dreaming of a perfect world.
Owkaye
And here lies the slippery slope.
On Tue, Aug 11, 2009 at 8:25 AM, owkaye owk...@gmail.com wrote:
If users paid due diligence to those they follow and only
followed those people who demonstrate some value to them,
follower churn would not exist. Period.
Obviously they won't so maybe it's
Step 1.) turn off email notifications (legitimat, but easily mitigated
problem).Step 2.) getting spammed? Unfollow that user (question why you
followed them in the first place).
On Tue, Aug 11, 2009 at 8:35 AM, Kevin Mesiab ke...@mesiablabs.com wrote:
And here lies the slippery slope.
On
And if followed by an obvious spammer should we not block them and
then let Twitter make it clear to other users how many times they've
blocked. A few black marks against a spammer and they won't get
followed back anymore.
This is like the feedback rating in ebay it encourages you to
David,
I don't know Ruby, so I don't know if this is possible.
But, if possible you need to edit your copy of the Twitter API wrapper
and set the user agent to something that is unique to your service.
If you use the same user agent as everyone else who are using that
wrapper, then you are
I appear to still be getting request timeouts on one of my servers.
On Aug 9, 3:13 pm, Ryan Sarver rsar...@twitter.com wrote:
*Finally* have what we hope is good news for everyone. As of about 10
minutes ago we have been able to restore critical parts of API operation
that should have great
We're currently experiencing another wave of Distributed Denial of Service
(DDoS) attacks against our system. Expect periodic slowness and errors until
the attack passes or is countered by our operations team and hosting
provider. Updates will be provided as we get them.
Thanks for your patience.
I have a spare bazooka in my basement. Let me know. I can FedEx it to
you.
Dewald
On Aug 11, 4:23 pm, Alex Payne a...@twitter.com wrote:
We're currently experiencing another wave of Distributed Denial of Service
(DDoS) attacks against our system. Expect periodic slowness and errors until
the
Srikanth,
By third party i meant some one like 'TwitViewer' (some one who
would pay and register their app in appstore and trick the users to
believe in them but who do not work the way they were expected to )
That's not a valid use case for faulting the authentication mechanism.
The
Hi Dave,
I'm not sure which twitter wrapper you are using. But if you're using Dan
Croak's from here:
http://github.com/dancroak/twitter-search
You might need to update your gem, and make sure you specify the name of
your app as the agent instead of using the default twitter-search.
Yu-Shan
Would be very helpful to know the definition of quick
as relates to following churn suspensions.
As Cameron pointed out earlier, as soon as they do that,
the following churners will adjust their methods to be
just inside that definition of OK.
This seems like a really
Why would it be hosted in your app? Why can't you open Safari?
On Tue, Aug 11, 2009 at 13:29, Bradley S. O'Hearne
brad.ohea...@gmail.comwrote:
Srikanth,
By third party i meant some one like 'TwitViewer' (some one who would pay
and register their app in appstore and trick the users to
I never said that your system does unfollow. I point out that
tweetlater does bulk auto follow and bulk auto return follow, and you
do so using Twitter's follow limits as a guidepost. That's fine. But
I thought it a bit funny how you then write Amen when someone said
that if Twitter published
Thanks for the update Dewald. Keep us posted if things change.
Best, Ryan
On Tue, Aug 11, 2009 at 6:26 AM, Dewald Pretoriusdpr...@gmail.com wrote:
Ryan,
I am now doing geometric backoffs on 502s and connection refuses.
I did not do exact math, but I seem to be getting between 2 and 5
In addition to setting a unique user-agent, I believe it was requested that
we set a referrer header that pointed back to a domain.
On Tue, Aug 11, 2009 at 9:30 AM, David Fisher tib...@gmail.com wrote:
While i haven't done scientific testing of this, I was able to run up
to 3-4 instances of
Our operations staff has informed me that the attack ceased several minutes
ago. Site performance should be returning to normal.
On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote:
We're currently experiencing another wave of Distributed Denial of Service
(DDoS) attacks against
I have no problems debating with you, if you can keep your facts
straight. Or rather, if you bother getting the facts in the first
place.
Dewald
On Aug 11, 2:09 pm, TFT Media tftmedia1...@gmail.com wrote:
I never said that your system does unfollow. I point out that
tweetlater does bulk auto
Awesome work Josh. Thanks for posting this out to everyone and I
especially like the Streaming API support.
Best, Ryan
On Mon, Aug 10, 2009 at 9:50 AM, Josh Roessleinjroessl...@gmail.com wrote:
Hello twitter developers:
Just posting here to announce a library for python I have been putting
The referrer is not as important as the user-agent. You can also put
your URL in the user-agent instead.
-Chad
On Tue, Aug 11, 2009 at 4:09 PM, Larry Wrightlarrywri...@gmail.com wrote:
In addition to setting a unique user-agent, I believe it was requested that
we set a referrer header that
Thanks Alex for getting that added to the wiki.
Ryan, thank you for the kind words glad you like it
The streaming API is pretty cool and it was a top priority for me to include
it.
On Tue, Aug 11, 2009 at 3:13 PM, Ryan Sarver rsar...@twitter.com wrote:
Awesome work Josh. Thanks for posting
I'm so happy gmail has a star feature, that deserved one.
Tim.
On Wed, Aug 12, 2009 at 7:28 AM, Dewald Pretoriusdpr...@gmail.com wrote:
I have a spare bazooka in my basement. Let me know. I can FedEx it to
you.
Dewald
On Aug 11, 4:23 pm, Alex Payne a...@twitter.com wrote:
We're
Hi,
We're trying to figure out what's the recommended way to implement a
widget (flash) with oauth. We actually already implemented it but just
before we finished testing it broke with the latest changes.
Now the questions are:
1. Would such an application be considered web or desktop.
2. Can
On Tue, Aug 11, 2009 at 4:11 PM, Alex Paynea...@twitter.com wrote:
Our operations staff has informed me that the attack ceased several minutes
ago. Site performance should be returning to normal.
On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote:
We're currently experiencing
Owkaye
Would be very helpful to know the definition of
quick as relates to following churn suspensions.
As Cameron pointed out earlier, as soon as they do
that, the following churners will adjust their
methods to be just inside that definition of OK.
This seems like
I am using search.json and track.json and I noticed that the date
format for created_at is different.
search.json: Tue, 11 Aug 2009 20:23:36 +
track.json: Tue Aug 11 20:23:36 + 2009
Is there a reason why Twitter uses different formats for the same
information?
Is there any interest in
On Mon, Aug 10, 2009 at 9:50 AM, Josh Roessleinjroessl...@gmail.com wrote:
Hello twitter developers:
Hi Josh
That's great, it looks very clean. I'll give it a try soon.
BTW, you raise NotImplemented in (at least) cache.py. That should instead
be raise NotImplementedError.
Terry
We do intend to move to unified format. This inconsistency is the result of
the Search system being developed independently of Twitter before it was
acquired.
On Tue, Aug 11, 2009 at 13:33, Jonas boxnumbe...@gmail.com wrote:
I am using search.json and track.json and I noticed that the date
Hello,
I need to be clear on something.
Scenario 1:
Suppose We have a twitter app where 1 user logs in everyday. And
we have 1 whitelisted IP address.
So If each user sends 3 tweets/hours, It will be over(3) the
whitlisted IP rate limit, which is 2.
In this case, we need to use extra
My guess is it's still ongoing. I'm seeing far more rejections per
second, and the number of backed-off retries have also increased.
Dewald
On Aug 11, 5:37 pm, Andrew Badera and...@badera.us wrote:
On Tue, Aug 11, 2009 at 4:11 PM, Alex Paynea...@twitter.com wrote:
Our operations staff has
I've tried logging into a handful of sites built around the Twitter
API without success. I'm seeing the same login issues right now as
when the DDoD happened. Twitter is aware of the downtime issue on
their status page, http://status.twitter.com, but are they aware of
the API issues (e.g., being
Thanks Terry for catching that mistake. I'll get that fixed and pushed out
ASAP.
Josh
On Tue, Aug 11, 2009 at 3:48 PM, Terry Jones te...@jon.es wrote:
On Mon, Aug 10, 2009 at 9:50 AM, Josh Roessleinjroessl...@gmail.com
wrote:
Hello twitter developers:
Hi Josh
That's great, it looks
On Aug 11, 5:53 pm, shiplu shiplu@gmail.com wrote:
Scenario 1:
No, you don't. Status updates are POSTs, which do not count against
your 20,000 rate limit.
Dewald
Yes, I've just been informed that the attack has resumed, and that our
service provider is putting network hardware in place to counter the attack.
We're trying to work with them to ensure minimal impact to the API, but in
the near term there may be issues with OAuth and the Streaming API.
This is
Alex,
Did not see this post and posted a new message. Still receiving lots
of errors and no one can login on our site, tweetphoto.com, right now
along with a handful of others (that I've tried myself). Just wanted
to give you a heads up. Thanks!
Sean
On Aug 11, 1:11 pm, Alex Payne
Please see the other thread in this group.
On Tue, Aug 11, 2009 at 13:55, Sean Callahan seancalla...@gmail.com wrote:
I've tried logging into a handful of sites built around the Twitter
API without success. I'm seeing the same login issues right now as
when the DDoD happened. Twitter is
We're aware of these issues; sorry.
Our ops team tells me that the countermeasures that are being put in place
should not cause the 302 redirect behavior that impacted OAuth and other
services late last week. If you're seeing that behavior, please post here
and we'll coordinate with them to
On Wed, Aug 12, 2009 at 3:57 AM, Dewald Pretoriusdpr...@gmail.com wrote:
On Aug 11, 5:53 pm, shiplu shiplu@gmail.com wrote:
Scenario 1:
No, you don't. Status updates are POSTs, which do not count against
your 20,000 rate limit.
Dewald
Oops! Basic Mistake!
But what about I am talking
Also, please be sure to provide packet dumps and full headers where
possible so we can more easily determine the source of the issue.
Thanks, Ryan
On Tue, Aug 11, 2009 at 2:00 PM, Alex Paynea...@twitter.com wrote:
We're aware of these issues; sorry.
Our ops team tells me that the
On Tue, Aug 11, 2009 at 5:01 PM, Andrew Baderaand...@badera.us wrote:
On Tue, Aug 11, 2009 at 4:57 PM, Alex Paynea...@twitter.com wrote:
Yes, I've just been informed that the attack has resumed, and that our
service provider is putting network hardware in place to counter the attack.
We're
I don't have a domain to point back to. I'm doing data-mining and
analysis on a server that isn't public.
I have set the User-Agent to something unique (I thought you were
saying to change it for every request?).
Yet I'm still getting rate limited and told to back off a lot. Ryan S
said it might
Just found out that our hosting provider put some hardware in place that may
cause disruptions. Our operations team just spoke them, and they should be
taking it down in 15 - 30 minutes.
On Tue, Aug 11, 2009 at 14:03, Andrew Badera and...@badera.us wrote:
On Tue, Aug 11, 2009 at 5:01 PM,
JDG,
Why would it be hosted in your app? Why can't you open Safari?
The ideal usage pattern in an application is not to leave the
application. Opening Safari requires exiting the current application.
Opening a UIWebView within your application is the way to go.
Brad
On Aug 11, 2009, at
For me the API behavior is now back again to this morning, with around
2 to 5 rejections per second, and most being successful on the first
or second backed-off retry.
Dewald
On Aug 11, 6:22 pm, Alex Payne a...@twitter.com wrote:
Just found out that our hosting provider put some hardware in
Persistent connections for notifications certainly allay my fears
around latency and throughput for well-behaved hubs.
I don't see any real cost savings, other than some minor bandwidth
savings on the fan-out. We'd incur significant development cost to
support this alternative approach, as we've
On Wed, Aug 12, 2009 at 7:01 AM, shiplushiplu@gmail.com wrote:
Oops! Basic Mistake!
But what about I am talking about GET requests.
If you're doing a GET 3 times every hour, then it would be better not
use a whitelisted IP. This way, the rate limit will count to each
user, not the IP
Why would it be hosted in your app? Why can't you open Safari?
Obviously Safari is *more* trusted. But if you've already installed
an untrusted app onto your machine, the untrusted app has enough power
to keylog, brute force your keychain (or other password db), send
personal info over
I want to believe! If there are compelling arguments, we'll consider
this deeply. So far I'm still unconvinced.
The Streaming API is built only on open standards: HTTP, XML, JSON.
Anyone can build a Streaming API client in a few hours of work using
well worn libraries and techniques. (Only a
On Wed, Aug 12, 2009 at 6:41 AM, Julio Biasonjulio.bia...@gmail.com wrote:
On Wed, Aug 12, 2009 at 7:01 AM, shiplushiplu@gmail.com wrote:
Oops! Basic Mistake!
But what about I am talking about GET requests.
If you're doing a GET 3 times every hour, then it would be better not
use a
It's quite impressive but I get nothing back from most of the curl api
request I make to twitter. Fully whitelisted on ip, lots of ratelimit
spare, total failures from twitter all the time.
A new favourite appeared today from a
http://twitter.com/friends/ids/accountname.xml
get:
?xml
If you include the full headers in your response output, that would be
helpful in tracking this down.
On Tue, Aug 11, 2009 at 17:17, freefall tehgame...@googlemail.com wrote:
It's quite impressive but I get nothing back from most of the curl api
request I make to twitter. Fully whitelisted on
Geometric backoffs are more generally know as exponential backoffs. If
ya google that, ya get a couple of useful and interesting things:
http://en.wikipedia.org/wiki/Exponential_backoff
http://en.wikipedia.org/wiki/Truncated_binary_exponential_backoff
Could we please not quote the *entire* *original* *message* with every reply?
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- They told me I was gullible ... and I believed them.
Sorry Cameron :-) it's just so easy to hit that button :-)
peace
Neil
On 12 Aug 2009, at 04:02, Cameron Kaiser wrote:
Could we please not quote the *entire* *original* *message* with
every reply?
--
personal: http://www.cameronkaiser.com/
--
The same TOS that applies to users applies to developers, along with this
one: http://apiwiki.twitter.com/Terms-of-Service
http://apiwiki.twitter.com/Terms-of-ServiceIf you haven't already, I
encourage all developers to familiarize themselves with both. You may also,
now, find more value in
As I've pointed out in other posts to this group, and I will be the
first to acknowledge that there are conflicting opinions and facts on
this, it is my understanding and experience that for GET requests that
require authorization the rate limit is per user per IP address:
-If *EITHER* the
On Tue, Aug 11, 2009 at 20:48, Dean Collins d...@cognation.net wrote:
Any other developer being sued by Twitter today?
I might be. Oh wait, no, I'm not, because I know the difference between a
lawsuit and a cease and desist letter that enumerates all the things I'm
doing that violates
1 - 100 of 119 matches
Mail list logo