mirrors/fep
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 11:46:04 +00:00
Code Packages Wiki Activity

[0499] Add example for embedded activity delivery (#405)

Browse Source 
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/405
Co-authored-by: a <a@trwnh.com>
Co-committed-by: a <a@trwnh.com>
This commit is contained in:
a
2024-10-03 21:21:52 +00:00
committed by silverpill
parent 464ce8c551
commit 60a1797484
1 changed files with 28 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fep/0499/fep-0499.md
+28 -1
View File
@@ -19,7 +19,7 @@ This FEP introduces a server-wide endpoint for delivering activities to multiple
sharedInbox allows servers to reduce network traffic when delivering Public activities to multiple recipients, but it doesn't work when delivering to collections of actors, or when delivering to private audiences using bto or bcc. If an activity is addressed to a collection and that activity is delivered to a remote sharedInbox endpoint, then this introduces a requirement for the remote server to know the contents of the collection (or at least the local subset of its contents). In the common case of delivering activities addressing followers collections to a sharedInbox endpoint, then the remote server must first recognize that this collection id is specifically a followers collection, and then guess which local actors are following that activity's actor. This is prone to issues and can also have disastrous outcomes when follower state drifts out of sync.
We can eliminate the dependency on shared follower state and allow for delivery of non-Public activities by introducing a new endpoint that likewise allows delivering to multiple inboxes, but without requiring the remote server to know anything.
We can eliminate the dependency on shared follower state and allow for delivery of non-Public activities by introducing a new endpoint that likewise allows delivering to multiple inboxes, but without requiring the remote server to know anything. This enables addressing arbitrary collections as well as the use of `bto` and `bcc` more efficiently.
## Prior art
@@ -115,6 +115,33 @@ Content-Type: application/ld+json; profile="https://www.w3.org/ns/activitystream
## Terms defined
<div resource="https://w3id.org/fep/0499#multibox">
<h3 id="multibox">multibox</h3>
<dl>
<dt>URI</dt>
<dd><code>https://w3id.org/fep/0499#multibox</code>
</dd>
<dt>Comment</dt>
<dd property="https://www.w3.org/2000/01/rdf-schema#comment">An optional endpoint used for wide delivery of activities to multiple inboxes.</dd>
</dl>
</div>
## References
- Christine Lemmer Webber, Jessica Tallon, [ActivityPub][ActivityPub], 2018
- Christine Lemmer Webber, [Rebooting the Web of Trust 9: Keeping Unwanted Messages off the Fediverse > Proposed Suggestions > MultiBox][multibox], 2020
[ActivityPub]: https://www.w3.org/TR/activitypub/
[multibox]: https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/topics-and-advance-readings/ap-unwanted-messages.md#multibox
## Copyright
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
To the extent possible under law, the authors of this Fediverse Enhancement Proposal have waived all copyright and related or neighboring rights to this work.
]
}
```
## Terms defined
<div resource="https://w3id.org/fep/0499#multibox">