ostatus

OStatus interview with Tyler Gillies

Today's interviewee for the OStatus interview is Tyler Gillies, the resident hacker at ReadWriteWeb.com.

Give us an overview of your software. What is it, and what does it do?

Tyler: I've been using StatusNet since the first day identi.ca was released. You can find me at Tyler or tjgillies.

My first implementation of OStatus was robin. You can find it at robin. It is a rails based app that implements all the main features of status.net (webfinger/salmon/pubsubhubbub, etc), however, it is not currently being actively maintained. Please feel free to fork and commit patches. I have a plan to re-implement robin using "upgraded" technology, probably nodejs and redis.

Why did you decide to implement social web federation?

Tyler: I chose to pick social web federation because I only had two choices. Either federate, or don't. I didn't want to live in a walled garden. (I own http://opengard.in)

What problems did you have?

Tyler: Honestly, the specs on salmon are a little weird, and it was frustrating back then, because status.net, me and cliqset.com were the only ones who actually had a working implementation of salmon, so there wasn't a big support community. Also the documentation for the ruby ssl library is almost non existent.

How can users try out OStatus in your software?

Tyler: I don't currently have a website up running robin, but if they are familiar with rails, they can download it and try to get it running themselves. I am currently working on a location based app that will probably end up using OStatus to federate messages.

Check out geoloqi, I am developing the nodejs server.

- Tyler

Over the next couple of weeks there will be more OStatus interviews posted right here, so stay tuned!

OStatus interview with Pablo Martin

Today's OStatus interview will be with Pablo Martin, a developer from the Lorea project.

Give us an overview of your software. What is it, and what does it do?

Pablo: Lorea is a project to create secure social cybernetic systems, in which human networks will become simultaneously represented on a virtual shared world.

Its aim is to create a distributed and federated nodal organization of entities with no geophysical territory, interlacing their multiple relationships through binary codes and languages.

On the scope of the project we use different open source software, like elgg, postfix or ejabberd to implement such communication, where we're developing key modules to extend their possibilities.

Why did you decide to implement social web federation?

Pablo: One of our main goals is to have good federation mechanisms for communication among networks of people. We think federation is critical for privacy in the internet because it guarantees you can decide where your data is while still being able to communicate with people on other networks.

Why did you choose OStatus?

Pablo: Our systems want to talk to everyone that wants to speak to them, so we decided to implement OStatus since its an open standard with high alignment with our project in the scope.

What parts of the OStatus suite have you implemented?

Pablo: We have implemented activity streams, salmon and pubsubhub support for many types of objects. We also have some extensions currently, and are in the process of finishing of webfinger support for better connection with StatusNet.More detailed info can be followed at: https://n-1.cc/pg/dokuwiki/1760/doku.php?id=federation

What problems did you have?

Pablo: Our main problem is the activity streams/OStatus ontology misses some important things for us. Other thing I can see I regard as problematic is the difficulty to do inter-network federation tests with other software.

How can users try out OStatus in your software?

Pablo: On a shared node, they can participate on remote groups to a certain extent, and message or friend remote users, also soon subscription of remote OStatus profiles will be possible directly for users (right now the admins of networks are the only ones capable of pulling remote users or groups). Also, our profiles can be subscribed to by OStatus users. Current nodes supporting OStatus federation include http://redesenred.net, https://n-1.cc, https://red.artelibredigital.net.

On personal nodes, since the user is the admin there are a lot more things that can be done including a lot of experimental use of OStatus with other techniques. Any group or profile can be subscribed to.

- Pablo

OStatus interview with Tuomas Koski

Hello OStatus community! OStatus will be releasing a series of blogs that include interviews with a handfull of professionals talking about their thoughts on OStatus. Our goal is to see who is using OStatus, what they are using it for, and what they like/dislike. Today we will be posting our first OStatus interview and the interviewee is Tuomas Koski.

Tuomas is a 30 year-old Finnish rock'n'roll coder living in Paris. He has been participating in different open source projects and federations over the past six years. Presently, he is working in the private sector, in the energy business and he is starting his own company as well.

Give us an overview of your software. What is it, and what does it do?

Tuomas: Buddycloud is a location based microblogging service. Buddycloud is mainly about two things: user generated channels and places.

A channel is somewhere between a Twitter posts and IRC conversation. A user starts a topic (a thread) in a channel and people can add comments to it.

Buddycloud at the moment has two kind of channels, user channels and topic channels. Each user has their own user channel where they can express themselves how ever they want. Every user can create other channels as well. We call these kind of channels "topic channel's".

The channels can be even open to anyone or only available for defined users. So these are both like “groups” in activity streams.

We believe in rich and quality content and we also want that content to be in a context. We want to see a system that when I see a comment, for example on a widget on a web page, I can very quickly see the whole context and the full short conversation.

Originally buddycloud was only a mobile application (and still mainly is - the web version is very very alpha release and a huge hack) but because of being a mobile application first has had a strong location and place integration from the start.

We believe in a location system where user can have privacy and - once again - valuable context to it. We don't believe in location as street addresses are "Boulevard Goblin 8, 75013 paris" but locations like "Home", "The Gilt Club" or even places like "Sleeping".

We believe that user being placed to a place should be automatic, no "check-ins or check-outs". Because of this, in buddycloud, the user "bookmarks" a place only once. and when she arrives there the next time she will be placed there automatically.

Users can of course choose if their location is public or is displayed only to the trusted people. Location and places are calculated from wifi spots and cell towers. Of course GPS is supported to.

Why did you decide to implement social web federation

Tuomas: Social networks are really not networks if they do not network together. I believe that microblogging is like email service. Everyone should be able to host their own system if they want or need. People/organizations should have full control of their data and users and accounts. People should be able to control what is shown. There's no profiling, no marketing no terms changing. And so on.

Why did you choose OStatus?

Tuomas: It's a great team of enthusiastic people. OStatus is trying to create protocol where every user can control their "stuff" as they want. Possiblity of user being able to take their data and switch to another service is also great and I support it truly.

What parts of the OStatus suite have you implemented?

Tuomas: All. Buddycloud is close to be fully OStatus compliant in production. In theory we are. We had all Activity Streams, pubsubhubbub, Salmon, Webfinger implemented but it was a bit against our "business logic" so at the moment we have only pubsubhubbub and activity streams enabled in “production”.

So why havent' we put all OStatus stuff out yet? Why is it greating some problems? The core of buddycloud is XMPP based. And the all the “business logic” our application has that were build upon the possibilities of XMPP. We are working to change our logic to support all OStatus use cases.

Since buddycloud is already in "production" and takes more time to change, I have started another project "MiniMe - the Minimalistic Personal Microbloggin Service" with my friend Julien Da Silva. It's fully OStatus compliant microblogging service. The idea behind it is to have example implementation of all OStatus protocols. Also the idea is that it's super simple to install: just copy/paste. How ever the easy install part is not reality yet.

What problems did you have

Tuomas: No problems really. Biggest problem is to have multiple different implementations to test against. Also to understand all differences of every implementations business logic takes time since it's not visible. With this i mean that for example different services are using for different things.

How can users try out OStatus in your software

Tuomas: More about MiniMe can be read here: http://code.google.com/p/minime-microblogger/ I will be heavily updating the project page the coming days. Buddycloud can be found here: http://buddycloud.com/ or just start following me in your status.net installation using URI http://buddycloud.com/user/xmpp.lobstermonster.org/tuomas

- Tuomas

OStatus discussions will be held at the Federated Social Web Summit 2010!

The Federated Social Web Summit will be held on July 18th, 2010 in Portland, Oregon. The purpose of the summit is to get contributors of the federated social web together to discuss current issues and successes in the open source community, and more importantly discuss what the future holds.

Some of the invitees include StatusNet, Google, Facebook, Twitter, Tumblr, and Mozilla, just to name a few. At the summit there will be discussions on OStatus in hopes of creating a larger OStatus network thus encouraging more people to continue to move towards a truly distributed social Web!

It's started!

Hard to believe it, but the OStatus process is underway.

OStatus lets people on different social networks follow each other. It's transparent to your friends, colleagues and family which software or service you use. They can get your status updates on their own sites and reply, like, or re-post your updates.

OStatus isn't a new protocol; it applies some great protocols in a natural and reasonable way to make distributed social networking possible.

  • Activity Streams encode social events in standard Atom or RSS feeds.
  • PubSubHubbub pushes those feeds in realtime to subscribers across the Web.
  • Salmon notifies people of responses to their status updates.
  • Webfinger makes it easy to find people across social sites.

OStatus weaves these protocols together to make an easy-to-implement distributed social network.

Sites like Google Buzz, StatusNet, WordPress.com, and Tumblr have implemented some or all of these protocols today. We hope that defining the junctures where the protocols work together will encourage adoption of the entire suite.

The OStatus spec is a first step in this direction. We're eager to work with other implementers to make it better, to smooth the rough edges, and to improve the overall experience.

Everyone interested is invited to join the ostatus-discuss mailing list to get this discussion moving.

Thanks to everyone who's made these protocols work so well together. We hope that OStatus can bring these efforts one more step forward.

Syndicate content