mirror of
https://codeberg.org/fediverse/fep.git
synced 2026-08-05 19:55:46 +00:00
FEP-fc48: Use Create activity to create collections (#770)
Clarify that side effects are activities. Reviewed-on: https://codeberg.org/fediverse/fep/pulls/770 Co-authored-by: silverpill <silverpill@firemail.cc> Co-committed-by: silverpill <silverpill@firemail.cc>
This commit is contained in:
@@ -36,13 +36,13 @@ A generic server MUST support the following basic activities:
|
||||
|
||||
A generic server SHOULD support other activity types defined in the [ActivityPub] specification.
|
||||
|
||||
Other activities MUST NOT have side-effects. Any additional operations, such as collection updates, MUST be specified using the `result` property or sent as separate activities.
|
||||
Other activities MUST NOT have implicit side-effects. Any side-effects, such as collection updates, MUST be specified by clients as additional activities. Clients can embed them into an activity using the `result` property, or send them as separate activities.
|
||||
|
||||
## Managing collections
|
||||
|
||||
A generic server MUST automatically create `inbox`, `outbox` and other actor collections defined in the ActivityPub specification after registering an actor.
|
||||
|
||||
A generic server MUST create the collection specified in `target` property when a client publishes `Add` or `Move` activity. To create an empty collection, clients can publish an `Add` activity without `object`.
|
||||
Other collections MUST be created by clients using `Create` activities where `object` is an empty collection.
|
||||
|
||||
## References
|
||||
|
||||
|
||||
Reference in New Issue
Block a user