Angus Logan

The IE team just announced a few little extensions for IE that make it a great browser for creating & consuming Facebook content.

Web Slice – get it

Search Provider – get it

Accelerator for sharing – get it

Awesome post on the Inside Windows Live blog – a must read.

Some statistics:

• The average length of a Messenger session (a conversation) is 9-11 minutes
• About 59% of sessions are over 5 minutes, with about 10% over 20 minutes long
• 1.6 billion sessions per month are over 30 minutes long
• People use Messenger to exchange over 380 million photos a month —over 4.5 billion photos a year (this is in addition to the tens of billions of photos people also share each month via Windows Live SkyDrive and Hotmail)
• Messenger users have 230 million voice & video conversations per month
• Average voice session length is about 18.2 minutes
• Average video session length is about 13.3 minutes
• 9% of video calls and 13% of voice calls are longer than 1 hour
• Usage of international voice and video sessions differ geographically.
• Brazilians use voice & video only 13% of the time for international connections while users in other countries, such as Spain or Germany, use voice and video 50-75% of the time for long distance chats with friends and family.

Think about the intersection of the biggest websites in the world, Internet Explorer, and you. If you are a browser wizard, can cut code, rock as a product manager (what should we build etc.), have industry credibility & would love to work with me:-

alogan @ BLAHmicrosoft.com

I’ve spent the past week and a half in Europe (London, Madrid & Paris) and the way Windows Live Messenger is such an integral part of people’s lives here is amazing.

The Messenger Web Toolkit team just announced a new minor release (version 3.7) which has some infrastructure updates (using ASP.NET AJAX) but more importantly, we’ve added Offline Messaging, millions of consumers can now send send a message to their friends, even if they aren’t online.

We’ve also added support for more browsers, including Firefox 3.6 and Chrome 3. 

Check out the announcement here and if you have feedback http://bit.ly/AskMessenger.

If I wasn’t working on Windows Live, I would go and work for the SketchFlow team. Their product has absolutely changed the way I communicate concepts to customers, and complex UI interactions to my engineers.

The SL team just posted a great example of how Sketchflow has been used in house (and by vendors) at Microsoft to spec and sign off an internal app.

Check it out

I’ve been working with some of our centralized Windows Live security and privacy folks recently. These guys are super skilled at what they do – and luckily, they are sharing some of the lessons learnt about securing Windows Live when using ASP.NET MVC.

Read the whitepaper

I’m a complete travel junkie and I’m also a productivity nut. That is why I love this little start up called TripIt. In fact, I’d say I have a bit of a corporate crush on them. – killer product and nice guys.

Anyway, the Crunchies are open for nominations and I think everyone should vote for TripIt – what are you waiting for? Vote now

You can also share your TripIt  trips with your Windows Live friends – set it up

stats since Jan 2008

This just rocked my world: http://www.getpivot.com and see Brandon Watson’s post about how he made a Crunchbase viewer – VC’s listen up! http://bit.ly/3JqZQA

UPDATE: Steve Clayton has shared his thoughts too

This is pretty exciting news, check out the announcement (below) and read what David Rudin has to say about it. below are a few excerpts from the announcement post:

The Open Web Foundation was founded to help developer communities collaborate and share technical innovation on the web, bringing to the world of formats and protocols the same successful grassroots approaches established by the open source community. Modeled after the Apache Software Foundation and Creative Commons, the Open Web Foundation seeks to facilitate the creation and implementation of specifications with legal agreements that make such work simple, safe, and sustainable.

This reusable agreement is designed to be easily adopted by a wide range of specification communities and organizations as an alternative to the challenging -- and costly -- process of negotiating new licensing agreements every time. Specifications made available under the Open Web Foundation Agreement may include everything from small ad-hoc formats sketched out among friends to large multi-corporation collaborations that ultimately grow into international recognized standards with the help of formal standards setting organizations. 

There are lots of interesting specifications which will have the OWFa applied to them:

We are further pleased to announce that the following companies have committed to apply the OWFa to the following community and proprietary specifications:

• MashSSL Open 1.2.0 (SafeMashUps)
• Media RSS 1.5.0 (Yahoo!)
• OAuth Core 1.0 Revision A (Facebook, Google, Yahoo!)
• OAuth WRAP 0.9 (Facebook, Google, Microsoft, Yahoo!)
• OpenService Format Specification version 0.8 (Microsoft)
• PubSubHubbub (Google)
• Salmon Protocol (Google)
• Simple Web Tokens 0.9 (Facebook, Google, Microsoft, Yahoo!)
• WebSlice Format Specification version 0.9 (Microsoft)
• XML Search Suggestions Format Specification version as of 11/11/2009 (Microsoft)

Get involved

The Open Web Foundation is open to everyone without charge and we actively solicit feedback and participation from the community at large, whether or not they are Open Web Foundation members.  The Legal Affairs Committee is open for self-nominations for participation in the drafting and review process itself, and interested individuals are encouraged to join the Open Web Foundation general discussion list to offer input and support.

James Senior just told me about his pet project, the Web Application Toolkit for Making your Website Social.

This Web Application Toolkit shows how, using a few lines of code with the Windows Live Messenger Web Toolkit, it is possible to add social capabilities to a Web site. The Windows Live Messenger Web Toolkit is a JavaScript based set of controls and libraries that allow a developer to quickly and easily add instant messaging to a Web site and harness the power of the Windows Live Messenger network that is used by 330 million users around the world. The Web Application Toolkit will also show how to bring information about users from Windows Live such as their presence, profile information and profile picture.

Check it out

We’ve been working hard on the Windows Live Messenger Web Toolkit (MWT) which allows you to connect your web site to 330M+ people who use Windows Live Messenger every month! Today we’d like to announce the availability of the Messenger Web Toolkit v3.5 which will enhance the user experience, make it easier to enable sharing via Messenger scenarios on your site (new sharing control), and enable new scenarios (e.g. people who don’t use Messenger will be able to see display pics / names). Specifically, the improvements we have made are:

• User experience: smoothed out the user experience, added a first run experience, expanded the browser support, increased the performance
• Developer experience: reduced the amount of code for you to implement “Share via Windows Live” and the Messenger Web Toolkit is now built on the Microsoft Ajax library.
• New scenarios: Allow people who don’t use Messenger to see display pictures and names of Messenger users.

How did we figure out what are the most important things to get in this release? We listened to and incorporated the great feedback from our partners (some award winning), and were able to come up with new and exciting scenarios.

User Experience: Sexier, faster, supported in more browsers

To bring more people to your site and get them to spend more time there, the user experience needs to be superb. We have made the Messenger Web Toolkit user experience better in many ways:

• Speed: In March 2009 we extended Windows Live Hotmail to use the Messenger Web Toolkit (see the post). By having our bits running at Hotmail scale we were able to gather a ton of information around performance and we’ve acted on it: the MWT will now load faster (full/first time loads and cross page navigation).
• Availability/Reach: added browser support for Firefox 3.5, Safari 4, and Google Chrome 2 - now more people can connect & share with their Windows Live friends on your site.
• Education: One of the most tangible UX changes we’ve made is the first run experience for the Web Bar (a single control you can use if you don’t want to build your own experience). When you first use the Web Bar on a site, a small popup will inform the user they can sign in and tell them the key things they need to know to start connecting and sharing with their friends.

• Looks: we have also updated the web controls and web bar user experience to cleaner

Developers: Easier to add sharing controls and aligned with more tech

We’ve done two things for developers 1) created a new control for sharing which reduces the amount of code required and 2) changed the underlying JavaScript libraries to the Microsoft Ajax libraries.

Sharing control: aside from in-page chat, the next most common scenario we see is sharing via instant messaging. Sharing content is important and it is often a major driver of user acquisition (or user retention). To understand the differences between sharing via a public feed, newsfeed and instant messaging read my post on user acquisition.

The gist is: a user’s friends are more likely to click through to see the content/service being shared with them if it is done via instant messaging and in a conversational way.

To make sharing via Windows Live Messenger much easier we have created a new control, msgr:share. The sharing control reduces the amount of code required to the following:

// include the JavaScript libraries
<msgr:app … insert the code for app tag here… />
<msgr:bar></msgr:bar>

<msgr:share
  message="I am sharing the Messenger Web Toolkit http://dev.live.com/messenger with you"
  picker-label="Select Contacts">
</msgr:share>

The control contains a user experience which will sign the user in (via the consent flow), show the contact selector control, and send an IM with the predefined content.

Aside from visible features such as the sharing control, we have also done some infrastructure work. The Windows Live Messenger Web Toolkit is now built with the Microsoft AJAX Library. With this integration, a Messenger Web Toolkit application works with the standard browser runtime library for Microsoft web development tools. Prior to version 3.5, the Web Toolkit worked with the Script# runtime library named 'sscorlib'. See Microsoft Ajax to determine whether you need to make any changes with your application.

Something for people who don’t use or aren’t signed into Messenger

People using Windows Live Messenger generally chat with people they have ‘friended’ in Messenger. However, sometimes people who use Messenger on a web site may want to chat with other people they know from that web site (who are not their friends on Messenger). We call this feature Application Contacts. The cool thing about this is when I sign into a web site (and grant permission to sign into Windows Live Messenger) which uses Application Contacts, other site visitors can chat with me while I’m on the site, or anytime when I have Windows Live Messenger client open (all the time, like hundreds of millions of other people).

We have made a lot of enhancements to Application Contacts (more information), but the major change is that you don’t need to be signed into the Messenger Web Toolkit for all scenarios. People who are not Windows Live Messenger users (or are not signed into Messenger on the web site) can still see the profile picture and display name of user’s the web site chooses to display. This is particularly interesting for commenting and user profile scenarios. To use this functionality a new Messenger Application Key must be used. This is analogous to a service account. Our documentation on Application Contacts outlines how to get a key.

Previously, if you wanted to show the display pictures/names to a user who wasn’t signed in to Messenger the pics/display name weren’t available. Using the updated Application Contacts functionality you can now show display names and pictures to people who aren’t Windows Live Messenger users (or people who haven’t signed in yet). See the before & after:

Party on

Try out the new bits dev.live.com/messenger and if you have ideas or questions, hit us in our forum.

/Angus Logan, Technical Product Manager

I just saw a bunch of noise about FourSquare’s application on Android. Foursquare is a great location based service which lets you “checkin” to restaurants and other venues, and have that automatically shared with your friends.

My buddy Anand Iyer who just went to work for Windows Mobile gave some new bits he has been working on: a FourSquare client on Windows Mobile. The FourSquare mobile web interface is nice, but it just isn’t rich enough – having the data cached, easy to access is important.

The bits are still somewhat secret (not share yet) but what I think people are missing in this whole iphone app and android app building spree is: YOU WANT RICH APPLICATIONS ON YOUR MOBILE. Web based mobile just doesn’t cut it.

Next time you are building a mobile interface, ask your self: should I go for the masses and create something generic which may only drive 5 minutes of use per user. Or should I go for something specialized which will drive 50 minutes use for 25% of your user base.

I’m personally not bought into the overall value of URL shorteners. I think the COGS are high, and you only monetize in nefarious ways:

1. tracking visitors who who aren’t aware they are being tracked and selling their behavioral data
2. getting a nice set of IDs and then adding a landing page (or even better, driving people to search instead of taking them to the content).

But… Bit.ly adds something different. they add nice stats and tracking which I find extremely useful (especially when I try to drive people to content via blogs, tweets and emails).

One of the neat things I found was a Bit.ly plugin for Windows Live Writer, check it out here

You simply highlight the URL and it converts it into a bit.ly.

nice and easy to use.

Here are some sessions for y’all to vote up at SXSW. It is easy! Just click the Thumbs Up and if you don’t have an account it will only take you a few seconds to create.

Web Mail - Is There Room Left to Innovate? (Web Mail)
Web mail has been around the block, and everybody’s got it. Its role may be narrowing to the place you manage online bills, shopping, travel, and photos with mom, with conversations migrating to social networks and IM, but companies are still pounding the digital pavement for new users. If web mail isn't going anywhere, where does it go from here? Vote Now

The Stream Has Become A Tidal Wave (Social Media)
The stream is overflowing. How do you make sure the stream is still useful when there is SO MUCH getting pushed into it? Vote Now

Social Network Interop (Open Standards)
Portable contacts, life streaming and various ‘Connect’ offerings have begun to break down the silos and walled gardens that are social networks. Come hear a panel of experts discuss some of the technologies, design issues and future direction of this trend. Vote Now

Securing Web Behemoths – Web Applications That Are Large (Security)
As the trend of ‘webifying’ continues, the smallness and simplicity of web applications will become a thing of the past. This raises the challenge of securing these web behemoths. An industry panel of Security engineering managers will discuss the approaches they use to secure their web behemoths. The attendees will gain awareness into the panelists’ security engineering programs & gain access to tools that they could apply at their companies. Vote Now

ActivityStrea.ms: Is It Getting Streamy In Here? (Open Stack)
From Facebook's newsfeed to Twitter's relentless real-time updates, the metaphor of the "stream" has taken social networking beyond blog posts and on to rich social activities. Learn about ActivityStrea.ms — the open format adopted by Facebook, MySpace, and Windows Live — and how it's fundamentally changing the social web. Vote Now

OpenID: Identity Is the Platform (Open Stack)
Ignore the hype over social networking platforms and web OS's! The platform of the social web is identity. Facebook and Twitter Connect are just the beginning of the era of user-centric identity. I'll go beyond the basics of OpenID and learn how to effectively incorporate internet identity into your apps. Vote Now

Standards - Handling "Zero Day" Exploits (Security)
The OAuth exploit last year was a catalyst for developing ways to deal with zero day security issues in open standards. No one vendor is responsible for managing the process, how do you determine responsible disclosure in an open forum? You can't hide from open standards, and you can't stick your head in the sand about security. You'll learn from the pain of others how using open standards just got safer... or did it? Vote Now

User Acquisition Smackdown: Email Raiding, Stream Polluting or Instant Messaging? (Social Media)
Getting people to your website is critical (D’uh!). New people. Old people. A constant flow of sharing and content discovery is required to succeed.Some people are sneaky using address books, others publish to the stream - which one is best? Vote Now

Running a Business on Open Standards (Open Standards)
This panel will discuss the different standards for social applications and how a developer can utilize those to build and grow a business. It will focus on monetizing the Open Stack, and how developers can build a sustainable business model using industry standards. Vote Now

Protecting Your Service from Internet Terrorism (Security)
Historically, the enemy launched their attacks from far away from populated areas – you could detect them and nuke the entire area. They are getting smarter, moving into apartment buildings and no one likes nuking apartment buildings. In this panel, leaders in internet service abuse prevention will invite you into the “situation room”. Vote Now

Jorgen Thelin just posted Windows Live ID OpenID Community Technology Preview Status Update (August 2009).

Community Technology Previews must be expected to come and go. They are used to get feedback from developers, validate ideas, disappear and come back. Sometimes they are even used to prove the feature/service is economically viable and is what developers/users want & need. Jorgen provided an update on the future:

Currently, we do not have a schedule that I can publicly share for when we will release full Production support of OpenID for Windows Live ID users, but rest assured that we are working actively to provide OpenID functionality to all of our 500+ million Windows Live ID users!

In addition to multiple entry-points, and being able to explain unique vs. static identifiers to end users – the main challenge was aliasing:

In the CTP, Windows Live ID users were required to create an OpenID alias (such as “http://openid.live.com/john”) attached to their account, and then to use that alias not just at the OpenID relying party site, but also as the way to identify themselves to the Windows Live ID OP. When arriving at the OP sign-in screen, users were required to enter their OpenID alias (instead of their normal Windows Live ID user name) plus the password (or one of their other associated credentials, such as an Information Card) from their main Windows Live ID account.

We had envisaged that using an alias for OpenID sign-in could provide some separation of the two identity networks. However, the usability model for this approach has turned out to be unfeasible and/or just plain confusing to users!

Read more about it along with the other lessons