If context
contains ordered activities, servers can easily sync their copies of context
by fetching the collection until they encounter activity with a certain timestamp. That could be useful for backfilling in federated groups.If context
contains objects, backfilling would be limited to comments (no reaction backfilling, which can be important for Reddit-like services).
Posts
-
How do you use `context` (if at all)? -
If you Announce(Object) are you not following FEP 1b12?Information about Legacy Compatibility was not included on purpose: https://codeberg.org/fediverse/fep/pulls/20#issuecomment-687050But I still think it would be helpful to include. Perhaps in a different FEP, because FEP-1b12 was finalized.
-
If you Announce(Object) are you not following FEP 1b12?Minor changes are allowed:
A proposal with status
FINAL
can not be changed or updated in a way that would lead to adjustments to implementations.The paragraph proposed by @bumblefudge sounds like a normative change, but not a backward incompatible one, so I wouldn't object against including it.
-
I think in order to reconcile FEP-400e and FEP-1b12 the following changes can be made:I think in order to reconcile FEP-400e and FEP-1b12 the following changes can be made:
- Both FEP-400e and FEP-1b12 implementations: support FEP-7888 (context collection)
- FEP-400e implementations: upgrade to Conversation Containers
- FEP-1b12 implementations: add
target
property toAnnounce
activity that points to context collection.
Activity types will still be different (
Add
vsAnnounce
), but consuming implementations can easily accept both.