- From: Michiel de Jong <michiel@unhosted.org>
- Date: Mon, 9 Jul 2012 14:25:06 +0300
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: Markus Sabadello <markus.sabadello@gmail.com>, Flemming Bjerke <web@bjerke.dk>, public-fedsocweb@w3.org
On Mon, Jul 9, 2012 at 12:51 PM, Melvin Carvalho <melvincarvalho@gmail.com> wrote: > You will never convince everyone on the web to use the same stack. Yet, that is what i propose we do. :) We will define one stack that defines how to be on the fedsocweb. Not very strict though, we should make it very modular, and with small steps. Different parts of it will be optional, that's fine, for instance if my friend's node doesn't run xmpp, then it will just say "chat not available" for that friend. In your case, you will probably show up in my friends list without a full name and without a photo, because you don't run webfinger. that's fine, i can still email you. There may also be parts of the stack that overlap, like private messages via smtp or via xmpp or via PuSH. We can indicate that this is the case and explain the differences. As long as everybody announces which components of the stack they support, and which not. There's a difference between what a fedsocweb node should implement and what it should accept from other nodes. If my friend is on a node that runs the facebook protocol instead of webfinger, then we will just translate it. Be strict in what you send, but generous in what you receive, and then everything will be nice. I'll try to find some time to make a start with writing this up, but basically the stack i'm thinking of would be: web hosting (required) + optionally (parts of) OStatus + optionally xmpp + optionally smtp. depending on which things you implement, you would get different functionalities.
Received on Monday, 9 July 2012 11:25:33 UTC