Comments on: Open Social compatibility: social networks and applications vendors working together http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together Digital Lifestyle Aggregation - helping to establish open source infrastructure Sat, 05 Jul 2008 23:59:07 +0000 http://wordpress.org/?v=2.2 By: wooden serving trays http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243397 wooden serving trays Sat, 17 Nov 2007 09:18:34 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243397 haven’t seen the opensocial specs in detail yet, but the graph really shouldn’t use the email address as the unqiue identifier. haven’t seen the opensocial specs in detail yet, but the graph really shouldn’t use the email address as the unqiue identifier.

]]> By: tony http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243317 tony Tue, 06 Nov 2007 22:30:29 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243317 While i agree that it would be great if openSocial was what you described, it is not the case. openSocial is at it's heart about app/widget portability, and has nothing to do with portabilitly of user data, including social graphs. the only kind of cross network portablitity would be provided by the app developers, for example, if i make an app that stores a users favorite movies, i would then store a list of movies associted with a unique network/user id that is given to me by the social network, when that users profile loads, some javascript sends the id of that profile to me, and i return the movie list. i can also do things like push an feed item saying this id added this movie to its list and the network can do what it pleases with it. the only possiblity for portablility here is if i, the app developer, allow users to link multiple id to a single movie list in my database. the networks themselves share no data. with that said, i'm sure some interesting grey box techniques could be used to scrape data from multiple networks, which could make it possible to have some sort of portable profile that just exists in the cloud and that be exported. While i agree that it would be great if openSocial was what you described, it is not the case. openSocial is at it’s heart about app/widget portability, and has nothing to do with portabilitly of user data, including social graphs. the only kind of cross network portablitity would be provided by the app developers, for example, if i make an app that stores a users favorite movies, i would then store a list of movies associted with a unique network/user id that is given to me by the social network, when that users profile loads, some javascript sends the id of that profile to me, and i return the movie list. i can also do things like push an feed item saying this id added this movie to its list and the network can do what it pleases with it. the only possiblity for portablility here is if i, the app developer, allow users to link multiple id to a single movie list in my database. the networks themselves share no data.

with that said, i’m sure some interesting grey box techniques could be used to scrape data from multiple networks, which could make it possible to have some sort of portable profile that just exists in the cloud and that be exported.

]]> By: Marc Canter Speaks Out and Loud About OpenSocial! (Were You Surprised?) | BoomTown | Kara Swisher | AllThingsD http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243312 Marc Canter Speaks Out and Loud About OpenSocial! (Were You Surprised?) | BoomTown | Kara Swisher | AllThingsD Tue, 06 Nov 2007 07:20:41 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243312 [...] Canter doesn’t care if it’s a rumble or not, as long as it moves the needle forward on opening up [...] […] Canter doesn’t care if it’s a rumble or not, as long as it moves the needle forward on opening up […]

]]> By: Between the Lines mobile edition http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243303 Between the Lines mobile edition Sat, 03 Nov 2007 15:08:41 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243303 [...] See also: Marc Canter on OpenSocial compatibility–social networks and applications vendors working together [...] […] See also: Marc Canter on OpenSocial compatibility–social networks and applications vendors working together […]

]]> By: 2007 November 02 archive at Cloudlands http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243298 2007 November 02 archive at Cloudlands Fri, 02 Nov 2007 21:40:34 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243298 [...] and still preserve all the interactions with their friends (the bit that really matters).” Marc Canter says: “Me - I’m just sitting here, smiling and wondering about interop and whether all [...] […] and still preserve all the interactions with their friends (the bit that really matters).” Marc Canter says: “Me - I’m just sitting here, smiling and wondering about interop and whether all […]

]]> By: Myspace joins Google & Co. in OpenSocial » nonsmokingarea.com » Blog Archive http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243296 Myspace joins Google & Co. in OpenSocial » nonsmokingarea.com » Blog Archive Fri, 02 Nov 2007 19:30:12 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243296 [...] Marc Canter - Open Social compatibility: social networks and applications vendors working together [...] […] Marc Canter - Open Social compatibility: social networks and applications vendors working together […]

]]> By: Jeremiah Owyang http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243294 Jeremiah Owyang Fri, 02 Nov 2007 13:58:00 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243294 Marc There's a lot of geek speak on the Open Social announcement. If you need to explain it to executives, I've tried to make it very clear and concise from this post, weighing the pros and cons. http://tinyurl.com/3dtqs6 Love to hear any feedback, even if you don't agree. Marc

There’s a lot of geek speak on the Open Social announcement. If you need to explain it to executives, I’ve tried to make it very clear and concise from this post, weighing the pros and cons.

http://tinyurl.com/3dtqs6

Love to hear any feedback, even if you don’t agree.

]]> By: John Furrier http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243293 John Furrier Fri, 02 Nov 2007 12:15:50 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243293 Marc: you've been beating the drum for years for social interconnect. When I was briefed on OpenSocial a couple of weeks ago I was smiling and thinking of you. Continue to push the envelope on the implementation issues and keep your eye on the efforts of this 'open' alliance. Lets hope that its open. The world is going to turn out just the way that you envisioned it years ago. Congrats. Marc: you’ve been beating the drum for years for social interconnect. When I was briefed on OpenSocial a couple of weeks ago I was smiling and thinking of you. Continue to push the envelope on the implementation issues and keep your eye on the efforts of this ‘open’ alliance. Lets hope that its open. The world is going to turn out just the way that you envisioned it years ago. Congrats.

]]> By: Eric http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243291 Eric Fri, 02 Nov 2007 10:46:47 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243291 Got what wrong? Got what wrong?

]]> By: Joseph Poon http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243289 Joseph Poon Fri, 02 Nov 2007 06:58:19 +0000 http://blog.broadbandmechanics.com/2007/11/open-social-compatibility-social-networks-and-applications-vendors-working-together#comment-243289 <i>user’s social graphs also have to be under their control and a full disclosure of that social graph’s unique identifiers (eg. their email address) is crucial if any developer is able to do anything with this social graph - that is not inside the firewalls of a social network (SNS.)</i> I haven't seen the opensocial specs in detail yet, but the graph really shouldn't use the email address as the unqiue identifier. That's a really bad idea because it's incredibly difficult to automate user behavior using emails. Make it URLs so that people can then support OpenID and even more importantly, you can get contextual data to act on the user's behalf. The end result of open social data is automating human behavior so you don't have to worry about day-to-day crap. For instance, it's impossible to me to automate arranging calendar synchronization over email -- whereas if you had an HTTP endpoint, you can hit the URL, check if you both had the calendar protocol/endpoint set up (whether it be via AX, uFormats, whatever). I know email is presently the unique identifier on the web, but I think the identity community should be looking forward, not backwards. user’s social graphs also have to be under their control and a full disclosure of that social graph’s unique identifiers (eg. their email address) is crucial if any developer is able to do anything with this social graph - that is not inside the firewalls of a social network (SNS.)

I haven’t seen the opensocial specs in detail yet, but the graph really shouldn’t use the email address as the unqiue identifier. That’s a really bad idea because it’s incredibly difficult to automate user behavior using emails. Make it URLs so that people can then support OpenID and even more importantly, you can get contextual data to act on the user’s behalf. The end result of open social data is automating human behavior so you don’t have to worry about day-to-day crap. For instance, it’s impossible to me to automate arranging calendar synchronization over email — whereas if you had an HTTP endpoint, you can hit the URL, check if you both had the calendar protocol/endpoint set up (whether it be via AX, uFormats, whatever). I know email is presently the unique identifier on the web, but I think the identity community should be looking forward, not backwards.

]]>