Please enter your username below and press the send button.A password reset link will be sent to you.
If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.
This link recently saved by stuart_henshall on September 18, 2009
Many of the notes I made yesterday for Jajah's @call service would apply to this solution. Both have a fundamental problem... they are giving away free minutes. That costs real bucks quick. These solutions have to move beyond "minute" models. Danielle is right to use oAuth and recognize that these services can tie into any social network. Where Phweet really differs is recognizing that the "context" for the call is important and that we don't always want to share our number even via a DM on Twitter if possible. What Phweet demonstrates in my view is not about voice rather it is about the negotiation opportunity. That's why we have a URL. That's the core contract between the parties.
This link recently saved by stuart_henshall on June 01, 2009
"Twitter may not replace the landline, the cell phone or voice and texting communications but it will certainly supplement them as a way to get around telecom data plans. Tweeting inside a browser does not have the same data cost for the telecom user that texting does which adds another huge non-metered communications opportunity for businesses and consumers. It opens the question of what large cellular services providers will do when conversations move away from their ability to track them. TwitterBerry accounts, used on RIM (RIMM) Blackberry handsets make it nearly impossible for messages to be tracked by data use."
This link recently saved by stuart_henshall on March 24, 2009
The Salesforce announcement that they are adding Twitter so clients can respond is logical. What companies haven't effectively done yet is enable effective escalation of service related issues. Twitter provides context and profile. That's a Smart Contextual Caller on the line and it doesn't need to be an interruption.
This link recently saved by stuart_henshall on October 08, 2008
Ken Camp makes the point that unified communications have to include the emergence and integration of social media tools. I like to think of this as the new directories, the names rather than numbers. Add in location and the mix becomes more interesting and powerful.
This link recently saved by stuart_henshall on September 23, 2008
This link recently saved by stuart_henshall on August 28, 2008
Ken Camp is just one of the bloggers keeping an interesting discussion going around VoIP on planes and whether the person in the seat next to you should be able to talk. I'm for talkzones! I'm not sure I'll sit in them. I'm also very lucky Phweet played a great part in this story. For that I've got Andy Abramson's quick thinking to thank yet again. Ken's right, in the end usage comes down to manners and some common sense.
This link recently saved by stuart_henshall on August 27, 2008
I like this post, plenty of great advice. We are also at the point where we need more discussion on non-delivery. Eg does a company know to fix notification settings before doing anything else? "all @ replies"? How real-time are they? Many apps have a latency factor. How do you deal with this? Then I'd like to see more discussion about how to escalate the conversation. That's one reason we built Phweet. Talk can be expensive. Not talking can cost you even more. We're headed for a world where leaving public talk requests and unanswered ones may be a useful sign of whether the company is really ready to listen.
This link recently saved by stuart_henshall on August 25, 2008
If I posted all the links that have emerged over the last couple of days on how Andy beat the airlines VoIP ban with Phweet I'd fill a few pages. Some of the pictures are just really cool and hightlight it from all sorts of different perspectives.