Does context in AP have to be a collection, or can be be like a Flag activity? Say I wanted to Create(Note) about a Flag I'd received, I'd need:
1) A way to address the remote moderation team (moderation group actor)
2) A way to say "this note is about this Flag activity", using inReplyTo would feel weird here, but maybe context would work?
@thisismissem semantically, yes, it can be a flag or anything else you want. Functionally, for real world implementations?
I'm trying to think through what letterbook would do, and I suspect it would do the right thing. At least at the point of receiving the message. I would need some logic in reports to connect them back to that context, but i think that's likely to be straight forward
@thisismissem what I really want is context to be
1. A stable identifier that I can index
2. An indicator of whether and how reply control is implemented
3. A collection of related content-like objects, if reply control is implemented
In that order.
I think using a Flag (or its ID) satisfies that
@jenniferplusplus yeah, I don't think we'd have a collection for notes on a flag though, because the notes would be directly addressed to group actors for the moderation teams
Only use case I could think of is maybe inviting another moderation group actor to the thread of notes on a Flag, but that feels a bit weird with permissions.
@thisismissem Which is fine. If it's a collection, that makes it useful as a place to retrieve notes/etc that I didn't directly receive. But in this case it's overwhelmingly likely that there would only be 2 servers involved in the discussion anyway. So that's fine.
@jenniferplusplus even if it's 3-way plus, it'd have to all be directly addressing to avoid note leakage to as:Public
@thisismissem@hachyderm.io @jenniferplusplus@hachyderm.io
For what it's worth, @trwnh@mastodon.social 's FEP 7888 doesn't explicitly define what context
means semantically with regard to other objects, so to use it for flag reports makes complete sense to me. I don't know where @scott@authorship.studio is getting the idea that context
is only for threads, but given that it was discussed under the umbrella of the "threaded" discussion WG, I can see why one might make that assumption.
Were I to implement this in NodeBB, each individual Flag
activity would be translated to a NodeBB "report", and they'd contain a context, which is the flag itself.
With regard to your concern re: addressing, if you queried the context, you'd get an OrderedCollection
containing objects that you have access to view, but since in NodeBB only moderators can view flag reports, anybody querying it over ActivityPub would just get an empty collection.
@julian @jenniferplusplus @trwnh @scott @evan well, we'd be sending Create/Update Note about a Flag, so thinking context would be that Flag on the Notes
Not necessarily with a collection of notes about the Flag
@thisismissem@hachyderm.io that's fair, I don't know how we handle federating flag reports right now (as @oplik0/@opliko@infosec.town) handled that aspect.
Having the context contain the individual notes regarding a flag would also work.