> 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

> > On Jan 31, 2008 5:58 PM, Andy Bilodeau <andyc...@gmail.com> wrote:

> > > 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.

> > > On 1/31/08, Jesse Stay <je...@thestays.org> wrote:

> > > > 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

> > > > On Jan 31, 2008 4:45 PM, Andrew Badera <and...@badera.us> wrote:
> > > > > 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?

> > > > > On 1/31/08, Jesse Stay <je...@thestays.org> wrote:

> > > > > > 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

> > > > > > On Jan 31, 2008 12:21 PM, Andrew Badera <and...@badera.us> wrote:
> > > > > > >http://blog.twitter.com/

> > > >https://www.blogger.com/comment.g?blogID=23958943&postID=191028904555...

> > > > > > > On 1/31/08, Hamish Campbell <HN.Campb...@gmail.com> wrote:

> > > > > > > > So.... where have all the tweets gone? Been a day and a bit now...

> > > > > > > --
> > > > > > > --Andy Badera
> > > > > > >http://andrew.badera.us/
> > > > > > > and...@badera.us
> > > > > > >  (518) 641-1280
> > > > > > > Google me:http://www.google.com/search?q=andrew+badera

> > > > > > --
> > > > > > 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

> > > > > --

> > > > > --Andy Badera
> > > > >http://andrew.badera.us/
> > > > >  and...@badera.us
> > > > > (518) 641-1280
> > > > > Google me:http://www.google.com/search?q=andrew+badera

> > > > --
> > > > 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

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

> > --
> > 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- Hide quoted text -

> > - Show quoted text -