WebCamp break out session #1 – Adoption challenges (for social network portability) and ways for solving them

Source: dsevilla @ Flickr

Adoption challenges (for social network portability) and ways for solving them;

source: WebCamp wiki

Disclaimer: this is a partly cleared transcript of discussion; I didn’t follow the authors of comments in order to be able to catch as much as I can. Correct me if I quoted someone incorrectly and please don’t be angry with me.

Present at the discussion:

  • Stephanie Booth, 8 years blogging, Freelance social media consultant, interested in blogging, and everything that’s online
  • Gerry Shanahan,, social media things, side of things
  • Sven Latham, IT consultant, used to run blog directory, semantic web and social networking is definitly as one of the interests
  • Paddy Holahan, Mobile blogging, NewBay founder and CEO; looking at this through the eyes of the operator, integrating with all the social operators
  • Jure Cuhalev, Zemanta, wishing to integrate with others
  • Smitashree Choudhury, doing a Ph.D. in Social media, working with media stuff
  • Justin Tomboulian, Microsoft, lives in Kyoto, Japan – responsible for solutions delivery; part of the network that takes care of 80k users ecosystem; trying to solve big-company illness problems; internal private social network and return the learnings to the community
  • John Breslin, DERI, interested in porting of data, SIOC, data portability initiative

The topic is: “Adoption issues”; what prevents people from using new technologies? The discussion turns to the question, why the big guys (FaceBook, etc.) are not adopting these solutions. Can we show that if we have portability, we will have more users.

40% of pictures on MySpace were referenced through PhotoBucket, so this was their biggest weakness when being acquired. So MySpace bought them, but the question is – was this a good thing for users? It means that MySpace killed the data portability of PhotoBucket. If you are looking at the photo that is sitting in photo-bucket, but is embedded into MySpace -> is this real portability or just “view-ability?”

So what portability really is? Should we copy the objects, or just reference it? It embedding YouTube portability of the video?

Quick explanation of aggregation vs. federation. News reader is aggregation -> data is on the web site, and I’m using special glasses to take a look at the data; it’s an aggregated view. Federation Is actually about “moving” data around. “Aggregation does not mean portability”; Reflection from a startup point of view: API’s are part of the discussion about portability, and the question was – why would we let others user precious data that users gave us. “It’s ours”. The point that Stephanie tried to get across: if you make your data available to other services, then this data is more valuable to users since then it will be available as parts of other sites.

The discussion turns into the fact weather FaceBook keeps a copy of your data and if you can get it removed. The right to delete the data is fundamental part of data portability. “Who’s data is this blog post? Just authors or of everyone that was there”. It is also hard from technical perspective. It’s also noted that web pages are cached and it is hard to quickly remove it from Google cache. It can be months, or days. Is it your right to delete your comments on a forum and disrupt the community. There is also a question of deleting blogs and the comments with them. The content becomes “part of community”, and with the deleting of the blog you are also removing other peoples original contribution. Users bill of right is mentioned –

What is the business model of “all these services”? “The because effect” – you do not make money with your blog, but because of it. The business models should turn more into that, instead of locking down the data to their islands.
What can you “bring” with you? Do you “move” -> delete original after copying; making a copy and having two copies; or are you existing in kind of a shared space that gets synced back and forth. Is business model – we are making money “with” the users content, not “because” of it.
If this content is great, then there must be money in that? Is that a good way of thinking about business models? The value of FaceBook is monetized eyeballs; they make money with branding ads since they actually charge according on time users spend on their site. They can’t make money from AdWords, they have to brand. These big sites do not have interest to open up their data until the competition comes. Using other big players in industry is possible for them to leverage their interest to make the data a bit more open.
What users want – is freedom of data; and companies want more face time, so there is no real interest for them to open data. “Is this similar to FOSS vs. proprietary debates”.

Data portability is a lot about business models. As long as business model issues are not solved, you can offer as much technical solutions as you want, you will not get adoption. “Users can vote with their feet”. Amnesty App – enabling users to migrate in one hop to another service. Static data formats are a problem, because we can’t know what will matter in a few years.

Ideal thing is that I have a store somewhere where I have all the information that I can allow others to read it. Who’s going to build it and the fact is that you can not design it correctly for the future. You could turn around it around and charge it to providers or the users, depending on the point of view on your data. What kind of business model is behind that?

2 thoughts on “WebCamp break out session #1 – Adoption challenges (for social network portability) and ways for solving them

Comments are closed.