I'm guessing the "conversation" value in an #ActivityPub Note object is #Mastodon specific, and other implementors have adopted it as a pseudo-standard?
Did some digging and it doesn't seem well supported. Happy to use it for #nodebb but bsd.network, for example, just sends the object id with #ctxt appended, which when queried just returns the same object. #Mastodon not surprisingly doesn't send one at all.
What I'm trying to get as is it doesn't seem there is one property I can rely on, so I may just have to create my own contexts as I go.
@devnull yeah, the intent is that “context” from as2 vocab is used for grouping, but the bigger issue is that many/most projects seem to neglect grouping almost entirely, in favor of constructing reply trees. pleroma at least will use it. streams probably does too. it’s not guaranteed to resolve to anything. pleroma uses https uris that dont resolve. streams uses Collections that do resolve.
@trwnh Perfect. Yes, this #FEP, while still a draft, looks to be following what I'm looking to accomplish.
I have some concerns over whether "context.audience" would conflict with "audience" as defined in FEP-1b12, but that property is at top-level so I think we might be okay...
While I'm not at the point of making any commitments, I will definitely consider FEP-7888 as I move forward.
@devnull if youre specifically targeting 1b12 compat, you can disregard the bit about Announce activities (assuming i didnt take it out already, i forgot)
side note, it does irk me a bit that we have 400e, 1b12 and 7888 for describing what is basically the same thing (a relay/mailing-list type of actor). at least 400e and 7888 agree it should be an Add activity instead of an Announce. (400e differs in one thing: it suggests using "target" instead of "context". idk why; that usage is invalid...)
Add comment