You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Create's id (…&resource=activity) mistakenly returns just the Note instead of the Create object too when resolved.
I see a few failure modes that could result from this. For example, a server that fetches an actor's outbox to backfill the profile timeline whenever its first local follower appears could end up with defective versions of these posts, distinct duplicates, or reject them entirely.
Boosting the outbox-retrieved version of these Notes onto other instances would most likely also fail in many cases, as Announces normally don't contain their object inline and ids must be treated as opaque blobs. It's possible it could still work in some circumstances, but this would depend on the receiver resolving one id to another and editing its ingested copy of the Announce in response, which it probably shouldn't do if it wants to avoid glitches.
The text was updated successfully, but these errors were encountered:
Looking at Postcasting 2.0, the outbox contains
Create
activities withobject
s shaped like this:If I navigate to the
Note
using itsid
(…&resource=post
), I see different data and the ID doesn't contain this suffix:The
Create
'sid
(…&resource=activity
) mistakenly returns just theNote
instead of theCreate
object too when resolved.I see a few failure modes that could result from this. For example, a server that fetches an actor's outbox to backfill the profile timeline whenever its first local follower appears could end up with defective versions of these posts, distinct duplicates, or reject them entirely.
Boosting the outbox-retrieved version of these
Note
s onto other instances would most likely also fail in many cases, asAnnounce
s normally don't contain theirobject
inline andid
s must be treated as opaque blobs. It's possible it could still work in some circumstances, but this would depend on the receiver resolving oneid
to another and editing its ingested copy of theAnnounce
in response, which it probably shouldn't do if it wants to avoid glitches.The text was updated successfully, but these errors were encountered: