FEP-f06f: Object observers
Summary
Object observer is an ActivityPub actor that can be followed to receive object updates.
This proposal is intended to complement FEP-bad1: Object history collection.
Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119.
Observers
Object observer can be specified using the observer
property.
It MUST be a followable actor and SHOULD have an Application
type. Observer doesn't perform any activities on its own, but forwards to its followers all activities that affect the observed object.
It SHOULD have a WebFinger address (consumers should be able to follow it even if they don't understand observer
property).
Use case: subscribing to a conversation
When conversation is represented by a collection, a collection observer can be created to support conversation subscriptions.
This actor can be attached to a collection via observer
property, and can forward Add
and Remove
activities that modify it.
Non-forwarding observers
If forwarding is not desirable, object observers can use Announce
activity to distribute observed activities.
参考文献
- Christine Lemmer Webber, Jessica Tallon, ActivityPub, 2018
- a, FEP-bad1: Object history collection, 2023
- S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, 1997
著作権
CC0 1.0 ユニバーサル (CC0 1.0) パブリック ドメイン
法律で認められる範囲において、この Fediverse 拡張提案の著者は、この作品に対するすべての著作権および関連する権利または隣接する権利を放棄しています。