open social networking
TRANSCRIPT
Data portability◦ The ability to efficiently export user-generated
content (UGC) held within a social network Open social graph◦ The availability of interpersonal relationship data to
a given social network from another
Morally important – we should own our UGC Lack of export options could discourage use
of network, as users do not want to relinquish control (cf concern about Facebook’s ‘data black hole’
Export options, from RSS to embeddable widgets increase opportunities for viral growth of network
Important for a competitive market
Offers the chance for long tail, best of breed, SNs to emerge
Removes, to some extent, the necessity to achieve a critical mass before app becomes useful
Encourages user adoption as removes barrier of having to build a network of friends each time
Avoids spammy invite emails!
Pros ConsAllows third party apps to take advantage of pre-existing social graph, creating a quasi-open social graph
Massive user base
Provides an excellent user experience
Provides a fairly capable API
Ad revenue earned is app developers’ to keep
Encourages viral app adoption through news feed and directory
Dependent upon Facebook’s continuing good will/good fortune – what if it goes bust or falls out of favour?
Requirement to build upon Facebook fundamentally limits application possibilities
Facebook graph can never be as ubiquitous as an open social graph encompassing all social network users, everywhere
Extended OpenID (xOpenID) is a development of OpenID which could be the best vehicle to achieve an open social graph
It is OpenID which also holds information on social relationships
If we are serious about the future of social networking, surely relationship data is just as important as email and real name is today when using a web app
xOpenID contains:◦ Personal ID data (such as email, real name etc)◦ Database of other xOpenIDs and the user’s
relationship to them (probably via an XFN attribute) Each user automatically maintains their own
‘master’ list of contacts on xOpenID which can then become contacts on a given social networking site, depending on user choice and relationship to user
Builds on pre-existing standards (OpenID and XFN) Achieves a good balance between centralisation (one
place which can be queried for a user) and decentralisation (no one person can have a monopoly over the social graph)
No reliance on direct inter-social network exchange of data, so no scope for a network to, for example, block a particular rival yet still accept imported data.
A user is able to maintain multiple xOpenIDs (as many users do now with OpenID) by interconnecting them with the “me” XFN attribute
Also solves the social networking fatigue problem (via OpenID) of having to enter personal identity information into every new social network
xOpenID requires universal adoption by social networks in order to become useful.
There is a ‘chicken and egg’ problem – there is no pressure upon social networks to use xOpenID until all other social networks are.
There may even be a disincentive to do so, as it could enable greater churn- currently the bane of social networks.
Facebook adopts it; If the up-and-coming player were to adopt it
then enough people would have it for it to be useful for niche social networks and gradually for other major networks
To create massive positive pressure for social networks to adopt it will always be more powerful than trying to circumvent non-adoption
Social network
Relationship and identity data UGC
xOpenID, XFNWidgets, XML, ‘make public’
option, APIs etc