diff options
Diffstat (limited to 'specification/forgefed.md')
| -rw-r--r-- | specification/forgefed.md | 32 |
1 files changed, 10 insertions, 22 deletions
diff --git a/specification/forgefed.md b/specification/forgefed.md index 08dd0aa..1496b54 100644 --- a/specification/forgefed.md +++ b/specification/forgefed.md @@ -2,8 +2,6 @@ title: ForgeFed --- -# ForgeFed - DRAFT - **Editors:** - deesix @@ -30,28 +28,18 @@ platforms. # Status of This Document -# Table of Contents - -1. [Overview](#Overview) -2. [Conformance](#Conformance) -3. [Objects](#Objects) -4. [Actors](#Actors) -5. [Client to Server Interactions](#Client to Server Interactions) -6. [Server to Server Interactions](#Server to Server Interactions) -7. [Acknowledgements](#Acknowledgements) - -1. Overview +# Overview ForgeFed is an extension of [ActivityPub](https://www.w3.org/TR/activitypub/) and follows the same "actors" model, with a client-to-server protocol and a server-to-server protocol. -2. Conformance +# Conformance The key words MAY, MUST, MUST NOT, SHOULD, and SHOULD NOT are to be interpreted as described in [RFC2119]. -3. Objects +# Objects Objects are the core concept around which both ActivityPub and ForgeFed are built. Examples of Objects are Note, Ticket, or Image. @@ -59,7 +47,7 @@ Objects are wrapped in Activities, a subtype of Object that describes some form of action that may happen, is currently happening, or has already happened. Examples of Activities are Create, Delete, or Follow. -4. Actors +# Actors A ForgeFed implementation MUST provide an Actor of type `Repository` for every repository that should support federation. @@ -67,32 +55,32 @@ repository that should support federation. A ForgeFed implementation SHOULD provide an Actor of type `Person` for every user of the platform. -5. Client to Server Interactions +# Client to Server Interactions ForgeFed uses Activities for client to server interactions, as described by ActivityPub. A client will send objects (eg. a Ticket) wrapped in a Activity (eg. Create) to an actor's outbox, and in turn the server will take care of delivery. -5.1. Follow Activity +## Follow Activity The Follow activity is used to subscribe to the activities of a Repository. The client MUST send a Follow activity the a Person's outbox. The server in turn delivers the message to the destination inbox. -5.2. Push Activity +## Push Activity The Push activity is used to notify followers when somebody has pushed changes to a Repository. The client MUST send a Push activity the a Repository's outbox. The server in turn delivers the message to the Repository followers. -6. Server to Server Interactions +# Server to Server Interactions -6.1. Follow Activity +## Follow Activity The server receiving a Follow activity in a Repository's inbox SHOULD add the sender actor to the Repository's followers collection. -7. Acknowledgements +# Acknowledgements |