Group items tagged

autonomo.us is an independent group of hackers, activists, and scholars exploring the ideas of user freedom and autonomy as they relate to network communication technologies.

MySpace and Google demonstrated an interesting mashup of the MySpace Data Availability API, oAuth and the iGoogle gadget specification at the oAuth Summit a couple of weeks ago. The application, which pulls the core MySpace feature set into iGoogle, is not yet publicly available, although MySpace has said to expect in in August.

Chris Saad, cofounder and chair of the nonprofit ­DataPortability Project, notes that many current methods of transferring data expose users to huge security risks. For example, it's a common practice for social sites to ask users to submit the usernames and passwords for their Web-based e-mail accounts when they first sign up; an automated service can then search the network for people listed in their address books. "The door is open right now for any application that scrapes your Gmail address book to go ahead and scrape your shopping cart as well, or scrape your searches, or keep your username and password and pretend to be you," says Saad. "It's a nightmare of security, and it's something we need to solve sooner rather than later."

Search Monkey will be the first use of structured data by Yahoo, but they could potentially be used to affect other parts of the search results or ranking algorithms in the future, according to Kumar. Yahoo will provide more details at an upcoming developer conference it's planning in the coming weeks.

Social networks are becoming more open, more interconnected, and more distributed. Many of us in the web creation world are embracing and promoting web standards - both client-side and server-side. Microformats, standard apis, and open-source software are key building blocks of these technologies. This model can be described as having three sides/legs/arms/spokes - pick your connection: Information, Identity, and Interaction. DiSo (dee • zoh) is an umbrella project for a group of open source implementations of these distributed social networking concepts. or as Chris puts it: "to build a social network with its skin inside out". Our first target is Wordpress, bootstrapping on existing work and building out from there.

The bigger downside of Friend Connect is that Websites using it cannot mash up the data with their own to make compelling new applications. Glazer confirmed that the data will be sent to third party sites via an iframe rather than directly through a set of APIs (as Michael speculated on Friday). However, Glazer also says that he wouldn’t be surprised if eventually Google or somebody else makes it possible for Websites to combine the Friend Connect data with their own.

The next trick will be building awareness and adoption. When you consider that 0% of all websites (or enterprise apps) accept i-cards or OpenID, and 0% of sites issue cards, it’s small wonder that 0% of users today even know what an identity selector is. We’ve got our work cut out for us!

As an example, the Dataportability movement has framed the problem in terms of Data and Portability. This brings to mind exporting and importing “my” data from vendor to vendor. That’s a start toward liberating users from vendor silos. However, I think the real win is in user-centric services, where the location of the “data” is essentially irrelevant–even as it is hosted under the control of the user–and all user-authorized vendors can access the data through approved services.

I always say that you have to manage you online indentity and that you have to put effort in gaining online authority. This because the online world is getting more and more integrated with the real world and as a person you have to have an online authority to become popular in networks. But there are so many social networks and it takes so much time. Well possible dataportability may help to manage all your profiles online! Just watch the video.

How do you explain to an end-user what DataPortability is, why they might want it, and where they might get it?

How do you explain to a developer what DataPortability is, why they might want it, and how they might achieve it?

Developers learn most effectively by developing something. Users learn most effectively by using something.

What is needed though is a discussion about this and what the best practices in these cases should be. One option would be the opt-in for such XFN-markup but of course those links would still be available although not that easily extractable. Making it more private would probably harm the site’s usefulness. Removing them might also harm social services such as dopplr which make good use of them to find your contacts on dopplr.

So it’s many questions to be answered and I wonder what a good process might be to answer them. Surely there is the  around but of course they cannot just publish guidelines and the problem is solved. A broader discussion is needed and for a start maybe an exact description of the problem and coming from these some proposals to solve it.

Despite the valid concerns that some have with Google’s Social Graph API, I thought I would talk about the technical possibilities. My social graph may be of particular interest becuase I had used my Wordpress blog’s XFN feature to mark up the blogs I read as “muse” and my profile on at least 10 social networks as “me.” Using the Google’s Social Graph API demo you can see my extensive list of FOAF and XFN URLs. There is also a machine readable format that could be fed into a new social network to find friends on that network. (click for a larger version)

Today, organizations are spending an excessive amount of time learning about OpenID, installing and configuring Open Source libraries, customizing and integrating with existing infrastructure, and maintaining the latest features and capabilities of OpenID. With the comprehensive JanRain RPX solution, a software as a service platform, you can capture all the benefits of OpenID for your website without all the hassles.

As the web grows exponentially in scale and complexity, an issue that becomes increasingly pressing is data ownership. There has been a lot of noise lately about how Facebook Connect, Google Friend Connect, and even MySpace’s Data Availability.

The Data Portability Project is trying very, very hard to solve these serious issues. They’re seeking to unite the socio-rhetorico-legal precedent with the growing list of open technologies and specifications (OpenID, OAuth, RSS, OPML, MicroFormats, Creative Commons, to name a few) and make sure that these proprietary bits, bytes, friends, enemies, birthdays, activies, pictures, videos, lifestyles, etc. are made open to the content creators (read: YOU, not Mark Zuckerberg).

For website owners it only makes sense to support any kind of ” [Facebook/ Google/ Open] Connect” solution, if the majority of their user-base also maintains their social graph at one of those “Social Graph/Identity” providers. Speaking for Germany: that is neither for Facebooks Connect nor Googles Friend Connect (also with the Plaxo combo) the case yet!

We build a solution upon the OpenStack, because than it will work with much more websites, who support the OpenStack as well as a consumer

If you look at the rest of the world - outside of “Facebook-Land” - you also realize and understand much better, why it is so important to find an holistic solution approach - build on open standards - to solve the issue FB Connect addresses: we live in a very diversified world and if everybody comes up with a proprietary solution, it will be just a big mess in the end.

Beginning today, Windows Live™ ID is publicly committing to support the OpenID digital identity framework with the announcement of the public availability of a Community Technology Preview (CTP) of the Windows Live ID OpenID Provider.

Note that the Windows Live ID OP supports only the OpenID 2.0 protocol.

The current Technology Preview release is for testing purposes only