- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Thu, 20 Sep 2012 11:09:02 +0000
- To: public-fedsocweb <public-fedsocweb@w3.org>
- Cc: Simon Tennant <simon@buddycloud.com>, Andrei Sambra <andrei@fcns.eu>
Excerpts from Evan Prodromou's message of 2012-09-20 10:58:42 +0000: > 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 I would find it interesting if people working on BuddyCloud and MyProfile could compare it to their architectures :)
Received on Thursday, 20 September 2012 11:09:30 UTC