Helge's dashboard

Helge replied on July 04, 2008 10:38 to the problem "Google calendar doesn't send email reminders for some of my events any more" in Google:

When I try to delete this problem I get "AccessDeniedError"

Helge replied on July 04, 2008 10:36 to the problem "Google calendar doesn't send email reminders for some of my events any more" in Google:

Somehow the problem disappeared. But I don't know why. I haven't changed a thing. I hope this doesn't happen again.

mdy replied on July 04, 2008 10:26 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

Thanks, santiago! I had an account where the IM was not yet verified and it showed me #3. Since then, I have clicked the 'delete and start over' button (which is how I know it reverts to #2 after you delete) so I can't see what it would have displayed now.

I actually prefer it to be the way you now describe it. Since it's currently not possible to verify IM, it's better to just not display IM device settings at all if it's not yet verified. Otherwise, people who have added IM but haven't yet verified it may get the impression that it's possible to verify.

santiago replied on July 04, 2008 08:40 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

Hi mdy. I don't think no. 3 is quite accurate. I added IM some time ago but never got verification. Now all I see are options to edit my Mobile Phone settings just like no. 2. Pending verification gone, option to add/edit/delete IM gone.

mdy replied on July 03, 2008 04:24 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

Looks like the http://twitter.com/devices page has been updated and what you see depends on your IM status.

1. If you already have IM added and verified, it will show you your current IM settings and allow you to change notifications to OFF and allow you to delete.

2. If you haven't tried adding IM before, you won't even see an option to add it. You'll only see an option to add or change your phone device settings.

3. If you have already added IM but it's still not verified, you will still see your unverified IM settings and the verification code that needs to be sent. If you hit 'delete and start over,' you'll get a screen similar to #2 above.

robotfrog replied on July 03, 2008 03:50 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

I appreciate Jason's response as an employee, but frankly twitter as a business, not an employee, needs to respond. I'm still using it, but I've advised colleagues to look elsewhere due to this situation. Capabilitiy problems, databases down, website overload, it's all quite amateur -- especially as these events keep repeating themselves over and over. Really, change the stupid webpage, tell people it isn't working, and quit promising that you're going to fix it. I'm giving it another week, then I'm looking elsewhere.

waffles replied on July 02, 2008 21:09 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

That would have been a lot more helpful a month ago when it went down in the first place.

Chris Thomson replied on July 02, 2008 20:53 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

A notice is going to be put up on the devices page today, according to @jack. Here's what I @'d to him:

"@jack: Is Twitter going to put a notice on the devices page saying IM is down so that newbies don't spend hours trying to figure it out?" (tweet link)

And he replied:

"@chris24 Yes. Today." (tweet link)

waffles replied on July 02, 2008 13:31 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

Is it sad when that's the best thing I've heard in this thread for a long time?

A comment on the problem "Twitter IM down May 23rd-May24th" in Twitter:

So, Jason, why can't you put up a notice on the devices page? That's what I just don't get. It's rude and stupid not to do so. It displays a disregard for your users that just makes no sense to me. What's the upside of NOT putting that information where a new user will see it, and so making them run in circles trying to figure out what's wrong on their end. Please explain it to us! RP – Russ Palmeri, on July 02, 2008 00:08

jesse replied on July 01, 2008 22:47 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

All of us should post links to this thread on our Twitter accounts.

waffles replied on July 01, 2008 22:32 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

In my mind, there's a big difference between "It'll be back Thursday" and "We'll try our best to have it up in the next few days/weeks/before the end of the month."

Honestly, we've heard that it's being worked on. So what exactly is making this take so long? Is there a soft deadline y'all have set for yourself to get it back up? And if so, when is it?

At this point, being completely transparent is about the only way to save face. We've heard the "It's coming back" speech before. And at least with me, it no longer holds a grain of truth until I can see some sort of action to back it up.

A comment on the problem "Twitter IM down May 23rd-May24th" in Twitter:

This still doesn't address the fact that several areas of your site still advertise IM as a (working) feature -- especially on the devices pages, where it seems like you can activate it on the spot. Newer users trying to activate this feature (like me) get frustrated when they try to set up something that isn't working (see my previous posts.) – SeanO, on July 01, 2008 19:30

A comment on the problem "Twitter IM down May 23rd-May24th" in Twitter:

Thanks for the update Jason. I'm glad to hear that IM will come back eventually ;) – Chris Thomson, on July 01, 2008 19:19

A comment on the problem "Twitter IM down May 23rd-May24th" in Twitter:

Thanks, Jason, for the update! – Eric Suesz, on July 01, 2008 19:10

Jason Goldman replied on July 01, 2008 18:52 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

Wanted to provide you with an update on the situation with IM. We are
going to bring this service back. We think it's a central part of what
Twitter does.

To bring it back, we had to replace a good chunk of the code that was
powering the older IM service. That work is mostly complete.

However, releasing the new code is challenging given the current
amount of site load. We don't want to bring IM back only to have to
take it away again. So we're working to stabilize the site and will
then bring IM back.

I know this explanation isn't as satisfying as "It will be back on Thursday." But I don't want to mislead.

boink replied on July 01, 2008 15:31 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

What's our alternative then? Friendfeed? Pownce? Plurk?

waffles replied on July 01, 2008 14:08 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

Seriously, if something doesn't work then you should let everyone know. Current users need to be told so they don't think something is wrong on their end. New users need to be told for the same reason, and because I know some people signed up because of IM support.

There is no reason why we should be into July and no solution to the problem is in place.

So Twitter, what is going on?

Why is it taking this long to get IM back up to working?

Why haven't the users been told for the past 40 days or so what the real status of IM is? And no, status updates int he status blog saying that it's being worked on don't count.

I mean no offense in this next request, so for those effected please don't take any. But...

I want to hear this in video form from the heads, and not some employee responding to this thread. Not only do I think the heads of Twitter will have better information, I think they need to prove that they stand behind their product. Because as of now, the customer service has gone to Hell with this whole issue.

fabio replied on July 01, 2008 13:56 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

twitter is saying: bye-bye customers..........and I say: bye-bye twitter....

jesse replied on June 30, 2008 23:33 to the problem "Twitter IM down May 23rd-May24th" in Twitter:

Except that they *still* advertise it on the front page for new users, and users who never set it up. No, I think this is just blatant laziness/incompetence/disregard.