[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Social-discuss] introduction & my thoughts

From: Melvin Carvalho
Subject: Re: [Social-discuss] introduction & my thoughts
Date: Thu, 27 May 2010 01:12:47 +0200

2010/5/26 Pepijn de Vos <address@hidden>

After watching a few of the ideas passing by on this mailing list I though I'd introduce myself.

I'm Pepijn de Vos, a web developer with a strong interest in social media.
I program mostly PHP, Python and Clojure.

I'm the author of a p2p network plugin for Wordpress, which is at the moment not maintained.

I'm not an network specialist, but my experience with port forwarding and server installations tell me that someone has to get really, really smart to get real p2p working.
It's just to complicated for the average person to run his own server.

Very much so.  Once everyone can run a personal server with a personal data store, even using the most basic protocols, 99% of the social web is in front of you.  I've yet to see many good solutions to this ... skype is great but proprietry ... Ubuntu One perhaps is in the right direction?
And then we have not yet talked about the issues of security, changing IP addresses and locations and offline users.
The solution from Bjarni Rúnar Einarsson sound very interesting though.

I personally think it is more feasible to go for an XMPP style federated approach or maybe more like Git and Mercurial.
That means we still need servers, but it's decentralized; Every server can talk to every other sever, and so can their clients.
Maybe this could even be an extension to XMPP?

Have you seen ?  They are doing good things with xmpp, imho.

I have a test on my computer which user Mercurial to pull and merge user profiles, in which case a website like bitbucket could be turned into a social network.

Another thing that can't be said enough:
I think a common protocol is very valuable in this case.

What makes you think one does not exist today?  If you look closely at HTTP you might find it can do more than you expected.

I want to share one more idea of mine, which I call reverse oauth(I know, bad name).
Normally you tell Twitter to grant access to a certain application.
With reverse oauth, every user takes the place of an app and a server at the same time.

Not a bad name, but be careful not to infringe the OAuth license.

The holders of the OAuth patents may have some protection there.  (IANAL)

This means that every user has its own key and secret and can ask permission to your account.
After you grant them access, they get an access token to you account.
You, like any other user, maintain a list of access tokens to access the accounts of your friends.
I'm not an encryption expert either, but I imagine you can do some nice encryption and validation with this token as well.

Nice system, makes sense.  Access tokens are normally a useful weapon.

Pepijn de Vos
Sent from my iPod Shuffle

reply via email to

[Prev in Thread] Current Thread [Next in Thread]