Stay N' Alive - Latest Comments in Twitter Kills Important Features on the API With Just a Few Hours Notice

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

naterkane — Sun, 01 Jun 2008 04:15:58 -0000

it just has to do with taking a reactive instead of proactive approach to development.
moving their api to a cloud (amazon's or someone else's) would relieve a lot of their stress. it's difficult to stress-test any application or api, especially when it's setup to have so many different points of I/O.

this is the post i was talking about in my last comment. it's a bit more of a rant than anything else, but i'm just getting frustrated by all of the content-less noise that people are generating around what is going on with Twitter. http://www.naterkane.com/blog/2008/05/29/a-twee...

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

jessestay — Sun, 01 Jun 2008 03:01:03 -0000

They say they know how to fix it, and based on their latest blog post, they
seem to have the expertise to do it. With mistakes like yesterday's though,
I still wonder what's going on.

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

Bernie Goldbach — Sun, 01 Jun 2008 02:54:51 -0000

I wonder if the Twitter staff have commissioned an externally-evaluated code audit on both the core processes and the API calls because from the outside looking in, I doubt that any amount of new hardware will boost Twitter reliability.

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

Brent — Sun, 01 Jun 2008 01:00:43 -0000

no, but will do. thanks.

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

jessestay — Sun, 01 Jun 2008 00:43:05 -0000

Brent, I'm not sure what that is - have you tried submitting a request over
at Get Satisfaction? (getsatisfaction.com/twitter)

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

Brent — Sun, 01 Jun 2008 00:40:57 -0000

right on. i can dig that.

lately I have been getting this fun little popup asking me to log my username and password AFTER I have logged in, and mostly when I go to the Replies section. I click Cancel, and it goes away... for a few minutes. Any idea what it is? http://www.flickr.com/photos/mopedronin/2540736... Besides 'annoying' I mean.

And 'Twitter is over capacity'... >.>

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

jessestay — Sun, 01 Jun 2008 00:18:03 -0000

Brent, in layman's terms, be very careful relying on Twitter as your main
underlying business model. They have admitted and shown their architecture
is not ready for it.

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

Brent — Sun, 01 Jun 2008 00:06:33 -0000

I'm afraid I didn't understand a single thing written in this article. What is it you are trying to say, in layman's terms?

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

jessestay — Sun, 01 Jun 2008 00:05:04 -0000

naterkane I agree and that's why they're under the gun. People are under
the impression they're much bigger than they are when in reality they don't
have the infrastructure to handle their popularity.

Re: Twitter Kills Important Features on the API With Just a Few Hours Notice

naterkane — Sat, 31 May 2008 23:56:51 -0000

I just wrote the other day about anyone who relies on an API they don't control as a critical part of their business or app are idealistic (and maybe even foolish to a degree). APIs that are developed by larger companies (Yahoo!, Amazon, etc.) who are just extending an existing infrastructure are of course reasonably reliable enough that many people have had great successes building on those APIs. A small company like Twitter however can't be trusted to be anything more than a toy. A toy that has been very useful and changed the way many people and companies communicate, but still just a toy.