Rampidbyter Rampid byter: A byte of my .Net developing life.

I’m not a huge fan of social networks partly because it seems most hardware vendors have switched from pushing performance to being mobile, and from being mobile to being socially connected. In that switch from performance to being socially connected most any hardware systems created today are always internet enabled with some sort of dashboard with instant Facebook/MySpace/Flickr/ or Twitter account hookup.

To even use these features a person has to constantly signup for an account, dump their personal information, manage yet another personal Id/password/profile, and then keep their profile up-to-date. There has been some progress made in terms of single account sign-in with OpenID, but there has been no progress in single profile management.

When developing applications it’s easy to create a PAD (Portal Application Description) for sharing product information from one author to many different consumers. It would be incredibly kick-ass to develop a SPD (social profile description) file that a person could create, and would allow social media sites to import/maintain the profiles on the social media sites using the user generated file. That gets into the whole how do you get the social media sites to open up to enable a consistent profile format across sites, who ultimately maintains these profiles, and about securing the contents of the profile file against duplication/impersonation.

Still I think it would be awesome, and it would spare me the trouble of having to log into these social sites to update my profile. Luckily my actual profile about who i am and what I do doesn’t change much. Still I would like to see social sites coming to me for updates instead of the other way around. Oh, maybe call it the OpenMe project or something of the like.