The Widgets Shall Inherit the Web

1
The Widgets ShallInherit the Web

• Widget Summit
• 4 November 2008

2
Widget authors Youre ahead of your time!

• Widgets thrive in an environment with
• existing users, data, social graph, and activity
• Its a symbiotic relationship
• Widgets have had to live where the data is
• embedded in existing social network pages
• (and often without good APIs)
• But soon, the data will come to you!
• Thanks to the rapidly emerging Open Stack

3
In a world with lots of socially-aware sites
4
and lots of open social web building blocks
5
how do the pieces fit together?

• and what will the new Social Web look like?

6
(No Transcript)
7
Reminder The social web today is broken

• On each site, we still have to
• Re-create an account
• Re-enter our profile info
• Re-find our friends
• Re-establish our relationships
• New social apps have limited options
• Create yet-another-silo (and start from
  scratch) -or-
• Make a widget inside an existing walled garden

8
but we know how to make things better!
9

• Create a portable, durable online identity
• OpenID
• Sign up / sign in with an existing account
• Link / share your profile data between sites

10
Example Sign up for Plaxo with OpenID
11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14

• Create a portable, durable online identity
• OpenID
• Sign up / sign in with an existing account
• Link / share your profile data between sites
• relme (XFN)
• Consolidate your online identity with me-links
• Social Graph API
• See what your users said about themselves

15
(No Transcript)
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
Public profiles enrich online identity
21
(No Transcript)
22

• Build and maintain real relationships
• Contact APIs
• Find people from your current address book
• Leverage previously established relationships
• OAuth
• Share private data between trusted sites
• Friends-list portability
• Continuous discovery across multiple sites

23
(No Transcript)
24
(No Transcript)
25
A periodic check of new people from your
networks on other sites
26

• Stay up-to-date with the people you know
• OpenSocial
• Build social apps that can run anywhere

27
OpenSocial
28
OpenSocial Large and Growing Rapidly
29

• Stay up-to-date with the people you know
• OpenSocial
• Build social apps that can run anywhere
• RSS / Atom
• Syndicate your activity to share with others
• Jabber (XMPP)
• Real-time update stream between sites

30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
(No Transcript)
44
(No Transcript)
45
(No Transcript)
46
(No Transcript)
47

• How does friends-list portability work?
• Tell the site your Social Graph Provider
• Site fetches your data to find local friends
• Site lets you connect to people you want

48

• How does friends-list portability work?
• Tell the site your Social Graph Provider
• XRDS-Simple (discovery) OAuth (access)
• Site fetches your data to find local friends
• Site lets you connect to people you want

49

• How does friends-list portability work?
• Tell the site your Social Graph Provider
• XRDS-Simple (discovery) OAuth (access)
• Site fetches your data to find local friends
• Site lets you connect to people you want
• Can periodically look for new matches

50

• How does friends-list portability work?
• Tell the site your Social Graph Provider
• XRDS-Simple (discovery) OAuth (access)
• Site fetches your data to find local friends
• ??? (no standard way to do thisyet)
• Site lets you connect to people you want
• Can periodically look for new matches

51
(No Transcript)
52
(No Transcript)
53
Portable Contacts The missing piece

• Effort underway to standardize
• contact schema
• discovery / auth
• common operations
• Focused on ease speed of adoption
• Active involvement from large small players
• More info current draft spechttp//portablecon
  tacts.net

54
Building blocks in action contacts portability

• User signs in with an OpenID
• Site fetches OpenID URL ? looks for
  X-XRDS-Location
• Site parses XRDS-Simple doc to discover available
  APIs
• Site tries to access contacts API ? gets a 401
• WWW-Authenticate response header specifies OAuth
• OAuth Discovery (via XRDS) provides OAuth
  endpoints
• Site sends user though OAuth flow to grant access
• User returns to site with authorized access token
• Site can now access users contacts data via API
  token

55
so how do these building blocks fit together?
56
(No Transcript)
57
(No Transcript)
58
(No Transcript)
59
(No Transcript)
60
(No Transcript)