25% of my requests are still getting timed out..is there any rate
limit in place?
On Aug 9, 9:11 pm, Patrick wrote:
> I am still having problems logging in using Basic Authentication.
>
> Because I don't use OAuth I cannot give you feedback on that. Sorry.
>
> kozen
>
> On Aug 10, 3:13 am, Ryan
Since we have a lot of devs monitoring this now I'd like to bring back
the discussion that we were having before this whole mess started.
Is the intention of Twitter to allow (for whitelisted IP's) 20k
requests per hour per USER or 20k requests per hour per IP.
I don't want to seem to be beating
Mr. Trident, if that is your real name,
You can use the Search API to look for the keyword, and post process
for your users. You could also use the /follow method to track the
userids in question, and post process for the keyword, or use the /
track method and post process. I'd think that /track
Hello,
I am running a contest on twitter, and I need to keyword search the
tweets of only the contestants. The first thing that comes to mind is
to create a twitter account and then follow only the contestants. This
enables me to:
A. Get recent status updates for all friends but not to keyword s
> I think it'd be a nice feature to set posts with certain hashtags to
> "hidden" or something like that.
>
> Just tell me your thoughts - is this nonsense, if so - why? Or does
> this already exist..
I think it's a great idea for third party application.
In fact, I'm writing a Twitter API lib
I am still having problems logging in using Basic Authentication.
Because I don't use OAuth I cannot give you feedback on that. Sorry.
kozen
On Aug 10, 3:13 am, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone. As of about 10
> minutes ago we have been able to restore
I just tested OAuth from Twibes.com, it worked twice in a row. Thanks
guys for whatever you're doing.
On Aug 9, 7:42 pm, Vignesh wrote:
> My app is also working fine ... just beginning to fire up the crons...
>
> On Aug 9, 4:55 pm, Kyle Mulka wrote:
>
> >http://twilk.comworksconsistently now wi
On Sun, Aug 9, 2009 at 5:23 PM, Eric wrote:
>
> Any idea when the limit will be increased to 20,000? I'm sure myself
> as well as other sites are suffering a bit because of the limitation
> of API calls.
>
Please read the history of the mailing list. There *IS NO ETA* on anything;
it merely depe
With a DOS attack, you are sending requests to the server in order to
tie up resources. The reason for the sequence numbers in TCP is order
to make sure that data can flow to and from client and service. With
HTTP, a TCP packet is sent, and a response is sent. However for a DOS
you don't need the
I'm sorry Joel I keep getting a PHP timeout on the code you sent. I'll
troubleshoot more and see if I can give you any more details (increase
the maximum time, etc). Who knows, maybe its Twitter. Any other
thoughts? I'll get back to you more with some detailed info. Are you
able to get that exact
Really weird...using the exact same .NET code and oAuth. From our
website if we try to post a tweet directly from our webform we get a
401 Unauthorized error. But if a tweet gets sent out via a windows
service we have that works behind the scenes the tweets are going out
just fine.
Any ideas??
My app is also working fine ... just beginning to fire up the crons...
On Aug 9, 4:55 pm, Kyle Mulka wrote:
> http://twilk.comworks consistently now with OAuth and everything.
> Whatever you guys did seems to have fixed the problems. Is the DOS
> attack still as strong as it was before?
>
> --
>
TCP/IP is the protocol underneath HTTP, is not a web service protocol and
requires a whole different method to manage and use connections. Think of
it as the raw data pipe by which the HTTP protocol is used to communicate
between a client program (i.e. a web broswer) and the server program (i.e. a
Thanks for the quick feedback, John. I'm checking it out and will let
you know what happens.
On Aug 6, 10:15 am, John Kalucki wrote:
> Josh,
>
> It seems that you can accomplish most of your goals by using the /
> track feature in the Streaming API. You can then make far fewer calls
> to the Se
Ryan/Chad,
Two more questions related to good API usage practices ...
1. When i am seeing a http error 502, it *seems* to always be the
"Twitter is over capacity!" error. Are their any other times when I
should expect to see the 502 error?
2. When I *do* get a 502, how long do you want me to b
Ryan,
Does this mean that I'll see 150 *or* 2? Or is there a situation
where I would see anything in between? Or some other value?
I'm wanting to ensure that I enhance my library to handle the various
numbers that might be coming back to me.
Scott
On Aug 9, 2:45 pm, Ryan Sarver wrote:
>From Wikipedia:
"Some upper layer protocols provide their own defense against IP
spoofing. For example, Transmission Control Protocol (TCP) uses
sequence numbers negotiated with the remote machine to ensure that
arriving packets are part of an established connection. Since the
attacker normally c
On Sun, Aug 09, 2009 at 03:50:44PM -0700, David Cramer wrote:
>
> So short story I've been changing our application from Read to Read/
> Write access, and I cannot get it working. I've checked and double
> checked the app settings, and it asks for "read and update access" on
> the authorize page.
Did you configure a callback for your application OR passing it when getting
the request token?
On Sun, Aug 9, 2009 at 3:49 PM, Andy wrote:
>
> We're still having trouble with oAuth. When sending users to get
> oAuth'd, they are given a code (like a desktop app) rather then being
> redirected to
http://twilk.com works consistently now with OAuth and everything.
Whatever you guys did seems to have fixed the problems. Is the DOS
attack still as strong as it was before?
--
Kyle Mulka
On Aug 9, 3:13 pm, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone. As of about
Folks,
I looked through the API, the online discussion, and wrote test code
to check both the authorize and authenticate methods. I have not been
able to find any difference between the two, apart from the request
URL (and, perhaps, some differences in language between Twitter's
authorize and au
> 5. Unexpected rate limiting / blacklisting
Most annoyed issue for me. Rate is 150/hour for my whitelist ip now.
So short story I've been changing our application from Read to Read/
Write access, and I cannot get it working. I've checked and double
checked the app settings, and it asks for "read and update access" on
the authorize page. Once authorized, however, it continues to say
"Read-only application can
Yes,
We are. It was working fine until the DDoS attack. Thats when it
started this weird behavior on it's on.
See: http://yfrog.com/09scrngp
For a screenshot of the apps settings...
On Aug 8, 11:14 pm, Bill Kocik wrote:
> Are you passing a callback_url parameter when you retrieve the request
No longer being rate_limited at 150. Back to us being whitelisted.
Thanks for the fix.
On Aug 9, 12:13 pm, Ryan Sarver 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 gre
Any idea when the limit will be increased to 20,000? I'm sure myself
as well as other sites are suffering a bit because of the limitation
of API calls.
On Aug 7, 4:54 pm, Chad Etzel wrote:
> Hi Paul (and everyone),
>
> Thanks for your appreciation and your comments.
>
> On a personal note: I sta
We're still having trouble with oAuth. When sending users to get
oAuth'd, they are given a code (like a desktop app) rather then being
redirected to our web app.
I've checked and tried toggling the setting and still no dice.
The app is assosiared with the account is @adcause Thanks for all the
h
Are there any new limits with verify_credentials() now? I'm showing it only
works half the time, even under the 15 requests per hour limit. Anyone else
seeing this?
Jesse
On Sun, Aug 9, 2009 at 3:13 PM, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone. As of about 10
On Sun, Aug 9, 2009 at 2:16 PM, Ed Anuff wrote:
>
> On Aug 9, 10:46 am, Bill Kocik wrote:
> > All that said, I agree with the spirit of your post. It would be good
> > if our Twitter API-wrapping libraries were able to handle all of this
> > in stride (or at least the 302's...not much you can do
Or you could actually read my email, my goodness people are so rude.
No threats in my email, please read again in context.
Peace
Neil
On 9 Aug 2009, at 19:30, Scott C. Lemon wrote:
Uh ... for all of you hotdog men, threatening to move on to another
"band that are still playing and have fans
My App works fine now!
Good news for everybody!
Finally, we can run our app again!
2009/8/9 Arik Fraimovich :
>
> On Aug 9, 10:13 pm, Ryan Sarver wrote:
>> *Finally* have what we hope is good news for everyone.
>
> Everything seems to behave much better now.
>
> Thank you and the rest of the te
On Aug 9, 10:13 pm, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone.
Everything seems to behave much better now.
Thank you and the rest of the team !
--
Arik Fraimovich
In all honesty, I think you are stuck. The responsible thing to do is
follow this list and wait until the API is reported 100% functional.
Writing a new app is bound to have testing issues, currently you have
zero way of knowing if it is your app, the API, routing blocks, or
even congestion
Scott,
You *should* be getting the proper rate limits. Things have changed in the
last 30 minutes or so, so be sure to check again and let us know if you
still seeing the variable throttling.
Best, Ryan
On Sun, Aug 9, 2009 at 11:15 AM, Scott C. Lemon wrote:
>
> Chad/Ryan,
>
> Thanks for all of
search.twitter.com is not working for me from either API or directly
in the browser. Is it working for others? If I am blacklisted, how
does one go about getting it fixed?
Are those additional 302 redirects also subtracted from our rate
limits on GETs?
Dewald
Thanks Ryan, just tested my oAuth system and it work perfectly.
Thanks for all your work guys & gals!
On Aug 9, 9:33 pm, Mario Menti wrote:
> Seeing similar improvements here (twitterfeed) - feeds with error statuses
> have decreased from 120,000 a few hours ago to just over 10,000 now, so am
>
> 5. Unexpected rate limiting / blacklisting
Mostly I'm noticing rate limiting.
- Ben
1. I'm finding that OAuth breaks for periods, then works for periods
(not 1/6 requests, more like works 6 times, then breaks 6 times). When
it doesn't work in Safari, if I dump my twitter.com cookies it usually
works the next try.
Uh ... for all of you hotdog men, threatening to move on to another
"band that are still playing and have fans." ... PLEASE DO!
I can promise you that you will not be missed by twitter, or anyone
here.
For all of the whiny developers who didn't plan for a rainy day ...
maybe this is time for you
The 302 issue has not been made very clear:
1. does the redirect need to be re-signed?
2. is this only the token calls, or all calls to the API methods?
Also, I don't know if it's related or not, but paging on the blocks/
blocking method does not work. i.e. all page parameters return a full
list
Seeing similar improvements here (twitterfeed) - feeds with error statuses
have decreased from 120,000 a few hours ago to just over 10,000 now, so am
assuming it's safe to revert to our default settings and stop the throttling
we put into place a couple of days ago.
Mario.
On Sun, Aug 9, 2009 at 9
On Aug 9, 4:29 am, Steve Andaz wrote:
> Whilst i understand your working on fixing the problem, what i dont
> understand is how come its taking so long. . . . Over the past 18
> months with the extensive popularity of twitter shouldnt you have
> invested in the security used by other social net
Chad/Ryan,
Thanks for all of the updates so far ... I'm actually jealous that you
get to really know what it's like to deal with a DDOS attack of these
proportions. Having been involved in the past with some large scale
DDOS attacks (where the FBI and Government even got involved) I know
that it
On Aug 9, 10:46 am, Bill Kocik wrote:
> All that said, I agree with the spirit of your post. It would be good
> if our Twitter API-wrapping libraries were able to handle all of this
> in stride (or at least the 302's...not much you can do about 408's and
> such).
Is there a list of which librari
We are getting timeouts via appengine for search api calls for
LinksAlpha.com. All our data aggregation activities are ending up with
almost no data for the past 3 days.
Thanks
Vivek Puri
http://LinksAlpha.com
Ryan,
Many thanks for the continued updates. You guys are handling this far
better than most would.
Regarding OAuth: I'm also having difficulty updating OAuth app
properties on the website -- the update form continues to return a
"400 Bad Request" when it's submitted.
Obviously not a huge prior
I'm actually clean - no problems for the last 2 days. I do, however
have my app just following all re-directs. If it would help I can pull
the follow on 302 and let you know what happens.
Brian Roy
justSignal
On Aug 9, 10:42 am, Dewald Pretorius wrote:
> On Aug 9, 2:34 pm, Ryan Sarver wrote:
Hi Ryan,
Many thanks for the update.
On twitscoop, we have issues with the search api, which apparently
returns erroneous or ill-formed timestamps.
eg. http://www.twitscoop.com/search?twitter you'll see the latest
tweet will be dated "14465 days ago" :))
Cheers
On Aug 9, 7:34 pm, Ryan Sarver
I have just started writing a Twitter App for a small company (great
timing lol). Part of it works and part of it is down. Is there any
where else I can check to see which parts of the API are down? I have
continually checked status.twitter.com, however I want to make sure
that any errors I'm seei
Holding steady after 2,000 GETs in rapid succession, and heaven knows
how many POSTs. So, it looks like we are back in business.
Dewald
I am slowly firing up my cron jobs, and so far so good.
Dewald
I am still getting these bizarre "OK: 200" errors with returned
content like...
"http://www.w3.org/TR/html4/strict.dtd";> -->
On Aug 9, 12:35 pm, Dewald Pretorius wrote:
> Ryan,
>
> Are there any new requirements we have to comply with for calls to the
> Search API?
>
> I presume we
Most calls seem to be working much better for us.
in response to the rate_limit_status call, I get HTML back
occasionally.. looks like the fail whale page and 502 twitter over
capacity..
Got this one about 10 min ago.
08-09-09 19:40:15rate_limit_status response(502): PUBLIC "-//W3C//DTD X
Well there was the Twitter TV program, maybe this is it. Maybe we're
in a
Borat style movie already ;-)
I think it should be in the style of 24 : I can see it now, clock
counting
down - Jack Bauer torturing sysadmin; developers being exposed
as double agents oh the intrigue :-)
Of co
On Sat, Aug 8, 2009 at 2:37 AM, Chad Etzel wrote:
> You may have to follow redirects more than once *wink wink nudge nudge*
>
> with curl you can add --location flag. There's a good bit of info in
> the man page as well.
So instead of doing
curl --netrc -s -D - http://twitter.com/account/rate_li
Yea, and we all threatened to go to Pownce.
That didn't go so well (seeing that Pownce is now dead)
dave
On Aug 9, 3:05 pm, Dossy Shiobara wrote:
> On 8/9/09 1:53 PM, David Fisher wrote:
>
> > Anyone that was around in 2006/2007 knows that Twitter was excessively
> > unstable then, and people d
> It is like a surreal tech soap opera on this list though :-) Hey maybe I
> could pitch this to Fox .
>
> All the best
> Neil
>
DO IT! Maybe Twitter would have made a good reality show. Lots of
super-dramatic angles and queues pointing at sysadmins typing at a
console. :)
The mailing list
Ryan,
Are there any new requirements we have to comply with for calls to the
Search API?
I presume we have to handle 302s there as well? Anything else?
Dewald
On Aug 9, 4:32 pm, Paul Kinlan wrote:
> OAuth, Search and the friendship methods are working for me...
> Paul
>
> 2009/8/9 Bill Kocik
OAuth, Search and the friendship methods are working for me...
Paul
2009/8/9 Bill Kocik
>
>
>
> On Aug 9, 3:13 pm, Ryan Sarver wrote:
> > Please test your apps from their standard configs to see what results you
> > get and let us know. I am primarily interested in unexpected throttling
> and
>
Thank you for the good news, Ryan. It looks like Twitter Karma is
starting to work again, too.
On 8/9/09 3:13 PM, Ryan Sarver 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 hav
On Aug 9, 3:13 pm, Ryan Sarver wrote:
> Please test your apps from their standard configs to see what results you
> get and let us know. I am primarily interested in unexpected throttling and
> issues with OAuth.
OAuth appears to be working for my app. Thanks!
What did you guys do in 2007? Twitter was down all the time then. Your
blood pressure must have been through the roof with weekly visits to a
shrink if you responded this way every time it went down.
How many people had bet their business/livelihood on Twitter in 2007?
Compassion all-round
*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 affect on your apps. As such, most of your apps
should begin to function normally again. I have tested a few OAuth apps and
they seem
Appreciate your updates Ryan, here are the issue we are still
experiencing at HootSuite
1. 302 redirect. We still have to follow redirects in order to
retrieve proper contents, but not a big deal
2. Rate Limiting. All of our server IPs (supposed to be whitelisted)
are bound with 150 limit
3. Gene
On 8/9/09 1:53 PM, David Fisher wrote:
Anyone that was around in 2006/2007 knows that Twitter was excessively
unstable then, and people didn't whine/complain as much.
Sure we did, there were just fewer of us at the time. Weren't you
around in 2006/2007? Perhaps you have a short memory reten
I remember another service that used to have constant problems due to
their astronomical growth ... what was it called? Oh, yeah, Friendster.
What ever happened to them?
Oh, there was also a service that became wildly popular and grew faster
than it could handle ... remember playing a Flas
On 8/9/09 12:47 PM, Stuart wrote:
> * I can't believe you lot don't realise that constantly demanding
status
> updates, while certainly important to you, is little more than a
> distraction for those who are actually fighting the good fight.
>Dossy Shiobara | do...@panoptic.com | htt
On 8/9/09 12:47 PM, Stuart wrote:
* I can't believe you lot don't realise that constantly demanding status
updates, while certainly important to you, is little more than a
distraction for those who are actually fighting the good fight.
I hear there's this popular service that makes it easy to
On Sun, Aug 9, 2009 at 2:52 PM, Sean Callahan wrote:
>
> Agree with what you said. Very well put. It is affecting most all of
> us. Our photo sharing service (TweetPhoto) is tied into 20 apps whose
> users aren't able to upload photo onto our platform. I've communicated
> by adding an alert to our
Hmmm just realized Twitter posts via the API from www.LiveBaseballChat.com
aren't showing up in the twitter search stream.
So anything with #Twins or #Tigers from @LBBchat is showing up in the profile
http://twitter.com/LBBChat
BUT NOT appearing in http://search.twitter.com/search?q=tigers
Agree with what you said. Very well put. It is affecting most all of
us. Our photo sharing service (TweetPhoto) is tied into 20 apps whose
users aren't able to upload photo onto our platform. I've communicated
by adding an alert to our homepage about the issues which broadcasts
the message and hop
Hi Ryan,
Some details from my perspective...
1. OAuth rarely works - I tried a number of your apps and it seems
to work 1
out of 6-7 times. As a note, it worked better with Safari, but not
every
time.
Sporadic all day today. At its worst I'd agree that about 1 in 7
succeeds, but it oft
Not to mention that http://search.twitter.com still appears to be completly
blocked from the app engine.
Paul
2009/8/9 Naveen Ayyagari
>
>
> 1. OAuth rarely works - I tried a number of your apps and it seems to work
>> 1 out of 6-7 times. As a note, it worked better with Safari, but not every
>
1. OAuth rarely works - I tried a number of your apps and it seems
to work 1 out of 6-7 times. As a note, it worked better with Safari,
but not every time.
-Not applicable
2. 302 redirect
- not sure anymore since our code has been updated to follow them
automatically.
3. Genera
It will be fixed when it is. Stop complaining. We're all in the same
boat. The ETA is "when its done".
dave
On Aug 9, 1:08 pm, freefall wrote:
> Decentralisation.
>
> On Aug 9, 5:47 pm, Dewald Pretorius wrote:
>
> > I wonder how many times this weekend has Chad heard, "FO, we're busy,"
> > whe
A few of you are acting like real children and a few of you still have
your heads screwed on right.
I'm confident they are doing everything they can. Chill and enjoy your
weekend. They'll get it sorted out.
What did you guys do in 2007? Twitter was down all the time then. Your
blood pressure mus
The one client we are having the most issues with is simple a
timeline / DM checker for iPhone push notifications... because these
are ALL get request I'ved made sure that they all have the follow
location enabled now.
Just oAuth and random blocking/rate limiting that I hope they work on
next :)
I'm disgusted by you guys. Were any of you around in 2007 when Twitter
was down nonstop? Did you bitch and moan as much then? You're acting
like children.
The reason they are still facing issues is because of the DDoS. Oh,
and they are still also coping with scaling overall and astronomical
growt
When calling http://twitter.com/statuses/user_timeline.xml via OAuth
(no id passed, looking for information on the authenticated user), I
am seeing this response:
Not sure if that's in the list of things being monitored, but there
you go.
On Aug 9, 1:42 pm, Dewald Pretorius wrote:
> On Aug 9
They haven't overreacted. If you think you can do better, then apply
for a job with them. Have you tried your account from multiple IP
blocks?
They have faced a crushing attack. They are working on it and they
have worked hard to communicate with us the status of things.
Anyone that was around i
:D
On Sun, Aug 9, 2009 at 11:42 AM, Dewald Pretorius wrote:
>
> On Aug 9, 2:34 pm, Ryan Sarver wrote:
> >I will continue to give ongoing updates
> > every 5-6 hours throughout the day even if nothing has changed so that
> you
> > know we are still focused on it.
>
> Now THAT'S what we're talkin
It is true, perception at this time is very important - even more
actually.
Annoyed people can make hasty choices, write unfavorable articles etc.
So as crappy as it is to keep feeding us all updates, it's worth it a
100 fold in the long run especially since Twitter's business is based
Nice story Adam, however the band are actually trying to run a
business, not doing this for love/free. I can assure you the investors
in Twitter will be looking to turn profit. Of course if the band are
laid up then the danger is the hotdog man (and all his customers) will
go to another ban
On Aug 9, 1:07 pm, Jesse Stay wrote:
> I'm really surprised at
> all the people having issues with 30* redirects when it's an HTTP standard
> in the first place.
Don't be so quick to judge - Twitter's been sending 302's with a
Location header that specifies a relative URL, which goes against
On Aug 9, 2:34 pm, Ryan Sarver wrote:
>I will continue to give ongoing updates
> every 5-6 hours throughout the day even if nothing has changed so that you
> know we are still focused on it.
Now THAT'S what we're talking about!
Thank you Ryan. It may not seem important to busy Twitter folks to
I agree, and I know the Twitter Ops guys are probably exhausted and
working around the clock to keep the system running. I have the
utmost respect for it having been responsible for a website before
that suffered from DDoS attacks on occasion.
Twitter.com seems to be running pretty well right no
***Scenario***
A band broadcasts their music on a radio station all the time, and people
are able to freely tune into it, or go buy their music. They go and play in
a city park for free every day just because it's a much nicer experience for
the listener then to be just sitting at home listening o
I see this behavior 1/4 times I call rate_limit_status and I call
rate_limit_status every 5 minutes..
On Aug 8, 2009, at 9:01 PM, CaMason wrote:
>
> To confirm, I am also seeing this behaviour. Some output I've received
> on numerous occasions this evening:
>
>
> -bash-3.2# curl --interface eth
I wanted to send an update to everyone who is monitoring this thread and
keep you abreast of where we stand.
First of all, the attack is still on going. We continue to work with our
service provider and the other companies who are being attacked to resolve
the issue as best we can. But it is contin
Decentralisation.
On Aug 9, 5:47 pm, Dewald Pretorius wrote:
> I wonder how many times this weekend has Chad heard, "FO, we're busy,"
> when he tried to get a status update for us.
>
> On Aug 9, 1:42 pm, Jesse Stay wrote:
>
>
>
> > Good luck.
>
> > On Sun, Aug 9, 2009 at 6:01 AM, Jacob wrote:
I got thinking about the whole DDoS situation, and while I certainly have my
own opinions around all of this, there's nothing I can do about it. What I
can do though is figure out ways I can improve the systems I'm working in.
The place I think this starts is in our own Twitter libraries we work
Just so I'm clear, my suggestion on PubSubHubbub isn't meant to be a
complaint. I'm hoping it at least starts a worthy and constructive
discussion on standards-based real time distribution. I'm hoping I'm being
constructive here - I'd like to see Twitter survive the next DDoS, and I'd
also like to
Your site was probably making too many API requests in too short a
time.
Also, do you have a unique user agent set when you access the API? And
are you respecting any 302 redirects on GETs and POSTs?
On Aug 9, 1:56 pm, Sean Callahan wrote:
> Hi Guys,
>
> After the original DDoS attack our servi
> "Stuart" == Stuart writes:
Stuart> * I can't believe you lot don't realise that constantly demanding
Stuart> status updates, while certainly important to you, is little more
Stuart> than a distraction for those who are actually fighting the good
Stuart> fight.
I woke up this morning with
Hi Guys,
After the original DDoS attack our service, TweetPhoto.com, was
blocked. After communicating my IP addresses an waiting about 48 hours
it vegan working Friday afternoon. All of a sudden yesterday
afternooon no one could login to our site. I wonder why our site was
restored Friday in term
On Sat, Aug 8, 2009 at 9:06 PM, Jesse Stay wrote:
> I know Twitter has bigger priorities, so if you can put this on your "to
> think about" list for after the DDoS problems are taken care of, I'd
> appreciate it. Perhaps this question is for John since it has to do with
> real-time. Anyway, is
On 9 Aug 2009, at 16:35, Dossy Shiobara wrote:
On 8/9/09 10:00 AM, Joe Bowman wrote:
First off, to people stating that Twitter Ops needs to work 30 hour
shifts, and any ops person who hasn't, isn't a real ops person. A
real
ops person knows that after about 15 hours their mental capacity t
I wonder how many times this weekend has Chad heard, "FO, we're busy,"
when he tried to get a status update for us.
On Aug 9, 1:42 pm, Jesse Stay wrote:
> Good luck.
>
> On Sun, Aug 9, 2009 at 6:01 AM, Jacob wrote:
>
> > I have thousands of people coming to my application only to get
> > "Twitt
Good luck.
On Sun, Aug 9, 2009 at 6:01 AM, Jacob wrote:
>
> I have thousands of people coming to my application only to get
> "Twitter Api is not responding!" can Twitter team help me?
> I'm aware of the API difficulties, but, I need some answers or maybe a
> date when the problem will be fixed.
1 - 100 of 161 matches
Mail list logo
