Group items tagged

Tahoe is a secure, decentralized, fault-tolerant filesystem. All of the source code is available under a Free Software, Open Source licence. This filesystem is encrypted and spread over multiple peers in such a way that it remains available even when some of the peers are unavailable, malfunctioning, or malicious. The one-page summary explains the unique properties of this system.

TeleBlog regular Branko Collin gave a nice explanation of how microformats could aid pickups of information from book reviews for Technorati. Josh Gay of the Free Software Foundation, whom I met Friday at a library conference in NYC, has also been a big booster of the concept. I  can see why. As described by Wikipedia, “any page created, or any content added to microformats is placed into the public domain for maximum possible reuse.”

That sounds anti-commerce. But actually microformats could help even commercial sites by, say, bringing more traffic to a book review magazine than it would receive otherwise. Theoretically Yahoo could create a page listing reviews for a certain book and automatically pick up ratings from each publication’s writeup. Such a capability, in turn, might just drive you to visit the sites and see how the reviewers justified the rating. What’s more, other sites could ride Yahoo’s coattails and reproduce the Yahoo page.

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.

Anyone who has been involved in Open Source software development knows that you have to have a steering group, and there has to be some hierarchy. You can't get a ship moving in any direction with 50 oars in the water each rowing in their own direction. I understand that in order to have buy-in from so many different groups, no one wants to alienate anyone, but the reference made at the meeting (and I'm sorry I forgot who made it) to OpenID was a valid one. They developed the technology, then took it out to various companies and asked for buy-in. In order to "strike while the iron is hot," the luxury of having 100 people all defining things differently and addressing different concerns before there is even a rudimentary roadmap makes the scope of the project much larger than it has to be, and slows down progress.

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.