On the fritz

1 view
Skip to first unread message

Hamish Campbell

unread,
Jan 31, 2008, 2:19:09 PM1/31/08
to Twitter Development Talk
So.... where have all the tweets gone? Been a day and a bit now...

Andrew Badera

unread,
Jan 31, 2008, 2:21:50 PM1/31/08
to twitter-deve...@googlegroups.com

Jesse Stay

unread,
Jan 31, 2008, 6:43:11 PM1/31/08
to twitter-deve...@googlegroups.com
Why can't Twitter broadcast a message to everyone when there are
issues? I don't think everyone follows the blog, and not everyone
checks Twitter to find out what's happening. I would love to have
more communication like that - I know people are getting frustrated
with the many outages, and lack of communication. Perhaps a global
friend that is unremovable and everyone follows? You could then use
that follower to broadcast system status messages to all.

Jesse

--
Jesse Stay
Facebook, Bebo, OpenSocial Expert

Partner, CSO: http://www.SocialOptimize.com
Co-Author: I'm on Facebook -- Now What???
http://FacebookAdvice.com
Blogger: http://www.jessestay.com
http://www.socialoptimize.com/blog

Phone: (801) 853-8339

Andrew Badera

unread,
Jan 31, 2008, 6:45:33 PM1/31/08
to twitter-deve...@googlegroups.com
Personally, I'd rather the dev team were working to fix the problem, than writing emails to us about it. It's a free service. There's a blog, and they're getting better about using it. Why does there need to be more than one point of public contact, when that point provides up to date information in an interactive fashion?

Jesse Stay

unread,
Jan 31, 2008, 7:46:24 PM1/31/08
to twitter-deve...@googlegroups.com
The problem is, no one knows there's a blog (I saw someone suggesting
the other day that Twitter get a blog). There needs to be a resource
that Twitter can announce stuff like this and have all of their users
know why things are happening, even if it's sending messages like, "we
just got a blog - add us to your rss to find out why and when we are
down". The biggest complaint I hear out there isn't necessarily the
outages - we know Twitter is going through growing pains. It's the
lack of communication that I hear most complaints about. Twitter is a
big conversation - I doubt people would complain about occasional
additions to the conversation explaining to those complaining why
Twitter is down. Twitter themselves need to join the conversation,
use their own tools!

Jesse

Piers Karsenbarg

unread,
Jan 31, 2008, 7:49:20 PM1/31/08
to twitter-deve...@googlegroups.com
I think the phrase is "You get what you pay for"

Jesse Stay

unread,
Jan 31, 2008, 7:53:48 PM1/31/08
to twitter-deve...@googlegroups.com
It's not me complaining (okay, I'm frustrated too) - it's others I'm
hearing complaining, and I've heard a large number of threats to leave
Twitter because of it. I'm just giving some friendly advice. Take it
how you want - I'll leave this conversation alone from here on out.

Jesse

Andrew Badera

unread,
Jan 31, 2008, 7:57:53 PM1/31/08
to twitter-deve...@googlegroups.com
It would be nice if the error page had a link to the blog.

Andy Bilodeau

unread,
Jan 31, 2008, 7:58:25 PM1/31/08
to twitter-deve...@googlegroups.com
Umm...using Twitter to announce that Twitter is down is like calling
the phone company to tell them your phone line is down.

If Twitter is broke for us, it's broke for the dev team too.

I agree there could be more advertising of the existing blog, but for
the dev team to create an additional stream of information might be
asking for a bit much.

Maybe they could Utter (www.utterz.com) about outages...or use Jaiku
or pownce...or just make sure their blog is up to date.


--
Andy Bilodeau (andycaster)
http://andycast.net

Jesse Stay

unread,
Jan 31, 2008, 8:05:09 PM1/31/08
to twitter-deve...@googlegroups.com
I know the Twitter devs can't do it in every case, but they can
definitely get "in the conversation" more. The only thing I don't see
on Twitter is Twitter itself. I like the idea of the error page
having a link to the blog - there still needs to be a way to get the
word out to the other 40-50% using external clients though. Last
night I was able to send messages on and off - I'm sure Twitter could
have sent something out during those up times to just warn of the
situation.

Jesse

Hamish Campbell

unread,
Jan 31, 2008, 8:16:53 PM1/31/08
to Twitter Development Talk
An un-removable friend isn't great, since those of us building bots
and apps don't won't service notices getting in the way --- but a
'default' friend that everyone gets when they start out (and can be
removed) isn't a bad idea... even if it's just a bot that points to
new twitter blog posts.

Anyway, good to see the team are sorting it out.

BTW: Yes, it's free, but that doesn't mean they don't need some
'constructive' feedback when so many app writers and developers have
dedicated time to using their platform.

Also, it might be free now, but you can bet that the end-game is not
for twitter to continue it it's current form ad-infinitum. The value
of twitter (to the owners) is the number of people using it and the
number of people developing for it. We are customers -- perhaps not in
the traditional sense -- but customers nonetheless.

Ciao,

Hamish Campbell

On Feb 1, 2:05 pm, "Jesse Stay" <je...@thestays.org> wrote:
> I know the Twitter devs can't do it in every case, but they can
> definitely get "in the conversation" more.  The only thing I don't see
> on Twitter is Twitter itself.  I like the idea of the error page
> having a link to the blog - there still needs to be a way to get the
> word out to the other 40-50% using external clients though.  Last
> night I was able to send messages on and off - I'm sure Twitter could
> have sent something out during those up times to just warn of the
> situation.
>
> Jesse
>
> > >https://www.blogger.com/comment.g?blogID=23958943&postID=191028904555...
> Phone: (801) 853-8339- Hide quoted text -
>
> - Show quoted text -

Jesse Stay

unread,
Jan 31, 2008, 9:05:40 PM1/31/08
to twitter-deve...@googlegroups.com
I agree - perhaps "unremovable" isn't the best idea. A default friend
would be a great idea though!

Jesse

Scott Orn

unread,
Feb 1, 2008, 1:31:16 PM2/1/08
to Twitter Development Talk
This reminds me of the early days of eBay. It crashed constantly and
was a huge issue. However perverse, it actually get's me even more
excited about Twitter. The outages are a combination of traffic
skyrocketing and the company trying to rearchitect to handle even
greater loads. They're at least actively trying to address it and the
skyrocketing usage is great news for all of us building applications
on top of Twitter. I'm very confident they'll figure it out, just like
eBay did, and we'll be really well positioned as the first apps/
services out there when a broader part of the population adopts.

My friends and I are finalizing our Twitter application direction. If
you are a talented technical person and looking for something
interesting, give me a shout at scot...@gmail.com and put Twitter in
the Subject line.

Keep the faith folks, these are good problems to have for Twitter.

Scott


On Jan 31, 6:05 pm, "Jesse Stay" <je...@thestays.org> wrote:
> I agree - perhaps "unremovable" isn't the best idea. A default friend
> would be a great idea though!
>
> Jesse
>

Andrew Badera

unread,
Feb 12, 2008, 7:38:17 AM2/12/08
to twitter-deve...@googlegroups.com
Not to beat a dead horse, but for those unaware, Twitter (for whatever reason, I still don't get it) uses getsatisfaction.com to discuss a lot of ongoing or current issues, and the active discussions are also available as a feed at https://help.twitter.com/

Of course, this has received no more real publicity or promotion than the blog ... but it's out there for those who want it.
Reply all
Reply to author
Forward
0 new messages