Re: User stories for Social API

> On 4 Feb 2015, at 15:24, Evan Prodromou <evan@e14n.com> wrote:
> 
> On 2015-02-04 09:05 AM, henry.story@bblfish.net <mailto:henry.story@bblfish.net> wrote:
>> 
>> There is no need for a Federation protocol if you do things correctly
> Our charter has three parts:
> Social data syntax
> Social API
> Federation protocol
> It sounds like you object to that framework, which is your prerogative.
> 
> Maybe for our next telecon you could sketch out an alternative vision, without a server-to-server protocol?

yes, that is not difficult. When you say client you mean browser, when you mean server 
you mean a machine that is usually without a display, and that is constantly bound to 
the internet. In my world - the world of HTTP and APIs - clients and server are just roles
that computers play. A computer program can be in server role in one moment and then client
the next. One multiple core machines they can be both simultaneously.  So there is no
server/server api. There can only ever be client/server relations.

I gave a talk on this a while ago  « Social Web »
https://archive.org/details/D2T303201308011300TheSecureSocialWebBblfish <https://archive.org/details/D2T303201308011300TheSecureSocialWebBblfish>

and in many other places.

Now having said that, we should try to get this sorted before the next teleconf,
because otherwise we will have to push back the writing out of use cases for yet
another week. For the moment I don’ t know if 
 - you are going to take down any use cases I put up that are cross  organisational? 
 - if you are not going to get upset if I turn siloed user stories into social web user stories?

Henry


> 
> -Evan
> 

Social Web Architect
http://bblfish.net/