Will the SixApart TypePad hosted blogging service integrate SkypeWeb into their comments system when Skype finally releases their extended presence solution? I've blogged the benefits previously of integrating a Skype identity component with blog comments. Similarly, by creating a www.CommentPings.com to register blog comments, commenters would no longer lose the networking value of their comments as they become searchable. Skype-to-comments would also create the opportunity to introduce solutions for audio comments etc.

SkypeWeb is a new feature of Skype 2.0 that allows Skype users to display their Skype online status on a Web page, email, blog, any other HTML enabled content or any other Internet-enabled application.
 - Skype Developer Zone Blog!

Could SixApart abandon TypeKey in favor of Skype user authentication? Short term, that is probably a longshot. However, this blog would adopt "skype names" as an authentication approach in an instant. It would improve the opportunity for dialogue and offer the opportunity for multichats on any post to be opened (for those that "tick" add me to the multi-chat discussion on this post).

We know there have been discussions between both parties, while recently Skype moved their blogs to SixApart's MovableType platform. It continues to use Skype as its log-in authentication for commenters. Adding Skype authentication adds value. There are some management issues... like authentication to your Skype client rather than the Skype server that would be required.

Typepad and the blogger would get both the advantage of a profile and a more personalized way to arrange contact. It would also provide more opportunities for "commenters" on the same post or blog to introduce themselves. Something current systems with hidden e-mail addresses don't allow.

SkypeWeb, announced last year, will be launched officially in a few weeks. For now you can sign up for the beta at the Skype Developer Blog which will give you access to basic details.

That's enough speculation for tonight.

Microsoft's Windows Live will include Expo, a user commerce service.
Craigslist meets eBay meets Yahoo! Groups using Passport /  Windows Live identity, location awareness, collaboration and communication tools. Get a chat message every time a used bicycle is posted for sale in your town this week. Talk to someone selling a car. See what your friends and family are selling. Find a job. Join the Elvis Figurines group.

Discussion points for SkypeBay:

1. Are we integrating PayPal and Skype into marketplaces faster than Microsoft?
   
2. How well are we supporting Craigslist-style local micro-markets?
   
3. How many of our category managers are using Skype as their prime phone?
   
4. Are we helping people connect for activities, career, advice, and other things that UPS can't package?
   

Microsoft demoed Windows Live Messenger (WLM) beta on the show floor. (Snapshots coming soon.) Better looking than MSN Messenger 7.5 (lots of cutesy user interface removed, panes better organized) but it's a small point. One rep claimed the Messenger Beta is better than Skype because:

• audio quality ("we played with the codecs"),
  
• integration of identity and contacts across the Live family (hotmail/live mail),
  
• third party apps delivered through the system, and
  
• having more users (about 200 million) than anyone else.

The team seems to treat Messenger as a walled garden, like US mobile carriers. The product is closed except to partners who pay for the privelege or who have something specific the Messenger team wants. For example, they were bragging about two handset partners who'd come aboard, but WLM doesn't publish an SDK (software development kit). So the hundreds of handset manufacturers here at CES can't tightly integrate their products with WLM. Like carriers, WLM sells advertising right in the user interface, polluting with distractions what for many is their dominant communication tool, and with no way to turn them off. Even the exclusive software developers allowed inside the garden walls cannot build telephony plug-ins at all. This is far from being a strategic communications platform that others can build on.

I have to agree with him about the convenience and power of a common Passport/Live identity. The convenience of single sign-on is a great draw. And having more people in your ID cloud and in connected clouds (like Yahoo!'s someday soon) builds critical mass. It is unclear, by the way, if the IM interop agreement with Yahoo! extends to voice.

Someone in the crowd pressed him on the number of users, asking specifics on the number of active voice/telephony users. He didn't know. I suspect, given the low emphasis of voice in past UIs, there is an infinitessimal but quickly growing body of MSN voice regulars. Helping the average MSN user become multimodal (text to voice) will be a challenge as steep as Skype's (voice to video).

Two other points: Windows Live Messenger voice calls will not support voice conferencing. And users must cut a deal with MCI for call-out services. Both put Microsoft at a disadvantage vs. Skype.

But I'm not worried for Microsoft. Most Microsoft products take years of iteration to mature, and their move to thrice yearly release cycles will help Microsoft overcome these weakness. Their platforming tradition may prevail over short-term walled garden opportunities. What's more, the power of incumbency is real, as is their willingness to explore new ideas. Skype's race for users, features, and new ideas is still a very high stakes game.

See also: the blog, the product page, the faq.

About to visit your family for a Chrismakah party and, on your way out the door, you realize: no gift. What do you do?

Introducting the Skype Journal Labs Last Minute Privacy Shield.

It's simple, affordable, and stylish. It shows you are plugged in to the public policy implications of our interconnected lifestyle. It demonstrates you care about your giftee's confidentiality, privacy, and digital identity. Recycled from recycled paper, so it is uberecofriendly. And it folds nicely on the way to the party.

Variations: You may decorate your privacy shield with stickers, colors, or a collage of other people's faces you cut from a magazine or download from the web. You may also choose bags of different sizes and from different stores: a Tesco bag says one thing, a Nordstrom bag says another.

Lessons Learned: 1. Do not attempt with plastic bags. Really. 2. Use a clean bag never used to carry fish.

This gent put his 277 Skype contacts to use today as he changed his "real name" to "1968 DB5 - Bid: £30k - 4 hrs left" for a while.

It's a great example of "field overloading," where users put a form field to novel uses. In this case, using Skype's p2p white page cloud to share a classified automobile-for-sale advert. Overloading is often a response to users wanting to use a system for more things.

You can easily imagine sharing your eBay listings, romantic status, career availability, or your public calendar. Some you'd make public, others shared to select friends or your whole buddy list. Putting your social capital to use at the edge of a network.

The Skype team that defines the user profile fights to keep it simple and small. Big and complex slows down the Skype ID cloud. Even small changes to the profile can double the bandwidth Skype clients use to keep the cloud moving or to search the cloud.

Skype product architects should pay attention, though. This is opportunity knocking, tipping its hand. Can you spell "Edge Commerce"?

Have just read Richard Stastny's comprehensive recount of the goings-on around ENUM at the IETF meeting in Paris. I can't but help feel that, despite the good intentions, some decidedly anti-competitive actions are going on here by the carriers.

In essence, the telcos are keeping control over a numbering business that is being run as a cartel that keeps out non-POTS VoIP applications, and discourages new POTS entrants. And since there is (today) no defensible service element in "VoIP service" other than the trivial routing function, the erection of artificial barriers to enable rent-seeking is priority #1, #2 and #3 in telcoland.

The importance of phone numbers is too easily dismissed in a world of email addresses, Skype IDs and IM buddies. Numbers work across all alphabets and typefaces, are relatively unambiguous, are easily entered and displayed on restricted UIs, and can easily be conveyed verbally and in print. We have a system for mnemonic mapping to letters where necessary. Competing global numbering schemes are unlikely to emerge, because of potential for namespace confusion (although local versions such as SMS short codes do sprout up). Numbering is serious business, if somewhat obscure and technocratic. Despite their sometimes confusing split semantics as "naming" and "routing" objects, they need not be casually dismissed as an obsolete anachronism of the pre-IP world.

The technical problem any ENUM system solves is the conversion of a phone number to any other form of URL (and back again). The specific business problem that Carrier ENUM purports to solve is one of trust. If the user is empowered to create records in the routing table for IP communications, you face two problems. Does the user really own/control the ID that they are mapping from? And do they own the one that they are mapping to?

The puchase of the voice service acts as the "trust anchor" — if we gave you the phone number and VoIP URL, the mapping must be correct.

Yet in doing this Carrier ENUM denies you any possibility of asserting ownership over your phone number independently of purchasing an overpriced "voice service". It's a bit like you only being able to buy domain names in conjunction with getting an email account at AOL or MSN. If you happened to want to use your email address (think: "phone number") in some crazy new-fangled service like instant messaging (think: VoIP), you've got a problem. Oh, sure, you can do it in various numbering range ghettos that aren't routed by half the world (and are charged at random rates by the other half). It's like Microsoft's support for Apple — sure, we like competition, as long as it knows its place.

With domain names, I can obtain clear ownership. I get to set a record for my domain that says who I'm empowering to manage the domain's details for me. In other words, someone thought through the various roles of ownership, assignment, management, operation, etc. in advance. They made a reasonable stab at creating a system that separated them. With hindsight we know it's not perfect and involves excessive expense, but it's quite good.

What you would really like to be able to do is enter someone's phone number in Skype, call them, and if they're using a Skype-enabled device you get an ecrypted, wideband audio Skype call. But we can't do that easily today because I could claim to have your phone number, and calls to you would come to me.

I'm totally guessing, but I assume that the PhoneGnome device (which bridges PSTN and VoIP calling) has some patented secret provisioning sauce to tackle this problem. The device, I suppose, places a free PSTN out-call and uses caller ID to associate the SIP address and PSTN number. (Self-provisioning would allow you to fib too easily.) But it doesn't scale well unless we all buy one; and an $119 device is kind of expensive if all you want to do is prove you are the owner of a phone number so you can use it in an IP service like Skype.

Carrier ENUM makes me feel a bit queasy, because there's no need to be a "carrier" to do VoIP or ENUM. If the VoIP application is independent of transport, will I be able to declare myself to be a carrier, obtain numbers, and participate in Carrier ENUM? Methinks not, and that smells bad. (I also suspect Carrier ENUM is great for perpetuating the dependence on SIP proxies and smart networks a-la IMS, and preventing P2P connections. You can bet the technical rules will subtly stop any domestic IP connection from being classed as "carrier grade" and allowed to participate in Carrier ENUM as a peer.)

So is the only alternative the unattainable nirvana of User ENUM, where the plebs seize control? Not necessarily, but we could take some baby steps along the way.

If I were a regulator, I'd be looking to unbundle the phone number trust function.

Luckily, we've already got a model for it, at least in the UK. If you want to port your wholesale DSL line from one company to another, the requestor must receive an authorisation code issued by the incumbent. And the incumbent must authenticate the user when they request the code.

Break apart this mechanism, and it provides me a way of requesting codes, and third parties using them to authenticate my ownership, but without actually completing a number port.

This only works for the phone number ("E164 number" in telcospeak). If I wanted to map it to my Skype ID, I still need a similar mechanism to assert ownership of that ID. This strikes me as a problem easily solved with today's digital ID technology ;)

It would not be unreasonable for a "virtual VoIP network operator" like Skype to charge you for access to this trusted directory function. Particularly if the receipient was a POTS (or POTS-on-IP) competitior that wants to disintermediate the Skype network while still allowing the use of Skype IDs! (There's an business model struggling to emerge in every VoIP operator…) Given the near-zero barrier to market entry, let the market find a price, I say.

Since numbers are also de-provisioned and re-cycled, invalidating the truth of ownership, there needs to be a mechanism to publish these events. This is non-trivial. But even if we don't solve this problem at all, the system seems stronger than the contract-based alernative of DUNDi, where the user unilaterally asserts truth in identifier ownership, and post hoc regulation deals with miscreants. At least we got the records right up front, even if they age badly.

This solution may be a turkey. I've no idea. But there are plenty of other possibilities lined up. For example, I could port control of my number to Skype, but retain the actual voice service somewhere else. If DNS can separate out the ownership, registration and operation roles, so can numbering. Part of the problem is being presented with a false dichotomy of Carrier vs. User ENUM. Another part is ENUM accepts the legacy world of phone numbers on the carrier's terms - such as accepting only the management roles that existed in the old world. It may seem pragmatic now, but we'll regret it later as new features take decades to reach "numbered" devices via the numbering cartel.

A deeper part of the problem is the assumption that we want a single, monolothic POTS application — that calling any phone number should make a single device "ring" and be answered. The idea you would place a bell in your house and remotely allow anyone in the world to activate it day or night will seem truly quaint to our grandchildren. ENUM focuses tightly on legacy phone numbers and their messed-up meanings, rather than offering a general frameworks for inter-service interoperability. Is ENUM a good answer to a bad question?

Anyhow, let's disaggregate the functions behind the Carrier ENUM curtain. Let multiple domain-specific registries and directories emerge, re-combining the elements in new and useful ways. Let them be safe in the knowledge that the records in their directories have at least some kernel of truth to them. Let some competition into places that don't know what competition and innovation are.