Re: ActivityPump API

Hi Evan and all,

After carefully reading the ActivityPump API, I like the approach. I 
think that federating directly with AS is more straightforward than the 
PuSH/Salmon mix. We are close to comply with SWAT0 using OStatus in 
Social Stream, and the feeling is that PuSH and Salmon are somewhat 
repeated, besides XML is too verbose.

Thinking more about distributed social networking, I find there are two 
separated aspects. On the one hand, a remote site tries to learn about a 
user, her profile, activities, stuff, etc. On the other site, we have 
activity notifications between sites.

The last can be described using JSON AS + Audience Targeting + 
Responses. I think that federation between sites could be achieved with 
only one activity point per site. This way, notifications to several 
users in the same site could be delivered only once. Authorization could 
be handled in the similar way Facebook does with apps (note that apps 
are also authorized to publish on behalf of users if the permission is 
granted)

What do you think?

Best regards.


El 20/09/12 12:58, Evan Prodromou escribió:
> I thought people on this list might find the new API document I wrote 
> for the ActivityPump interesting:
>
> https://github.com/evanp/activitypump/blob/master/API.md
>
> It's a simple (/I/ think) API that follows the patterns of Atom 
> Publishing Protocol but uses Activity Streams JSON as a feed and entry 
> format. (It's based on work I did on StatusNet, which has a similar 
> API based on the Activity Streams Atom serialization.)
>
> tl;dr version: each user has two primary streams (represented as 
> Activity Streams multi-page collections): an /outbox/ that contains 
> activities they've done, and an /inbox/ that contains the activities 
> of people they follow. To make something happen, you POST an activity 
> to the outbox.
>
> One side-benefit is that the inbox makes a nice endpoint for delivery 
> of activities from remote servers. This serves the same purpose as 
> PubSubHubbub and Salmon in the OStatus stack -- but considerably 
> easier, I think. It requires Dialback authentication, however, which 
> is a) easy but b) only a few weeks old.
>
> I'd love any feedback here or as a github issue. There are plenty of 
> test cases in the ActivityPump repository.
>
> -Evan
>
>
>