Skype Journal

Home - Contact Us - Policies - Advertise - About News feed Independently covering the Talk Revolution since 2003

Friday, November 20, 2009

Live From The RealTime CrunchUp: No Skype

Stream videos at Ustream

Skype and live voice/video conversations haven't been part of anything in this event, or the others like it. I blame Skype's branding problem:

  • Skype is antisocial software, not a place or way to discover future friends or colleagues.
  • Skype is just for your closest circle, fewer than ten contacts.
  • Skype is an isolated network that doesn't interop with others.

That branding is reinforced by Skype's product focus. Fear of strangers, as shown by the inane and inadequate profile and privacy systems. Little support for large numbers of contacts because the "average" user doesn't need them (and can never graduate to power user if power features remain buried or unbuilt).

P.S. Every conference organizer should Ustream.tv all sessions. Cheap or free and brings thousands of people into the room with an interest in just one session or who cannot attend. You can't buy the resulting word of mouth in a realtime world.

tags: , , , , ,

Call me at +1-510-316-9773, Skype me, follow @skypejournal and @Phil Wolff.
Visit our Skype Journal private roundtable, one of the longest running public Skype chats.

Labels: , , , , ,

Wednesday, October 21, 2009

Research Topics in Collaboration

I wanted to follow up on my Monday post about the importance of collaboration products to Skype's business strategy. The great thing about collaboration is that it is very hard. Collaboration is less a discipline than a catchall term. It's peopleware more than technology, anecdotes more than evidence. Universities have no Collaboration Studies department in schools of business, humanities, engineering, or medicine. Industry and governments study collaboration but produce narrow benefits, poorly shared.

Frankly, there's no Collaboration Science to inform the design of the next generation of tools like Skype.

Society needs it. The web needs it. I want to do it.

So what questions about collaborative behavior and collective productivity could investigations answer? Which avenues could radically improve the ability of live and time-shifted talk to become work effort? What collaboration patterns and social software designs can break down barriers and bridge teams and connect project stakeholders?

I made a list and called it Skype Journal - Research Topics in Collaboration (not attempting any creativity there). The research areas showed four themes:

  • Talk is a component within larger relationships
  • Talk systems are part of a larger interconnected network of information systems
  • Work adds constraints that help focus conversation
  • Collaboration as collective productivity

and the topics fell in three clusters:

  • Getting Started (Ridiculously Easy Group Formation; Group Goal Forming; To Do Lists, Calendars, Personal Time Management, and Getting Things Done Together; Fame and Reputation)
  • Being Better Together (Augmenting Inline Conversation; From Discovery to Action; Decision Making and Decision Support; Collaboration Afoot; Situational Awareness; How Collaborators Use Search and Personal/Collective memory; Gestures of Tomorrow)
  • Crossing Boundaries (Intergroup Collaboration; Earning Trust and Using Whuffie; Collective Presence and Project Presence/ActivityStreams; Transparency and Collaboration; Backchannels; Scaling Collaboration from Tasks to Projects to Programmes)

It's a quick read, needs pictures and I consider this a rough, incomplete draft. The questions are a sample to get a feel for the space to be studied. 

How can we answer the questions? Research. Each topic is amenable to a different blend of usability testing, instrumented communication tools, prototyping, field ethnography of high function collaborative teams, and analysis of data from virtual teams.

I'd like to assemble a body of knowledge that turns our digital tin-cans-with-strings into engines of effectiveness.

Help me kick start this. (Yes, this is a bit self-referential.) What topics are missing? Prior art? Can this research occur in an open space or must it happen inside a corporate firewall? Of all the research topics, which ones are low-hanging fruit and which are harder to reach but outstanding value? Here's the pdf.

Skype Journal - Research Topics in Collaboration - 2009q4

 

 

 

tags: , , , , , ,

Call me at +1-510-316-9773, Skype me, follow @skypejournal and @Phil Wolff.
Visit our Skype Journal private roundtable, one of the longest running public Skype chats.

Labels: , , , , , , , , , , , , ,

Wednesday, September 30, 2009

video: Ribbit Conference Gadget for Google Wave

Google Wave opens up to more developers today. Ribbit's voice conference gadget is a featured bot. Here's the demo.

Q. What technology does BT/Ribbit have, making this possible, that Skype doesn't? Q. Does this scale if Ribbit has to pay for each minute? Q. What advantages does decoupling chat from IM bring to users?

From the Ribbit blurb:

The Ribbit Conferencing Gadget allows Wave participants to escalate an online collaboration session to a real-time audio communications session, allowing participants to talk with each other while collaborating. The Conferencing Gadget is persistent in the Wave and allows any Wave participant to:

Create an audio connection with multiple Wave participants

Add non-Wave participants to the session

Mute or hold any of the individual participants from the stream

Disconnect any participants from the stream

End the session

Labels: , , , , , ,

Monday, September 28, 2009

Why Skype needed to kill off its developer program

Man Pruning Tree

Killing Skype's developer program was an exercise in business discipline. You prune your tree of small, weak, sickly branches so nutrients and sunlight let the whole tree flourish.

Skype's developer program (SDP) has been bloodless for years. By every measure. Growth in programmers. Number of ecosystem products. Value contributed.

What devalued Skype's developer program?

5. Musical chair management.

I've lost count of the number of managers who've taken a stab at leading Skype developer relations in the last six years. It takes time and focus to be good at devrels, to build your devrels organization, to establish rapport and relationships with prospective partners.

4. Underfunding.

Skype's management shortchanged the developer program for Skype's first four years. DevRels never got the budget or headcount it needed to educate, evangelize and support developers. Software and hardware certifications, intended to promote the Skype brand and build trust, instead became a barrier to entry and a costly delay. 

Metaphor Bank:
Prune a tree,
Remove chometz,
A controlled burn,
Put down a diseased pet,
Excise a tumor
,
Balance a project portfolio,
Dumping ballast,
set developers free (Schumpeter creative destruction).

3. Broken trust.

Two steps forward, one step crushing partners. Skype me for the sad details of developers who bet on Skype's constancy and lost. Lost money. Lost jobs. Lost careers. A trail of tears and dashed hopes.

2. Who You Know.

Want to get something done with Skype? You needed an inside friend. Skype's much better now that a process culture's emerging, but it's still true.

1. Six Year Old Technology.

The perfect developer relations program cannot put lipstick on a pig.

1a. Client-only Calling APIs: So no putting Skype inside your app.

Skype's web services are all proprietary, off-limits to the ecosystem. Skype runs "naked Skype" server farms to support its Skype Lite mobile application. Skype Lite does most things a desktop client does, through Internet APIs, and without resource hungry user interfaces. It's an internal Skype as a Platform service.

Skype's third-party developers want Skype as a Platform. A SaaP would bring Skype features and the Skype network to web and mobile applications. Web applications are nearly always better business than rich clients. They cost less, don't have installation problems, are less prone to user failure, are always fresh, and take less time for customers to get their first Aha! experience.

1b. Closed Skype client: So no putting your app inside Skype.

Skype keeps users from seeing third party developers. With the Adobe Photoshop Plugin and Firefox Extension architectures, for example, you can write apps that live inside Photoshop or Firefox. They improve a user's productivity and alter the user experience. They bring specialist expertise to the exact point where users need them.

While Skype's Public API (downloadable SDK) lets your desktop program talk to Skype's desktop software, it doesn't let you change what users see and do. The Skype UI is off-limits, verboten, pristine.

So you cannot offer inline language translation, extended emoji sets, inline Yahoo! Calendar reminders, or enrich contact profiles with updates about your friends' activities. If you cannot put your enhancements where a user needs them, why build them? 

In short, the business and technology sides of the SDP were impaired to the point of irrelevance.

Skype needs to reset the program. And its platform.

More soon.

tags: , , , ,

Call me at +1-510-316-9773, Skype me, follow @skypejournal and @Phil Wolff.
Visit our Skype Journal private roundtable, one of the longest running public Skype chats.

Labels: , , , , , , ,

Thursday, May 7, 2009

Open Arms: a data portability approach

Open Arms hug

Caveat Lector: this is a rough draft of my thinking on what a Portability EULA /TOS should say/do/include. Please comment. - Phil

We've discussed Graceful Exit, the ability for people to control their departure from a site or service.

Open Arms starts at the beginning of your relationship with a service. Let's summarize it, break it apart, and explain why this is a powerful way to do business.

Open Arms is a combination of policy and technology.

The policy says:

When you come to our site,
bring all of yourself.
We'll help you put it to use
in our context.
We'll make it easy to come.
We'll keep it safe.
We'll respect ownership as you see it.

What you add while you are here
will join your collection
and be portable in turn.

The elements.

All of yourself.

Bring your identity, your contacts, your history with your contacts, your photos and videos, your playlists, everything digital.

We'll ignore what we cannot use.

Put it to use in our context.

Every site has a context.

  • Things it does
  • Purposes people share
  • Community standards of behavior.

For example:

  • Monster brings work and workers together.
  • Flickr helps people manage what comes out of their cameras.
  • YouTube is a community of video.
  • QuickBooks helps you manage your business.
  • Chemistry helps you find true love.
  • Amazon and eBay bring buyers and sellers together.

We need your data. These sites could help you do more and do it smarter with more and fresher and truer information from you. Monster could create team job search features if it knew your social graph. Chemistry could be more accurate if it had your music and video playlists.

Our sites are verbs. We do things. The more data you bring, the richer the data, the fresher and more standardized the data, the more we can do, the more creative we can be.

Most people don't try new sites because it's hard to recreate data. Especially for every site you visit.

Easy.

So for Open Arms to work,  bringing your onlife to each site you join must be fast, simple, easy, and obvious. And correct.

Safe.

We will protect everything you share. We will protect it from damage, theft, natural disaster, financial ruin, legal physical threats, from legal threats, from Martian invasion. As best we can. And we'll explain the threats we perceive and how we're protecting you and your onlife from them. 

Ownership as you see it.

"Ownership" is a tricky word: it means one thing to lawyers, something else to most people. Our online and mobile social experiences are a little ahead of the law. So all we can do is try to the right thing for you and for all of our guests.

We'll respect that your stuff is only "mostly" yours and that you may not have permission to share them with strangers. You may not have permission from the subject of a photo, or their parents. You may have clipped a blog post to share under fair use, but not for general distribution. You may have a confidential email that could endanger lives if leaked.

We will assume everything you bring is private to you and that you will tell us what can be shared, with whom, and under what conditions.

We'll make it easy for you to re-use your choices, so you don't have to explain yourself everywhere you go.

Portable in turn

Reciprocity works. So we're going to share with other sites the part of your onlife you spend with us, as you see fit. So you never feel we're holding your data hostage.

What's next?

So, we've "Open Arms" at the start of our relationship and "Graceful Exit" at the end. Next up "Ever Fresh" in between.

Labels: , , ,

Thursday, April 30, 2009

Can digital pipes handle swine flu epidemic spikes?

Pandemics change human behavior for millions of people. Our networks may not be ready for those changes.

avisoimportante-Chupacabras Just stay home. Wash your hands. Advice from the US CDC for people at risk of the 2009 swine flu. Mexican authorities urge avoiding face-to-face contact in many-to-many places like hospitals, museums, theaters, cinemas (releases of X-Men Origins and Star Trek are postponed), churches, sports events, public markets.

importantnotice-Chupacabras Working at Home. While television (or streaming video) might substitute in sports and music events, bringing other work home is harder.

  • Can mobile phones and the Internet create alternatives for information, education, service, and entertainment workers?
  • Can employers keep workers home?
  • Can employers quickly offer full digital command, communications, collaboration, coordination, and control services to sites scattered throughout a city?

maskedsoldier-Chupacabras-Online communities swarm in response to emergencies and threats. 9-11, Tsunami relief, Katrina, Mumbai invasion, Southern California wildfires had four stages.

  1. Spreading alarms ("hey did you see?") through many online media to trigger swarming. today, this includes tags and #hashtags, improving discoverability and transmissibility of the event and the event's memes. People want to know more. As people flock to the news, they create an overwhelming amount of repetition and echo and noise. So people start... 
  2. Organizing to improve/concentrate/filter information. People want to make sense of the spew. At the start people create new topical blogs, email lists, facebook forums, YouTube channels. Volunteers transcribe television and radio reports, retweet headlines and commentary, timelines of government responses. In short filtering, digestion, and meaning step in. Then people want to help other people (and themselves). So you see
  3. Online serves offline. Volunteers build specific services connecting online news/community to local people/places/activities. For Tsunami relief I participated in an instant call center via Skype community volunteers. Other services put together online databases of victims, or geomashups of hotspots, or fundraising projects, or medical information.
  4. Aftermath. People are helped, most of the online world goes back to their lives, and some of the legacy systems persist to serve those still concerned or affected by the event.

maskcrowd-Chupacabras-

By contrast, people shun common places and take refuge in their homes in a biological outbreak/epidemic/pandemic.

This creates new problems.

  • Stage Leapfrogging. Surprise! Step 1 (alarming, swarming) will take place in hours. You'll move immediately to Step 2, managing information overload. You could wake up having missed your chance to shape your community's and business's response. Or first access to preventive measures. 
  • Social Infrastructure Demand Scales. While millions are affected by most major disasters, pandemics could affect hundreds of millions, especially those in big cities where people congregate. Is twitter ready for 100 million new users? Facebook? CDC.gov? Amazon and Google cloud computing?
  • Infrastructure Demand Shifts Home. Capacity is in the wrong place. Are the nation's ISPs ready to move data to residential pipes at workplace speeds, without residential caps, all day, every day? How fast can mobile carriers supplement residential coverage? Who would fund this buildout? Can we beef up the last mile faster than an epidemic spreads? Can we allocate resources based on where an epidemic hits first and worst, instead of using pure market forces?
  • Cannot Filter Meaningful Signal from Abundant Noise. Today's tools don't help people consistently and reliably pick the vital, life changing information from the ordinary. So you'll miss product recalls, medical updates, neighborhood alerts in the lossy spew of mailing lists, social updates, and newsfeeds. Would you trust your family's life to a #hashtag ?
  • Local Focus Without Local Filters. Many of our systems depend on hundreds or thousands of people looking intently at one topic. What happens when we have must hyperlocalize news and community? The ratio of participants-per-topic falls fast as people focus on their own lives, their own work, their own neighborhoods. Does your block have enough people updating the network so the social network benefits kick in? We clearly don't have tough, accurate filters/readers to help us focus by:
    • Geography (streets, blocks, buildings, neighborhoods),
    • Topic (all those people who might have congregated at baseball games, pubs, museums, city hall), and
    • Occupation (by employer, workplace, team, process, project, agency)
    • Clinic (chains of information, care, supplies, volunteers, alerting)
  • Service Gaps. The digital divide has dramatic health effects on the poor, homeless, and underclasses. Tens of millions of the vulnerable are without mobile phones, email, or any frequent internet access. How do you connect offline people to online services?

What can we do to prepare?

See also:

photos credit cc:by Randal Sheppard 

Labels: , , , , , , ,

Wednesday, March 11, 2009

SkypeSync supports Portable Contacts API

3-6-2009 3-05-28 PM by you. 
3-6-2009 3-12-00 PM by you.

The SkypeSync desktop utility imports your contacts into Skype from other platforms. The new SkypeSync 1.8 adds sources supporting the Portable Contacts API. The standard is supported by Plaxo, so SkypeSync supports import of Plaxo contacts into Skype.

SkypeSync supports other sources too, including webmail address books from Google and Yahoo! using email standards and mobile phone contacts via the SyncML protocol. I described SkypeSync's mobile data portability last year,

Skype's own Contacts > Import Contacts... wizard in Skype for Windows 4 imports from Yahoo! web mail and Outlook desktop mail. SkypeSync steps in to fill gaps in Skype's coverage.

SkypeSync suffers from a few limits beyond its control.

  • Searching the Skype p2p user directory is so slow it makes looking up Skype names difficult.
  • Backward compatibility means I now have six "Alec Saunders" contacts instead of one with his five phone numbers. UPDATE: Skype limits max number of phone numbers per Skype contact to three.
  • Skype does not permit programmers to search the Skype Find/Prime business directory.
  • And there is no place for SkypeSync to store medata from other sources (address information, emails, employers) as notes about my contacts.

On my wishlist for future releases:

  • Dozens of other sources.
  • Offer intermediate steps before adding contacts.
  • Push Skype contacts into Plaxo and other services. 

Step by step... 

3-6-2009 2-44-25 PM by you.

Pick your source. Today you can choose from SyncML mobile phones, Outlook, GMail, Yahoo! mail address book, and Plaxo.

3-6-2009 2-54-40 PM by you.

I chose Plaxo, where I have more than a thousand contacts pulled from my Google, Yahoo!, LinkedIn, and Facebook accounts.

Skype is picky about phone numbers: they need a "+" in front, in the US a "+1". 

3-6-2009 3-00-17 PM by you.

So you've defined your source and set your numbering.

Now you can start your importing. Trial mode limits you to 15 names from any source.

3-6-2009 3-00-31 PM by you.

And go...

3-6-2009 3-02-06 PM by you.

Whoops. I need to give SkypeSync permission from my Skype client.

3-6-2009 3-02-25 PM by you.

So, trying again, SkypeSync adds 15 contacts to Skype.

3-6-2009 3-04-25 PM by you.

Results

I buy the software and, with a "full license", import all 3970 of my Plaxo contacts.

They are labeled "SkypeSync" so you can see who's been imported.

SkypeSync by you.

Most of my contacts don't have Skype names, just phone numbers: the green phone icon. Some of them have two phone numbers. SkypeSync creates two contact entries, one for each phone number. Inconvenient, but needed for compatibility with older versions of Skype. Skype for Windows 4.0 supports multiple phone numbers for each Skype name, but this hasn't always been the case.

SkypeSync by you.

Looking at the screenshot above, some people are offline. They have Skype names in their Plaxo profiles.

Sadly, SkypeSync automatically sent these people an invitation to connect in Skype. Should this be opt-in? Should SkypeSync offer you the chance to not-add a former girlfriend, someone suing you,

Strangely, Skype sent an email notifying the new invitees. This is new to me. 

License

Trialware

Cost

€12, pay with SkypeOut credit

Easy of Use

1green1green1green1blankgreen1blankgreen

Does What It Says

1green1green1green1green1green 

Useful

1green1green1green1green1green

Fun

1green1green1green1blankgreen1blankgreen

Social

1green1green1green1green1green

Certifications

Not Skype certified

Labels: , , , , , , ,

Monday, March 2, 2009

Jaduka names voice mashup king to CEO spot

image

In his inaugural post, Thomas Howe articulates the platform challenge: to make realtime talk easy for non-voice programmers.

Andy Abramson bets Thomas will strengthen Jaduka's focus on enterprise integration. Rich Tehrani's interview with Thomas covers the whole company. Gary Kim says Thomas brings street cred.

Thomas Howe's been on Jaduka's radar for a while. Patrick Murphy called Thomas one of the top three Telco 2.0 thought leaders last December.

Jaduka is one of the few companies positioned to dominate talkification of the web. Their platforming strategy is

Congrats to Thomas and the whole Jaduka crew. See you at eComm.

See also: Should Skype buy Jajah? Lypp? Truphone? Jaduka? and Jaduka's Trevor Baca at eComm 2008.

Labels: , , ,

Monday, February 9, 2009

Skype hosts video cards for Valentine's Day

Cupid and a rainbow Teddy bear with heart balloons Closeup of Teddy bear with heart balloons Coming to the house of love with heart in hand and a present

Skype sets the mood with free video valentines. Pick your cover…

Happy Valentine's Day Happy Valentine's Day For My Valentine Be My Valentine

Record your love note using a webcam, and address it to the one(s) you love.

From the Skype media team:

Roses are Red, and Violets are Blue
Chocolates are sweet, but what about you!?

To make someone smile and giddy with glee,
Just video call your Valentine; it's easy and free!

With a click and record, your readers can share, 
Their Valentine's wishes as though they were there.

While overpriced roses can stir up some hype,
What better surprise than a quick call on Skype!

So say 'I Love You' to him, her, or mom, 
By recording a video card at Skypevideocard.com.

Observations from the 2008 Christmas/Chanukah Video Greeting Card version still apply: Skype can use your video as they like, including your name and the name of your recipient. Skype will delete your videos when it suits them. No encryption. While Skype video cards are a great example of marketing fun and elegance, my concerns still stand:

The video card site doesn't use Skype. At all.

  • No use of Skype names or address books to send video greetings.
  • No use of the Skype client to record the video message. Or to view video messages from others.
  • No use of the Skype client as a way to continue the conversation in a voice, chat or video call.
  • No use of Skype's advanced audio/video codecs for higher quality.

Skype Video Card highlights where Skype's technology is creaking with age at the end of 2008.

<geek>

  • Skype doesn't offer a browser-based client. Rich Internet Apps improve virality and adoption with less downloading and faster time-to-value.
  • Skype's APIs don't expose an open web services platform beyond simple presence. So third parties cannot build Skype into, oh, say, video card apps running in browsers.
  • Skype doesn't support third-party authentication, identity interop, profile synchronization, or personal contact synchronization, or personal contact group synchronization. Far from the data portability ideals.
  • Skype's identity model does not facet identity. So you're stuck with one profile for everyone. For family. For every job. For every relationship. Forever.
  • Skype clients don't support inline media sharing. No playing of images, videos, sounds or other objects during a conversation.

</geek>

Love, Phil

Labels: , , , , , , , , , , , , , ,