- From: James M Snell <jasnell@gmail.com>
- Date: Wed, 4 Feb 2015 07:45:17 -0800
- To: Evan Prodromou <evan@e14n.com>
- Cc: "public-socialweb@w3.org" <public-socialweb@w3.org>
The lack of federation between existing social platforms is due largely to the lack of incorporating federation requirements into the design of the platform and it's API. That's not evidence that the Social API and Federation API are two separate things. Rather, it demonstrates that if you want real Federation, you really ought to bake it into the design from the beginning. Yes, there are distinct aspects of federation that would qualify it as a separate top level bullet point within the Social API's list of features, but I do not view Federation as an entirely separate entity. On Wed, Feb 4, 2015 at 7:26 AM, Evan Prodromou <evan@e14n.com> wrote: > On 2015-02-04 09:56 AM, James M Snell wrote: >> >> Nor should we fool ourselves into thinking that the social API and >> federation bits are two separate things. > > Given that most social networks today a) have client APIs and b) don't have > federation, it seems pretty clear to me that they are two separate things. > > Could you explain how I'm fooling myself? > > -Evan > >
Received on Wednesday, 4 February 2015 15:46:08 UTC