VentureBeat - Latest Comments in Twitter: Don’t blame Ruby, blame Scoble

Re: Twitter: Don’t blame Ruby, blame Scoble

nolimitdomains — Fri, 27 Jun 2008 12:47:41 -0000

Twitter is no where to be found again today!
Oh where oh where has my little Twitter gone?
Geez, did they ban me for being funny?
Were my posts soooo entertaining that a few people felt the need to
"put a hit on me?"
Was it that last joke I told..? u know the one about the @@##!@
I am embarrassed! When a Free site wont let you in...
It Sucks!

Re: Twitter: Don’t blame Ruby, blame Scoble

Avatar X — Mon, 02 Jun 2008 05:00:46 -0000

seesmic is fine in IE7 and IE8 for that matter. the problem seems to be lots of random time outs. that happen in any browser. i use IE8 (modded) and Flock 1.2.

Re: Twitter: Don’t blame Ruby, blame Scoble

Yohan Yukiya 사요한 謝雪矢 — Sat, 31 May 2008 22:45:10 -0000

"You work PR like a third world nation. When you are in doubt, blame America right?"

What's that supposed to mean? Don't mix the two. PR and blaming America are two totally different things.

Ouch from us here in the 3rd world countries.

Re: Twitter: Don’t blame Ruby, blame Scoble

Yohan Yukiya 사요한 謝雪矢 — Sat, 31 May 2008 22:34:38 -0000

Yes. Time to move to Jaiku and Pownce "popular" people, and the rest of us will follow.

Re: Twitter: Don’t blame Ruby, blame Scoble

Yohan Yukiya 사요한 謝雪矢 — Sat, 31 May 2008 22:32:51 -0000

Yah. "Popular" people made Twitter famous. They put twitter where it is now today. Blaming these "popular" people is not the way to go.

I wonder what will happen to twitter if these popular people they are talking about suddenly leave them and move to Jaiku and Pownce?

Maybe that will help them solve their problems, because these popular people will be bringing with them a HUGE CHUNK of their userbase.

How about we do just that?

Im just curious...

Re: Twitter: Don’t blame Ruby, blame Scoble

Laforge129 — Sat, 31 May 2008 21:33:49 -0000

Now as I know more and more, it's not Scoble who did this, they need to fix the problem at hand, not enough servers that can't handle the load!! Then they need to have it also auto-switch when one goes down. All this would lessen the load per say.

Re: Twitter: Don’t blame Ruby, blame Scoble

Scobleizer — Sat, 31 May 2008 14:05:34 -0000

I went over to talk with Twitter's founders/executives yesterday to hear their side of this story and here it is: http://qik.com/video/90546

Re: Twitter: Don’t blame Ruby, blame Scoble

stevemac — Fri, 30 May 2008 20:40:22 -0000

Chicken and egg. You don't have the money to do it right up front, but then when you need it you don't have the time to restructure for scaling reasons.

Will thinks like Amazon S3, Microsoft Mesh or Google's AppEngine be the solution to scaling issues?

Re: Twitter: Don’t blame Ruby, blame Scoble

Anonymickymouse — Fri, 30 May 2008 18:18:13 -0000

I'm with you Scoble. I have a feeling those guys either know what the problem is and don't want to say it, or really have no idea and are just scrambling to fix whatever is breaking the service at the moment.

How many stuck-up Ruby engineers with CS degrees does it take to build a stable platform?
Answer: It's impossible because you just keep blaming your users instead of fixing your crap.

If I seem overly harsh try looking at how they respond to developers on their Google Groups page (http://snipurl.com/2bnad), or another fine example of how they treat their users: http://snipurl.com/2bnao

It looks to me like the giant smug cloud that surrounds that place is what's clogging up their tubes.

Re: Twitter: Don’t blame Ruby, blame Scoble

Vinny — Fri, 30 May 2008 16:27:38 -0000

Not really. Friendfeed doesn't have anywhere near the volume that Twitter does, and doesn't have anywhere near the immediacy twitter users demand. Apples and oranges. I'm not saying Twitter's downtime isn't a problem; it certainly is, but comparing it to friendfeed isn't really fair.

Re: Twitter: Don’t blame Ruby, blame Scoble

Noah David Simon — Fri, 30 May 2008 15:52:55 -0000

no you are to blame to Shel. down with the Alist SPAM

Re: Twitter: Don’t blame Ruby, blame Scoble

Noah David Simon — Fri, 30 May 2008 15:51:08 -0000

the problem is 3000 friends or more on any network Robert Scoble! What is your real motive? MARKETING! with the kind of following you have, you should be taking on more social responsibility (no not soup kitchens... you should be involved in the social issues between people other then yourself. People are getting harrassed by your so called friends), badmouthing the troops in Iraq? You work PR like a third world nation. When you are in doubt, blame America right? We Won't Be Fooled Again

Re: Twitter: Don’t blame Ruby, blame Scoble

Nigel Eccles — Fri, 30 May 2008 15:33:44 -0000

Damn right. Tweet on!

Re: Twitter: Don’t blame Ruby, blame Scoble

Vinny — Fri, 30 May 2008 14:54:52 -0000

Nobody "Blamed Scoble."

Re: Twitter: Don’t blame Ruby, blame Scoble

Fred — Fri, 30 May 2008 14:41:33 -0000

I'm sorry, who are you again?

Re: Twitter: Don’t blame Ruby, blame Scoble

Chris Baskind — Fri, 30 May 2008 14:33:21 -0000

Yes, of course there's a difference in the architecture. But AIM has almost 40 million users. Twitter is breaking as they cross the 1 million threshold. Time for a re-think. Their database requirements must be staggering.

Re: Twitter: Don’t blame Ruby, blame Scoble

glynsync — Fri, 30 May 2008 13:45:04 -0000

Jesus, get one (1) grip. Question asked if there was anything users could do to reduce strain, Payne responded by illustrating the circumstances under which the current architecture was having problems (users with large numbers of followers), *without allocating blame or naming names*, and blogland goes apeshit.

I'm as annoyed at Twitter's crap scalability as the next person, but being this butthurt about defensively-implied fingerpointing is retarded.

Re: Twitter: Don’t blame Ruby, blame Scoble

William Pietri — Fri, 30 May 2008 13:15:38 -0000

Blaming the technologies is indeed a little weird. Responsible people load test before shipping, so that they know what will happen. The problem is Twitter's and Twitter's alone.

But if I were to point at a technological choice, I'd say it would be building this around a traditional database-centered architecture. The nice thing about Rails is that you don't have to think too hard to get something up and going. The downside is that when you're up and going, you may not have thought very hard.

Re: Twitter: Don’t blame Ruby, blame Scoble

Ben — Fri, 30 May 2008 13:05:07 -0000

RoR has been 'dead' for quite a while! It was a mistake to write Twitter in it.

Re: Twitter: Don’t blame Ruby, blame Scoble

113.com — Fri, 30 May 2008 12:33:10 -0000

Nobody to blame, except Twitter itself. Learn from Google (of 1998), people.

Re: Twitter: Don’t blame Ruby, blame Scoble

MG Siegler — Fri, 30 May 2008 12:19:57 -0000

Good stuff Mike, thanks.

Re: Twitter: Don’t blame Ruby, blame Scoble

Eric Rice — Fri, 30 May 2008 12:18:01 -0000

Twitter is teaching us to skim. 140 characters or less, get to the point. It's not making us smarter media consumers, regardless of WHO makes the media: outlets big or small.

So yeah, we might have missed the point but headlines and keywords sell, not details. We can thank ourselves for that.

Re: Twitter: Don’t blame Ruby, blame Scoble

Eric Rice — Fri, 30 May 2008 12:15:16 -0000

Ahahahahahaha, seriously? I post more than Scoble and Chris Brogan posts more than me. I also have 3 + a couple fake accounts. I'm to blame, too. And I also get around that stupid-assed 140 character limit by posting sometimes as many as 70 tweets in a row. Sue me.

It's a lot of text and a database. I think that's been done on the internet before.

Dear Web 2.0: Never ever work in internet porn if you can't keep things up. And running.

Re: Twitter: Don’t blame Ruby, blame Scoble

mdoeff — Fri, 30 May 2008 12:13:42 -0000

I actually think they were blaming two separate groups - popular users like Scoble, Calacanis, etc. But they also mentioned the use of scripts. Re: these scripts, the issue is not that few people follow the spam users. The issue is that the spammers are running rogue applications that follow massive amounts of followers in a short amount of time. Here is a screenshot of an app that looks for EVERYBODY who is currently using Twitter and follows them. http://www.livelybrowser.co...

Re: Twitter: Don’t blame Ruby, blame Scoble

MG Siegler — Fri, 30 May 2008 12:10:30 -0000

Ha ha, no my bad, I missed your clever insert.