Showing posts with label OpenID. Show all posts
Showing posts with label OpenID. Show all posts

Friday, May 1, 2009

Don't Fear Data Portability...fear the LACK of it!

[This was in response to an article over at Internet Evolution by Nicole Ferraro]




Data Portability, Privacy, and Ownership are three completely separate things that are nevertheless intimately related. Regarding data portability, if you are away from home and suddenly the local doctor needs to access your medical records, wouldn’t you want them to be able to do that quickly and securely? Unfortunately, without data portability, he may very well be able to get the data – but not be able to use it because it is in a format his systems are unfamiliar with.

The concept of single sign-on (OpenID, Facebook Connect, etc.) is a great example of Data Portability, though it only scratches the surface in terms of overall usefulness. Nevertheless, single sign-on allows information to “talk” to other systems in ways that are defined by concepts rooted in data portability.

People should be scared of unbridled access to information without constraints, accountability, and security. But, data portability is not something to be afraid of. It is an empowerment that operates transparently and provides options without limiting choices. And, with any luck it will be a core component of data solutions that puts a smile on everyone’s face.

Steve Repetti
www.radwebtech.com
www.dataportability.org
www.twitter.com/SteveRepetti

Saturday, February 7, 2009

Facebook’s Move to “Openness” Setting de facto Standard?

Yesterday, Facebook took a further step in opening its network by introducing enhancements and new features to its developer APIs. Facebook’s new APIs make it easier for applications to update user statuses, links, and upload videos from outside of Facebook. This effort will likely generate a flurry of activity in the developer community as new applications are created and existing ones enhanced to take advantage of these new capabilities.

[Add to this the earlier announcement of Facebook’s support of OpenID and things are definitely starting to get interesting]




But beyond the power and convenience of integration and data portability from external sources, the real story lies just below the surface. Facebook is striving to become the ultimate repository for all of your social-media information and this is another step along that path. Their platform is becoming a global data-store and their APIs are empowering developers and users with standardized methods of interaction.

On the one hand there is very little about this that is open. Facebook controls the data, its access, and its availability. Facebook defines the integration, they determine the protocols, and the APIs, and even who can and cannot use any of this. This “openness” is all under the oversight, control, direction, and whim of the giant.

Yet, when you think about it, Facebook has made huge strides in extending its world beyond the looming walls of their garden. And, while I don’t think this was their original intent, they have nevertheless listened to their user base and observed the opportunity the market presents.

Some may call it baby steps, others an attempt at world domination. But the winner today is the user (and yes, it’s pretty good for Facebook too!); and the benefits continue to evolve. Along the way, these initiatives will provide new and innovative methods for interaction with users and data that may lead to de facto standards for data portability. Will that actually happen? That depends on Facebook’s “real” position on openness, the user’s tolerance and acceptance of that position, and the response from the other great giant seeking dominance in the global data-store market – Google.

Tuesday, January 6, 2009

Twitter Hacked, Reactively Eyes Solutions, Tweets on the Edge of Data Portability

The recent meltdown of Twitter security raises important issues related to Data Portability, most notably issues of security, integrity, and responsibility, that are relevant to all users. It also serves to demonstrate the need for prioritization by data stores.

Had Twitter simply said, “we will take your data and do whatever we want with it – including giving your login credentials to whomever we want” then no one would have had a problem. Of course they would probably have a lot less users.

But that is not what they said – and that is not the expectation that users had. In fact, in addition to the specific “terms of service” agreement that everyone accepts when they become Twitter users, there is an implied relationship that is created that defines the expectations of both sides. One of those is the reasonable expectation that your login information (including password) would be private and protected.

Now, obviously this is a dynamic world and there are lots of bad guys out there. And it will never be perfect. But there are straight forward solutions to many of these issues – especially in this day and age -- provided their implementations rate the necessary priority in the eyes of the Twitters (and other data stores) of the world.

To Twitters credit, their response has been quick -- and still in process. But more folks need to be proactive, not simply reactive.

Elias Bizannes, a fellow DataPortability board member, talked about this at length over at the official Data Portability blog, as did DP board member Christian Scholz here.

OAuth by itself is not the answer – but it is an important part of the solution. Ultimately the solution involves technologies such as OAuth and OpenID, but it also requires a mindset, commitment, and acceptance of responsibility in proactively keeping the rights of users always in the forefront. This is a main tenant of Data Portability and is an issue likely to dominate the headlines for some time to come – one way or the other. Companies will increasing be called out – or praised --- on this issue depending on their policies and priorities.