Karthik Setty's dashboard

Hi Santosh, Here's what you can do: 1. Confirm your device using twitter's international number (hopefully you'll start receiving smses) 2. Connect your twitter account with vakow account (to post via vakow's number) – rg, on June 13, 2008 06:42

I am using Vodafone (Hutch) and still I am not able to send SMS it says "Message sending failed."

Actually, figured it out. I didn't realize you had to specify the site and CSS... I was expecting it to work for just any site. It wasn't working for Google, but I'm in Singapore, so I needed to add "www.google.com.sg*"... it's working now. Really, really cool. The photo browsing feature is awesome.

On that note, is there a reference out there for the CSS styles for different sites. I'm sure I could find it, but any links you could provide would be appreciated.

rogi i'll need a much more detailed error report to help. detailed steps on how you created the ssb, and what you are doing with it that leads to unexpected behavior.

I'm having this problem even with 3.1.1 ; Fluid version 0915

Do you currently pay (if you're not on roaming)? No (it's against TRAI guidelines). So, receiving messages from Twitter doesn't cost either. – sol, on May 27, 2008 19:07

No you don't. Receiving the SMS is not charged. However, twitter only lets you receive 250 SMSs per month. – Preshit, on May 27, 2008 17:56

Do i need to pay for recieving twitter messages on my mobile phone ?? I am from india...

Hi Todd, I had safari 3.0.4, upgraded to 3.1.1 and it works like a charm! You have an amazing product. Thanks for you help! – Karthik Setty, on April 29, 2008 12:21

Hi k, you will need to make sure you have safari 3.1 installed. Run software update, update your safari and you'll be good.

Hi Non-Sequitur,

I hear you. And good points all.

We have myriad systems and scripts in place to check and triple check everything, texting/paging and otherwise notifying us at all hours if something even seems close to being a problem. Unfortunately this was one of those rare conditions where something we had not anticipated bit us (and you). We've new systems going into place right as I type this to make sure this edge case and any others we can anticipate around this issue won't come up again.

As for a status message on the site, coincidently enough one of the things I added to the site just yesterday was a message banner through which we can notify Sandy's clients of any issues (specific to them or otherwise). It is already in action for issues around account activation, but I'd just not yet had the chance to enable additional notifications. That'll be in tomorrow, I can assure you.

Rael

Well to be honest I was thinking that even something that was nothing more than a few scripts that checked her status and/or queue and sent out via email. Preferably from you all instead of a third party like Get Satisfaction. This way mobile users would not be flooded with a million emails that were not related just because we created or responded to other Get Satisfaction issues.

Also I still think that a little status icon on the website would be a good move. After all if we check that and the site is down then it is obvious that Sandy is most likely having issues of her own.

Hi Non-Sequitur,

Thanks for your thoughtful suggestions!

For an out-of-band email process with the ability to pick and choose topics you're interested in, GetSatisfaction's "Follow this topic" functionality seems to fit the bill.

For Sandy status updates, visit http://getsatisfaction.com/iwantsandy... and click the "Follow this talk topic" link beneath the first post.

If you're also interested in any new features, fixes, etc you might also consider following the "Updates" topic at http://getsatisfaction.com/iwantsandy.... We post there with detailed notes whenever we push a new version of anything to our servers.

(Do make sure you have your GetSatisfaction account set up send you email about topics you follow (under Account > Email & Notifications) [see http://getsatisfaction.com/satisfacti... for more info].)

We are usually pretty on the ball about posting to there when there are status updates (good and bad) to report. And it is completely out-of-band and so doesn't rely at all upon Sandy or iwantsandy.com being available.

Having this on the main site wouldn't be much of a protection in the eventuality that the site weren't reachable, I'm afraid.

The one thing that would have made all of this probably a lot smoother today would have been if I'd moved a little faster to post in the first place.

If you've any suggestions or pointers to other things that might have worked well, please do pass them my way. While balancing fixing the problem and reporting back with anything approaching helpful details is prime for me, anything else I can do to accomplish more of both of these goals is pure gold!

Best,

Rael