Group items tagged

A few months ago, we announced that we were opening the social graph and invited others to join us. An effort like that encompasses many different technology projects and all kinds of different companies; in just a few months the idea of opening up social networks has received a lot of attention. Today we're excited to share an amazing new plugin for Movable Type that allows you to aggregate, control, and share your actions around the web and we're the first to bring this sort of functionality to free and open source blogging tools.

It's worth revisiting some of the successes the openness movement has accomplished in just the past few months: Google's OpenSocial released new versions of its APIs and we hosted a wildly successful hackathon to help support the creation of new widgets for the standard. OpenID 2.0 shipped and both Google and Yahoo! are now supporting OpenID, bringing hundreds of millions of new IDs to the community. The group DataPortability.org was formed and released a video reinforcing these themes around openness. And finally, we've made good on our promise to let you show off all the services you belong to, with TypePad and Vox automatically letting you list your accounts around the web on your blogs using Microformats to link to your profiles. And as of today, the same ability is available for Movable Type.

As we explained half a year ago, we're on a mission. Like we said then, blogs change the way we communicate. Just like with TrackBack, OpenID, opening the social graph, and so much else in blogging, we're hoping that we can influence everyone else to follow our lead and move blogging forward with us. Bringing your actions around the web under your control is a fundamental next step to making all of our blogs even more powerful and expressive.

It was kind of heartening today - after reading yet another press release about some BigCo joining the DataPortability effort - to stumble upon this roadmap timeline of activities leading to a DataPortabilioty enabled web.  Kind of heartening in a cute naive way.

So lets please lighten it up on the press releases and claims of support - when its just not clear what the hell these companies are supporting or what they’re doing - at all.

I’m sure some folks are wondering exactly what this means. Even though I was close to the decision making around this, I believe it is still too early to tell. Personally, I share Marc Canter’s skepticism about Dataportability.org given that so far there’s been a lot of hype but no real meat.

As far as I can tell, Dataportability.org seems like a good forum for various social software vendors to start talking about how we can get to a world where there is actual interoperability between social software applications. I’d like to see real meat fall out of this effort not fluff. One of the representatives Microsoft has chosen is the dev lead from the product team I am on (Inder Sethi) which implies we want technical discussion of protocols and technologies not just feel good jive. We’ll also be sending a product planning/marketing type as well (John Richards) to make sure the end user perspective is also being covered. You can assume that even though I am not on the working group in person, I will be there in spirit since I communicate with both John and Inder on a regular basis.

The social web is booming, signing up new users and generating new pieces of unique content at a steady clip. A recurring theme of the social web is "data portability," the ability to change providers without leaving behind accumulated contacts and content. Most nodes of the social web agree data portability is a good thing, but the exact process of authentication, authorization, and transport of a given user and his or her data is still up in the air. In this post I will take a deeper look at the current best practices of the social Web from the point of view of its major data hubs. We will take a detailed look at the right and wrong ways to request user data from social hubs large and small, and outline some action items for developers and business people interested in data portability and interoperability done right.

Basically what people are saying is that it’s a bad idea to give sites your usernames/passwords when you sign up. This creates a bad anti-pattern and sets a horrible precedent for users who simply give their email user/pass to hundreds of different startups with dismal security standards making it very easy for hackers to get to your sensitive data. It’s called the “password anti-pattern”.

In my mind Flickr provides probably the best page-flow pattern. So I’m saying the PROVIDERS are making this anti-pattern possible. Facebook must make it VERY easy to export users, so must Gmail and so must Yahoo etc. This must be standardized so that containers (using Open Social terminology) can provide that data using some kind of token system, and it must also happen in a process that doesn’t ask for you user/pass. I believe that because it’s not possible, networks are leaving developers with no other option but to do screen scraping.

Social networks are great: you can stay in touch with friends all across the world and find new ones based on your interests. But often, social networks serve a single purpose or interest. For instance photos, videos or classmates from school and university. This is not a problem by itself, but when you want to keep track of all your contacts in all these social networks, this is a lot of work for you to update your contacts list in all the social networks you are in. And you also might need to get a member of a social network, although you're not interesed in the subject, but only want to track your friends activities. NoseRub only defines the social network and some basic content types like media, links, micropublishing and text. You can now add all your contacts to a NoseRub network and aggregate several social networks into just one. And you always have full control of your data, as you can install NoseRub on your own server and have it connect to other servers out there.