PresenceNext

Ivar Ekman points out Google’s Jaiku poses a privacy risk.

Ahem. That’s the point of disclosure.

Presence: Dimensions of Disclosure Influence

1. Recipient
2. Data
3. Social Context
4. Time Value
5. Licensing

And presence.

Presence is the approved radiation of your latest information.

Presence authorization is not a binary disclosure to Everyone or Nobody.

Authorization can be, must be, tailored to the recipient.

Four dimensions of influence:

1. You might base disclosure on attributes of the recipient.

• Groups they belong to (family, co-workers, people I hate),
• age (adults-only data),
• location,
• citizenship,
• security clearance,
• social proximity,
• relationship history (people you’ve talked/chatted/met with in the last year).

Jaiku and facebook share presence based on group affiliation and social connection.

2. Perhaps authorization is more closely tied to which data you share. Some people share their calendar. Do you share just your availability? Your location at a given time? What you’ll be doing? With whom?

3. Social context frames the authorizing decision. Perhaps you don’t share your political life at work. Or your fantasy blog with your family.

4. Time and your Sense of Now change the value of information. Do seconds matter? Minutes? Hours? Some information is better shared late. Perhaps you enjoy sharing the restaurants you visit, but not while you are there. Other information loses value quickly: minute-to-minute election day results, for example.

5. Licensing sets terms of use. Perhaps you agree not to share this data. Or to only share it under certain conditions.

The blend informs disclosure. Of what you share with whom, in each context and precisely when must inform disclosure. You should be able to share your latest blonde jokes only with your blonde friends (data and hair color of the recipient).

Presence is subscribed to, actively requested, not only available for public scraping.

Presence subscription calls for subscribers to disclose too.

So Authorization looks like Negotiation…

“I want to subscribe to information about you.”

“Are you representing a human?”

“Yes, here are my credentials.”

“Ah, looks like you are on my client’s friend list. Here’s a list of feeds you’re eligible for.”

“Jokes! Cool. Yes, I would like to see your joke stream.”

“I need more information. Have you ever tripped over a wireless phone?”

“Yes, I am a blonde.”

“Great. You agree to only share these with other blondes?

“On my blonde honor.”

“You should be able to see the blonde jokes stream now.”

Since Dave Winer and Netscape first promoted RSS in 1997, syndication meant being public, sharing your content with Google.

Skype, Jaiku, and all presence providers must rethink their

tags: <!– –>skype skypejournal presencenext presence context socialcontext disclosure rich presence

Voice, Presence and the Social Software Stack - Interop for the Facebook age (for architects and geeks)

Managing Editor, Skype Journal

Reef9 Media Corporation

A childhood geek, Phil used Rand computers in 1968, spent a summer coding a Univac in 1972, graduated from high school in 1976, wrote microcode in 1977, etched circuit boards in 1977,

Phil Wolff is a technology futurist and product strategist, covering Skype and live collaboration since 2003 for Skype Journal. Phil is an alumnus of Gateway, Compaq, Bechtel National, LSI Logic and was VP for strategy and technology for Adecco SA, a global 500 firm. Phil enjoys cinema and curling.

Voice, Presence and the Social Software Stack

architects and geeks, and business strategists

Let’s talk about “Interop for the Facebook age.” The Social Software Stack brings structure to thinking about how social networks, live communication, and messaging interoperate. (insert overview of the stack here) One layer in the stack is Presence, our subject for today.

Presence is only starting to change now after being frozen for 40 years. Before we get into presence architecture, let’s explore metaphors for presence, what presence means, and what presence does. (insert exploration here)

CIA.vc blends automated updates from software development workflow with live human status updates. The system messages come from “checking out” and “checking in” your work from an online code repository. The live talk is on IRC - internet relay chat. The bot posts trigger human observations, feedback, interaction.

     <CIA-5>  jupiter * r9203 xchat-gnome/buildsystem.diff:
              update for new plugins
     <staz_>  what are the new plugins?
<purple_cow>  nothing functional yet
<purple_cow>  working on 308765 and 320477
     <staz_>  ok
     <staz_>  thanks

Archived to web, the live stream becomes history: an organized, searchable narrative of a project’s story.

While designed for the open source coding community, this model fits many workplaces. There’s an art to picking which system messages are most meaningful, create the best conversational triggers, and occur infrequently so they don’t turn into spam.

I found a link to this article in Network World on Slashdot today. It is interesting reading because if the feds want something they will soft regulate it into existance. What does soft regulation mean? Well for IPv6 they are mandating that devices being bought by the Defense Department all be IPv6 forcing the major vendors to put it into their stacks.

The interest in presence technologies seems to be new, given that few federal agencies have deployed the technology. Less than half of survey respondents – 44% – said they use these systems, but another 28% said they plan to roll it out over the next 18 to 24 months. The remaining 28% of respondents have no plans to use the technology….

The interest in presence technologies seems to fit with other survey findings that point to increased use of mobile phones, BlackBerries and other PDAs. The survey found that 83% of respondents use PDAs and 73% use wireless laptops.

A smaller share of federal network managers use instant messaging – only 46% – and soft phones only 21%. Both of these technologies often come bundled with presence features.

“A lot of the mobile devices used by first responders and warfighters support presence,” Burns says. “This finding is a recognition that you can offer new capabilities that will directly address the mission of the agency.”

TwitterGrams distribute short and small audio clips via twitter. 30 seconds to a minute with a few characters of text.

As twitter
is to
blogging,

This is another stupid idea by Dave Winer. Dave’s other stupid ideas included podcasting, RSS syndication and aggregation, hosted content management, WYSIWYG blogging authoring, river style news readers, and other stuff that’s changed my life and how the world communicates. I don’t know if I can handle another revolution this month.

Maybe I could learn to love a River of TwitterGrams. A stream of aggregated short audio and video clips. Updated throughout the day. Embrace Continuous Partial Attention and ignore the Interruption 2.0 Manifesto.

I don’t understand a few things about Dave’s implementation of this.

• Why do I need to push the post through an intermediate service?
• Why not just post to twitter directly and ping a server with metadata? The publish-and-ping architecture works now for blogs, podcasts, and vlogs.
• Why limit update intervals? Wouldn’t this inhibit those who create front ends for your service? I could see wordpress.com offering authors the chance to cross post to twitter and TwitterGram. So one “publisher” may distribute hundreds of TGs per minute.
• Why force mp3 as the only medium and format? Why not allow any kind of small payload? Video, playable games, playlists.
• Since you’re building a service that pushes TGs out to one microblogging service, why not let the API include a list of destinations? So one post/ping to you lets my TG go to jaiku, facebook and other selected services?

Just for fun I recorded The Jabberwocky (slightly over Dave’s 200k limit) and a short explanation of the Internet Radio Day Of Silence.

For the Supernova 2007 Open Space Day.

Casting call: Actors, Directors, Gatekeepers, Context Brokers, Agents, Calendar Keepers, Sensor Nets, Operators.

My notion: what might we learn about “presence” if we role play four scenarios?

Scene 1. The DND Button

Scene 2. Calling Oprah Winfrey

Scene 3. The Job Offer

Scene 4. Walking Down The Street

I’m hoping the roles and interactions, and some of the metaphors might be clearer afterward. Or at least the questions might be more focused.

So far I see five roles emerging (this is wrong but it’s easier to revise than start from scratch).

1. Presence generators and publishers.

2. Aggregators

3. Instigator agent

4. Gatekeeper

5. Context provider

There may also be a defined role for raw data provider or sensor network.

tags: presence presencenext supernova supernova2007 roles roleplaying improv play

tags: aggregation digital digitalid fame identity im opencallerid openid presence reef9 skype syndication

Phil Wolff, Kaliya Hamlin - Barnes and Noble, Jack London Square - Raw notes

Put together a list of potential orgs/people to invite

• Categories - not inclusive

• Academe

• danah boyd

• Lee Dryburgh

• Microsoft

• Dare Obasanjo

• Aaron from mindgarden

Preparation package / prework

• Questionnaire - your views
• brief bios
• “accelerated butt sniffing”

Synching with other presence events

• Possible, but deferred

Sponsorship

• tied to tangibles, like the report, the meals, venue 

Designing the conversation

• questions that move conversations forward, appreciative inquiry (AI)
• can we use next generation presence in planning and conducting this conference

Venue Hunting

• Sensibility of a retreat
• Tech facilities

Timeline

1. Now
2. Pre-invite - 10 people
   • Anchor tenants, people that draw other people
3. Invite - 30 people
• Fill out form - ask good questions
• If I could present, what would i present on?
• Have you presented on this?
• Link to slides or video or pdf
4. Rite of Passage for non-invitees: Essay, why you should come, what you’ll contribute.
5. Confirmation
6. Before You Come
• Things we need. e.g. projectors, video cameras
• decks for ppt karaoke
7. Welcome
8. The Event

Miscellaneous to do

• Phil - get on Gordon Cook’s list
• Phil - see “Anthropology of IM” article in The Economist
• Site - before
  • write an About This Event page
  • write Event Deliverables
• Site - for the event
  • PresenceNext community - continuing the conversations
    • bio/personal pages
    • company/org pages
    • listservs
    • refer a friend
    • wiki
    • blog aggregator
    • event registration
    • sponsors
    • membership

Orange, like RSS.

A person’s head radiates out.

Typeface: Calibri.

Hugely derivative.

Makes a point, though.