Now you can make a clickable Skype link in Second Life. TDavid of TD Scripts saw my latest Second Life post and whipped up a little service. Form a URL with your Skype name using this format:

http://tduri.com/s-SKYPENAME

That page turns it into a skype:SKYPENAME link that tells your Skype to call that link. Your browser sees a skype:SKYPENAME URL.

So, for me, that's

http://tduri.com/s-evanwolf

You can now create a Skype Me link if you're in Second Life or anywhere else that doesn't know Skype tags from shinola.

Variations:

• sa- add
• st- text
• su- user info

Bonus #1: Promoting a Skype 3.0 public chat? Give an invitation in Second Life by using the "Promote Your Public Chat" link with TDavid's script. Just copy from the promotional link everything after the skype: and paste it in TDavid's script where you'd put your Skype name. I did that to create the url in this link: The Skype 3.0 discussion.

CaptainAmerica Maverick gave me a bracelet tonight. A Skype presence bracelet. It shows my Skype availability when I wear it in Second Life. And if you're in 2L with me, you can use it to Skype me (I'm "Phil Arrow").

Stephen "CaptainAmerica" Klosky is using Skype's "SkypeWeb", a web service that takes a Skype username and returns that user's public status.

Web services are the life blood of Web 2.0, published protocols that open a company's software engines to programmers. SkypeWeb is Skype's only public protocol.

Skype must do more to empower developers who want to blend Skype into the rest of cyberspace. On Skype Journal's short list:

1. Turn the Skype client messaging APIs into web services. All of them.
2. Skype user authentication as a web service.
3. Directory service for public chats, public conference calls, and open contact groups.

Offering a "Naked Skype," (Skype devzone wiki, Skype issue database) a bundle of protocols to the cloud, would let developers blend Skype with any service, including email (like Microsoft, Google, and Yahoo!).

Skype is in an earnest race. (Skype management has not acknowledged this.) The company wins who publishes the most complete, friendly web services for live communication. The measure of success: developers everywhere mashing up your communications with their social networks, mashing up your social network with their services. Skype's performance so far: not in the game.

Today, for example, I must use the unscalable Skype client on projects to: 

• Write a web page that shows a Google map of the locations of a logged-in visitor's contacts, colored by contact group, indications of when they are likely to be online.
• Build a web based feed aggregator that crawls urls mentioned in buddy profiles, showing updated web pages and blog posts.
• Run gateways between the Skype network and SIP services.

In the Skype 3.0 public chat, Julian Bond said Skype's new Skype4com ActiveX wrapper gets us partway there. I suppose it does, if all you care about is embedding a Skype widget in web pages or rich clients. So much more is needed.

Web services will unleash the power of Skype's

• communication infrastructures,
• identity infrastructures,
• social infrastructures and collective social capital, and
• commercial infrastructures.

Web services open new markets, attract new customers, reinforce your value propositions.

In Second Life, web services literally open up new worlds. Skype's rivals get it and are acting now. Where is Skype's leadership in this race?

As mentioned elsewhere I have had significant exposure to a variety of phones that have been designed to work with Skype, either as the primary purpose of the device (Skype WiFi phones, Skype Cordless phones) or as an application within a more versatile mobile "personal assistant" platform (Windows Mobile platforms and, by year end, Symbian platforms such as the Nokia N-series). In addition I have now had the opportunity to work with a few wireless phones made by Nokia and Research in Motion (Blackberry). A few comments that could help Skype ecosystem product managers going forward:

Battery life: many of these phones have a battery life of four to six hours idle time. Probably best to license RIM's Blackberry power management -- I can get four to five days of idle time on my 8700. Any device that will have a hope of broad market acceptance should have at least two days idle time.

DTMF tones: This is a fairly basic and widely deployed feature of the Voice 1.0 phone infrastructure; yet I am constantly amazed at the cavalier approach taken to making sure "TouchTones" work with any Skype client, whether a softphone or a hardware device. Here are some of my experiences:

• Skype itself would not work reliably with DTMF tones prior to version 2.0; that issue has been resolved at this point (within the Skype client's "Dial" tab).
• The Skype WiFi phones do not support DTMF; therefore they limit the usefulness of SkypeOut when calling businesses that use IVR systems or other services, such as voice mail systems, that require a DTMF response. I have also experienced USB phones with the same issue.
• At the other extreme the RTX Dualphone and VoIPvoice Cyberphones do provide the appropriate support; the Sony Mylo aslo supports DTMF but you have to remember to put their unique keyboard in NUM mode to enter the tones.

Chat: I view Skype as having two primary features: Instant Messaging (presence and chat) and Voice. For USB phones, the IM activity remains on the host PC; however, for PC-independent devices there are issues:

continue reading.....

Yesterday came out of stealth mode the TalkPlus project that has been over two years in development; underlining this project's viability was a coincident announcement of a $5.5 million financing by Menlo Ventures. Om broke the story early yesterday morning; Ken Camp, Stowe Boyd, Voxilla and Alec Saunders, amongst others, have posted their initial impressions. I spent an hour yesterday afternoon discussing TalkPlus with Jeff Black, Founder and CEO. Jack provided some of the operational details that were not covered in the press release. First an overview from the press release:

TalkPlus today announced plans to revolutionize the way people use mobile phones by offering new and innovative Voice 2.0 calling services that work with existing mobile phones globally. Under development for more than two years, TalkPlus' patent-pending technology will provide customers a wide array of new and advanced calling services previously unavailable from mobile phone carriers.

First Offering: A Second Number That Works on Your Mobile Phone

With an additional phone number from TalkPlus, mobile users can now take advantage of having two numbers on their mobile phone. This additional mobile number is fully functional and unique; it works just like a mobile number issued by a carrier. By having a separate number to both place and receive calls on the same phone, subscribers get greater convenience and flexibility, as well as the benefit of an additional layer of privacy. With a second number, TalkPlus subscribers will be able to easily manage personal and work lives, while carrying only one mobile phone.

Subscribers will also benefit from an online management center, where they can easily control the TalkPlus Number's advanced call screening, voicemail, and contact management features.

Incorporated into the "Second Number" feature set will be an independent voice mailbox, a rules based engine for call management, bidirectional calling (in and out) such that a user can, say, separate her personal and business life, while using one phone handset with one carrier account. If you want to apply these management features to your original (well publicized) mobile number, you can port that number to the TalkPlus service and have a new (probably unpublicized) number applied to your basic carrier service.

But the calling support services go beyond capturing voice mail. Here are a couple of  examples:

continue reading.....

Initiated when Andy invited me to participate in the Nokia blogger program back in June, I have now had the opportunity to work with several mobile platforms and, over time, made several attempts to work with programs that access Skype from the mobile phone. I've also been following the Skype perspective on mobile here, here and here where expectations are set for processor power (minimum 400 MHz on Skype for Mobile), wireless access requirements (WiFi and/or 3G) and other operational limitations on a mobile platform.

As a guideline for user simplicity, I look for an experience where I can (i) easily "ping" a contact and enter text for a chat session and (ii) simply access a (Skype) Contact or dial a number to make a voice call - an experience that has a minimal installation and learning curve for the user public; an experience that will readily gain broad market acceptance. For the record the platforms I have worked with include:

Device	IM Client	OS/Keyboard	Wireless
Dell Axim X50v	Skype for Mobile	WinMobile/ MS PocketPC Stylus	WiFi
Nokia N70*	Quick IM, SoonR, EQO	Symbian S60/T9	GPRS, 3G
Nokia N91*	EQO	Symbian S60/T9	GPRS, 3G, WiFi
Blackberry 8700*	WebMessenger	Java/ Blkbry QWERTY	GPRS/EDGE
SMC Skype WiFi	None	Linux/ T9? (no DTMF)	WiFi
Sony Mylo	Skype for Sony Mylo	Linux/ Mylo QWERTY	WiFi

* also accepts SMS messages

At the moment the best platform on which to experience Skype on a mobile device is the Sony Mylo with its embedded Skype client. It has both the standard Skype IM and Voice functionality (as well as supporting file transfer). It does not require any special setup other than to use the embedded Opera browser to log onto fee-based WiFi Hotspot services. Of course its other limitation is the availability of WiFi connectivity although Jon Arnold is already proclaiming 2007 as the Year of WiFi. The Mylo does present the most authentic and most complete Skype user experience. Skype-to-Skype calls are straight forward. Calling any PSTN number worldwide, provided you have SkypeOut access to the dialed number, is a simple matter of going to the Skype Dial menu, entering the PSTN number (with +Country Code) and clicking. Finally, as noted by both myself and others, the Mylo has superior voice quality due to its embedded VeriCall voice engine. One minor shortcoming is the lack of Outlook Contact synchronization; but this is not necessary given the overall intended Mylo experience as a personal communicator and not primarily a wireless phone.

continue reading.....

How does Skype fit into the mix of other social media? If you recall, Lilia Efimova started using the ULRTMT - Universal Language Real-Time Message Translator this summer. Lilia and her online friend Andrea Ben Lassoued wrote "Weblog-mediated relationship: a co-constructed narrative" and it's being included as a chapter in a new textbook.

Their essay documents their professional relationship's evolution. The chart, at left, has three columns: Lilia's blog on the left, Andrea's blog on the right, and mutual territory in middle. The top of the chart is 2003 and the bottom is April 2006. They discovered each other in the blogosphere, reading each others' posts. After a while, they commented on each others' blogs, bookmarked each others' posts on del.icio.us, and swapped the occasional email. After a few months of more intense intercourse, they escalated to Skype conversations.

It is a solid ethnographic case study by professional social scientists. It spans a long time and covers multiple media channels (how we really interact with each other online). In this case, discovery and low level interaction earned (banked) a small amount of trust.

Enabling factors:

• Reciprocity of potential benefits from communicating to each other

• Vulnerable writing

• An ability to go beyond blogging in our choice of communication media

Lilia Efimova
Mathemagenic

They build on that trust until they were ready for more direct communication, with more substance, vulnerability, and immediacy (Skype).

I'd love to see this analysis of online relationship-building extended to other groups and situations. How do entrepreneurs find each other? How do job seekers discover potential employers and choose media during job search? How do new project teams negotiate the fit of modes to communication tasks? How long do some patterns persist, and do people repeat them across different relationships? How effective is shifting into work/task mode before fully establishing lower levels of trust?

I'd also like to see the end of a relationship. Can you salvage a fading relationship by experimenting with other communication channels? What are the textual or other early warnings indicators that a person is fading from "friend" to "former friend" or "contact"? How much asymetric communication can most people tollerate?

Which behaviors affecting user adoption and migration: What factors affect the success rate in dragging your (family, friends, work colleagues) into new channels? Are social network hubs more able to migrate their networks? Or do hubs who switch lose their power and start from scratch?

The ability to create great experiences comes from deep understanding of human nature. If you'd like to fund a more exhaustive study, let me know. I'm organizing research proposals.

Marcelo Rodriguez rounded up five products that connect Skype and SIP products in his post, Is a Skype-SIP Peace At Hand? 

• VoSky Exchange
• Skype2PBX
• Uplink
• ChanSkype 
• Pika Connect for Skype

We all want interop, and these products are gaining loyal followings. They build audio pipes between SIP and Skype voice callers. We've been calling these Level Three Skype integration in our Skype Journal Connectivity Maturity Model. 

Skype Journal Connectivity Maturity Model

Level 0. No connection.
What's VoIP? What's Skype?

Level 1. Skype indifferent.
Devices doing nothing but input or output like the most basic of USB phones. On the software side, the only software is Skype.

Level 2. Skype aware.
Configurations are Skype-aware or Skype-smart devices, like the Kensington Vo300, the YapperNut YapperBox.

Level 3. Skype conversant.
Level 2, plus audio pipes between apps, especially across the SIP barrier. You call with your SIP phone, something happens in between, and my Skype phone answers.

The move from Skype to SIP at Level 3 costs you all the benefits of rich conversation. You lose:

• Availability and geopresence
• Mood messages
• Caller authentication
• Access to caller profiles
• Launching text chat or video in the same call
• File transfer and folder sharing
• Voice messaging
• Access to Skype voicemail
• Skype multichat and conferencing
• Broadband audio quality 
• End-to-end encryption
• Chat/call permalinks 
  (e.g. skype:?chat&id=%23leedryburgh%2F%24evanwolf%3Bd5b446f89da627a3)

Level 4. Skype equivalent.
Level 3, plus restoring most of the missing elements. 

Does this model work for you? What's Level 5? What do you call it when the other system has capabilities beyond or different from Skype and you can't translate them?  

How do you voice enable the whole web? With Adobe Flash. My host walks me into his tiny war room at Adobe North. The tables strewn with copies of VON magazine, and Sinnreich's Internet Communications Using SIP. The white board has an architectural map on the left, laying out the technologies he'll need to build, buy or partner, and revenue models for each. On the right he's listing interconnect standards for call termination.

The goal is audacious. Outside of Microsoft, however, Adobe may be the only place on the planet with a hope of making VoIP ubiquitous. My host, an Adobe entrepreneur in residence, is building a startup to "just add voice." And video. And conferencing. You know, voice 2.0.

He assumes Adobe makes platforms for developers, not end products. So he's looking at companies like Skype and Yahoo! as potential customers, not rivals. He wants to help them build applications without worrying about the telecom plumbing.

• The MySpaces of the world should be able to call their own directory services from Flash but let Flash make the connection.

• The Salesforce.coms should be able to design a video customer service widget without worrying about the cameras or the codecs.

• Amazons could create live chat rooms for clusters of related books without invading customer privacy or setting up data centers.

These businesses add value with their social networks, their workflows, and rapport with their communities. They don't want to be in the "Skype" business, just their own. Among other things, this means Adobe doesn't need to convince every user on Earth to get an Adobe ID; people will use existing namespaces.

Adobe builds on others' value by creating baseline, ubiquitous infrastructure. Making commodity features from expensive, risky, perishable, complex systems. It's a platforming strategy. If Adobe's growing voice team (open Senior Product Manager and Computer Scientist - VoIP) can make coding for calls simple and elegant, a million flash designers and developers will add it to their toolkits. Contrast that with the hundreds actively developing for the Skype API.

Adobe is already active in the telecom industry. They license flash to mobile phone manufacturers, promoting the Flash developer channel's flash apps to carriers. Some of the most compelling mobile experiences are courtesy of Flash designers. About 70 million devices have Flash embedded.

Flash is also important to the advertising industry. 77% of banner ads are in Flash, says Adobe. If you think click-to-call advertising has a future, wait until you have click-to-talk-with-a-satisfied-customer or click-to-join-the-concert-in-progress.

If the Masked Entrepreneur can make it work and sell it to his internal stakeholders, it will be part of the next major release of Flash in 18 months or so. Adobe says the "Flash player is installed on nearly 98% of Internet-connected desktops."

That's a short window for Skype and Microsoft to respond. Skype product management has pretty much deprioritized developer requests since Summer 2005 to plug into the Skype cloud via a "Naked Skype", "headless Skype" or "Skypenet." Skype could be offering web services and server software that cleanly plugs other systems into the Skype cloud. They aren't working on it according to several sources within Skype's development team. Will Adobe's signaling wake up Skype to the industry power of being not just a social network but the leading infrastructure provider? Skype management didn't return calls by post time.

Seems that the discussion of the merits of email and (Skype) Chat are warming up again:

• Andy highlights the delays in knowing who is really online in Skype; he also mentions he has been receiving some chat spam.
• Jaanus admits that, despite claiming Skype chat to have many advantages over email fifteen months, ago he is still a heavy user of email.
• Rachel needs Skype presence to work in real time to effectively operate her MusicIP activities. She did at least get a personal response from Skype Customer Support.

Today at 2:46 a.m. I received an email from Andy; being an occasional nighthawk I responded to it immediately as I thought he wanted me to do an interview with one of his clients later in the day.  Andy comes back (at 3:13 a.m.) with: "I just received this reply to a message from September 6th !!!!".  I looked again at the original and sure enough, the email was originally sent Sept. 6 as stated within the message. My network tells me I am not the only one to receive e-mails from Andy today (Sept. 20) that were sent Sept. 6.  I guess it's Andy's snail-based communications system working its way across North America. (SMTP: Snail Message Transport Protocol?)

Anyway, it's a great example for putting some perspective on the two nines (99%) reliability of the Internet. At least I seem to get most of my Skype chat messages within a few hours (minutes?) of their being sent.

May the debate continue!

Powered by Qumana

Monday afternoon's first Fall VON 2006 plenary session, IM: The State of Presence, featuring a panel of executives and managers from the GYMAS-five representing over 90% of the IM usage worldwide:

• Dan Casey, Director, Windows Live VoIP and Messenger Product Management, Microsoft
• Jeff Bonforte, Director of Voice Product Management, Yahoo!
• Nitzan Shaer, Director, Mobile Devices, Skype
• Mike Jazayeri, Product Manager, Real Time Communications & Google Talk, Google
• Ragui Kamel, Sr. Vice President & General Manager, AOL Voice Services, America Online.

As mentioned previously Carl Ford ran his usual vibrant Q&A format, offering each member of the panel an opportunity to provide commentary on several topics surrounding IM and where it is going. It was a very informative and stimulating discussion overall. Carl's questioning covered why IM, video usage, the role of presence, mobile reach, business models and projections in for the future.

Why do users want Voice with Instant Messaging? From the students avoiding contention when sharing one phone line in a five-student apartment to business productivity enhancement, we heard stories about new scenarios enabled where IM and voice facilitate social networking to newly announced collaborative applications that share spreadsheets. Oh, and for the younger generation, IM allows students to avoid being seen holding discussions in the classroom; did I say to allow private discussion sessions in the boardroom? The new challenge arises when a group of youth want to do a conference call but Stephanie is is not on IM but at the mall shopping for new shoes.

Nitzan talked about how IM with Skype allows users to create one centralized ID that can be used across weblogs, sharing pictures, and enhancing a discussion using video.

continue reading.....

This is the second post in a series reviewing wireless devices in the emerging Personal Handheld Assistant space; the ultimate aim is to identify roles that Skype can play in this market of converged functionality devices. This is a special post in the series that was triggered by a VON Fall 2006 session. Links to other posts in this series are available at the end of this post.

Monday afternoon I attended the first Fall VON plenary session: IM: The State of Presence featuring a panel of executives and managers from the GYMAS-five representing over 90% of the IM usage worldwide. Carl Ford ran his usual vibrant Q&A format, offering each member of the panel an opportunity to provide commentary on several topics surrounding IM and where it is going. It was a very informative and stimulating discussion overall.

One major direction for IM is the extension of IM's access and reach by its incorporation into wireless devices. We heard about many of the issues that challenge the ability to provide seamless wireless IM clients, including login barriers, coverage and the relatively high cost of data services.

But the session confirmed a belief I had started to hold about a month ago during my evaluation of several wireless platforms. In particular, my evaluation of one Skype WiFi phone demonstrated to me the futility of providing such a device:

• The battery life was about eight to twelve hours in standby mode
• It could not handle DTMF tones
• The basic clock would arbitrarily drop a couple of hours
• It provides the presence functionality of Skype's IM client but no text chat capability
• Skype was the only application that runs on the device
• While the Skype client provides Skype names and the Contacts' other phone numbers (if available via the Contact's registration), there is no address, email or other information such as provided by synchronization with Outlook.
• They would only work in open access WiFi zones; they would not work in WiFi hotspots requiring a browser-based logon.
• They were purely engineering toys that demonstrated one could make the concept work but they badly needed an experienced wireless phone product manager to get the feature set right.
• In a market of multi-function devices in a similar price range, a Skype-dedicated device could not be price justified.

I came away with the feeling that, while they perform more or less as advertised, Skype WiFi phones are nothing more than a prototype engineering demonstration of Skype on a wireless platform.  Certainly they would have a very limited market -- maybe in enterprises that wanted to provide "walled garden" communications amongst geographically disbursed nomadic employees. But they certainly are not a wireless phone that will gain broad consumer acceptance and market share of any significance.

Combining this experience with my experience with Nokia N-series phones, the Blackberry and Skype for Mobile on the Dell Axim I have to recommend that Skype drop the concept of a dedicated Skype WiFi phone and focus their efforts on getting Skype incorporated into those other wireless platforms. (It is for this reason that I did not bother to mention which brand of Skype WiFi phone I evaluated; it's the entire product concept that is a problem.)

continue reading.....

This is the first post in a series reviewing wireless devices in the emerging Personal Handheld Assistant space; the ultimate aim is to identify roles that Skype can play in this market of converged functionality devices. Links to other posts in this series are available at the end of this post.

Over the past couple of months I have received several wireless handheld phones/devices from Nokia (manufacturer of the last three cell phones I have owned), Research in Motion and SMC for evaluation. In addition I have been using a WiFi-enabled Dell Axim X50v as a PDA over the past two years and a Canon PowerShot A610 for photography; the Axim, of course, can run Skype Mobile, . Recently Sony announced its WiFi-enabled mylo; meanwhile last week saw the arrival of the Blackberry Pearl 8100.With such a variety of feature sets and user experiences, one needs to take a pause to review what is fundamentally important in a wireless handheld device to provide a basis for reviewing these devices, particularly in view of the convergence emerging in the various Nokia, Windows Mobile and (RIM) Blackberry devices.

This avalanche of handheld devices has made me ask the questions:

• How much convergence of functionality do I want or need on a handheld device?
• Where should Skype play a role in wireless-enabled handheld devices?
• Can my previous three devices (phone, PDA, camera) be combined into one unit or do I continue to need three device holsters on my belt?

continue reading.....

I'd like to send my wife an SMS. In Skype I've got a group called "Family", which includes her entry. However, she hasn't filled in her mobile number in her profile, because that means exposing it to anyone she adds to her buddy list.

I can instead create a new entry for her mobile, or enter it directly, so this isn't a massive deal. I could even hand some bonus money to a telco and SMS her from my mobile. It does serve to illustrate a bigger point, though, on how different communications systems can create value by managing privacy differently.

There are several ways of technically resolving the situation. A simple one is that I have a local copy of her profile that I can extend and annotate -- a proper object inheritance mechanism. Another is that I can request her number off her.

continue reading.....

AOL has a long history of innovation. Initially launched as a proprietary pre-Internet personal communications platform building up to several million users via dialup connections, AOL has evolved its integration into the Internet to the point where it recently broke down its "closed garden" business model and opened up the majority of its content and services to anyone visiting their site. It has certainly gone down a bumpy road with its history of balancing the conflicting needs of innovation against the needs of an operation bureaucracy looking for a profitable business model. At one point it was the poster child for the Bubble 1.0 bust as the business world tried to work out business models to provide a profitable combination of both infrastructure services and (syndicated) content. Breaking down the walled garden is but one example of the direction it is going under new leadership.

Last week there were several posts (Aswath, GigaOm) about the closure of AOL's TotalTalk, where AOL effectively recognized there is little to gain by playing in the pure legacy telephone replacement game and has decided to abandon it. Earlier this week there were several posts (Jon Arnold, Andy Abramson, Mark Evans) discussing Vonage's latest quarterly results; the common theme is that Vonage is spending such enormous sums on customer recruitment that there is little hope of profitability in the foreseeable future. Cablecos and legacy telcos offering DSL services have a leg up as they already have a customer base to whom they can market. But Andy at VoIP Watch sums it up best when talking about the demise of AOL Total Talk in his Requiem for the Future of VoIP:

Rather than look at it as a failure, my take on this is AOL really has seen the future sooner than others. Much like the BT announcement earlier this week about their softclient, and like their other online portal player competitors including Yahoo, Google and MSN, AOL's Voice Team has seen the future of telephony and is moving in that direction with AIM PhoneLine, and the burgeoning ecosystem that already has started to bubble earlier this month at the VoIP Developer's Conference, and will likely have a big boost at VON in Boston next month.

But unlike Yahoo and MSN who have so many internal battles to fight, AOL as part of Time Warner has leadership that is smart enough to not fight a marketer (Time Warner Cable) who wants to sell a phone 1.0 replacement, and instead is focusing on Phone 2.0 and where it can be.

Today AOL issued a press release outlining their execution on the Voice 2.0 Manifesto through building an ecosystem around their AIM Triton IM client and its AIM PhoneLine service called the Open AIM PhoneLine initiative. AOL will introduce three API's this fall that will give developers and hardware partners the ability to:

• Personalize the AIM Phoneline service by adding ringback tones and unique ring tones for frequent callers.
• Enable a wide variety of USB devices such as speakerphones and phone adapters that will allow standard cordless phones to initiate and receive calls with the AIM Phoneline service.
• Build new call management functionality into the AIM Phoneline service such as context and relevance-based call handling that could treat each call on the basis of rules that use Caller ID, online presence, calendar activities and more.

continue reading.....